Opened 13 years ago
Closed 13 years ago
#4255 closed defect (fixed)
PostNAS - ogr2ogr does not handle array field correctly
| Reported by: | astrid_emde | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.9.0 |
| Component: | default | Version: | svn-trunk |
| Severity: | normal | Keywords: | |
| Cc: | marina.thust@… |
Description (last modified by )
- datasets with only one value don't get imported
- you will find the SQL Schema at http://trac.wheregroup.com/PostNAS/browser/trunk/data/konvert/postnas_0.6/alkis_PostNAS_0.6_schema.sql
select distinct artderflurstuecksgrenze from AX_BesondereFlurstuecksgrenze;
Attachments (3)
Change History (8)
by , 13 years ago
| Attachment: | NBA_RIO_20110802T000000_0von0_0_0_funktioniert.xml added |
|---|
by , 13 years ago
| Attachment: | NBA_RIO_20110802T000000_0von0_0_0_fehlerhaft.xml added |
|---|
comment:1 by , 13 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | ogr2ogr does not handle array field correctly → PostNAS - ogr2ogr does not handle array field correctly |
comment:2 by , 13 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 13 years ago
| Cc: | added |
|---|
comment:4 by , 13 years ago
Hum, the explanation is simple, the solution not.
In the funkioniert case, there are 2 values for <artDerFlurstuecksgrenze>, so OGR as expected (from the code point of view ;-) ) returns a IntegerList field. In the fehlerhaft case, there is only a single value, so OGR as expected returns a Integer field.
The issue is that OGR is not aware of the NAS schema and relies on the data to establish the field names and types. So, apart from an ad-hoc patch to force "artDerFlurstuecksgrenze" to be IntegerList, I don't see an obvious cleaner approach.
comment:5 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
with two values for artDerFlurstuecksgrenze