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.
Developers working with Google's next generation of its popular mapping API (our Google Maps API Profile) will be pleased to learn that some new features have been added to the API. Since its initial release a little less than a year ago, v3 of the Google Maps API has steadily been growing in terms of features and functionality. The latest addition of features are three new "layer classes" that make it dead simple to add KML (or GeoRSS), traffic, or bike routes as overlays on a Google Map.