November 11, 2015
View all 2 Followers
View all 755 Related Articles
Related Articles (755)
If you've done much searching for locations using web tools--and who hasn't by now--you've likely discovered some errors along the way. Sometimes a map marker is down the street from the actual location. Geocoding, the process of converting an address to latitude/longitude coordinates, can be an inexact science. A new geocoding service from MapQuest (our MapQuest API profile) aims to help you improve where you place that marker with Address Point Data.
There is no shortage of great tools out there to help you get in shape and keep track of your progress. You may be familiar with Nike's Nike+ system, that is heavily integrated with the iOS platform. It offers a great deal of data, but if you're like me, it wasn't enough to really rave about. Helpful, yes. Impressive, potentially. But FitBit, with its new FitBit API, has the potential to be much more.
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.