Hi Even Rouault,
Thanks. I had not found those SQL dialect docs for some reason so no
wonder it was not making sense.
I am now using ...
ogr2ogr -overwrite -f PostgreSQL PG:"dbname=original_hirise"
Beyer_Hirise_Areas_KML/MC-01-0-0-0.kml -nln gdal_hirise_from_kml -a_srs
"EPSG:4326" -dialect SQLit
On jeudi 24 novembre 2016 16:54:31 CET Michael Z Freeman wrote:
> Hi,
>
> Still having trouble with this after updating to ogr2ogr/gdal 2.1.1.
>
> Some of it is undoubtedly my unfamiliarity with GDAL. I'm on the steep
> part of the learning curve ! But fun.
>
> "ogr2ogr -f PostgreSQL PG:"dbname=
Hi,
Still having trouble with this after updating to ogr2ogr/gdal 2.1.1.
Some of it is undoubtedly my unfamiliarity with GDAL. I'm on the steep
part of the learning curve ! But fun.
"ogr2ogr -f PostgreSQL PG:"dbname=original_hirise" -a_srs "EPSG:4326" -lco
OVERWRITE=YES -explodecollections -nlt
Hi,
Thanks for this !
I eventually realised that I'd got in a muddle because I had failed to
understand what "wkb_geometry" is (
https://en.wikipedia.org/wiki/Well-known_text ). I think I thought it was
the gdal way for setting the SRID or something like this. So after seeing
the light I am using
esult with OpenJUMP. It shows both the geometry collections and
exploded collections fine for me with names and descriptions.
-Jukka Rahkonen-
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/gdal-dev-Unable-to-extract-features-from-KML-tp5296670p5296708.html
Sent from the
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
