Skip to content
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

Make more helpful error message for ArcRAVE when Basemap can't load #183

Open
shelbysawyer opened this issue Feb 9, 2022 · 5 comments
Open
Assignees
Labels
🐛 bug Something isn't working enhancement New feature or request

Comments

@shelbysawyer
Copy link
Contributor

I came across an issue with imagery basemaps not loading in ArcRAVE.

I opened this project and tried to add the basemaps after opening the hillshade and DEM layers. This is the error message that came up:

RAVEissue

Sorry if this is a known issue, but thought I'd throw it in here in case it's not.

@shelbysawyer shelbysawyer added the 🐛 bug Something isn't working label Feb 9, 2022
@joewheaton
Copy link
Contributor

I had same problem @shelbysawyer. Thanks for posting. I think that this is a known issue where the web mapping services that work in QRAVE don't work in ArcRAVE (more than just the xyz). Also these services are notoriously unreliable. I'm going to rename this a little more specifically and move to the ArcRave repo.

@joewheaton joewheaton changed the title ArcRAVE: Basemap Issue Make more helpful error message for ArcRAVE when Basemap can't load Feb 9, 2022
@joewheaton
Copy link
Contributor

@philipbaileynar I will let you assign this for whenever we get a round of updates to ArcRAVE next. Can we please update message to:

Error! Unable to add the Web Mapping Service (WMS) to the map. 
Note that WMS are often unreliable, addresses and credentials change without warning and ESRI's handling of WMS can be inconsistent. 
If this is an important Basemap, try visiting the original source provider and manually adding the WMS using ESRI's Add to Map dialog. 

Exception from HRESULT: 0x80040217.
  • or something to that effect...

In other words, help them out beyond just catching the error and providing a cryptic message that makes them think they did something wrong. Lets remember the principle of "self-service". It might be worth having @jtgilbert go through all the error messages in ArcRAVE and QRAVE, and just making them a little more helpful and readable and empathetic with users."

@joewheaton joewheaton transferred this issue from Riverscapes/riverscapes-tools Feb 9, 2022
@joewheaton joewheaton added the enhancement New feature or request label Feb 9, 2022
@jtgilbert
Copy link

I went through all the basemaps in QRAVE yesterday. None caused errors but some just don't show up. Arc definitely handles them much worse, especially basemaps that are made of multiple parts.

Because of their lack of reliability, I think it's worth having a conversation at some point about which ones we should work to keep and maintain, and maybe ditching others. A lot of the USGS TNM-based ones are kind of redundant, for example the transportation basemap is the same TIGER data we have in RSContext projects, with the same symbology.

@jtgilbert
Copy link

Also, all basemaps available in Arc work for me (are added to map without throwing an error) except for NED 3DEPE.

@joewheaton
Copy link
Contributor

I went through all the basemaps in QRAVE yesterday. None caused errors but some just don't show up. Arc definitely handles them much worse, especially basemaps that are made of multiple parts.

Thanks for doing that @jtgilbert.

Because of their lack of reliability, I think it's worth having a conversation at some point about which ones we should work to keep and maintain, and maybe ditching others. A lot of the USGS TNM-based ones are kind of redundant, for example the transportation basemap is the same TIGER data we have in RSContext projects, with the same symbology.

Remember users will not necessarily always be using a riverscapes context project, so none of these layers are "redundant" in that common use case. However, it is worth having a conversation about which ones should be ditched because they are so unreliable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants