Nik,
Using OGR_F_SetFieldX() only modifies the in-memory value, but has
no effect on serialization. You have to use OGR_L_SetFeature() to make sure
that the modified feature is written back to the datasource.
As it seems to be a common pitfall, I'm going to improve the doc of the
OGR_F_Set
Hi,
I can successfully built GDAL on OSX as long as my target is /usr/local but
when building for the framework I and getting some errors.
The first one seems easy no fix:
$ ./configure --with-macosx-framework
configure: WARNING: unrecognized options: --with-macosx-framework
checking build s
Hi List. I'm using GDAL/OGR 1.11 in an Objective-C (iOS)
application.
I'm attempting to store double values in an OFTReal field using
OGR_F_SetFieldDouble() and then to retrieve these values later using
OGR_F_GetFieldAsDouble(). If I retrieve the value immediately, it
works fine. However, after
Hi Andre,
Thanks for the tip - I guess there's a lot more that can be done with the
overpass API than I'm using right now!
In my case I need to process a lot of square regions (with random center
coords). Will try to see if the "river problem" can be fixed by fetching a
larger region than needed
Am 01.01.2017 um 22:52 schrieb Simon Lyngby Kokkendorff:
And indeed - worked like a charm when I ran ogr2ogr on a pbf file
containing the whole of England. The River Thames is represented nicely, as
was the case with osm2pgsql. Was surprisingly fast also compared to
osm2pgsql!
So definitely a "t
