How "open" should mapping APIs be?

572 views
529 views

Published on

Ignite talk from Where 2.0 about map APIs and standardized interfaces.

Published in: Technology, News & Politics
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
572
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

How "open" should mapping APIs be?

  1. 1. How “open” should mapping APIs be? Adam DuVander, MapScripting.com @adamd KAMYAR ADL
  2. 2. 6,000 years and still #1 World Map, 1513
  3. 5. new VEMap('mymap'); new YMap(document.getElementById('mymap')); new GMap2(document.getElementById('mymap'));
  4. 6. FreeEarth Google Map24 MapQuest Microsoft MultiMap OpenLayers OpenSpace OpenStreetMap ViaMichelin Yahoo new Mapstraction('mymap', 'yahoo');
  5. 7. “The wrapper APIs are needed for developers who want everything.” WEB09 Pamela Fox, Google
  6. 8. GREG MA
  7. 10. “ Provide standard interfaces where functionality is standard. Innovate beyond that.” Andrew Turner, GeoCommons
  8. 11. MR. MATH
  9. 14. <video> tag
  10. 15. Is <map> next? maybe we’d call it <geo>
  11. 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 .”
  12. 19. TRACY HUNTER
  13. 20. How open should mapping APIs be? What do you think? LE VENT LE CRI Adam DuVander, MapScripting.com @adamd

×