[GRASS-dev] Re: [gdal-dev] interpretation of nodata in OGR
libraries
Frank Warmerdam
warmerdam at pobox.com
Tue Oct 7 15:08:02 EDT 2008
Markus Neteler wrote:
>> Reviewing the mk_att() function in v.out.ogr's main.c I don't see
>> any effort to distinguish between null and non-null attributes so
>> I think the problem is just a limitation of v.out.ogr. If possible,
>> I'd suggest fixing it there.
>
> Sounds good :)
> Does anyone know how to fix
> vector/v.out.ogr/main.c
> to support NULLs? I see db_set_value_null() in
> lib/db/dbmi_base/value.c
> which might be relevant.
Markus,
Once you establish which GRASS attributes are NULL, you can ensure they
are pushed out to OGR as null by just skipping the step that sets them.
Perhaps that will help a bit.
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
More information about the grass-dev
mailing list