search

PiRSquared17 / morisoliver

Automatically exported from code.google.com/p/morisoliver
0 stars 0 forks source link

Add more basemaps #44

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
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 commented 9 years ago 
We would like to add the Bing aerial basemap because the orthos are very good.

Original comment by emily.hu...@state.ma.us on 30 Aug 2011 at 12:16

GoogleCodeExporter commented 9 years ago 
Issue 53 has been merged into this issue.

Original comment by emily.hu...@state.ma.us on 30 Aug 2011 at 12:17

GoogleCodeExporter commented 9 years ago 
Can we add Google Hybrid to list? DFG would like this.

Original comment by Aleda.Fr...@state.ma.us on 14 Sep 2011 at 6:35

GoogleCodeExporter commented 9 years ago 
Google Hybrid looks good but I think our DFG folks will want to zoom in more - 
are there closer levels available?

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

GoogleCodeExporter commented 9 years ago 
I added 2 more google layers + 3 yahoo layers.

I'm afraid there is a bug w/ geoext & bing layers that cause the app. to bomb 
if a user tries to launch the mapper w/ bing as its basemap.  So I'm leaving 
those off the list.  Not allowing them to be initial basemaps would be 
confusing and require a good bit of exception handling.

Hindsight being 20/20, I'm not a real fan of geoext.  It hides too much stuff 
underneath glossy covers.

As for the rest of your baesmap requests, I'm not familiar w/ them.  Can you 
point me to the data source(s)?

Original comment by cpl...@gmail.com on 19 Sep 2011 at 5:01

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Whoops.  Forgot to say that you must add this to all your .php launch scripts.

<script 
src="http://api.maps.yahoo.com/ajaxymap?v=3.0&appid=euzuro-openlayers"></script>

Original comment by cpl...@gmail.com on 19 Sep 2011 at 5:08

GoogleCodeExporter commented 9 years ago 
For Comment 7:  type="text/javascript"  ?

Original comment by Aleda.Fr...@state.ma.us on 19 Sep 2011 at 7:14

GoogleCodeExporter commented 9 years ago 
Sure.  If you want to be a proper coder, I suppose.  :P

Original comment by cpl...@gmail.com on 19 Sep 2011 at 7:29

GoogleCodeExporter commented 9 years ago 
OK, I added the script line but I don't see the 3 Yahoo layers yet.  Did I need 
to put it in a particular place in the .php? I put it here:

    <link rel="stylesheet" type="text/css" href="css/ext-ux-wiz.css" />

    <script type="text/javascript" src="http://api.maps.yahoo.com/ajaxymap?v=3.0&appid=euzuro-openlayers"></script>

    <!-- editing tools -->

Original comment by Aleda.Fr...@state.ma.us on 19 Sep 2011 at 7:33

GoogleCodeExporter commented 9 years ago 
Ah, I probably need to check out another version.

Original comment by Aleda.Fr...@state.ma.us on 19 Sep 2011 at 7:36

GoogleCodeExporter commented 9 years ago 
I see the extra basemaps now.

Original comment by Aleda.Fr...@state.ma.us on 19 Sep 2011 at 9:05

GoogleCodeExporter commented 9 years ago 
Could we document here what the new 

var defaultBase 

values are in the .php? googleHybrid for example?  

I'm sure it's somewhere in the code...

Original comment by Aleda.Fr...@state.ma.us on 20 Sep 2011 at 4:50

GoogleCodeExporter commented 9 years ago 
Charlton, can you let me know about the Google Hybrid - whether we can have 
more zoomed in levels?  Because I have a group (DFG) that would use it now for 
a little project but these levels aren't enough so I have to decide what to do 
for them...

Original comment by Aleda.Fr...@state.ma.us on 20 Sep 2011 at 5:07

GoogleCodeExporter commented 9 years ago 
Allowed defaultBase values are:  
custom|googleSatellite|googleTerrain|googleRoadmap|googleHybrid|yahooStreet|yaho
oSatellite|yahooHybrid|openStreetMap.

