The TravelTime platform API makes location-based data searchable by travel time rather than distance. It can map travel time areas for all common modes of transport (drive time maps, public transport commute maps, walking time maps and cycling maps - it's also possible to combine these modes). When used within a location search, it can search, map, sort and deliver results based on time rather than distance.
For example if asking ‘where’s reachable within 30 minutes drive from my location?’ it can map the area and search through thousands of destinations. It also sorts the destinations from shortest to longest time.
> Create a larger search area by searching 2+ origins simultaneously (combining shapes)
> Identify a unique search area suitable for 2+ points of origin (like the centre of a venn diagram)
> A > B routing
> Adjust results based on the time of day
> Property search sites - Where should my family live to ensure <30 minute commute?
> Hotel search and accommodation search - Which hotel is quickest to access the sights?
> Job search - Which job roles are within 45 mins commute from my house?
> Retail - Find the quickest store to reach
> Entertainment - Find the closest cinema, restaurant, place to visit
> Local councils and government - find public services by travel time
API methods support specification of an origin point by latitude and longitude, a travel mode, a time limit, and the type of destination. Returned data provide destinations of the requested type within the specified travel time range. Methods also allow specification of a point of origin, destination, and travel mode to receive the fastest available route. The API also supports geocoding for specified U.K. postal codes.
When developing a location-based application, displaying the most relevant information is the key to success. Countrywide.co.uk managed to increase their conversions by up to 300 percent when delivering points of interest by travel time. In this article, we’ll explain how to search and display
Planning a trip, whether just down the road or into the next city, normally revolves around the distance of the desired location. It's common practice to search for the distance between two points on a map, then take a rough guess as to how long it will actually take to get there. But we all know that distance isn't the only factor to consider. What about mode of transport, peak traffic hours or alternate routes? All these can dramatically affect how long it actually takes to get to your destination. This post will discuss how iGeolise's Travel Time and the Travel Time API changes the way people search and the results that are produced.
The W3C Proximity Sensor API is a specification that defines a sensor interface for monitoring the presence of nearby objects. It is designed to extend the W3C Generic Sensor API to provide proximity...