Google지도에 액세스하기위한 라이브러리로서의 감수

Question

제안 하시나요? 감자 (라이브러리) Google지도에 액세스하는 계층으로?

적극적으로 유지 관리되는 프로젝트입니까? 공급자가 독립적 인 주된 이유를 제외 하고이 라이브러리를 사용하여 다시 서/ 잃어버린 것이 있습니까?

Answer 1

Have used this for a pretty major product, easy to use and extend. Well recommended so that mapping product can be swapped out in the future if needs be.

Cheers,

Rob

Answer 2

After reading this post I researched the same question and I think a little clarification might be in order.

OpenLayers has a larger user base than Mapstraction but still smaller than GoogleMaps(GM had over 1000 posts in the last two weeks, OpenLayers developer forum had 169 posts in october, mapstraction had 33. Its not a totally fair comparison because the questions on OpenLayers and Mapstraction seem to be a bit more sophisticated developer types and have less spam. I think both open layers and mapstraction support the use of google maps within google's the TOS by wrapping the full google maps js api.

One advantage of Mapstraction over OpenLayers is that more direct access to googles api while open layers supports fewer ports of the google api but supports them more pretty consistently across the maps it supports. This list serve question covers it pretty well http://www.mail-archive.com/dev@openlayers.org/msg02039.html

We have been considering a move from GoogleMaps to mapstraction and here are a few thoughts on my experience getting started with the Mapstraction api wrapper.

On their home page they link to a complicated buggy demo that doesn't cover the current version of google maps. If you dig around git hub there is a api v3 demo here https://github.com/mapstraction/mxn/blob/master/examples/googlev3.html

The code base on github seems well writtern but their documentation is shakey.. in fact when you search for "mapstraction" on google the API Doc site link points to obsolete docs that don't cover v3 either. If you download the git hub source there are autogenerated docs that do cover v3 but no nice simple getting started example. Their mailing list is difficult to search but I didn't see any examples on their either. It also appears that while they abandoned code.google.com for the main source trunk they still rely on it in all the examples to host the js files and inject dependency using the .js(apitype) setup. like this http://mapstraction.googlecode.com/svn/trunk/source/mxn.js?(openlayers) I ran into some chatter on the list serv that suggested the google js file often excluded necessary patches in the code base. I haven't found a nice getting started doc, or email that explains their preferred scheme for linking code or injecting api dependency.

All these are small issues and they appear to have a good core team. So, if you need to support google specific maps functions they seem like a good way to go.

For reference here are their simpler examples https://github.com/mapstraction/mxn/tree/master/examples/

Answer 3

you might also look at http://openlayers.org/