Messages

Tant que les dessins des jalons ne seront pas dans le sens du parcours, (comme j'ai modifié sur mon image) je ne peux pas les utilisés.

Ce n'est pourtant pas bien compliqué de comprendre que la flèche dans le symbole du jalon n'indique pas la direction sur la carte qui est en dessous, mais
- flèche gauche : tourner à gauche (même si on va vers le sud, et que dans ce cas c'est bien à gauche sur le terrain, mais à droite sur le dessin de la carte qu'on a sous es yeux)
- flèche droite : tourner à droite (même si on a fait tourner le dessin de la carte sur l'écran pour la mettre en biais)
- flèche tout droit (et donc "vers le haut" dans son dessin) : aller tout droit...

Si tu veux vraiment que ça corresponde à ce que la carte est en train d'afficher, ce n'est pas l'icône du jalon que l'on fait tourner, mais la carte : Règlages Carte / Orientation de la carte / Orienté par la boussole ou Direction en haut (GPS)

Before re-installing, you should first
- stop the application : Go to Apps, select OruxMaps, then "Force stop"
Then restart it. Should be enough.

But if the pb persists :
- Force again stop of Oruxmaps
- Completely stop then restart your smartphone

Only in the case the problem persists after these two tries, maybe you can imagine to re-install OM

Hi @YvanCB and @Juanjo,

did you see that a new version of MOBAC (2.31) has been published today ?
Among some other modifs, there is the update of MBTiles atlases to have the "limits" of the map set to the higest zoom, ie. to what is covered by ALL zooms present in the map.

Don't hesitate also to support my request on MOBAC's forum....

If I understand, we have to wait for a new Mobac's release?

Yes, it would be the best.
If you are in hurry, you can also generate your own version. It's clearly explained here : https://sourceforge.net/p/mobac/forum/general/thread/3a86f69952/
Personnally, I did it (it's easy), and resulting version works as expected.

BTW, it makes little sense to skip zoom levels as you do.

I would even say more : With MBTiles format, you MUSTN'T skip zoom levels. Otherwise, when you zoom in OruxMaps at a level that is not present in the Atlas, OM displays what is in the atlas....ie. an empty map !
It's actually the ONLY known drawback of MBTiles format vs OruxMaps Sqlite format (in OM Sqlte, when a level is missing, OruxMaps displays a numeric zoom of the level below, rather than an empty level)

And even with OruxMaps Sqlite format, it would make no sense to skip zoom levels. In your example, if you add the missing levels, 12, 14 and 16, your atlas will be only 25% larger than without them

Now, on the root of your initial question, Juanjo's answer is the right one.

In OruxMaps format, the bounds of the map are defined level per level (in the xml file), and OM consider the "smallest" bounds (the one covered by all levels) as the map bounds.
While in MBTiles format, they are defined ony once (in the database) for all levels, and it is the "largest" bounds (the one covered by at least one level) that are memorized as the map bounds.
To reach your request, then, two solutions :
- do as described by Juanjo (because in this case, all the levels have the same bounds)
- or ask a modification of MOBAC (in MOBAC's forum) to put in MBTile databse the bounds of the highest level rather than those of the lowest one.
But clearly, there is nothing to modify in OruxMaps itself

I just asked for the modification in MOBAC. (see here : https://sourceforge.net/p/mobac/forum/general/thread/3a86f69952/ )
We'll see how it will end...

[MAJOR]

Hi,

according to me, YES, there are several MAJOR advantages to use "MBTiles SQLite" format instead of "Oruxmaps SQLite".

The main reason is that tiles, in "Oruxmaps SQLite" are 512x512 pixels, while, natively, most of servers serve tiles 256x256 pixels. As a result, with Oruxmaps format, Mobac is obliged to combine several tiles to produce one, with two major drawbacks :
1) It takes a lot of time.
2) Transparency of tiles (in case of origin tiles are PNG with transparency) is LOST

The first point is not really "sensible" if MOBAC has to download tiles from server, since the time lost in recreating  tiles is almost negligeable vs. time spend in network download. But in case tiles are already present in local tilestore, atlas generation, that is in this case free of network time, may be 10 times or more longer with Oruxmaps format than with MBTiles sqlite format.

The second point is of even higher importance : When reprocessing tiles to generate 512x512 px tiles, native transparency (if it exist) is lost. This remove capability to create "composite" maps directly in Oruxmaps, with an opaque background superposed with a transparent atlas (like tracks from WMarkTrails or Strava, or etc...).

On the other hand, there is one "drawback" (that is not really one) to use MBTiles format in Oruxmaps : In case you have created an atlas in which not all conscutive levels are present (eg. an atlas with only levels 10, 12, 14 and 16), when you zoom in Oruxmaps, missing levels are "displayed" (and screen remains empty for these levels, since data is missing) while with OruxMaps format, missing levels are "skipped" (replacing them by digital zooming of lower level).
Nevertheless, this is not really a drawback, since IMHO there is no interest to let some intermediate levels missing. An atlas with level 10, 12, 14 and 16 is only 20% smaller than the same atlas, with all intermediate levels 10, 11, 12, 13, 14, 15 and 16

Personnally, a long time ago, I used to generate "OruxMaps sqlite" format atlases. But since I discovered the "MBTiles sqlite" format, I now use ONLY this one.

No one knows ?

Yes, of course, since one is set as default....
Actually, I have several ones, one associated to each OpenAndroMaps mapsforge map.

Why this question ?

OK, @Agus, you show me it's not greyed in your case, but that doesn't explain why greyed in MY case

And @Matt, no, the default POI option is set in my case.

And I have the issue with BOTH free version (7.4.26) and GP version.... as you can see in screen copies.

In the Settings / Maps / Mapsforge settings, there is an option named "Search POI, tap gesture" that is always (in my case, at least...) greyed out, and the cannot be selected.

I'm not sure to 100% understand how it should work if selected.... but I cannot test it... since I cannot select it 

So my question is : why is this option greyed out. Is it linked to another option that would be incompatible with it ?

Thanks for any valuable answer !

Hi Lenz,

it's tricky (normal for a trick...  ) but, I agree, it works.

On the other hand, there is a very more simple way to create an offline map based on OSM Mapnik : create it using MOBAC (https://mobac.sourceforge.io/)

Hola!! Prueba este truco,es muy sencillo.
Haz un mapa compuesto de OSM mapnik con cualquier otro mapa.
Usa 0SM mapnik como mapa base de zoom 5 a 20 y el otro mapa como capa de zoom 0 a 5 .

Después puedes usar el creador de mapas para descargar este compuesto, evidentemente haz de elegir la descarga de los zoom de 5 a 20 que son los que ocupa el mapa de OSM mapnik.

𝕥𝕣𝕠ℕ𝕡𝕠

Hi @Tronpo

your "trick" doesn't work.
Any composite map including OSM Mapnik layer generate the same "error" message when trying to download it with map creator to generate an offline map.

The latest free version is not 7.2.6, but 7.4.26

[Only for the OSM Mapnik map]

What is surprising with OSM Mapnik maps is that there is very likely some "hard-coding" in OM to prevent offline map creation from this source.

Indeed, this is supposed to be managed thanks to <downloadable> tag in onlinemapsources.xml.
For any other map source, if <downloadable> is set to 0, offline map creation is impossible (and the message is the one indicated by @owmapper), but if it is set to 1, offline map creation is possible.

Only for the OSM Mapnik map, it is always impossible, whatever the value of <downloadable>