Add more basemaps

[GoogleCodeExporter]

More basemaps would be nice. They're all a little different and people have 
their favorites. Some other basemaps we could add: 

TopOSM, Bing, Cloudmade (Pale Dawn), Google Streetmap, Yahoo

Original issue reported on code.google.com by emily.hu...@state.ma.us on 29 Jul 2011 at 4:14

[GoogleCodeExporter]

Charlton, here's a link to the Mystic River map viewer that has CloudMade and 
TopOSM - MA as basemap options:

http://maps.mapc.org/myrwa/

Original comment by emily.hu...@state.ma.us on 26 Oct 2011 at 2:55

[GoogleCodeExporter]

Interesting.  I looked at their code, and it does go through OpenLayers very 
cleanly.  But Mystic River is passing along a required TopOSM key as part of 
the request.  I don't know anything about that, but perhaps CZM could check 
into it?

Original comment by cpl...@gmail.com on 30 Oct 2011 at 3:36

[GoogleCodeExporter]

Just found a new bug with the three Bing basemaps and creating a permalink. The 
map extent/zoom level isn't correct in a permalink with the Bing basmaps.

Original comment by emily.hu...@state.ma.us on 17 Nov 2011 at 9:33

[GoogleCodeExporter]

I have now removed the zoom & center params from the permalink.  Now the launch 
of the mapper will only count on a bbox being set.  This should keep it 
consistent across all basemaps.  In this case, Bing's zoom levels have a 
different starting index than the rest.  Long story.

v. 0.79
Committed revision 210.

Original comment by cpl...@gmail.com on 18 Nov 2011 at 10:00

[GoogleCodeExporter]

I played around w/ cloudmade for another client, and it works great.  You'll 
need to register for a key (free) and determine which level of access you need.

http://cloudmade.com/select/web

Once you do that, it's very easy for me to add layer(s).

Original comment by cpl...@gmail.com on 21 Nov 2011 at 3:39

[GoogleCodeExporter]

The permalink no longer works correctly now that the zoom and center params 
have been removed. The permalink map is zoomed out farther than the original 
map for all the basemaps. I've attached a screenshot of the original extent and 
the permalink extent of the default view of MORIS.

FYI, Marc and I found that the permalink extent is always zoomed out farther. 
Aleda only sees this happen when she resizes her browser so that it's not 
maximized.

Original comment by emily.hu...@state.ma.us on 21 Nov 2011 at 8:32

Attachments:

• original_extent.png
• permalink_extent.png

[GoogleCodeExporter]

Nasty Bing.

The center & zoom have been returned to the permalink, and I'm doing some 
special handling for bing basemaps.  Let's see if that does the trick.

v. 0.86
Committed revision 228.

Original comment by cpl...@gmail.com on 22 Nov 2011 at 3:09

[GoogleCodeExporter]

Permalinks of the other basemaps look good, but there's still a bug with Bing. 
When I'm zoomed in to the closest zoom level in one of the Bing basemaps and 
create a permalink, the permalink extent is zoomed out to the world. For 
example, I zoomed in to view a dock and could successfully create a permalink 
of it in all the basemaps. Here's the permalink with the Google satellite 
basemap:

http://170.63.166.213/map_ol_mop/moris.php?lyrs=MIMIC%202010%20Monitoring%20Site
s~massgis:MORIS.MIMIC_SITES_2010_PT~Red_Points&bbox=-70.92781348367335,42.326011
87003462,-70.92650590677945,42.32682292221829&coordUnit=dd&measureUnit=m&base=go
ogleSatellite¢er=-7895575.3006858,5210001.293007&zoom=13

This same extent with a Bing basemap creates a permalink that zooms out to the 
world:

http://170.63.166.213/map_ol_mop/moris.php?lyrs=MIMIC%202010%20Monitoring%20Site
s~massgis:MORIS.MIMIC_SITES_2010_PT~Red_Points&bbox=-70.9284672721212,42.3256063
4002161,-70.92585211833162,42.32722844438895&coordUnit=dd&measureUnit=m&base=bin
gAerial¢er=-7895575.3006858,5210001.293007&zoom=19

If you click the closet zoom level on the zoom slider in the Bing permalink, it 
zooms to the correct place.

Original comment by emily.hu...@state.ma.us on 22 Nov 2011 at 8:15

[GoogleCodeExporter]

I think this is an OpenLayers bug which will be fixed in version 2.12.  (We're 
at 2.11 now.)  I'm not sure what their release schedule is.

http://trac.osgeo.org/openlayers/ticket/3485

Original comment by cpl...@gmail.com on 22 Nov 2011 at 10:01

[GoogleCodeExporter]

The cloudmade and toposm-MA baselayers have been added.

v. 0.87
Committed revision 232.

The toposm-US link shows a map that has a blank basemap + a feature layer on 
top of it.  Visit http://toposm.com/us/ and click on the plus.  So it's not 
truly a basemap you're after -- you're after the combination.  While this is 
doable, it would be more complicated to maintain since I'd need to take care of 
an extra layer.  Can you live w/o it?

Original comment by cpl...@gmail.com on 23 Nov 2011 at 1:58

[GoogleCodeExporter]

Yes, we can live without TopOSM-US.

Original comment by emily.hu...@state.ma.us on 23 Nov 2011 at 3:37

[GoogleCodeExporter]

We just discovered a problem with CloudeMade getting offset with the WMS data 
in the Custom basemap.  Open MORIS, then change to Custom then CloudeMade.  The 
basemap and datalayers do not line up.  See screenshot.  Going from MORIS 
(Google basemap) directly to CloudeMade is OK.  We see the same offset issue 
when we open with Custom as the default basemap - then go to CloudeMade.

Original comment by Aleda.Fr...@state.ma.us on 28 Nov 2011 at 4:19

Attachments:

• cloudemade_after_custom_data_offset_problem.PNG

[GoogleCodeExporter]

Yep, I saw that and will roll it out w/ the next release.

Original comment by cpl...@gmail.com on 28 Nov 2011 at 4:47

[GoogleCodeExporter]

Verified. CloudMade and TopOSM-MA have been added and the CloudMade offset bug 
looks fixed. Won't fix the Bing permalink bug since it's probably an OpenLayers 
bug.

Original comment by emily.hu...@state.ma.us on 6 Dec 2011 at 4:28

• Changed state: Verified