[gdal-dev] Re: DXF writing and layers

Andreas Neumann a.neumann at carto.net
Thu Nov 4 11:58:10 EDT 2010

Hi Frank,

Still no luck here with the layers.

Just to be sure: the layers aren't present in the header file. They should
be created by ogr. Is this correct that I don't necessarily have to create
the layers in advance?

Well - I think I will report a bug and make you the data available that I
am testing with.

Thanks a lot,

On Wed, November 3, 2010 11:53 pm, Frank Warmerdam wrote:
> On Mon, Nov 1, 2010 at 6:52 AM, Andreas Neumann <a.neumann at carto.net>
> wrote:
>> While testing the writer I wanted to use the new feature of specifying a
>> column in the source dataset that contains the layer name a feature
>> should
>> end up in the destination dxf file.
>> My source is a Postgis table, and the layer name is stored in a column
>> called "layer".
>> I don't know the correct dataset creation option (dsco) or layer
>> creation
>> option (lco) to specify the column containing the layernames.
>> I tried:
>> -dsco LayerName=layer
>> -dsco layer=layer
>> -lco LayerName=layer
>> -lco layer=layer
>> But no matter which of the above options I try, all my features end up
>> in
>> layer "0".
>> If anyone has a hint how I could issue the ogr2ogr command so I can
>> specify the layer a feature should end up in, it would be much
>> appreciated!
> Andreas,
> Currently the dxf writer only looks for the attribute named Layer
> to identify the layer name.  It sounds like in your case it should
> work directly since the Postgres column name is also "layer".
> If it is not, please file a ticket and I'll dig into it.  Providing
> an input dataset to demonstrate the problem would be
> helpful.
> Best regards,
> --
> ---------------------------------------+--------------------------------------
> I set the clouds in motion - turn up   | Frank Warmerdam,
> warmerdam at pobox.com
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush    | Geospatial Programmer for Rent

Andreas Neumann

More information about the gdal-dev mailing list