Slashgeo Log In
Mapstraction - Bringing Mapping APIs Together
posted by Satri
on Wednesday June 07, @08:34AM
Permalink
Trackback URI
Slashdotthis
Diggthis
Del.icio.us
from the one-API-to-rule-them-and-in-the-darkness... dept.
Permalink
Trackback URI
Slashdotthis
Diggthis
Del.icio.us
from the one-API-to-rule-them-and-in-the-darkness... dept.
The OpenGeoData blog made me aware of Mapstraction. The full introduction from the website: "Mapstraction is a library which provides a common API for Google, Yahoo! and Microsoft's javascript mapping APIs to enable switching from one to another as smoothly as possible. The aim of Mapstraction in mainly to protect companies building commercial products on top of Google Maps from changes to terms and conditions, the introduction of ads, or the emergence of a competing library with better maps, different imagery or preferable licensing terms.
Mapstraction additionally fills some holes each provider's current offerings (taking advantage of existing open source solutions where possible) to normalise the feature set across platforms. In the future, Mapstraction will also talk to OpenStreetMap for people who want to build maps without restrictions on derived works."
Related Stories
Calendar: Where 2.0 2007 Coverage 5 comments
[+]
With Where 2.0 2007 going on at San Jose, several geoblogs covers the conference. The GEB, after introductory comments, offers a Day 1 report and summarize Google's Micheal Jones presentation. APB and Vector One both discuss where's the money to be made with webmapping. High Earth Orbit details the Mapstraction update announced (now, can anyone tell me what are the main distinctions between OpenLayers and Mapstraction?). Expect some more about Where 2.0 2007 later on.
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