Original comment by cpl...@gmail.com on 20 Sep 2011 at 8:02

GoogleCodeExporter commented 9 years ago 
I just bumped up the google zoom levels for these 2:

  lyrBase['googleRoadmap'] = new OpenLayers.Layer.Google(
     'googleRoadmap'
    ,{
       'sphericalMercator' : true
      ,type                : google.maps.MapTypeId.ROADMAP
      ,minZoomLevel        : 7
      ,maxZoomLevel        : 21
    }
  );
  lyrBase['googleHybrid'] = new OpenLayers.Layer.Google(
     'googleHybrid'
    ,{
       'sphericalMercator' : true
      ,type                : google.maps.MapTypeId.HYBRID
      ,minZoomLevel        : 7
      ,maxZoomLevel        : 20
    }
  );

Committed revision 126.

Original comment by cpl...@gmail.com on 20 Sep 2011 at 8:08

GoogleCodeExporter commented 9 years ago 
In comment 5 - is it a known bug?  Could you provide a link to it here?  I can 
try to keep track of when it's fixed so we can get the Bing basemap in the 
future perhaps.

Original comment by Aleda.Fr...@state.ma.us on 23 Sep 2011 at 1:15

GoogleCodeExporter commented 9 years ago 
We could add the bing basemap layers if we upgraded to OpenLayers 2.11.  Do we 
have the heart for that?

Original comment by cpl...@gmail.com on 23 Sep 2011 at 3:06

GoogleCodeExporter commented 9 years ago 
Sure!  I thought it was a bug they hadn't fixed yet.  Are there any other side 
effects?  I guess we should be hyper-aware in case something else might break.  
But that's probably not likely, right?

Original comment by Aleda.Fr...@state.ma.us on 23 Sep 2011 at 3:15

GoogleCodeExporter commented 9 years ago 
I thought you'd want to avoid any other variables like the plague!  I looked 
into it briefly and saw that I'd have to make a few tweaks here and there.

Original comment by cpl...@gmail.com on 23 Sep 2011 at 3:29

GoogleCodeExporter commented 9 years ago 
Committed revision 147.

