You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original Issue -
https://code.google.com/p/alageospatialportal/issues/detail?id=1070
Project Member Reported by chris.fl...@gmail.com, Jun 19, 2013
Shape files of type "Polygon 3D" cause errors during sampling such as the
following:
loading shape records error: /data/ala/data/layers/ready/shape/tams_reserves:
java.nio.BufferUnderflowException
java.nio.BufferUnderflowException
at java.nio.Buffer.nextGetIndex(Buffer.java:478)
at java.nio.HeapByteBuffer.getInt(HeapByteBuffer.java:336)
at org.ala.layers.intersect.PolygonZ.<init>(SimpleShapeFile.java:913)
at org.ala.layers.intersect.ShapeRecord.<init>(SimpleShapeFile.java:664)
at org.ala.layers.intersect.ShapeRecords.<init>(SimpleShapeFile.java:585)
at org.ala.layers.intersect.SimpleShapeFile.<init>(SimpleShapeFile.java:94)
at org.ala.layers.intersect.SamplingThread.intersectShape(SamplingThread.java:178)
at org.ala.layers.intersect.SamplingThread.sample(SamplingThread.java:93)
at org.ala.layers.intersect.SamplingThread.run(SamplingThread.java:67)
A workaround is exporting the shape file from the database using pgsql2shp, see
:http://code.google.com/p/alageospatialportal/wiki/ContextualLayerLoadProcess#3d
_polygons
the intent of the PolygonZ class is to handle 3d polygons. Either this class
should be fixed, or it should be removed and a more appropriate error message
should be thrown when a 3d polygon is found during the sampling process.
Jul 8, 2013 Project Member #1 leebel...@gmail.com
Can we check for a 3d polygon on import (which I presume is the only way a 3d
can occur?) and generate 2d version as above?
Original issue reported on code.google.com by moyesyside on 8 Aug 2013 at 12:09
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
moyesyside
on 8 Aug 2013 at 12:09The text was updated successfully, but these errors were encountered: