gvSIG bugs #1533
Spatial join geoprocess doesn't apply the output schema correctly
Status: | Fixed | % Done: | 100% | |
---|---|---|---|---|
Priority: | Normal | |||
Assignee: | ||||
Category: | - | |||
Target version: | - | |||
Severity: | Add-on name: | Unknown | ||
gvSIG version: | 1.11.0 | Add-on version: | ||
gvSIG build: | 1305 | Add-on build: | ||
Operative System: | Add-on resolve version: | |||
Keywords: | geoprocess, spatial join | Add-on resolve build: | ||
Has patch: | Yes |
Description
The output layer of spatial join geoprocess has an hardcoded field description which is different than those of input layers. So I attach a patch which, together with #1530 and #1531 patches, fix the issue described also in "Geoprocess spatial join in gvSIG 1.9 will change field definition and creates decimal places for integer values" (from Joinup): https://joinup.ec.europa.eu/software/gvsig-desktop/issue/geoprocess-spatial-join-gvsig-19-will-change-field-definition-and-creat
Cheers,
Antonio
History
#1
Updated by Antonio Falciano over 11 years ago
- Target version set to 1.13.0
#2
Updated by Francisco Puga over 11 years ago
- Assignee set to Francisco Puga
- gvSIG version changed from 1.12.0 to 1.11.0
- gvSIG build changed from 1417 to 1305
#3
Updated by Francisco Puga over 11 years ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset r39585.
#4
Updated by Álvaro Anguix over 10 years ago
- Project changed from Application: gvSIG desktop to | gvSIG desktop 1
- Category deleted (
Geoprocess) - Target version deleted (
1.13.0)