Adam DuVander
2009-Oct-10 05:17 UTC
[Mapstraction] Google v3 in Mapstraction v2 -- controls and tile layers
Hey all, Ed and I have been implementing v3 of Google Maps in the new Mapstraction framework. There are a few items where we''d like your thoughts. 1) Presumably to be more efficient, controls (zoom, scale, map type) are added at load time in Google v3. Mapstraction currently can only add controls after the map loads. My suggestion would be to add an optional "options" object to the constructor, which can hold control options to be sent at load time. This could also be used for other data that needs to be used when the map is created (such as the Cloudmade API key). 2) A bigger issue (perhaps) is tile layering in Google v3, which is very different than the previous version. Mapstraction''s tile layer code is built off of how it was implemented in Google v2. I believe we can keep a similar method using the new custom overlays: http://code.google.com/apis/maps/documentation/v3/overlays.html#CustomOverlays It will require listening for map drag and zoom events, calculating individual tile locations and adding overlays. It''s possible we could even use similar logic to implement tiling in other providers. I have no idea how efficient this method would be, or if tile layering is even expected to be used with Google v3. Anyone have any thoughts? --Adam --- Adam DuVander I like maps: http://mapscripting.com I like simple: http://adamduvander.com
pamela (Google Employee)
2009-Oct-10 05:32 UTC
[Mapstraction] Google v3 in Mapstraction v2 -- controls and tile layers
The OverlayView isn''t really designed for TileLayers - some people have hacked it to try and do them, but it ain''t easy. We''re working on native TileLayer support in the next few months. On Sat, Oct 10, 2009 at 4:17 PM, Adam DuVander <mapstraction at duvander.com>wrote:> Hey all, > > Ed and I have been implementing v3 of Google Maps in the new Mapstraction > framework. There are a few items where we''d like your thoughts. > > 1) Presumably to be more efficient, controls (zoom, scale, map type) are > added at load time in Google v3. Mapstraction currently can only add > controls after the map loads. My suggestion would be to add an optional > "options" object to the constructor, which can hold control options to be > sent at load time. This could also be used for other data that needs to be > used when the map is created (such as the Cloudmade API key). > > 2) A bigger issue (perhaps) is tile layering in Google v3, which is very > different than the previous version. Mapstraction''s tile layer code is built > off of how it was implemented in Google v2. I believe we can keep a similar > method using the new custom overlays: > > http://code.google.com/apis/maps/documentation/v3/overlays.html#CustomOverlays > > It will require listening for map drag and zoom events, calculating > individual tile locations and adding overlays. It''s possible we could even > use similar logic to implement tiling in other providers. I have no idea how > efficient this method would be, or if tile layering is even expected to be > used with Google v3. Anyone have any thoughts? > > --Adam > --- > Adam DuVander > I like maps: http://mapscripting.com > I like simple: http://adamduvander.com > > _______________________________________________ > Mapstraction mailing list > Mapstraction at lists.mapstraction.com > http://lists.mapstraction.com/listinfo.cgi/mapstraction-mapstraction.com >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mapstraction.com/pipermail/mapstraction-mapstraction.com/attachments/20091010/b61c4f07/attachment.htm>