[OSRM-talk] osrm-extract coredump on unusual restriction relation

[Frederik Ramm]

Hi,

someone using the Geofabrik download server complained that the 
Australia+Oceania data was "corrupt" because their osrm-extract core 
dumped on the data. I tracked the problem down to this relation:

  <relation id="18608914" visible="true" version="2" 
changeset="161728680" timestamp="2025-01-24T21:21:46Z" user="green_leek" 
uid="3559445">
   <member type="way" ref="1353623290" role="from"/>
   <member type="way" ref="1353309251" role="via"/>
   <member type="node" ref="5735689525" role="via"/>
   <member type="way" ref="227894513" role="to"/>
   <tag k="direction" v="straight"/>
   <tag k="manoeuvre" v="continue"/>
   <tag k="type" v="manoeuvre"/>
  </relation>

- the fact that it contains a way and a node in a "via" role seems to 
break OSRM. Here's the complete XML to reproduce (I was running 
osrm-backend commit 203314b1aa5a4cbbd32b8bd47a5c68399bd9d04e as of 03 
Aug 2024):

<?xml version="1.0" encoding="UTF-8"?>
<osm version="0.6" generator="openstreetmap-cgimap 2.0.1 (3448771 
spike-06.openstreetmap.org)" copyright="OpenStreetMap and contributors" 
attribution="http://www.openstreetmap.org/copyright" 
license="http://opendatacommons.org/licenses/odbl/1-0/">
  <node id="1868843199" visible="true" version="4" changeset="161625085" 
timestamp="2025-01-22T06:51:33Z" user="green_leek" uid="3559445" 
lat="-33.9342081" lon="151.0260159"/>
  <node id="2365255245" visible="true" version="8" changeset="161627988" 
timestamp="2025-01-22T08:40:24Z" user="green_leek" uid="3559445" 
lat="-33.9337372" lon="151.0268777" />
  <node id="5735689525" visible="true" version="6" changeset="161627988" 
timestamp="2025-01-22T08:40:24Z" user="green_leek" uid="3559445" 
lat="-33.9337936" lon="151.0267612"/>
  <node id="12522304017" visible="true" version="3" 
changeset="161627988" timestamp="2025-01-22T08:40:24Z" user="green_leek" 
uid="3559445" lat="-33.9338966" lon="151.0265486"/>
  <node id="12522304018" visible="true" version="3" 
changeset="161666213" timestamp="2025-01-23T09:29:29Z" user="green_leek" 
uid="3559445" lat="-33.9339668" lon="151.0264139"/>
  <way id="227894513" visible="true" version="14" changeset="161625085" 
timestamp="2025-01-22T06:51:33Z" user="green_leek" uid="3559445">
   <nd ref="5735689525"/>
   <nd ref="2365255245"/>
   <tag k="highway" v="trunk"/>
  </way>
  <way id="1353309251" visible="true" version="5" changeset="161728316" 
timestamp="2025-01-24T21:05:50Z" user="green_leek" uid="3559445">
   <nd ref="12522304017"/>
   <nd ref="5735689525"/>
   <tag k="highway" v="trunk"/>
  </way>
  <way id="1353623290" visible="true" version="4" changeset="161728316" 
timestamp="2025-01-24T21:05:50Z" user="green_leek" uid="3559445">
   <nd ref="1868843199"/>
   <nd ref="12522304018"/>
   <nd ref="12522304017"/>
   <tag k="highway" v="trunk"/>
  </way>
  <relation id="18608914" visible="true" version="2" 
changeset="161728680" timestamp="2025-01-24T21:21:46Z" user="green_leek" 
uid="3559445">
   <member type="way" ref="1353623290" role="from"/>
   <member type="way" ref="1353309251" role="via"/>
   <member type="node" ref="5735689525" role="via"/>
   <member type="way" ref="227894513" role="to"/>
   <tag k="direction" v="straight"/>
   <tag k="manoeuvre" v="continue"/>
   <tag k="type" v="manoeuvre"/>
  </relation>
</osm>

Just in case someone runs into the same issue. Dropping the node from 
the relation fixes it, and I commented on the OSM changeset that created 
this relation 14 days ago, but didn't want to remove the node "to fix my 
routing engine" ;)

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"