In the session entitled “Mapping: Where the F#*% Are We Now?” I learned about a fascinating project called Mapstraction. Mapstraction is an API that abstracts the Google, Yahoo, and Microsoft mapping APIs.

If you program your maps mashup using Mapstraction then you’re not tied into a single company’s map product. It makes switching from Google Maps to Yahoo Maps (or vice versa) as silky smooth as possible.

This is important for two reasons:

1. Each map API company competes in both service quality and feature sets. the best company when you are first implementing you technology will not necessarily remain the best six months from now. This API prevents lock-in into an inferior product. With Mapstraction you benefit from all competition because you have no barriers to switching APIs.
2. When small map mashup companies (Flagr, Frappr, Plazes, etc) are discussing potential funding or exits, being tied into a particular company’s mapping API can be disadventageous. If you are dependent on Google Maps API and are negotiating with Google, then Google has some leverage. Similarly, if you are dependent on Google Maps API and are negotiating with Yahoo, then reimplementing your mapping code with likely be an annoying acquisition hurdle.

It looks like Mapstraction is still a little early, but I think it’s an exciting idea, and that’s why it qualifies as one of my SXSW gems. I’d be interested to know if people actually working in a map mashup startup think this is interesting.