gvSIG bugs #2528
Poligonar líneas da error
| Status: | Closed | % Done: | 100% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: |  Ignacio Brodín | |||
| Category: | Geoprocess | |||
| Target version: | 2.1.0-2251-testing | |||
| Severity: | Minor | Add-on version: | ||
| gvSIG version: | 2.1.0 | Add-on build: | ||
| gvSIG build: | 2227 | Add-on resolve version: | ||
| Operative System: | Linux | Add-on resolve build: | ||
| Keywords: | Proyecto: | |||
| Has patch: | No | Hito: | ||
| Add-on name: | Unknown |
Description
Sobre una capa de líneas (ej.capa adjunta) intentamos ejecutar el geoproceso de poligonar líneas y salta un error.
Adjunto log.
Related issues
Associated revisions
refs #2528 Corregido error en PolygonizeAlgorithm
History
#1
Updated by Antonio Falciano almost 10 years ago
- File sextante.log added
FYI the Polygonize geoalgorithm works fine with the layer in attachment in gvSIG 1.12, so we can exclude the presence of invalid geometries (i.e. linestrings made by two coincident points) or topology exceptions.
I can reproduce the error in BN2227 and attach the sextante.log (instead of gvSIG one). It's caused by the SextanteLogHandler according to the log. Hope this helps.
#2
Updated by Antonio Falciano over 9 years ago
It should be related to #2849.
#3
Updated by Álvaro Anguix over 9 years ago
- Related to gvSIG bugs #2849: Several SEXTANTE geoprocesses don't work fine due to the GEOMETRY field added
#4
Updated by Francisco Díaz Carsí over 9 years ago
- % Done changed from 0 to 100
- Target version set to 2.1.0-2251-testing
- Status changed from New to Fixed
#5
Updated by Álvaro Anguix over 9 years ago
- Status changed from Fixed to Closed