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

Reprojection of layers without EPSG code #129

Closed
uniomni opened this issue Apr 18, 2011 · 2 comments
Closed

Reprojection of layers without EPSG code #129

uniomni opened this issue Apr 18, 2011 · 2 comments
Milestone

Comments

@uniomni
Copy link
Contributor

uniomni commented Apr 18, 2011

It appears that GeoServer will happily accept and display layers with ESRI WKT spatial references. However, when downloaded again they always come in their native projection rather than the requested projection.

We noted that these layers have Native SRS set to UNKNOWN even though a valid WKT was supplied. We also noted that one can force reprojection through the GeoServer interface, but this is not feasible if layer upload and download are done from within an application.

We stipulate that an EPSG code is needed. However, as this is not provided by ESRI, it would be better if GeoServer could derived this code from the WKT projection.

Alternatively, forced reprojection should be specified through the REST interface whenever one which is not native has been requested.
This is a major problem as ESRI layers are extremely common.

@jj0hns0n
Copy link
Contributor

Punting to 2.1

@ingenieroariel
Copy link
Member

Since this cannot be fixed at the WCS level we can instead let users download the original file. This will be fixed by #1421

@pjdufour pjdufour modified the milestones: 2.5.x, 2.4 Jul 16, 2015
@jj0hns0n jj0hns0n modified the milestones: 2.7, 2.5 Aug 21, 2016
EmereArco pushed a commit to EmereArco/geonode that referenced this issue Jan 30, 2018
@afabiani afabiani closed this as completed Feb 2, 2018
travislbrundage pushed a commit to travislbrundage/geonode that referenced this issue Feb 9, 2018
Without this change, there is the potential for a MultipleObjectsReturned exception to be returned. Since we were already verifying that the service exists given the typename prefix, it makes sense to use the service id in the layer query so as to avoid the MultipleObjectsReturned exception.
marthamareal pushed a commit to marthamareal/geonode that referenced this issue Sep 24, 2021
Fix GeoNode#129 Users can access style editing even if they have no permission
marthamareal pushed a commit to marthamareal/geonode that referenced this issue Sep 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants