As explained in #468 BRouter currently has two parsers
"XML" Parser (doesn't really use a XML library and rejects valid XML) which should be only used for testing but is integrated into the build
PbfParser which is used in production but requires manual download of osmosis and building
We should just use PbfParser and remove the "XML" parser. This adds a dependency on osmosis/protobuf, but the JAR file size only slightly increased to 2.2 MB. I think this slight increase is worth avoiding the building hassle.
PbfParser has an optimization which polls its input file to allow reading a pbf file while update from osmupdate is still in progress. For small files (e.g. when testing) this causes a delay of at least two minutes, therefore it's now configurable using avoidMapPolling (e.g. java -davoidMapPolling=true).
As explained in #468 BRouter currently has two parsers
We should just use PbfParser and remove the "XML" parser. This adds a dependency on osmosis/protobuf, but the JAR file size only slightly increased to 2.2 MB. I think this slight increase is worth avoiding the building hassle.
PbfParser has an optimization which polls its input file to allow reading a pbf file while update from osmupdate is still in progress. For small files (e.g. when testing) this causes a delay of at least two minutes, therefore it's now configurable using
avoidMapPolling
(e.g.java -davoidMapPolling=true
).Fixes #468