Bundle osrm-components with node-osrm

[daniel-j-h]

Bundle osrm-components with node-osrm

[danpat]

Another alternative:

http://shapelib.maptools.org/

I've used this, it works. The shapefile format is significantly smaller than a GeoJSON output would be. For our use case, we would only need a very simple wrapper.

[TheMarex]

Yeah we don't bundle it because we don't want to depend on libgdal (of which we require a super outdated version that doesn't even ship with Debian anymore as far as I recall).

One way around this would be to let osrm-components emit geojson and use tippecanoe to convert it to vector tiles we can use.

[springmeyer]

What I can see on the osrm side is components not being supported by the mason build? Is this because of libgdal? @springmeyer any insights here - what's your take on this ticket?

Yes, we could support libgdal in the mason build (there are mason packages for gdal) but @TheMarex and I decided not to. I'm still in support of this because gdal is a large download and would slow down the mason fetch. I also agree that the best route forward is to target geojson in osrm-components to avoid a gdal dep.

[daniel-j-h]

Let's keep the discussion here free of upstream decisions, we already have

• Project-OSRM/osrm-backend#2176
• Project-OSRM/osrm-backend#1738

which outlines pros and cons of going the GeoJSON way.

[daniel-j-h]

Project-OSRM/osrm-backend#3570 just landed upstream unblocking us from bundling osrm-components with node-osrm in the 5.6 release. Let's ship this!