Hi,
With ogr2ogr, you can't read all keys from an OSM file.
As Even said, you have to use another loop to read all available keys in
the file. You can have a look at the QGIS QuickOSM plugin. You can open a
OSM file and ask the plugin to read all keys available in the file.
2016-11-19 8:30
During the last couple of days, both Jukka and Even helped me with some .osm
file issues. And I am grateful on that.
I would like to ask one more question, if that's ok:
Is it possible to open an .osm file through ogr2ogr.exe and somehow read all
the fields (keys) used in that .osm file? The
Hi!
On Fri, Nov 18, 2016 at 6:01 AM, jratike80
wrote:
> However, if you want to
> explode multilinestrings into linestrings use switch -explodecollections.
This one.
I wasn't seeing an explanation for this in "ogr2ogr --long-usage" (it
seems that I need to
Ari and all,
When I saw the announcement of https://github.com/QuantStack/xtensor I
immediately thought of recent conversations here. Maybe worth a look?
--
Sean Gillies
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
You need to have both: include all_tags in osmconf.ini and define with the
ogr2ogr command that field “all_tags” in PostGIS should be initialized as
hstore. If you do not define column type all_tags will probably become text
type column. Make a test and you will see it.
-Jukka Rahkonen-
Thank you for the useful reply Jukka!
The command you gave me:
ogr2ogr -f PostgreSQL "PG:dbname=osm" test.pbf -lco
COLUMN_TYPES=all_tags=hstore
does the same thing as "all_tags=yes" in the osmconf.ini file:
# uncomment to create "all_tags" field. "all_tags" and "other_tags" are
exclusive
Nelson A. de Oliveira wrote
> Hi!
>
> Sorry if it's not the appropriated place to ask this, but is there a
> way to convert MULTILINESTRING to LINESTRING?
> For example:
>
> =
> ogr2ogr -f "SQLite" -gt 65536 -dsco SPATIALITE=YES database.sqlite
> shape.shp
> ERROR 1: Cannot insert feature