That has bing maps added.  You MUST point it to an OL 2.11 install (grab it 
from here, http://openlayers.org/download/OpenLayers-2.11.tar.gz).

Also, you may want to pass along these short release notes to Saul just in case.
http://trac.osgeo.org/openlayers/wiki/Release/2.11/Notes

Original comment by cpl...@gmail.com on 23 Sep 2011 at 3:47

GoogleCodeExporter commented 9 years ago 
Peter Grace and I just discovered that the Google Satellite switches from ortho 
to oblique (what they call 45 degree view) at the "2000" level ("4000" is still 
ortho).  We need the ortho option instead, because otherwise the other data 
will not line up with the photo (the photo looks like you can see the buildings 
from the side instead of the top).  The maps.google.com lets you switch from 45 
to ortho again, even at closer zooms.  Can you change the way you access the 
orthos so that we don't get the 45 option? 

This link 

http://maps.google.com/maps?q=malden,+ma&hl=en&ll=42.437257,-71.068684&spn=0.000
461,0.001032&sll=37.0625,-95.677068&sspn=63.512641,135.263672&vpsrc=6&t=h&z=21  

shows you what the 45 looks like.  We tried to make a permalink out of 
maps.google.com with the 45 turned off, but it looks the same.  I hope there is 
still a way to specific that you don't want it.

Original comment by Aleda.Fr...@state.ma.us on 23 Sep 2011 at 4:01

Attachments:

GoogleCodeExporter commented 9 years ago 
Could we have more zoomed in levels for the Yahoo Satellite basemap?  If we 
can't get the Google Satellite to NOT do 45 degrees we may be able to use the 
Yahoo Satellite for the 911 project, but we need to get closer in.

Original comment by Aleda.Fr...@state.ma.us on 23 Sep 2011 at 4:02

GoogleCodeExporter commented 9 years ago 
Re: The OpenLayers upgrade - you're right, we shouldn't spread ourselves too 
thin just now.  Let's hold that until the end.

Original comment by Aleda.Fr...@state.ma.us on 23 Sep 2011 at 4:13

GoogleCodeExporter commented 9 years ago 
Oh, now I read we've already gone ahead.  Sorry, I feel like we're all over the 
map here (ha ha).  Can we pull back on the OL upgrade just for now, you're 
right, it's too many variables just now.

Original comment by Aleda.Fr...@state.ma.us on 23 Sep 2011 at 4:17

GoogleCodeExporter commented 9 years ago 
OpenLayers came up w/ an alternate way of accessing tiles directly from google 
to get around this, but it turned out to be a violation of the terms of 
service, so it's unavailable.

I'm pulling in the default min/max range of yahoo layers.  Do you see more on 
yahoo.com that don't appear here?

Re. the OL upgrade.  I already did it for my last couple of changes.  If you 
DON'T want me to include the upgrade, I'll need to rollback my changes before 
continuing to address other issues.  Please let me know.

Original comment by cpl...@gmail.com on 23 Sep 2011 at 4:17

GoogleCodeExporter commented 9 years ago 
When you say "an alternate way of accessing tiles directly from google to get 
around this" you mean the 45 degrees issue?  I guess we'll have to just 
document that.

I think I can get closer on the Yahoo - see screenshot:

Original comment by Aleda.Fr...@state.ma.us on 23 Sep 2011 at 4:22

Attachments:

GoogleCodeExporter commented 9 years ago 
OK.  I think I'm responding too quickly to everyone's comments.  Too much of a 
good thing.

I see that Emily is going strong, so I'll let you two comment away while I work 
on another project.  Once the dust settles, I'll see who is left standing.

I think P1 should be the extract, and it works well here.  If it still fails 
there, update that issue and I'll respond w/ the XML I see pass by here.

Committed revision 149.

Original comment by cpl...@gmail.com on 23 Sep 2011 at 4:23

GoogleCodeExporter commented 9 years ago 
Yahoo seems buggy when switching from custom to yahoo.  Start MORIS.  Switch to 
custom.  Zoom to some coastal location.  Switch to Yahoo (any of the 3).  You 
jump to Africa (0,0).  I think this is an OL bug.  I should be able to treat it 
just like Google, but it isn't behaving.  I'm inclined not to have yahoo w/ its 
bugginess.

Original comment by cpl...@gmail.com on 23 Sep 2011 at 6:05

GoogleCodeExporter commented 9 years ago 
Aleda, I rather unexpectedly landed in Benin earlier today but was unable to 
replicate.  If it's a Yahoo bug I agree that it should be dumped.  Too bad 
though as they have a some really nice looking data.

FYI
"Yahoo has found itself once again floundering with trying to figure out 
exactly what it is. This time, developers who have used its Maps API are in for 
an unpleasant surprise as the company plans on shuttering the service 
completely on September 13th of this year.

    As part of Yahoo!’s commitment to creating deeply personal digital experiences, we have been reprioritizing our current portfolio of mapping products to refocus on a great consumer Mapping and Local Search experience.

In short, if you were using any of the following, you’ll need to make some 
changes to address the closing:

    ActionScript 2 & 3 (Flash APIs)
    AJAX Maps 3.6, 3.7, 3.8
    REST API (Map Image API)
    Simple API – (No coding)
    GeoRSS – Version 2

Yahoo does extend the olive branch somewhat, stating that its Placefinder API 
for geocoding and the combination of Placemaker and Local Search API will 
remain alive for geocaching. Interestingly, instead of pushing abandoned 
developers toward Microsoft’s Bing Maps, Yahoo is ushering them toward 
Nokia’s Ovi Maps API.

The “even worse” news? If you’re hoping to use Nokia’s product for 
navigation right now via a Yahoo product, you’ll have to wait a while — 
“This work is in-progress and we plan to have something to announce later 
this year.”

Our thanks to TNW reader Adam Hopkinson for the tip."

Original comment by daniel.s...@state.ma.us on 23 Sep 2011 at 6:12

GoogleCodeExporter commented 9 years ago 
I've seen this too, is it intermittent?  Is it fixable?  We may need Yahoo 
because it may be the only close in orthophoto we can use.

Here are the current frustrating choices for orthos: 

1) use MassGIS - problems - slow right now problem + problem of white outlying 
areas
  (I *might* be able to fix that)
