April 21, 2017
View all 1 Followers
View all 874 Related Articles
Related Articles (874)
These days it might be hard to remember that the Yahoo Maps API was ever second fiddle to the Google Maps API. These days, it barely picks up its fiddle. And in less than two weeks, Yahoo will lift its once-mighty mapping API above its head and bang the fiddle repeatedly into the stage like Pete Townshend. The remnants, barely held together with strings and the crumpled instrument neck, will then go in some dumpster in Sunnyvale. It's okay, after all, because Nokia's Ovi Maps API will be a fine replacement. It's only the nostalgic, like me, who'll have any problem with seeing the Yahoo name disappear.
It's funny that when I talk to people in the travel industry about mashups and APIs, most of them get glazed looks in their eyes. Throw in terms like location based services or geospatial awareness and I've lost them. What most of them don't realize is that the majority of the travel apps that are starting to come out, both online and for mobile are mashups that are relying on location awareness and geospatial data. Many of them, like Pocketvillage are a consumer interface on top of a variety of APIs all normalized for a single homogenous user experience. That's right, it's essentially a metasearch tool that pulls in content from a variety of sources including Viator, GetYourGuide, TourCMS, Rezgo, AirBnB, and many others. What differentiates a metasearch like Pocketvillage from other metasearch applications however, is the fact that with location based services enabled, Pocketvillage can return content based on your current location. The issue right now however is that not all geo data is equal. Not all APIs provide geolocation information and some return it based on different criteria.