<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>As mentioned in comments about #269 I have been working on implementing a reader for Ordnance Survey ITN roads data.<br><br>This has been based off the code of OSMReader and extracting common interfaces.<br><br>Due to its use of a modified version of the CarFlagEncoder until the recent updates I have been able to use a parsed ITN dataset as the working graph for an unmodified graphhopper web app. I hope to figure out where the incompatibility has arisen with the recent changes in the next few days. Error thrown during web app start up follows.<br><br>INFO: An exception was caught and reported. Message: java.lang.IllegalStateException: Encoding does not match:<br>Graphhopper config: car:com.graphhopper.routing.util.CarFlagEncoder<br>Graph: car|speedFactor=5.0|speedBits=5|turnCosts=false, dir:examples/os-itn-sample-gh/<br>java.lang.IllegalStateException: Couldn't load graph<br><br><br><br>the code is available in engaric/graphhopper if anyone is interested though it is still in an experimental shape at this stage. <br>Currently supported features :-<br><br>1) Import of the basic road network<br>2) Import of road names<br>3) Grade separation. An interesting feature of the ITN dataset is that roads that pass over each other do have the crossing point listed as a node, so additional metadata must be parsed to separate the links.<br><br><br>Work in progress<br>1) Partial categorisation of road types to speed.<br>2) One Way systems<br><br>Work to be done<br>1) Restrictions<br>2) Conditional Restrictions<br>3) Optimisation of the import process<br><br><br>ITN is a copyright data set and not available as Ordnance Survey opendata. However a sample file can be download from <br><br>https://www.ordnancesurvey.co.uk/docs/sample-data/os-mastermap-itn-layer-sample-data.zip#sample-data-download<br><br>The dataset is a Great Britain road coverage appropriate for car navigation.<br><br>In some aspects the model of ITN can be compared to osm data, but in other areas it is modeled very differently. This means the parsing process is already 4 stage rather than the current osm preprocess/write 2 phase parse. Some elements that in osm would be modeled on the way elements (from what I can see so far) are modeled on separate elements in ITN.<br><br><br>Stuart Adam<br> </div></body>
</html>