Offline JuraMap (OsmAnd & Locus Map)
Offline map files: OsmAnd ¦ Locus Map
Only Google Play apps are considered.
In using JuraMap with the OsmAnd and Locus Map clients, please note that some of the north-facing slopes of the Jura Mountains do not have GPS coverage.
The JuraMap aims to recreate the network of roads tracks and paths as it existed before 1900 and before heavy machinery started to be used to create the modern road network.
Except for the relatively few pre-1880 tracks, all roads, tracks and paths are marked as paths. In some cases, the original paths probably followed the modern road alignment. So in these cases the modern road corresponds to the historical path. But in most cases, sections of the modern road network are ignored completely.
Most of the paths have been checked to be accurate to about the 15-metre GPS positioning accuracy. If you stray from a track it is recommended that you retrace your steps, especially in the many rocky, wooded and forested areas that cover the Jura Mountains.
Typically, for a smartphone, maps are downloaded beforehand and stored on the phone. Subsequent use does not require an Internet connection, which is useful if a map is used for say treking in a region where there is no internet coverage - as is the case for parts of the Jura Mountains.
OsmAnd is a GPS navigation and map application that runs on many Android and iOS smartphones and tablets.
JuraMap maps are made available in OsmAnd's .obf format (see below). A file is loaded and stored in a location that OsmAnd can access as a "local" file. Local files are selected by using the "Download maps" tab in the OsmAnd menu at the bottom left of the home screen.
For an Android smartphone, the simplest procedure is to create a folder in "Internal storage" using a file manager such as Files by Google that is often available by default. Using the file manager, the downloaded .obf file can be moved to the folder. The folder should be in an OsmAnd "Data storage folder" that is assigned by selecting "Data storage folder" in "Menu -> Settings -> OsmAnd settings ->Data storage folder -> Manually specified" where the path to the folder is entered. The path will typically be something like "/storage/emulated/0/mine" where "mine " is the name of the folder one created using the file manager.
In fact the simplest way to import the .obf file into OsmAnd is to click on the file once it is copied into the "mine" folder.
To avoid preloaded map tiles interfering with the JuraMap map, in "Menu -> Download maps -> Local", simply deactivate any "Standard maps" and "Clear all tiles" for "Online and cached tile maps".
A .obf file for the main JuraMap historical map is available here.
Using Locus Map
Locus Map is a GPS navigation and map application that runs on most Android smartphones and tablets.
JuraMap maps are made available in Locus Map's .map format (see below). Using say Files by Google, a downloaded .map file should be moved to Internal Storage -> Android -> Media -> menion.android.locus -> maps.
The map is then available in the Map manager -> Offline tab under "MENION.ANDROID - MAPS". Clicking on "JuraMap" opens the map in Locus Map.
If one has cleared storage and cache (which deletes the "maps" folder) it is probably best to restart the app and use the Locus Map "Map manager" to load the .map file from Download.
A .map file for the main JuraMap historical map is available here.
Using other mobile apps
It seems that one can make offline OSM maps for Navit (see guide). One can probably set up the Navit web client to download maps from a self-hosted OpenStreetMap website to a mobile phone. But the app is very focussed on routing so doing this is not worth the effort for the JuraMap hiking maps.
It seems that offline OSM maps are not easily created and loaded into a smartphone for Organic Maps.
For the technically minded, OsmAndMapCreator is used to convert the .xml file (called "osm.xml") created using the OpenStreetMap Rails port Postgresql database, called "osmdatabase", and Osmosis. As discussed elsewhere, the Osmosis command is:
- /home/usr/osm/bin/osmosis --read-apidb host="localhost:5432" database="osmdatabase" user="user" password="password" validateSchemaVersion="no" --write-xml file="/home/user/osm.xml"
For Windows10, if Java JDK is not installed, one can download and install the .exe installation file (“x64 Installer”) here. OsmAndMapCreator can be downloaded (description) and is then extracted to any folder. Using a terminal (search Windows using "cmd"), move to the OsmAndMapCreator folder. OsmAndMapCreator can be executed by submitting:
In the OsmAndMapCreator graphic interface, deselect all "Build xxx index" except "Build map index" and under the "File" tab open the option "Build .obf from the .xml file ..." Use this option to select the "osm.xml" file. The "osm.obf" file takes a minute or so to build. Further details are available on the OpenStreetMap wiki.
Alternatively, submit in terminal:
- OsmAndMapCreator/utilitiesx.sh generate-map osm.xml
to generate a map.
When the OsmAndMapCreator GUI opens, under Windows -> Settings one can specify the path to a rendering_types.xml file and a rendering style file.
A detailed description of how to use OsmAndMapCreator to create offline maps is also available.
The Mapsforge-Creator Map-Writer plugin for Osmosis is used to produce .map files from the OpenStreetMap "osm.xml" file. It is reasonably well documented. In brief, mapsforge-map-writer is downloaded from the Sonatype repository. Currently, clicking mapsforge-map-writer -> master-SNAPSHOT -> mapsforge-map-writer-master-20211104.091832-420-jar-with-dependencies.jar gives the necessary Java file that should be copied to the "osmosis ->lib -> default" folder of an osmosis installation. The latest mapwriter appears to be mapsforge-map-writer-master-20230426.074942-502-jar-with-dependencies.jar
For Windows10 running the latest version (0.48.3) of Osmosis, one can simply copy the "osm.xml" file to the "osmosis\bin" folder and run in a "cmd" terminal:
- cd c:\osmosis\bin
- osmosis --rx file=osm.xml --mapfile-writer file=osm.map threads=8 type=hd map-start-position=46.45,6.2 bbox=46.41,6.05,46.6,6.3
For us, the bbox bounds value is absolutely essential. Without it the .map file is not produced. There has been some discussion over the years of the Java enviroment variables. A straightforward version of the osmosis.bat file that accompanies the osmosis executable is:
set JAVACMD="C:\Program Files\Java\jdk-188.8.131.52\bin\java"
cd /D %MYAPP_HOME%
cd /D %SAVEDIR%
SET EXEC=%JAVACMD% %JAVACMD_OPTIONS% -cp "%PLEXUS_CP%" -Dapp.home="%MYAPP_HOME%" -Dclassworlds.conf="%MYAPP_HOME%\config\plexus.conf" %MAINCLASS% %OSMOSIS_OPTIONS% %*
27 April 2023