Ticket #12 (closed defect: fixed)

Opened 13 years ago

Last modified 13 years ago

column punktkennung character varying(15) - values from NAS are not transfered properly to the file

Reported by: astrid.emde Owned by:
Priority: major Milestone: 0.6 release
Component: ogr Version:
Keywords: Cc: warmerdam@…,frank.jaeger,frank.haertel@…

Description

in some tables we have the column:

  • punktkennung character varying(15)

Tables:

  • ax_grenzpunkt
  • ax_netzpunkt
  • ax_besonderergebaeudepunkt
  • ax_besondererbauwerkspunkt
  • ax_besondereropographischerpunkt
  • and some more

This column is defined in the database schema as character varying(15). It can contain text or just numbers (the numbers can be larger then int4)

The following observation was made: incoming from NAS 

<punktkennung>324065641000135</punktkennung>

result in the db column 

1768582343

I try to set up an example.

Change History

comment:1 Changed 13 years ago by astrid.emde

  • Owner Info deleted
  • Component changed from Info to ogr

comment:2 Changed 13 years ago by warmerdam

  • Status changed from new to closed
  • Resolution set to fixed

I have added special logic to ensure that punktkennung is always forced to width 15 and type string to avoid this behavior in gdal trunk.

​http://trac.osgeo.org/gdal/changeset/22337

comment:3 Changed 13 years ago by astrid.emde

I tested this change with the testdata

​https://trac.wheregroup.com/PostNAS/attachment/ticket/11/NBA_RIO_20110430T000000_0von0_0_0.xml

Works fine for me, the information punktkennung has the same value it has in the xml-file.

Thanks

comment:4 Changed 13 years ago by astrid.emde

  • I tested with gdal trunk from today 11.5.2011 (revision 22354)
Note: See TracTickets for help on using tickets.