Hi,
The main problem is that KML support such data models which do not suit well
with the simple feature model of GDAL. You can get some information about
that by reading http://www.gdal.org/drv_libkml.html.
In your case each feature has two geometries: one point and one polygon.
Best that can be
Hi,
Even through "ogrinfo" can see all the fields and the features in my KML I
can never get ogr2ogr to actually give me the feature info that I want:
name, description, point, polygon. The only format that actually shows is
JSON but that is a real pain to import into PostGreSQL. CSV and PostGreSQ
On dimanche 20 novembre 2016 09:43:19 CET Sean Gillies wrote:
> Hi Even,
>
> All the above (or below) sounds good to me. Could a "description" member be
> added as well?
Yes. Implemented per https://trac.osgeo.org/gdal/changeset/36339
>
> On Sat, Nov 19, 2016 at 4:24 PM, Even Rouault
>
> wrot
Hi Even,
All the above (or below) sounds good to me. Could a "description" member be
added as well?
On Sat, Nov 19, 2016 at 4:24 PM, Even Rouault
wrote:
> Hi
>
> Currently the GeoJSON datasource always return "OGRGeoJSON" as a layer
> name,
> which is quite boring (if you convert the geojson in
Am 19.11.2016 um 20:45 schrieb Djordje Spasic:
Thank you Etienne.
I am very interested in your reply, but I haven't quite understand you.
The ogr2ogr.exe file is using a particular python script to read the .osm file
and identify its unique fields?
Can you be a bit more specific please? Solving
