How "open" should mapping APIs be?
0 likes452 views
The document discusses how open mapping APIs should be and different perspectives on this issue. It mentions several existing mapping APIs and wrapper APIs that allow using different mapping services. Some opinions expressed are that wrapper APIs are useful for developers, standards should focus on common functionality while allowing for innovation, and that standards should be driven by developer and business demand rather than committees. The document asks the reader for their view on how open mapping APIs should be.
1 of 20
How "open" should mapping APIs be?
- 1. How “open” should mapping APIs be? Adam DuVander, MapScripting.com @adamd KAMYAR ADL
- 2. 6,000 years and still #1 World Map, 1513
- 5. new VEMap('mymap'); new YMap(document.getElementById('mymap')); new GMap2(document.getElementById('mymap'));
- 6. FreeEarth Google Map24 MapQuest Microsoft MultiMap OpenLayers OpenSpace OpenStreetMap ViaMichelin Yahoo new Mapstraction('mymap', 'yahoo');
- 7. “The wrapper APIs are needed for developers who want everything.” WEB09 Pamela Fox, Google
- 8. GREG MA
- 10. “ Provide standard interfaces where functionality is standard. Innovate beyond that.” Andrew Turner, GeoCommons
- 11. MR. MATH
- 14. <video> tag
- 15. Is <map> next? maybe we’d call it <geo>
- 16. DALE LANE Nick Black, CloudMade “The problems arise when standards are created by committees who are divorced from the development or business processes. Standards should be driven by demand .”
- 19. TRACY HUNTER
- 20. How open should mapping APIs be? What do you think? LE VENT LE CRI Adam DuVander, MapScripting.com @adamd