[GeoNode-users] SRC not established from *.prj. Non admin Users can´t select SRC of layers they upload.
daniel.victoria at gmail.com
Tue Oct 3 07:12:54 PDT 2017
We've encountered some issues with malformed .prj files. QGis would
recognize them fine but once imported into GeoNode, the projection would
end up wrong. If I remember correctly, it was how ESRI defined the
SIRGAS2000 datum. But this was some time ago, using GeoNode 2.4. Not sure
if it's fixed.
One work-around that we did, to debug the problem, was delete the .prj file
and redefine the shapefile projection in QGis. Then things would work.
On Tue, Oct 3, 2017 at 10:42 AM Stefan Steiniger <sstein at geo.uzh.ch> wrote:
> I don't have a problem with uploading data in UTM19S in V2.0, so I guess
> it's either a degression (not likely) or an issue with your *.prj
> file/definition strings. My shapefile are mostly from QGIS, though.
> > El 03-10-2017, a las 10:24, Ariel Neri <ariel.neriw at gmail.com> escribió:
> > Hi, i´m using Geonode 2.6. Neather I, nor the users of our geonode
> portal could find the way to establish the correct SRC on their layers (I
> thought they could from the metadata edition section but i was wrong),
> apart from the admin interface or Geoserver UI.
> > When a new shapefile is uploaded, a default SRC is set (40400), no
> matter what the *.prj inidcates. Only EPSG:4326 shapefiles are set
> correctly (most of our work is on UTM). Is this a miss-configuration on our
> GeoNode or that´s the way it works?
> > If it´s a local problem, would you indicate what files should i search
> for the problem?
> > At the moment i´m correcting that from Geoserver UI, but it would be
> very usefull if non-admin users could do it themselves on their layers.
> > Thanks
> > _______________________________________________
> > geonode-users mailing list
> > geonode-users at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/geonode-users
> geonode-users mailing list
> geonode-users at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geonode-users