Difference between revisions of "Geonode data upload"

From stgo
Jump to: navigation, search
(Created page with ">> return to Cedeus IDE ---- == Problems I discovered when Uploading Data to GeoNode == === Spanish characters === Problem: Sometimes, after upload names of attributes...")
 
(Transformation error)
Line 19: Line 19:
  
 
and also (looking ''/usr/share/geoserver/data/logs/geoserver.log'') I got:
 
and also (looking ''/usr/share/geoserver/data/logs/geoserver.log'') I got:
  2015-03-11 15:47:05,991 WARN [geotools.jdbc] - Failed to use ST_Estimated_Extent, falling back on envelope aggregation
+
  Caused by: java.io.IOException: transform error
org.postgresql.util.PSQLException: ERROR: stats for "red_ferroviaria.the_geom" do not exist
+
        at org.geoserver.catalog.CatalogBuilder.getLatLonBounds(CatalogBuilder.java:525)
  Where: SQL function "st_estimated_extent" statement 2
+
        at org.geoserver.catalog.CatalogBuilder.doSetupBounds(CatalogBuilder.java:466)
 +
        at org.geoserver.catalog.CatalogBuilder.setupBounds(CatalogBuilder.java:450)
 +
        at org.geoserver.catalog.rest.DataStoreFileResource.handlePut(DataStoreFileResource.java:405)
 +
        ... 88 more
 +
Caused by: org.geotools.referencing.operation.projection.ProjectionException: Transformation doesn't convergence.
 +
        at org.geotools.referencing.operation.projection.MapProjection.inv_mlfn(MapProjection.java:1385)
 +
        at org.geotools.referencing.operation.projection.TransverseMercator.inverseTransformNormalized(TransverseMercator.java:217)
 +
 
  
 
Solution:
 
Solution:
 
The problem is that there seems to be a misfit with the projection (remember, Chile's Easter Island is far off, so UTM 19S is perhaps not so good working as it is not in zone 19). To solve this issue I re-saved the shapefile as WGS84 (epsg 4326) in geographic coordinates (and also I used UTF-8 character encoding, just to make sure). This new shapefile I was able to load in GeoNode 2.0
 
The problem is that there seems to be a misfit with the projection (remember, Chile's Easter Island is far off, so UTM 19S is perhaps not so good working as it is not in zone 19). To solve this issue I re-saved the shapefile as WGS84 (epsg 4326) in geographic coordinates (and also I used UTF-8 character encoding, just to make sure). This new shapefile I was able to load in GeoNode 2.0

Revision as of 16:43, 11 March 2015

>> return to Cedeus IDE


Problems I discovered when Uploading Data to GeoNode

Spanish characters

Problem: Sometimes, after upload names of attributes or attribute values are not correctly represented, i.e. Categor�A

Solution: This is an encoding problem. Before hitting the upload button in geonode, select the file encoding. In most cases it encoding is Latin 1.

Transformation error

Problem: The shapefile upload fails with an error. In particular I get:

java.lang.RuntimeException: java.io.IOException: transform error

and also (looking /usr/share/geoserver/data/logs/geoserver.log) I got:

Caused by: java.io.IOException: transform error
       at org.geoserver.catalog.CatalogBuilder.getLatLonBounds(CatalogBuilder.java:525)
       at org.geoserver.catalog.CatalogBuilder.doSetupBounds(CatalogBuilder.java:466)
       at org.geoserver.catalog.CatalogBuilder.setupBounds(CatalogBuilder.java:450)
       at org.geoserver.catalog.rest.DataStoreFileResource.handlePut(DataStoreFileResource.java:405)
       ... 88 more
Caused by: org.geotools.referencing.operation.projection.ProjectionException: Transformation doesn't convergence.
       at org.geotools.referencing.operation.projection.MapProjection.inv_mlfn(MapProjection.java:1385)
       at org.geotools.referencing.operation.projection.TransverseMercator.inverseTransformNormalized(TransverseMercator.java:217)


Solution: The problem is that there seems to be a misfit with the projection (remember, Chile's Easter Island is far off, so UTM 19S is perhaps not so good working as it is not in zone 19). To solve this issue I re-saved the shapefile as WGS84 (epsg 4326) in geographic coordinates (and also I used UTF-8 character encoding, just to make sure). This new shapefile I was able to load in GeoNode 2.0