gvSIG bugs #4098
Geometry type of Shape does not match the geometry found in the shape
| Status: | Closed | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: | - | |||
| Category: | Geoprocess | |||
| Target version: | 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153) | |||
| Severity: | Major | Add-on version: | ||
| gvSIG version: | 2.3.0 | Add-on build: | ||
| gvSIG build: | 2421 | Add-on resolve version: | ||
| Operative System: | Add-on resolve build: | |||
| Keywords: | Proyecto: | |||
| Has patch: | Hito: | |||
| Add-on name: | Unknown |
Description
- add the layer in attachment (edifici.shp) in a view;
- execute the "Transform" (Affine transformation) geoprocess and try to apply e.g. a translation of 10 m along the x axis.
- the result layer is loaded in the ToC, but not visible in the view;
- there's the following warning in the gvSIG.log:
[...] Geometry type of Shape (5) does not match the geometry found (15) in the shape [...]
Related to #3838 ("Random vector layer" geoprocess).
Related issues
Associated revisions
refs #4098 Introducing subtypes in toolbox algorithm
refs #4098 Introducing subtypes in toolbox algorithm
refs #4098, #4151, #4156 . Modificaciones para que la gestion de capas con errores funcione de nuevo, presentando al usuario los errores producidos. Se han mejorado los mensajes de error en el proveedor de shape, dando informacion en ellos de como el usuario puede rodear el problema cuando esto es posible. Asi mismo se ha añadido la posibilidad de que en caliente se puedan corregir algunos problemas y se pueda volver a recargar la capa sin tener que quitarla y volverla a cargar.
History
#1
Updated by Álvaro Anguix over 8 years ago
- Related to gvSIG bugs #3838: Random layers generated from the toolbox are not loaded in the view added
#2
Updated by Francisco Díaz Carsí over 8 years ago
- Assignee set to Francisco Díaz Carsí
#3
Updated by Antonio Falciano about 8 years ago
This issue always happens in build 2426, differently from #3838. The only difference is that the warning is more explanatory than in the past:
[...] Saving a geometry of type 'POLYGON3D' in a shape of type 'POLYGON2D' [...]
#4
Updated by Antonio Falciano about 8 years ago
...but thanks to gvsig-desktop:r42756 I can easily see that edifici.shp is of MultiSurface3DM type, so the getShapeType() method used in the Transform algorithm is not able to get also the geometry subtype (not only the type) of the input layer. So IMHO this method needs some little improvements in order to support the new geometries.
#5
Updated by Francisco Díaz Carsí almost 8 years ago
He arreglado los algoritmos:
- GeometriesToPointsAlgorithm
- GroupNearFeaturesAlgorithm y
- TransformAlgorithm
En principio lo he intentado dejar para que los algoritmos que no he tocado se sigan comportando igual que antes, o sea, si funcionaban solo en 2D sigan funcionando en 2D.
Habría que ir probando el resto de algoritmos y arreglándolos si es necesario.
#6
Updated by Francisco Díaz Carsí almost 8 years ago
No pongo el tiquet a fixed a la espera de tomar una decisión al respecto (sobre lo de repasar todos los algoritmos).
#7
Updated by Joaquín del Cerro Murciano almost 8 years ago
- Related to gvSIG bugs #4151: Exeption Reading shapefile.shp added
#8
Updated by Joaquín del Cerro Murciano almost 8 years ago
Los arreglos de #4151, permitirian cargar las capas "dañadas" que generan estos geoprocesos.
#9
Updated by Álvaro Anguix almost 8 years ago
- Target version deleted (
2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153))
#10
Updated by Joaquín del Cerro Murciano almost 8 years ago
- Assignee deleted (
Francisco Díaz Carsí)
#11
Updated by Antonio Falciano almost 8 years ago
this is the situation in build 2433:
- the result layer is loaded in the ToC, but not visible in the view (so the issue persists);
- the warning described above is disappeared from the gvSIG.log (so we can't understand what's happened from the log);
- the checkboxes in Advanced properties of layer don't allow to load the result layer (because the layer is not "damaged").
Note: the result layer can be read in other applications (tested in OpenJUMP and QGIS), so it's not malformed.
#12
Updated by Antonio Falciano over 7 years ago
- Target version set to 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153)
- Status changed from New to Closed
The issue is disappeared in gvSIG 2.3 final, so I close the ticket.