gvSIG bugs #2004
The buffer geoprocess don't build the table fields correctly
| Status: | Closed | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: |  Ignacio Brodín | |||
| Category: | Geoprocess | |||
| Target version: | 2.1.0-2219-testing | |||
| Severity: | Add-on version: | |||
| gvSIG version: | 2.0.0 | Add-on build: | ||
| gvSIG build: | Add-on resolve version: | |||
| Operative System: | Add-on resolve build: | |||
| Keywords: | Proyecto: | |||
| Has patch: | No | Hito: | ||
| Add-on name: | Unknown |
Description
1-Open a line layer and the buffer geoprocess
2-Select only one ring and don't check the dissolve option
3-Run the geoprocess and when it finishes open the attribute table
4-The table should be the same as the original
The right behavior shoul be the next
If the dissolve option is not checked then the fields will be the same as the original layer.
If the dissolve option is checked and the influence area is "input and output" the table will have three fields (FID, FROM, TO)
If the dissolve option is checked and the influence area is not "input and output" the table will have two fields (FID, FROM)
History
#1
Updated by Ignacio Brodín over 10 years ago
Manuel, I've detected some problems building the table structure in the buffer geoprocess. I've described the behavior that I think that the buffer should have. Could you review that, please?
#2
Updated by Álvaro Anguix over 10 years ago
- Target version changed from 2.1.0-2223-rc1 to 2.1.0-2219-testing
#3
Updated by Ignacio Brodín over 10 years ago
- Status changed from New to Fixed
El comportamiento ahora parece correcto.
#4
Updated by Álvaro Anguix about 10 years ago
- Status changed from Fixed to Closed