Hi Jorge,
I don't see anything obviously wrong. Looking at the places where the variables
might be nullified and running Valgrind would be my best advice.
Just wanted to mention that in the likely simplified below snippet, you would
leak memory.
Even
Hello,
I have a stupid mistake in my
Hi Even,
Thanks for your hints. About the memory leaking, apart from the obvious
fact that CPLStrdup vars need to be freed, are you seeing something more?
On Tue, Aug 12, 2014 at 9:48 AM, Even Rouault even.roua...@mines-paris.org
wrote:
Hi Jorge,
I don't see anything obviously wrong.
Selon Jorge Arevalo jorgearev...@libregis.org:
Hi Even,
Thanks for your hints. About the memory leaking, apart from the obvious
fact that CPLStrdup vars need to be freed, are you seeing something more?
No, that was indeed what I meant. Not much more that could leak in the snippet
;-)
On
Even Rouault even.rouault at spatialys.com writes:
Hi Paul,
...
Others are less likely. I’ve learned that GeoServer is emitted GPKG files
without the application_id set.
Hum, do they plan fixing that at some point ? Couldn't they do the same trick
we do (direct editing) ?
According
Dear GDAL/OGR team,
I just realized that there is no support for the OGC POINT ZM geometry
in GDAL/OGR. It is well possible to read in a 3D point with an
additional attribute from the following OGC compliant WKT string...
POINT ZM(1. 2. 3. 4.)
... but the attribute value (i.e. 4.) is
On 12 August 2014 17:54, Gottfried Mandlburger
gottfried.mandlbur...@geo.tuwien.ac.at wrote:
Any plans to add POINT ZM support in GDAL in the near future?
It was proposed to Google Summer of Code [1] this year, but not selected.
I'm not sure if there is any ongoing initiative.
[1]
Selon Gottfried Mandlburger gottfried.mandlbur...@geo.tuwien.ac.at:
Dear GDAL/OGR team,
I just realized that there is no support for the OGC POINT ZM geometry
in GDAL/OGR. It is well possible to read in a 3D point with an
additional attribute from the following OGC compliant WKT string...
