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
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 this issue will mean a lot to me.
Sorry for distu
The parsing is done using python in the plugin. We can just use the parser
by calling the python file. Python is included when you install osgeo4w.
Yes you can set the osmconf.ini or directly use the goal ogr api to write
the output file.
On 19 Nov 2016 18:00, "Djordje Spasic" wrote:
> Thank yo
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 GMT+0
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 fin
