OruxMaps NG

Started by orux, May 14, 2026, 12:59:33 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

kkolesar

Quote from: Tronpo on July 23, 2026, 10:48:15 PM
I'll explain it better with a video

thnx for this...

Tronpo

Quote from: Hauke on July 24, 2026, 04:42:58 PMThanks Tronpo! Glad to hear that MapBox vector maps implementation continues to evolve. I will reach out to the developer privately as you suggest. Also to discuss if it would be an option to shift from the licensed MapBox to the free open source fork MapLibre, which is largly compatible.
What benefits would maplibre bring to the user?

aitorz

Hola!

Tengo una duda, ¿cómo se abre un mapa con transparencias como capa, sin utilizar los mapas compuestos?
Utilizo varios mapas que voy cambiando según la situación, y me gustaría abrir como capa por ejemplo "WT Hiking" sin tener que configurar un mapa compuesto por cada mapa de fondo que utilizo.

Parece que la opción existe en el menú "Opciones capa" -> "Administrar capas", con el botón "Cargar mapa como capa", pero cuando le doy sale el error "No se han encontrado mapas compatibles". ¿Como se usa este botón? ¿qué mapas o cómo tienen que ser los mapas para que sean compatibles con este botón?

Muchas gracias

Hauke

MapLibre is feature-wise similar to MapBox (As far as I understand, it is a fork, i.e. to some extent basically identical), but license-free. So OruxMaps could offer the MapBox-style vector maps features without additional subscription. You would not get the MapBox maps itself without license - I can only voice my perspective here - these premium maps are of no big value to me. Not sure what others think about them. My interest is having the vector map feature unlocked.

That said: I find ~10€/year extremely fair priced, so if OruxMaps stays with that, no big issue.

Tronpo

Quote from: aitorz on July 26, 2026, 11:57:55 AMHola!

Tengo una duda, ¿cómo se abre un mapa con transparencias como capa, sin utilizar los mapas compuestos?
Utilizo varios mapas que voy cambiando según la situación, y me gustaría abrir como capa por ejemplo "WT Hiking" sin tener que configurar un mapa compuesto por cada mapa de fondo que utilizo.

Parece que la opción existe en el menú "Opciones capa" -> "Administrar capas", con el botón "Cargar mapa como capa", pero cuando le doy sale el error "No se han encontrado mapas compatibles". ¿Como se usa este botón? ¿qué mapas o cómo tienen que ser los mapas para que sean compatibles con este botón?

Muchas gracias
Hola, no es posible actualmente, tienes que crear un mapa compuesto por cada capa que quieres usar a no ser que uses la superposición de mapbox bajo suscripción más detalles aquí 👇

https://tronpoonpo.blogspot.com/2024/10/superposicion-de-capas-mapbox.html

Lo que comentas de cargar mapa como capa es solo para imágenes georreferenciadas con la propia app, aquí más detalles 👇
https://tronpoonpo.blogspot.com/2024/10/imagen-mapa.html

Off-Track1234

OM 12.0.05 has a bug affecting waypoint navigation. It jumps over the first few route points. Even those that remain are strangely ordered as indicated by next/previous waypoint. The same routes in the same device are fine under OM 7.4.28.

kkolesar

