I went through the whole RFC and it looks great!
Even, this looks like an incredible amount of work and I wanted to thank you
for undertaking it.
Ragi
--
View this message in context:
Hello Tamas and Dennis,
This is my personal opinion and there may tons of people that disagree, but
I think it is more sane to always assume UTF8 encoding. There is
functionality among the various drivers to accept/return strings in
different encodings (through the CPL_Recode mechanism) but they
Hello Tamas and Dennis,
Indeed the C# bindings to not handle UTF8 characters correctly. I submitted
a bug report about it a couple of months ago with a reproducible case.
http://trac.osgeo.org/gdal/ticket/4971
For the case that I submitted, the values for the fields in C-API GDAL are
coming out
Hello quiztli,
I have it working on Windows and OSX. I believe EvenR did the port for
Linux.
If I had to do a wild guess, I would say that the dynamic library for the
esri implementation is not being found at run-time. Check your
LD_LIBRARY_PATH (Linux) / DYLD_LIBRARY_PATH (OSX) to make sure
Although FileGDB does have programmatic ways to preserve the FID, these are
not exposed through the FileGDB API yet. What people normally do in these
cases is to copy the fid to the target dataset as a non-primary key value. I
guess we could add something along these lines as an enhancement
ArcObjects to OGR:
https://github.com/rouault/gdal/blob/trunk/gdal/ogr/ogrsf_frmts/arcobjects/aoutils.cpp#L276
OGR to ArcObjects:
https://github.com/RBURHUM/arcgis-ogr/blob/master/src/OGRPlugin/OGRPlugin/ogrplugin_utils.cs#L209
Best,
- Ragi
--
View this message in context:
http://osgeo-org
Perhaps calling it 2.0 is not a bad thing and it sounds of less of a hassle.
Breaking the ABI (by rushing major API changes) just so that the semantics
of what 2.0 means, seems inappropriate. If/when the unification starts, we
could bump it to 3.0, 4.0 or any other number. There are quite a few of
Hi Frank,
Getting an official release of libKML 1.3 would be great.
By the way, there is a build issue of libKML with autoconf 1.12. I
submitted a bug and a simple fix with details
http://code.google.com/p/libkml/issues/detail?id=186sort=-id . If you
could commit that, that would be great,
