Re: [gdal-dev] Overcome attribute name limitation in shapefiles

2017-03-07 Thread Felix Obermaier
en/ptv-visum-shape.zip The supplementary file is „ptv-visum-shape.CTF“. Felix Von: Even Rouault [mailto:even.roua...@spatialys.com] Gesendet: Dienstag, 7. März 2017 10:35 An: Cc: Felix Obermaier ; Peter Halls Betreff: Re: [gdal-dev] Overcome attribute name limitation in shapefiles On mardi 7 mar

Re: [gdal-dev] Overcome attribute name limitation in shapefiles

2017-03-07 Thread Even Rouault
März 2017 14:56 > An: Felix Obermaier ; gdal dev > Betreff: Re: [gdal-dev] Overcome attribute name > limitation in shapefiles > Felix, > following your proposal would make Shapefiles cease to respect the > dBaseIV Standard and potentially seriously affect their interchangability.

Re: [gdal-dev] Overcome attribute name limitation in shapefiles

2017-03-07 Thread Felix Obermaier
undistinctness. Or I get a shapefile of that kind, which does not make it any better. Felix Von: Peter Halls [mailto:p.ha...@york.ac.uk] Gesendet: Montag, 6. März 2017 14:56 An: Felix Obermaier ; gdal dev Betreff: Re: [gdal-dev] Overcome attribute name limitation in shapefiles Felix

Re: [gdal-dev] Overcome attribute name limitation in shapefiles

2017-03-06 Thread Peter Halls
Felix, following your proposal would make Shapefiles cease to respect the dBaseIV Standard and potentially seriously affect their interchangability. There are a range of alternative formats supported by GDAL that achieve your goal: for example, I use SQL as my base format and only convert wh

[gdal-dev] Overcome attribute name limitation in shapefiles

2017-03-06 Thread Felix Obermaier
Hello, is it somehow possible to overcome the attribute name length limitiation of DBase files using GDAL? If so, how? If not, why not add (another) file the shapefile dataset of shapes (shp, shx), projection (prj), data (dbf) and encoding(cpg), one that is (re-) defining the column names, all