[n4r9]

Thanks for the article Dhanraj. I was wondering if you could expand on this part:

> Transforming this data into a usable format, such as that required for routing applications, necessitates expensive data pipelines.

What do you mean by "usable" here? I've worked with OSM data in .osm and .pbf formats for routing applications; there are a few things to look out for (e.g. badly formatted tags), and the ways/nodes graph models has a different structure to many proprietary formats, but generally speaking it's a one-off dev job to get some code up and running which directly imports data in those formats. Are you thinking more about importing the data into a postgres DB or something?

[dhanrajm]

You are correct about ingesting the osm data directly to something like Valhalla. What had in my mind when I mentioned "usable" is the data after that will be the output of some sort of quality control process. As you said, osm data will have quality control issues (being a crowd sourced) and organisations will want quality checked before the data is fed to their internal systems including inserting to database or to a routing engine.

[n4r9]

Cheers for the reply. By "quality control process" do you mean manually checking bridge height restrictions, recent road closures etc..., or do you mean something more automated such as filtering out badly formatted data?

[dhanrajm]

its mix of both. I don't think full automation is possible at the moment.