<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=DE link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-GB>Hi Nikos,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>I am using a similar approach to yours to extract data from OSM files to a GIS format. I chose Spatiallite as a format since it is superior to the Shapefile format in all areas.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>FYI here’s what I do:<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify;text-justify:inter-ideograph'><span lang=EN-GB>osmconvert -b="5.5,49,8,50.5" -o=saarland.osm.pbf "europe-latest.osm.pbf"<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify;text-justify:inter-ideograph'><span lang=EN-GB>ogr2ogr --config OSM_CONFIG_FILE /home/frank/gdal/osmconf.ini -f SQLite -dsco SPATIALITE=YES -progress -gt 65536 -t_srs "EPSG:31466" /tmp/saarland.sqlite /tmp/saarland.osm.pbf<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify;text-justify:inter-ideograph'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='text-align:justify;text-justify:inter-ideograph'><span lang=EN-GB>Please note the “–config” switch for a custom osmconf.ini. With that you can copy the config to a custom location and have several configs for many use cases.<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify;text-justify:inter-ideograph'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='text-align:justify;text-justify:inter-ideograph'><span lang=EN-GB>HTH<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify;text-justify:inter-ideograph'><span lang=EN-GB>Frank<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dipl. Geogr. Frank Broniewski<br>Waldhölzbacher Str. 51<br>66679 Losheim am See<br>06872 5090684<br>www.frankbroniewski.com</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>Von: </b><a href="mailto:nik@nikosalexandris.net">Nikos Alexandris</a><br><b>Gesendet: </b>Dienstag, 7. November 2017 16:15<br><b>An: </b><a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br><b>Betreff: </b>[gdal-dev] Extracting keys & values from OSM Planet</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dear OSM experts,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>a reproducible workflow that extracts specific tags from OSM's Planet</p><p class=MsoNormal>data set, includes:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1. downloading OSM Planet in form of a pbf file</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>2. convert pbf to o5m using `osmconvert`</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>3 extract areas of interest in separate `aoi_*.o5m` files, based on boundaries in form of .poly</p><p class=MsoNormal>files, using `osmconvert`</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>4. filtering for specific tags (i.e. highways), parallel tasks in 80 cores</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>```bash</p><p class=MsoNormal># custom function for 'highway' tags</p><p class=MsoNormal>function osmfilterhighway { osmfilter $1 --drop-version --keep="highway=track =footway =bridleway =path" > $(basename $1 .o5m)_highway.osm; }</p><p class=MsoNormal>export -f osmfilterhighway</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal># filter</p><p class=MsoNormal>find . -type f -name \*aoi*.o5m |parallel -j80 osmfilterhighway {}</p><p class=MsoNormal>```</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1. Is it any better using GDAL's `osmconf.ini` "method" [0],</p><p class=MsoNormal>over `osmconvert` and `osmfilter`, in terms of reliability/speed etc.?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>2. Is OGR handling well the conversion from .osm to ESRI Shapefiles?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>3. What is the way to split "other_tags" in multiple new fields *when*</p><p class=MsoNormal>knowing exactly which tags are contained and should be obtained?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thank you for any help,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Nikos</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>[0] https://svn.osgeo.org/gdal/trunk/gdal/data/osmconf.ini</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>