I mainly use OM for cycling. I came across a great feature for climbs in Garmin that shows the remaining distance and average gradient in % for the rest of the climb (if you're following a route).

Is something like that available in OM NG?


Tronpo

Quote from: kkolesar on July 29, 2026, 03:23:06 PMI mainly use OM for cycling. I came across a great feature for climbs in Garmin that shows the remaining distance and average gradient in % for the rest of the climb (if you're following a route).

Is something like that available in OM NG?

Yes!! In OruxMaps NG we have a similar function that was developed in the betas. It's called climber sections. Here I give you some details you can translate with the browser https://tronpoonpo.blogspot.com/2024/10/tramos-del-escalador_26.html for doubts I change my interface to your language and answer you here in the forum. TroNpo's sayings



kkolesar

Quote from: Tronpo on July 29, 2026, 07:55:16 PMYes!! In OruxMaps NG we have a similar function that was developed in the betas. It's called climber sections. Here I give you some details you can translate with the browser https://tronpoonpo.blogspot.com/2024/10/tramos-del-escalador_26.html for doubts I change my interface to your language and answer you here in the forum. TroNpo's sayings





That's amazing!

You're an endless source of information. Thnx!

ps/Do you maybe know why slopes are measured in degrees and not in percentages? I'm much more used to percentages and also on road signs are percentages.


Tronpo

Quote from: kkolesar on July 29, 2026, 11:45:33 PMThat's amazing!

You're an endless source of information. Thnx!

ps/Do you maybe know why slopes are measured in degrees and not in percentages? I'm much more used to percentages and also on road signs are percentages.


I think the slope is expressed in percentage because it is more intuitive, faster to interpret and more useful for those who move on the ground (drivers, cyclists, hikers).

The key is that the percentage directly describes how much the road goes up for every 100 metres travelled, while the degrees describe an angle, somewhat less immediate for most people. 10% means: For every 100 horizontal metres, you go up 10 metres.

That's a direct, almost visual relationship.

On the other hand, saying that a slope is 5.7° doesn't tell you anything about the real effort or inclination if you don't do the mental conversion. PS: just an inexhaustible source of curiosity :) knowledge is relative 😜

Off-Track1234

Yes... BUT ... even if you do not activate the "experiment" these "section markers" sometimes appear on your routes. They may or may not correspond with paths between route points. They appear as numbers on a white disc within the usual waypoint symbol. but they are not waypoints - they do not respond to controls that hide or show waypoints or route points. Then after you have torn out your hair trying to understand or control them, they may disappear from a route. Sometimes this may be when you load another route on screen. It seems like another bug - unless someone can explain how to control / hide them on screen?

Tronpo

#101
Quote from: Off-Track1234 on July 30, 2026, 07:10:07 AMYes... BUT ... even if you do not activate the "experiment" these "section markers" sometimes appear on your routes. They may or may not correspond with paths between route points. They appear as numbers on a white disc within the usual waypoint symbol. but they are not waypoints - they do not respond to controls that hide or show waypoints or route points. Then after you have torn out your hair trying to understand or control them, they may disappear from a route. Sometimes this may be when you load another route on screen. It seems like another bug - unless someone can explain how to control / hide them on screen?

Hello, this has nothing to do with it, they are distance indicators are placed along the route they are shown proportionally to the zoom level. You can configure whether you want to see them or not in configuration waypoint distance indicators and on the waypoint side panel. These indicators have always existed in the app

Tronpo

Quote from: Off-Track1234 on July 29, 2026, 12:23:23 PMOM 12.0.05 has a bug affecting waypoint navigation. It jumps over the first few route points. Even those that remain are strangely ordered as indicated by next/previous waypoint. The same routes in the same device are fine under OM 7.4.28.
Can you give me more information? Today take the test, load 5 waypoints on the map, activate waypoint navigation and everything works correctly.
In your case, how do you do it? Are waypoints that belong to a route? Does it happen in waypoint navigation or following route?
Just to be confirmed. Thank you

kkolesar

Quote from: Tronpo on July 30, 2026, 05:17:50 AMI think the slope is expressed in percentage because it is more intuitive, faster to interpret and more useful for those who move on the ground (drivers, cyclists, hikers).

The key is that the percentage directly describes how much the road goes up for every 100 metres travelled, while the degrees describe an angle, somewhat less immediate for most people. 10% means: For every 100 horizontal metres, you go up 10 metres.

That's a direct, almost visual relationship.

On the other hand, saying that a slope is 5.7° doesn't tell you anything about the real effort or inclination if you don't do the mental conversion. PS: just an inexhaustible source of curiosity :) knowledge is relative 😜

I was confused when reading your answer, than I saw a typing mistake in my question  ::) ... I had in mind, why in OM slopes are interpreted in degrees ... as you also wrote, it is much more intuitive in %







Off-Track1234

Quote from: Tronpo on July 30, 2026, 07:27:21 AMHello, this has nothing to do with it, they are distance indicators
Thanks Tronpo, that explains it. I have never seen them before, but must not have experimented with that setting before.

Quote from: Tronpo on July 30, 2026, 07:48:54 AMCan you give me more information? Today take the test, load 5 waypoints on the map, activate waypoint navigation and everything works correctly.
In your case, how do you do it? Are waypoints that belong to a route? Does it happen in waypoint navigation or following route?
Strange it does not happen to you, maybe something else I have unknowingly altered?. I load routes (defined by routepoints) for waypoint navigation, and it always happens in OM 12.0.05 NG but never under OM 7.4.28. They were originally from Garmin (via basecamp), imported as GPX, but that should not matter. In the simple example I will try to attach, the navigation is from Home. I do not move but in NG it jumps firstly to Ave (skips initial route points) then after a few seconds to SchoolTk at the end of the route. Trying next /previous waypoint, gives YelgunFd only (in the wrong direction); sometimes Home. It seems even more complicated in more complex routes, sometimes skipping over several route points in testing next / previous; but never finding others near the start.