ModRana offline routing guide - Revision history

sim6 at 22:23, 9 May 2014

2014-05-09T22:23:03Z

← Older revision		Revision as of 22:23, 9 May 2014
Line 119:		Line 119:

	== Planned features ==		== Planned features ==
-	* modRana project hosted repository with up-to-date data packs	+	* <del>modRana project hosted repository with up-to-date data packs</del> (done: [http://data.modrana.org data.modrana.org])
	* built-in map pack downloader & updater		* built-in map pack downloader & updater

sim6 at 22:21, 9 May 2014

2014-05-09T22:21:18Z

← Older revision		Revision as of 22:21, 9 May 2014
Line 7:		Line 7:
	== Enable offline routing in 6 easy steps ==		== Enable offline routing in 6 easy steps ==
	=== download routing data ===		=== download routing data ===
		+
		+	==== from monav repository ====
		+
	Compatible routing data packs are available from [http://monav.openstreetmap.de monav.openstreetmap.de]. Just download a relevant pack for your area. :)		Compatible routing data packs are available from [http://monav.openstreetmap.de monav.openstreetmap.de]. Just download a relevant pack for your area. :)
	It can be also done directly on the N900 like in this example:		It can be also done directly on the N900 like in this example:
Line 13:		Line 16:
	wget http://monav.openstreetmap.de/mapsets/Czech_Republic.zip		wget http://monav.openstreetmap.de/mapsets/Czech_Republic.zip

		+
		+	==== from modrana repository ====
		+
		+	[http://data.modrana.org data.modrana.org]
		+
		+	example:
		+
		+	cd MyDocs
		+	wget http://data.modrana.org/monav/europe/czech-republic/czech-republic_car.tar.gz

	=== unpack it to the Monav data folder ===		=== unpack it to the Monav data folder ===
Line 31:		Line 43:
	unzip Czech_Republic.zip -d .maps/monav_data/		unzip Czech_Republic.zip -d .maps/monav_data/

		+	or
		+
		+	tar xvzpf czech-republic_car.tar.gz -C .maps/monav_data

	You should get paths similar to these:		You should get paths similar to these:

int_ua: /* Planed features */

2013-10-30T20:34:51Z

Planed features

← Older revision		Revision as of 20:34, 30 October 2013
Line 103:		Line 103:
	The Monav GUI can be used for offline address search - I'll have to investigate if the same functionality can be used over the [http://code.google.com/r/thomasmiedema-python/source/browse/routingdaemon/routingserver.cpp monav-server] API.		The Monav GUI can be used for offline address search - I'll have to investigate if the same functionality can be used over the [http://code.google.com/r/thomasmiedema-python/source/browse/routingdaemon/routingserver.cpp monav-server] API.

-	== ~~Planed~~ features ==	+	== Planned features ==
	* modRana project hosted repository with up-to-date data packs		* modRana project hosted repository with up-to-date data packs
	* built-in map pack downloader & updater		* built-in map pack downloader & updater

93.96.159.117: /* Known issues */

2013-07-15T00:05:56Z

Known issues

← Older revision		Revision as of 00:05, 15 July 2013
Line 97:		Line 97:
	<del>''Monav actually doesn't return turns at all'' - just points for the route & name + type for the route edges. So an algorithm that analyses all edge junctions on the route and decides what is turn and what is not (based on sharp turns, edges changing type or name, etc.). Currently every route type change is just used to trigger turn.</del>		<del>''Monav actually doesn't return turns at all'' - just points for the route & name + type for the route edges. So an algorithm that analyses all edge junctions on the route and decides what is turn and what is not (based on sharp turns, edges changing type or name, etc.). Currently every route type change is just used to trigger turn.</del>

-	ModRana should no properly detect most turns. If you still see it miss a turn, please report it to the [http://talk.maemo.org/showthread.php?t=58861 modRana discussion thread] or [http://modrana.org/trac#Contactthedeveloper contact address]. :)	+	ModRana should now properly detect most turns. If you still see it miss a turn, please report it to the [http://talk.maemo.org/showthread.php?t=58861 modRana discussion thread] or [http://modrana.org/trac#Contactthedeveloper contact address]. :)

93.96.159.117: /* Generating your own routing data */

2013-07-15T00:03:35Z

Generating your own routing data

← Older revision		Revision as of 00:03, 15 July 2013
Line 56:		Line 56:

	== Generating your own routing data ==		== Generating your own routing data ==
-	If the online Monav data repositories don't cover the ~~are~~ you are interested in or if you just want to have fresh routing data for your ~~are~~ generated every hour from local OSM extracts - no problem! Generating your own Monav routing data packs is quite easy. :)	+	If the online Monav data repositories don't cover the area you are interested in or if you just want to have fresh routing data for your area generated every hour from local OSM extracts - no problem! Generating your own Monav routing data packs is quite easy. :)

	=== The Monav data generator ===		=== The Monav data generator ===
Line 87:		Line 87:

	To set the thread number, just edit the THREADS variable in the ''generate.py'' file. The number of threads should roughly correspond to the number of logical processing cores on your machine.		To set the thread number, just edit the THREADS variable in the ''generate.py'' file. The number of threads should roughly correspond to the number of logical processing cores on your machine.
-

	== Known issues ==		== Known issues ==

martink: /* Known issues */

2012-10-27T15:53:23Z

Known issues

← Older revision		Revision as of 15:53, 27 October 2012
Line 95:		Line 95:
	ModRana now properly handles most turn types and support for more advanced turn types (roundabouts, highway merging, etc.) will be added in the future.		ModRana now properly handles most turn types and support for more advanced turn types (roundabouts, highway merging, etc.) will be added in the future.

-	<del>* some turns are missed</del> '''fixed'''	+	* <del>some turns are missed</del> '''fixed'''
-		+
	<del>''Monav actually doesn't return turns at all'' - just points for the route & name + type for the route edges. So an algorithm that analyses all edge junctions on the route and decides what is turn and what is not (based on sharp turns, edges changing type or name, etc.). Currently every route type change is just used to trigger turn.</del>		<del>''Monav actually doesn't return turns at all'' - just points for the route & name + type for the route edges. So an algorithm that analyses all edge junctions on the route and decides what is turn and what is not (based on sharp turns, edges changing type or name, etc.). Currently every route type change is just used to trigger turn.</del>

martink: /* Known issues */

2012-10-27T15:53:06Z

Known issues

← Older revision		Revision as of 15:53, 27 October 2012
Line 96:		Line 96:

	<del>* some turns are missed</del> '''fixed'''		<del>* some turns are missed</del> '''fixed'''
		+
	<del>''Monav actually doesn't return turns at all'' - just points for the route & name + type for the route edges. So an algorithm that analyses all edge junctions on the route and decides what is turn and what is not (based on sharp turns, edges changing type or name, etc.). Currently every route type change is just used to trigger turn.</del>		<del>''Monav actually doesn't return turns at all'' - just points for the route & name + type for the route edges. So an algorithm that analyses all edge junctions on the route and decides what is turn and what is not (based on sharp turns, edges changing type or name, etc.). Currently every route type change is just used to trigger turn.</del>

martink: /* Known issues */

2012-10-27T15:52:49Z

Known issues

← Older revision		Revision as of 15:52, 27 October 2012
Line 90:		Line 90:

	== Known issues ==		== Known issues ==
-	* <del>directions are very basic</del>	+	* <del>directions are very basic</del> '''fixed'''
	<del>Monav actually doesn't return a turn type, so I'll have to add an algorithm that detects different turn types and assigns corresponding description (Marble also does it like this).</del>		<del>Monav actually doesn't return a turn type, so I'll have to add an algorithm that detects different turn types and assigns corresponding description (Marble also does it like this).</del>

	ModRana now properly handles most turn types and support for more advanced turn types (roundabouts, highway merging, etc.) will be added in the future.		ModRana now properly handles most turn types and support for more advanced turn types (roundabouts, highway merging, etc.) will be added in the future.

-	<del>* some turns are missed</del>	+	<del>* some turns are missed</del> '''fixed'''
	<del>''Monav actually doesn't return turns at all'' - just points for the route & name + type for the route edges. So an algorithm that analyses all edge junctions on the route and decides what is turn and what is not (based on sharp turns, edges changing type or name, etc.). Currently every route type change is just used to trigger turn.</del>		<del>''Monav actually doesn't return turns at all'' - just points for the route & name + type for the route edges. So an algorithm that analyses all edge junctions on the route and decides what is turn and what is not (based on sharp turns, edges changing type or name, etc.). Currently every route type change is just used to trigger turn.</del>
		+
	ModRana should no properly detect most turns. If you still see it miss a turn, please report it to the [http://talk.maemo.org/showthread.php?t=58861 modRana discussion thread] or [http://modrana.org/trac#Contactthedeveloper contact address]. :)		ModRana should no properly detect most turns. If you still see it miss a turn, please report it to the [http://talk.maemo.org/showthread.php?t=58861 modRana discussion thread] or [http://modrana.org/trac#Contactthedeveloper contact address]. :)

martink: /* Known issues */

2012-10-27T15:52:17Z

Known issues

← Older revision		Revision as of 15:52, 27 October 2012
Line 95:		Line 95:
	ModRana now properly handles most turn types and support for more advanced turn types (roundabouts, highway merging, etc.) will be added in the future.		ModRana now properly handles most turn types and support for more advanced turn types (roundabouts, highway merging, etc.) will be added in the future.

-	* some turns are missed	+	<del>* some turns are missed</del>
-	''Monav actually doesn't return turns at all'' - just points for the route & name + type for the route edges. So an algorithm that analyses all edge junctions on the route and decides what is turn and what is not (based on sharp turns, edges changing type or name, etc.). Currently every route type change is just used to trigger turn.	+	<del>''Monav actually doesn't return turns at all'' - just points for the route & name + type for the route edges. So an algorithm that analyses all edge junctions on the route and decides what is turn and what is not (based on sharp turns, edges changing type or name, etc.). Currently every route type change is just used to trigger turn.</del>
		+	ModRana should no properly detect most turns. If you still see it miss a turn, please report it to the [http://talk.maemo.org/showthread.php?t=58861 modRana discussion thread] or [http://modrana.org/trac#Contactthedeveloper contact address]. :)
		+

	* no address2address offline routing		* no address2address offline routing

martink: /* Known issues */

2012-10-27T15:48:57Z

Known issues

← Older revision		Revision as of 15:48, 27 October 2012
Line 90:		Line 90:

	== Known issues ==		== Known issues ==
-	* <del>directions are very basic	+	* <del>directions are very basic</del>
-	Monav actually doesn't return a turn type, so I'll have to add an algorithm that detects different turn types and assigns corresponding description (Marble also does it like this).</del>	+	<del>Monav actually doesn't return a turn type, so I'll have to add an algorithm that detects different turn types and assigns corresponding description (Marble also does it like this).</del>
-	ModRana now properly handles most ~~run~~ types and support for more advanced turn types (roundabouts, highway merging, etc.) will be added in the future.	+
		+	ModRana now properly handles most turn types and support for more advanced turn types (roundabouts, highway merging, etc.) will be added in the future.

	* some turns are missed		* some turns are missed