2) use Google - 45 degree problem - can't get around that
3) use Yahoo - buggy Africa issue - fixable? 
4) use Bing - need to upgrade OL

Yikes! 

If Yahoo is too buggy then we probably have to go for the OL upgrade at some 
point.

I'm still focused on the extract by poly.... Charlton, any chance can we check 
in by phone?

Original comment by Aleda.Fr...@state.ma.us on 23 Sep 2011 at 6:12

GoogleCodeExporter commented 9 years ago 
Dan, if it was closed on the 13th why is it still working?  Charlton, are they 
talking about the service we're trying to use?

Original comment by Aleda.Fr...@state.ma.us on 23 Sep 2011 at 6:14

GoogleCodeExporter commented 9 years ago 
Google, Bing, Yahoo, OSM.  Are there any other options?  I searched a while 
back and come up with much aside from a someday OpenOceanMap.

Original comment by daniel.s...@state.ma.us on 23 Sep 2011 at 6:27

GoogleCodeExporter commented 9 years ago 
REST API (Map Image API) sounds like what OL might be hitting.

Original comment by cpl...@gmail.com on 23 Sep 2011 at 6:28

GoogleCodeExporter commented 9 years ago 
FYI, geocoding in Yahoo is very flaky in MORIS.  Gotta be Yahoo since the same 
address work correctly with the Google data.

Original comment by daniel.s...@state.ma.us on 23 Sep 2011 at 8:51

GoogleCodeExporter commented 9 years ago 
Charlton, can you determine before go forward whether the Bing API also does 
the 45 degree thing?  (without an option of not having it?) Thanks.

Original comment by Aleda.Fr...@state.ma.us on 26 Sep 2011 at 2:15

GoogleCodeExporter commented 9 years ago 
Re: Yahoo bug with Africa - maybe this would also be fixed if I went to OL 
2.11?  Just wondering.  I'm checking with PeopleGIS now whether they are OK 
with this upgrade.

Original comment by Aleda.Fr...@state.ma.us on 26 Sep 2011 at 2:59

GoogleCodeExporter commented 9 years ago 
Charlton, I know little about this, but is this at all helpful in possibly 
turning off the 45 degree option?  setTilt(0)

http://code.google.com/intl/en/apis/maps/documentation/javascript/maptypes.html#
Enabling45DegreeImagery

I also see a comment by Andreas here:  
http://comments.gmane.org/gmane.comp.gis.openlayers.user/19492

"OpenLayers.Layer.GoogleNG uses the GMaps API on a lower level, and doesn't 
switch to the 45° aerial view at high zoom levels."

MassGIS has OpenLayers support, so if there's a chance we can turn this off 
I'll see if I can find it.  I start with PeopleGIS...

Original comment by Aleda.Fr...@state.ma.us on 26 Sep 2011 at 3:05

GoogleCodeExporter commented 9 years ago 
Now that we have so many basemaps, it might be good to list them in 
alphabetical order in the Basemaps menu:

Custom
Google Hybrid
Google Roadmap
Google Satellite
Google Terrain
OpenStreetMap
Yahoo Hybrid
Yahoo Satellite
Yahoo Street

Original comment by emily.hu...@state.ma.us on 26 Sep 2011 at 3:28

GoogleCodeExporter commented 9 years ago 
Aleda, the link you provided re. the GoogleNG is the thing that was found to 
violate the terms of service.

Original comment by cpl...@gmail.com on 26 Sep 2011 at 4:36

GoogleCodeExporter commented 9 years ago 
Sigh.  OK, good to know.  What about the possibility of setTilt(0)?  Any hope 
there?

