Uploading a shape file fails

[timlinux]

On a brand new install, uploading a simple shape file fails as per image below. I tried a few different shapefiles with the same outcome.

Power_corridors.zip

[timlinux]

Looking at geoserver backend, it seems the layer is actually uploaded to geoserver and then things go wrong when django is trying to add it to the layer model...

[timlinux]

Sorry for the noise here, just logging my diagnostics...

Looks like maybe geoserver is tripping up on the CRS:

PROJCS["WGS_1984_Albers", 
  GEOGCS["GCS_WGS_1984", 
    DATUM["D_WGS_1984", 
      SPHEROID["WGS_1984", 6378137.0, 298.257223563]], 
    PRIMEM["Greenwich", 0.0], 
    UNIT["degree", 0.017453292519943295], 
    AXIS["Longitude", EAST], 
    AXIS["Latitude", NORTH]], 
  PROJECTION["Albers_Conic_Equal_Area"], 
  PARAMETER["central_meridian", 24.0], 
  PARAMETER["latitude_of_origin", 0.0], 
  PARAMETER["standard_parallel_1", -33.0], 
  PARAMETER["false_easting", 0.0], 
  PARAMETER["false_northing", 0.0], 
  PARAMETER["standard_parallel_2", -24.0], 
  UNIT["m", 1.0], 
  AXIS["x", EAST], 
  AXIS["y", NORTH]]

The rsa layer seems to have a similar issue:

PROJCS["NSIDC_EASE_Grid_Global", 
  GEOGCS["GCS_Unspecified datum based upon the International 1924 Authalic Sphere", 
    DATUM["D_", 
      SPHEROID["International_1924_Authalic_Sphere", 6371228.0, 0.0]], 
    PRIMEM["Greenwich", 0.0], 
    UNIT["degree", 0.017453292519943295], 
    AXIS["Longitude", EAST], 
    AXIS["Latitude", NORTH]], 
  PROJECTION["Cylindrical_Equal_Area"], 
  PARAMETER["central_meridian", 0.0], 
  PARAMETER["standard_parallel_1", 0.0], 
  PARAMETER["false_easting", 0.0], 
  PARAMETER["false_northing", 0.0], 
  UNIT["m", 1.0], 
  AXIS["x", EAST], 
  AXIS["y", NORTH]]

I'm going to test with an EPSG:4326 layer

[timlinux]

Trying with another layer (EPSG:4326, attached) also fails this time with a somewhat cryptic [object: object] message as per:

Archive.zip

[gubuntu]

I can't comment on the EPSG: 4326 problem but can say that the Albers issue is because GeoNode only handles CRSs with standard EPSG codes, see also kartoza/geonode#435

[giohappy]

I did a test with your Power_corridors and confirm the EPSG issue.
Yes, GeoNode is weak on CRS side and we should defintely improve it...

@afabiani what's your opinion on this?