-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Geology to RAVE as Basemap #415
Comments
@philipbaileynar I believe that your suggestion of
is spot on. My understanding is that for services that work in both Arc and Q, we can just add to the basemaps.xml? @jtgilbert this sort of explains it, but is out of date documentation: http://rave.riverscapes.xyz/Technical_Reference/base-maps.html... see Riverscapes/RaveAddIn#182 |
There seem to be so many web mapping standards and each has a different URL format. This is an ESRI web mapping service and I'm unsure how it will play with both Q and Arc. I'm not sure we have tackled one of these before. I recommend experimenting with your local copy of BaseMaps.xml for both QRAVE and ArcRAVE to see what works. |
@philipbaileynar I have it displaying in basemaps for both Q and Arc. However, it brings in a legend in Q and does not in Arc. Is this something you guys have dealt with before? |
We have definitely encountered very different behaviour between how the two platforms handle web mapping layers! Sorry, I don't have much more to add. Remind me, do other web mapping layers in ArcGIS display legends? |
Yeah it looks like they generally don't. Should I push the changes as is then? |
Web mapping layers are the wild west of GIS! I think push. Can do no harm. Just less useful in ArcGIS. The original request for this layer came from a Mac/QGIS user... |
Discussed in https://github.com/Riverscapes/riverscapes-website/discussions/29
Originally posted by stephen-bennett November 30, 2021
I'd like to request that a geology layer be added to riverscapes projects as it is a fundamental driver of riverscape form and function
The text was updated successfully, but these errors were encountered: