How "open" should mapping APIs be?

  • 382 views
Uploaded on

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

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

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
382
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. How “open” should mapping APIs be? Adam DuVander, MapScripting.com @adamd KAMYAR ADL
  • 2. 6,000 years and still #1 World Map, 1513
  • 3.  
  • 4.  
  • 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
  • 9.  
  • 10. “ Provide standard interfaces where functionality is standard. Innovate beyond that.” Andrew Turner, GeoCommons
  • 11. MR. MATH
  • 12.  
  • 13.  
  • 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 .”
  • 17.  
  • 18.  
  • 19. TRACY HUNTER
  • 20. How open should mapping APIs be? What do you think? LE VENT LE CRI Adam DuVander, MapScripting.com @adamd