Original comment by Aleda.Fr...@state.ma.us on 26 Sep 2011 at 4:37

GoogleCodeExporter commented 9 years ago 
I see the discussion now about GoogleNG and terms of service.  For the record: 
http://trac.osgeo.org/openlayers/ticket/3481

Original comment by Aleda.Fr...@state.ma.us on 26 Sep 2011 at 4:41

GoogleCodeExporter commented 9 years ago 
This requires an upgrade to OL 2.11.

Since several key issues seem to depend on OL 2.11, I have assumed that Aleda 
will point all config files to OL 2.11 beginning w/ this version, v. 0.58.

But if it turns out that an upgrade on OL 2.11 breaks other things that weren't 
laid out as issues per the SOW, I suggest that we rollback and cut some of our 
losses.

I'll poke around and paste this same message to other issues that depended on 
an OL upgrade.

Original comment by cpl...@gmail.com on 6 Oct 2011 at 1:54

GoogleCodeExporter commented 9 years ago 
The three Bing basemaps work. Is there one closer zoom level available? It 
looks like I can zoom in one zoom level closer on Bing maps than I can in MORIS.

The Yahoo bug is still present, so we'd like to remove the Yahoo basemaps.

As suggested above, we'd like the basemaps to be listed in alphabetical order 
(with the exception of Custom, which we'd like listed first):

Custom
Bing Hybrid
Bing Roads
Bing Satellite
Google Hybrid
Google Roadmap
Google Satellite
Google Terrain
OpenStreetMap

Original comment by emily.hu...@state.ma.us on 18 Oct 2011 at 7:07

GoogleCodeExporter commented 9 years ago 
Yahoo basemaps have been removed and basemaps list has been reordered.

I'm adding the Bing maps w/o specifying min/max zoom levels, so you should be 
seeing all that Bing has to offer via OpenLayers.

v. 0.64
Committed revision 174.

Original comment by cpl...@gmail.com on 20 Oct 2011 at 1:22

GoogleCodeExporter commented 9 years ago 
All looks good to me Charlton.  Can you add a placeholder for "View metadata" 
tab that opens after you mouse over each name so that Aleda can add/update the 
links?  We'd like to add a URL for each basemap if possible.

Original comment by daniel.s...@state.ma.us on 20 Oct 2011 at 5:53

GoogleCodeExporter commented 9 years ago 
Comment 44 - yahoo is gone and basemaps are alphabetized - all set there.

Re: Comment 38 - did you get a chance to try setTilt(0) 

http://code.google.com/intl/en/apis/maps/documentation/javascript
/maptypes.html#Enabling45DegreeImagery

(this is different than the GoogleNG which we know is not allowed).

Original comment by Aleda.Fr...@state.ma.us on 20 Oct 2011 at 7:06

GoogleCodeExporter commented 9 years ago 
setTilt isn't offered in any version of OL that I've seen (even in the 
development version).

I think the references you see to map.setTilt(0) are for sites that are 
programming directly in the Google Maps API (we use OpenLayers and only pull 
Google Map's tiles as baselayers).

Original comment by cpl...@gmail.com on 20 Oct 2011 at 7:19

GoogleCodeExporter commented 9 years ago 
Rather than add dummy placeholders for metadata links, when you get them, shoot 
them here and I'll put them by the remaining basemaps.

Original comment by cpl...@gmail.com on 20 Oct 2011 at 7:21

GoogleCodeExporter commented 9 years ago 
Here are links to the other basemaps we originally requested:

1. CloudMade
> Map: http://maps.cloudmade.com/ (style = The Original)
> Metadata: http://wiki.openstreetmap.org/wiki/CloudMade

2. TopOSM - Massachusetts
> Map: http://toposm.com/ma/
> Metadata: http://wiki.openstreetmap.org/wiki/TopOSM

3. TopOSM - United States
> Map: http://toposm.com/us/
> Metadata: http://wiki.openstreetmap.org/wiki/TopOSM

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