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

Show more specific error message when importing unsupported types of ArcGIS layers #9108

Closed
jgoizueta opened this issue Jul 26, 2016 · 5 comments

Comments

@jgoizueta
Copy link
Contributor

As noticed by @julianamori in #9013, unsupported layers types (e.g. Raster) are simply ignored when importing a multi-layer resource, but cause an import error when importing a single layer.

In this case we log this error message internally:

2016-07-25 16:25:44 UTC: Additional error info: Invalid layer type: 'Raster Layer'

But the error the user gets is a generic one, which might be misleading:

Error retrieving data from datasource (1011)
There was an error retrieving data from the datasource. Check that the file/data is still present.

We can map the error to mor appropriate error code or add a new one for this case.

The error shown when a multilayer resource consisting only of unsupported layers should also be reviewed.

@saleiva
Copy link
Contributor

saleiva commented Nov 16, 2016

@jgoizueta is this still happening?

@jgoizueta
Copy link
Contributor Author

Yes, still happening. Can be reproduced with this layer:
https://raster.nationalmap.gov/arcgis/rest/services/LandCover/USGS_EROS_LandCover_NLCD/MapServer/21

Internally we log this:

2016-11-22 14:33:47 UTC: Additional error info: Invalid layer type: 'Raster Layer'

But the users sees only this:

image

@saleiva saleiva added this to the Dataservices - La Guardia milestone Nov 23, 2016
@rafatower
Copy link
Contributor

@saleiva I'd move this straight to the next sprint, unless this takes precedence on what was planned (I don't think so, the rest affects way more builder stability)

@stale
Copy link

stale bot commented Feb 19, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Feb 19, 2018
@rafatower rafatower removed their assignment Feb 20, 2018
@stale stale bot removed the stale label Feb 20, 2018
@stale
Copy link

stale bot commented Feb 20, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Feb 20, 2019
@stale stale bot closed this as completed Feb 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants