--- Anyway, it's better to not rely on field order. ITF and ILI go always together… when I give them to someone else, the attribute order has to correspond, because they using programs who looks to the ILI attribute order to import the ITF data
Anyway, it's better to not rely on field order. On Tue, Sep 20, 2011 at 8:16 PM, BSAP ( Andres Thomas ) <[email protected]> wrote: … i’ve tried, but there are several tables to be exported…. I can’t write –select table1.fid,table1.color,table2.fid,table2.mysize,etc… When I query one table with ogrinfo I see, that the attributes are listed in the same order like in the created ITF… if I only could change this… Von: Chaitanya kumar CH [mailto:[email protected]] Gesendet: Dienstag, 20. September 2011 16:11 An: BSAP ( Andres Thomas ) Cc: [email protected] Betreff: Re: [gdal-dev] Ogr2Ogr Interlis1 Export Thomas, OGR doesn't promise the same field order. Individual drivers can reorder the fields when they save the data. You may be able to reorder the fields using the -select option in ogr2ogr. On Tue, Sep 20, 2011 at 7:05 PM, BSAP ( Andres Thomas ) <[email protected]> wrote: Dear List, i have exported data from postgres to an itf with the following command: ogr2ogr -f "Interlis 1" mynew.itf,myili1.ili PG:"dbname='mydatabase' host='localhost' port='123' user='postgres' password='mypassword'" The ITF was created, but the attributes of one table i.e. are not in the same order like in the ILI-File… and also not in the same order like in the Postgres Database… Why that? Thx for your help, Thomas Andres _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev -- Best regards, Chaitanya kumar CH. +91-9494447584 <tel:%2B91-9494447584> 17.2416N 80.1426E -- Best regards, Chaitanya kumar CH. +91-9494447584 17.2416N 80.1426E
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
