I would love the ability to read OSM data in pbf rather than xml format http://wiki.openstreetmap.org/wiki/PBF_Format
Released
Reader for OSM data in pbf format
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+7- Participant
This is something we could use big time as OSM is the most important source for us in any time of crisis.
+40- Contributor
@mb_fdfa I do have an inelegant solution using scripted paramters and OSMConvert where there is a published parameter (Filename (Existing) with a configuration of *.pbf;*.osm;*.o5m;*.osm.gz and the OSM reader points to a scripted parameter. Mine is more complicated with filtering and clipping options, but it boils down to
import os.path import subprocess
#get parameters
inOSM = FME_MacroValues['OSM']
toolsDir = FME_MacroValues['OSMTools']
#get osm basename
(filepath, ext) = os.path.splitext(inOSM)
#create temp output file
outOSM = filepath + '-temp.osm'
#Create and run OSMconvert command line
runP = toolsDir+'/osmconvert ' + inOSM + ' -o=' + outOSM
subprocess.call(runP)
#return temp filename
return outOSM
+22- Safer
File size differences are huge (11GB in pbf, 171GB in XML) this would really save some space/processing if we could get the pbf format.
+22- Safer
@jdh @d2 @mb_fdfa -- I can advise that an Open Street Map PBF Reader has been in FME 2017 betas since build 17037 -- we've had no feedback on it yet and so would definitely welcome some. Thanks for your interest!
+40- Contributor
Are there plans to allow for common osm feature types like those available in the osm reader (highway, waterway, natural, etc), or will it only support data primitives (nodes, ways, relations).
+22- Safer
Thanks for the feedback. To be clear, you'd prefer the features be emitted with feature types more like the OSM reader? We'll look and see what we can do -- it does seem very reasonable.
+40- Contributor
The osm reader has a parameter as to whether to use basic (node/way/relation), broad (highway), specific (highway_primary) or user defined (fmi pipeline file).
The pbf reader uses the gdal osm config .ini, which produces nodes/way/relations. Even something like offering alternate config files with the distribution would be beneficial*, though my preference would be a parameter.
*Most of my users would not be able to create a custom config file.
+22- Safer
No plans at the current time for a PBF writer. Feel free to suggest as an Idea so we can track interest.
+7- Participant
Finally I have FME 2017 on my main Workstation and can try the new reader. Thanks, great it is there!
Although I haven't been able to try any real scenarios yet, I think that the suggestion from @jdh would be a useful enhancement.
+1This has been released as part of FME 2017.0 . Visit http://www.safe.com/downloads to download it and give it a spin.
+13- Safer
Hi
@jdh,
I'm pleased to let you know that the 2018.0 version of the now reader allows you to choose from the 26 broad categories and its sub categories (via OSM Map Features), which are represented as feature types similar to the OSM XML reader.
Let us know how it looks!
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.