kartoza / LEDET_BIMS

Limpopo Biodiversity Information Management System

GNU General Public License v3.0

1 stars 9 forks source link

Geonode upload error based on projection #267

Closed NyakudyaA closed 5 years ago

NyakudyaA commented 6 years ago

Problem

I tried uploading an shp with projection 3857 and this is what I get 3857

Solution

Ensure that the changes implemented in fixing this in Geonode are part of this image

@boney-bun can you take a look at this

gubuntu commented 6 years ago

looks like an issue with the extent, not the CRS?

our fixes are on kartoza/geonode and are focussed on QGIS server backend. So to fix this they would need to be tested on geoserver backend (get testinggs.geonode.kartoza.com working @boney-bun) merged upstream and then pulled into django-bims (or cherry-picked)

@NyakudyaA no 3857 data should be loaded anyway (most should be 4326 or local SA CRSs) so I would say this is low priority.

NyakudyaA commented 6 years ago

@gubuntu we used to have an issue like this in QGIS server. I think the codebase for reading CRS is the same wether it is QGIS server or Geoserver. When the layers are loaded through Geoserver all is fine. That's why I thought @boney-bun could look at it and just look and compare his changes.

NyakudyaA commented 5 years ago

This issue is an upstream bug in Geonode. I am going to open an upstream issue for this

https://github.com/GeoNode/geonode/issues/4103

evilGmonkey commented 5 years ago

Is there an Eta when this will be fixed or even a patch?