Talk:MoNav

From OpenStreetMap Wiki
Jump to: navigation, search

No longer works? Using NFS ?

I'd been trying to get MoNav working so as to utilise it in finding optimal routes between Ingress waypoints. I started by trying to preprocess the latest .osm.pbf file for Hampshire (England). This ran for a long time, initially filling my /home/users (not that much space on an SSD). So I started again on a partition with ~1.5TB free, and after it grew over 500MB I stopped it. Then I tried using osmium to define a bounding box around Winchester. But monav-preprocessor would just stop with "[15:57:47][2] Failed to preprocess routing module ".

So, I tried again with a Winchester only .osm map, converted to .osm.pbf, from www.openstreetmap.org/export#map=13/51.0558/-1.3099 - same error.

So, I tried finding a small .osm.pbf, and ended up using the Andorra one. The same error.

Then I tried grabbing the monav source and compiling (I had been using the monav Debian packages from Jessie). I had to fix the code up a little (patch available here: miggy.org/code/misc/monav-compile-on-Debian-Jessie.diff ). But still the same error on the Andorra file.

So, has something changed about PBF files that means the code not having been updated since April 2011 causes it to no longer work ?

Edit: No, it turns out that it doesn't play well with files on NFS. Due to how NFS on linux works you might get some temporary .nfsXXXXXXXXXXX files. These can prevent removal of the directory they're in. What does preprocessor/pluginmanager.cpp deleteDictionary() attempt to do? Remove all the files in a directory, and then the directory itself.

Edit2: The issue is in utils/directorypacker.cpp, this patch fixes it:

diff --git a/utils/directorypacker.cpp b/utils/directorypacker.cpp
index 3a3e58f..208d2ea 100644
--- a/utils/directorypacker.cpp
+++ b/utils/directorypacker.cpp
@@ -236,13 +236,16 @@ struct DirectoryPacker::PrivateImplementation {
 
                        initOutput();
 
-                       if ( !encode() )
+                       if ( !encode() ) {
+                               inputFile.close();
                                return false;
+                       }
                        // finish block -> only one file per block
                        if ( outputBuffer.buffer().size() != 0 ) {
                                if ( !storeOutputBlock( false ) )
                                        return false;
                        }
+                       inputFile.close();
 
                        qDebug() << "Compressed file:" << ( int ) ( 100.0 * ( outputFile.size() - lastSize ) / info.size() ) << "%";
                }

Athanasius (talk) 21:13, 3 September 2016 (UTC)

Turn Restrictions ?

Does MoNav already support turn restrictions? --Stephan75 09:57, 4 September 2010 (BST)

Not yet. The next release will most likely feature route descriptions, i.e., street names, less demanding preprocessing and better import of OSM data. The release after that will most likely feature turn restrictions and penalties. --ChristianVetter 13:33, 9 September 2010 (BST)

Problem in the Compilation section

The 'make distclean' removes also the build binary. Therefore the described procedure does not work. --Moren 09:25, 27 March 2011 (BST)

Map request for Lower Saxony

It seems that the reprocessor to convert PBF data in Monav format is NOT INCLUDED in the 0.3 setup.exe for Windows.

Besides this: is the preprocessor usable on a 32 bit Windows or Linux system, or definitevly 64bit required?

So when I cannot process my desired area to Monav map data, can you offer the German area Lower Saxony (Niedersachen) to the downloadable maps at http://monav.openstreetmap.de ? Thanx in advance! --Stephan75 12:09, 6 May 2011 (BST)

No, the preprocessor is not included for the Windows builds. It should work fine, though, but is is a huge amount of work to compile all the dependencies correctly. Since non of the authors use Windows on a regular basis no build is offered for the preprocessor. However, if somebody steps forward and wants to maintain a build, we'd gladly put it on the download page. 64 Bit is not required, it is recommended for larger areas ( >= Germany ), though. Regarding a map pack of Niedersachsen, I will contact Christoph Eckert about it, he maintains the map packages. --ChristianVetter 16:36, 12 May 2011 (BST)

"Press reload" :) --SlowRider 19:17, 12 May 2011 (BST) ... Many thanks for that! Works quite well!!! --Stephan75 10:22, 14 May 2011 (BST)

Map compilation

I tried to compile myself a MAP and followed the same example (just for test, before taking larger data) from the page for Saarland. It's not as a whole Germany, but the disk space usage reached 49GB during the processing of routing_bike/routing_bike.mmm. I decided to stop at that point. According to main page of monav the disk usage for whole Germany should be about 8GB? --MafiaInc 13:31, 13 Mar 2012 (EET)