rovaniemi / osm-graph-parser Goto Github PK

osm-graph-parser outputs some json graph representation.

Is this compatible with any of the many more-or-less established existing standards for encoding graphs in json? If not, would it make sense to use such a more-widely use format?

Philipp

P.S.: Probably the most widely known is http://jsongraphformat.info/, which also has links to 4 other formats ("Similar Projects") on their start page. A 6th would be the Netflix one: http://netflix.github.io/falcor/documentation/jsongraph.html

From the documentation and source code, osm-graph-parser currently just imports all ways tagged as some type of highway.
I suggest to make osm-graph-parser more flexible, by allowing to specifying inclusion and exclusion lists of keys and key-value pairs as command line arguments

Use cases might be:

--include-ways highway for the current behaviour.
--include-ways highway --exclude-ways access=no,access=private for all highways accessible to the public
--include-ways railway --exclude-ways railway=abandoned to get all railway tracks

Philipp

From the documentation, osm-graph-parser currently just reads all .osm files in the subdirectory map.

How about instead having the names of the .osm files as command line parameters?
This would allow more flexible use, and give osm-graph-parser a more familiar (since most tools reading some files and processing them work that way) interface for specifiying input files.

Philipp

e.g. --output graph.json