Missing data in extract.0sv

[dmaj]

Hey team!

I was using your awesome geocoding engine when I noticed something interesting.
Let me tell you more about it.

---

Here's what I did 😇

When I build the polylines with pelias, the file is smaller than the file generated by valhalla.
The smaller size results from missing streets in the result file. Unfortunately the missing data leads to faulty search results in Pelias.
As an example I have a street, which exists only once worldwide: "Lohmühlwiesen".
The problem occurs independently of the choice of the pbf file. Very fast it can be reproduced with this PBF file: https://download.bbbike.org/osm/bbbike/Karlsruhe/Karlsruhe.osm.pbf

If I generate the polylines with valhalla, then the street in question is in the result. If I use the generator of Pelias, then the roads are missing.

Filesize:
valhalla: 2769818 my_extract.polyline
pelias: 1541260 extract.0sv

Am I doing something wrong, or is that a mistake?

I also noticed that the Wiki is no longer available. So the link to the manual how to generate polylines with valhalla is dead.
https://github.com/pelias/polylines/wiki/Generating-polylines-from-Valhalla

[arnesetzer]

Just in case anybody digs this issue: At least the docker image uses the polyline extractor from missinglink (see https://github.com/pelias/polylines/blob/master/Dockerfile#L13) which currently only supports hard coded highway types and not the type mentioned here ("living_street") (https://github.com/missinglink/pbf/blob/04d4fff63f5e72e469a55a4769fe20f74589748d/tags/tags.go#L68).

In contrast valhalla extracts all highway types and also adds the relation name if availible.

[trafficonese]

I had the same problem, all ways with highway=unclassified were not included.
I had to adjust that with:
osmfilter roads.osm --modify-tags="highway=unclassified to =tertiary" -o=roads_named.osm

This should definitly be mentioned somewhere.