Yahoo! Maps severe, and odd, restriction

Yahoo! Maps Beta LogoYahoo! Maps is following on the tails of MSN and GoogleMaps in releasing a public, REST, API for its maps and North American (US only?) Geocoding. Yahoo! Maps API provides either an image or a Flash map (I don't like Flash - too much... flash?). However, the API actually lets programmers use the functions in their own flash apps, which should allow developers to provide slick interfaces without having to learn that icky Javascript/XHTML/XmlHttpRequest stuff. Well, I guess icky is a subjective term.

Features

Sensor-Based Location Limit


As great as having YAMA (Yet Another Mapping API) is, Yahoo! has placed a severe restriction on the application of the API.

You may use location data derived from GPS or other location sensing devices in connection with the Yahoo! Maps APIs, provided that such location data is not based on real-time (i.e., less than 6 hours) GPS or any other real-time location sensing device, the GPS or location sensing device that derives the location data cannot automatically (i.e. without human intervention) provide the end user's location, and any such location data must be uploaded by an end-user (and not you) to the Yahoo! Maps APIs.

Does this prevent someone from just telling an application where they are and displaying it? Yahoo! is only restricting *how* the information was gathered. It doesn't seem possible that Yahoo! (or NavTeq) can really restrict *how* the data was gathered, all they are seeing is lat/lon requests. What happens if I used a sextant to get the real-time position data?

GoogleMaps has its own restrictions, but the only similar one is :

"In addition, the Service may not be used: (a) for or with real time route guidance (including without limitation, turn-by-turn route guidance and other routing that is enabled through the use of a sensor), or (b) for, or in connection with, any systems or functions for automatic or autonomous control of vehicle behavior."

Granted, this may actually be an effect of using NavTeq's data. Which also begs the question, with all these mapping API's, they are still all displaying the same maps provided by a single source. This seems bad.

When will OpenStreetMap have its own dynamic mapping and API.

About this article

written on
posted in ProgrammingGeolocationMapsWeb Back to Top

About the Author

Andrew Turner is an advocate of open standards and open data. He is actively involved in many organizations developing and supporting open standards, including OpenStreetMap, Open Geospatial Consortium, Open Web Foundation, OSGeo, and the World Wide Web Consortium. He co-founded CrisisCommons, a community of volunteers that, in coordination with government agencies and disaster response groups, build technology tools to help people in need during and after a crisis such as an earthquake, tsunami, tornado, hurricane, flood, or wildfire.