• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
How "open" should mapping APIs be?
 

How "open" should mapping APIs be?

on

  • 768 views

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

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

Statistics

Views

Total Views
768
Views on SlideShare
766
Embed Views
2

Actions

Likes
0
Downloads
0
Comments
0

2 Embeds 2

http://www.linkedin.com 1
https://www.linkedin.com 1

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    How "open" should mapping APIs be? How "open" should mapping APIs be? Presentation Transcript

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