Hi,

Thank you both for your reply. It help me a lot.

@Mohammed : I am very interested about all details information you can provide.

@Patrick : Since I work for the National Mapping Agency of France, I have no problems with commercial data sources. We have a huge database full of geodata in all kind. Unfortunately, this data are not made for navigation, so we studding the possibility to adapt these data to a routing machine. OSRM can be the solution.

Thanks again, I'll let you know the results of the possibility to doing that if you're interested.

Regards,

Romain Wieser
_______________________________________________________________
Analyste |Pôle technique du Géoportail - Division Services (IDES)
*Direction des Services et du Système d'Information (D2SI)
*
T + 33(0)1 43 98 62 52 ●Poste 6252
73, AVENUE DE PARIS, 94165 Saint-Mandé cedex
ign.fr - geoportail.gouv.fr

On 21/05/2015 19:02, Patrick Niklaus wrote:
Hey Romain,

Mohammed already outlined the two options you have. In general I would
suggest using the second options, since producing correct `.osrm.*`
files is pretty complex and error prone. Also we don't keep that
format stable as the interplay between `osrm-extract` and
`osrm-prepare` often changes if you add new features.

You have a much better chance of translating your data to something
that looks like the OSM data model. A few things to keep in mind:

- Some importers seem to screw up the connectivity of street segments
- You need to figure out a good mapping from attributes of your source
material to OSM tags if you want to use the profiles provided by OSRM
- If your data is rather big, consider generating an OSM file in PBF
form [1]  (the XML format just does not scale for
continental/planet-size data)

I think cycle.travel runs on data from Ordnance Survy. So it is
absolutely doable, but I don't think you will find any importers
(targeting OSRM) for commercial data sources as OpenSource. (most
providers require you to sign a NDA before you are allowed to even
look at the documentation...).

Best,
Patrick

[1] http://wiki.openstreetmap.org/wiki/PBF_Format

On Thu, May 21, 2015 at 5:47 PM, Mohammed Ayoub NEGGAZ <[email protected]> wrote:
Hello Wieser,

The extractor used the osmium library which can only handle osm files.
Therefore, you need to either :

1. Create your own parser that should generates 4 files (.osrm, .osrm.nodes,
.osrm.names, .osrm.timestamp*) from the input document you got (you have the
option to not use a profile file if your datatype contain weights or speed
limits of each road segment aswell as restrictions).

2. Convert your datatype to OSM 0.6 (XML/PBF or other), I think there are
too many tools that can do this, ArcGIS can, I guess, import export from the
most commonly used geographical data.

* I can send you details information about the structure of these files as
well as datatypes  and methods to write/read them.

I hope this answer help you.

Good luck.
Best regards,

2015-05-21 16:36 GMT+02:00 Romain Wieser <[email protected]>:
Hello OSRM community,

For test purpose, I try to extract road network from an other source that
OSM. Anybody actually use a different source and be disposed to share the
experience ?

Furthermore, I wonder if there is more documentation about the extractor
tool as well as the lua scripting for profiles.

Thank you in advance,

Romain Wieser
_______________________________________________________________
Analyste | Pôle technique du Géoportail - Division Services (IDES)
Direction des Services et du Système d'Information (D2SI)
T + 33(0)1 43 98 62 52 ● Poste 6252
73, AVENUE DE PARIS, 94165 Saint-Mandé cedex
ign.fr - geoportail.gouv.fr

_______________________________________________
OSRM-talk mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/osrm-talk


_______________________________________________
OSRM-talk mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/osrm-talk

_______________________________________________
OSRM-talk mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/osrm-talk

_______________________________________________
OSRM-talk mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/osrm-talk

Reply via email to