Difference between revisions of "Geonode data upload"
(→Transformation error) |
(→Problems I discovered when Uploading Data to GeoNode) |
||
| Line 6: | Line 6: | ||
=== Spanish characters === | === Spanish characters === | ||
| − | Problem: | + | '''Problem:''' |
Sometimes, after upload names of attributes or attribute values are not correctly represented, i.e. <code>Categor�A</code> | Sometimes, after upload names of attributes or attribute values are not correctly represented, i.e. <code>Categor�A</code> | ||
| − | Solution: | + | '''Solution:''' |
This is an encoding problem. Before hitting the upload button in geonode, select the file encoding. In most cases it encoding is <code>Latin 1</code>. | This is an encoding problem. Before hitting the upload button in geonode, select the file encoding. In most cases it encoding is <code>Latin 1</code>. | ||
=== Transformation error === | === Transformation error === | ||
| − | Problem: | + | '''Problem:''' |
The shapefile upload fails with an error. In particular I get: | The shapefile upload fails with an error. In particular I get: | ||
java.lang.RuntimeException: java.io.IOException: transform error | java.lang.RuntimeException: java.io.IOException: transform error | ||
| Line 30: | Line 30: | ||
| − | 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:45, 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
