[Gvsig_english] gvSIG 1.9 and export to Oracle Spatial: field definition is changed - bug
Wolfgang Qual
wolfgang.qual at muenchen.de
Thu Mar 4 09:22:31 CET 2010
Dear list,
a colleague of mine noticed that field definitions of a layer will
change when that layer is exported to Oracle Spatial.
For example, if a column of the shapefile to be exported was of type
"integer" it will be "real" after exporting (and re-importing to
shape-format).
Also, field length is changed to a higher value. This has an additional
negative effect: the dbf-file will become much bigger (size of the file)
Is this a bug?
Best,
Wolfgang
(ps: the attached screenshots show the differences: first table:
original, second: oracle spatial layer; btw, strange that no type is
marked for former integer fields!
I checked it again after importing back to shapefile - there, manage
fields dialogue says: field ist integer (ogrinfo says: real))
-------------- next part --------------
A non-text attachment was scrubbed...
Name: feldbeschreibung_shp.png
Type: image/png
Size: 5170 bytes
Desc: not available
Url : http://listserv.gva.es/pipermail/gvsig_internacional/attachments/20100304/6c4c3901/attachment.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: feldbeschreibung_gdp.png
Type: image/png
Size: 6728 bytes
Desc: not available
Url : http://listserv.gva.es/pipermail/gvsig_internacional/attachments/20100304/6c4c3901/attachment-0001.png
More information about the Gvsig_internacional
mailing list