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.
You can create a larger search area by searching 2+ origins simultaneously (combining shapes) as well as identify a unique search area suitable for 2+ points of origin (like the centre of a venn diagram). It's also useful for A > B routing and adjusts results based on the time of day.
Suitable for 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.
The following is a list of historical changes that were made to this asset. Typically,
once an API is published on ProgrammableWeb.com, the data we keep about that asset gets updated over the course of its life. For example, the endpoint or home page of the documentation might change.
As a means of enforcing the integrity of our data, every time a non-trivial change is made to the data we keep about an asset,
we require the entry of some changelog text before that change can be saved. This way, we have a great audit trail of all
activity surrounding the asset. For each asset, the changelogs begins with the moment an asset is approved for publication on ProgrammableWeb.
If you spot an error in our data and believe that a record needs to be updated in some way,
the ProgrammableWeb team would very much like to hear from you at firstname.lastname@example.org
06-05-16 19:36:03[How-To] How to Search Locations by Travel Time With the iGeolise TravelTime API updated with Related API iGeolise Travel Time