Recent posts
#91
BETAS / Re: New beta 10.6.x
Last post by Starfighter - April 22, 2024, 05:11:21 PMQuote from: orux on April 19, 2024, 10:57:28 AMLos ajustes son, en teoría separados, para los visores que usan tecnología diferente (superposición vs multiplicación de colores).
Debes poder ajustar con diferentes valores para uno u otro tipo de mapa.
Prueba a cargar un mapa mapsforge, por ejemplo, con uno y otro visor, verás que los ajustes de opacidad pueden ser diferentes,
orux
Hola, Orux.
Aunque el tema de los sombreados es algo que he explorado en profundidad, tomándome muy en serio el papel de beta tester, me voy a limitar a seguir únicamente con la recientemente añadida posibilidad de controlar la gama de grises con los que se hace el sombreado.
Lo cierto es que los dos pantallazos que envié utilizan el mismo valor, 99, y mientras que en el visor "de siempre" el efecto es dramático, con el visor VTM se queda en un nivel medio claro de grises en su valor más oscuro, con lo que la prueba que me sugieres estaría hecha y no, definitivamente no hay ajustes implícitos separados; el mismo valor tiene resultados muy distintos para cada visor.
La configuración [Settings > Mapsforge settings > Apply hill shadows] no se ve afectada por el valor elegido en [DEM based maps > Shadows exageration] y tampoco ifluye que se seleccione [VTM map viewer], dando siempre la gama de grises de siempre (bastante claro).
A esto añado que [Mapsforge settings] sólo funciona con archivos HGT, dejando fuera de juego los archivos HDR+DEM que es donde el tema del sombreado se pone realmente interesante por el nivel de detalle que permiten alcanzar cuando se obtienen a partir de archivos LiDAR.
Si entiendo bien los conceptos detrás de "superposición vs multiplicación de colores" tenemos un nuevo problema. Solo el API de Mapsforge respeta la información de capas (superposición) contenida en los "renderthemes" en la que hay distintos grados de transparencia e incluso establece en qué capa debe ir el sombreado (este asunto lo he comentado con Tobias, el creador de los temas Elevate y Elements para OpenAndroMaps)
Volviendo a la configuración general [Settings > Apply hill shadows], que es donde realmente se aplica el resultado de [DEM based maps > Shadows exageration], y eligiendo sombreados detallados (HDR + DEM), siempre se utiliza la (multiplicación de colores), ignorando los "mapstyles" de Mapsforge aun con mapas OAM, provocando que más allá de un nivel medio-claro de grises se pierdan los senderos/caminos/pistas, debido a la transparencia indiscriminada aplicada para fusionarse con el sombreado. Por fortuna, el poder decidir la gama de grises permite utilizar estos sombreados detallados que antes no eran utilizables por demasiado oscuros con la consabida perdida de información debida a la forma fusionar las dos capas (shadows+oam map).
Si no me he expresado bien o necesitas algún pantallazo para ilustrar lo que comento sólo tienes que decírmelo y estaré encantado en ayudar con el tema.
Saludos,
#92
MEJORAS/NEW FEATURES / GPS Position (Slight Improveme...
Last post by Tronpo - April 21, 2024, 04:29:54 PMGPS position, distance indicators.
When using cursor down, the distance measurements of the circles are hidden by the square of controls or the altitude graph, in this case it would be interesting to have the measurements above the cursor.
It would also be useful to be able to visualize estimated time data, using alternate circles at 30-minute intervals for example (30-60-90-120), either together or individually.
When using cursor down, the distance measurements of the circles are hidden by the square of controls or the altitude graph, in this case it would be interesting to have the measurements above the cursor.
It would also be useful to be able to visualize estimated time data, using alternate circles at 30-minute intervals for example (30-60-90-120), either together or individually.
#93
ERRORES/BUGS / Google rues maps are broken in...
Last post by gagnes - April 20, 2024, 11:07:43 AMHello,
I have a black screen on Google Rues maps in 10.5
Works in 10.4 and 10.6.1 beta2
I have a black screen on Google Rues maps in 10.5
Works in 10.4 and 10.6.1 beta2
#94
BETAS / Re: New beta 10.6.x
Last post by Tronpo - April 20, 2024, 10:51:39 AMQuote from: odin on April 20, 2024, 08:51:22 AMHi orux, awesome work,
I picked up some bike sensors recently, so I was messing around in orux to see how they work.
I was wondering with the sensors like cadence / speed, could you make it so it retries to re-connect to them indefinitely (or a configurable time), sometimes I walk away from my bike for a few minutes and often forget to tell orux to reconnect to the sensor, also on the track statistic page it's a bit confusing what data is from the sensors and what's from the GPS, maybe a toggle to show sensor stats and a toggle to show GPS stats if possible.
I was also messing with some bike computer app, it could play back your ride route like a video from 1x to 100x speed and has like a little dot icon that moves through the route and shows riding speed as it plays through, I thought that would be pretty neat if orux could do that, but you could show more stats like altitude, speed, grade...etc
Hello, I would swear that there used to be the option to reconnect the peripherals... I don't see it now.
On the Sicami website (Oruxmaps GP integration)
You can see the playback of your route, in 3D with various speed and angle settings and much more how to share the playback, it is not to be missed, try it.
In Oruxmaps GP under subscription to featured maps you can also see the reproduction of the route.
#95
BETAS / Re: New beta 10.6.x
Last post by odin - April 20, 2024, 08:51:22 AMHi orux, awesome work,
I picked up some bike sensors recently, so I was messing around in orux to see how they work.
I was wondering with the sensors like cadence / speed, could you make it so it retries to re-connect to them indefinitely (or a configurable time), sometimes I walk away from my bike for a few minutes and often forget to tell orux to reconnect to the sensor, also on the track statistic page it's a bit confusing what data is from the sensors and what's from the GPS, maybe a toggle to show sensor stats and a toggle to show GPS stats if possible.
I was also messing with some bike computer app, it could play back your ride route like a video from 1x to 100x speed and has like a little dot icon that moves through the route and shows riding speed as it plays through, I thought that would be pretty neat if orux could do that, but you could show more stats like altitude, speed, grade...etc
Edit:
also minor bugs, when adding a second sensor to the BLE cadence / speed, it should show the mac address like the first sensor does, since there is no way to know if the second sensor is added, also for popup noticications it just says bluetooth sensor connected, maybe that could be improved to something like BTLE speed sensor connected / BTLE cadance sensor connected, same with the connection lost message.
I picked up some bike sensors recently, so I was messing around in orux to see how they work.
I was wondering with the sensors like cadence / speed, could you make it so it retries to re-connect to them indefinitely (or a configurable time), sometimes I walk away from my bike for a few minutes and often forget to tell orux to reconnect to the sensor, also on the track statistic page it's a bit confusing what data is from the sensors and what's from the GPS, maybe a toggle to show sensor stats and a toggle to show GPS stats if possible.
I was also messing with some bike computer app, it could play back your ride route like a video from 1x to 100x speed and has like a little dot icon that moves through the route and shows riding speed as it plays through, I thought that would be pretty neat if orux could do that, but you could show more stats like altitude, speed, grade...etc
Edit:
also minor bugs, when adding a second sensor to the BLE cadence / speed, it should show the mac address like the first sensor does, since there is no way to know if the second sensor is added, also for popup noticications it just says bluetooth sensor connected, maybe that could be improved to something like BTLE speed sensor connected / BTLE cadance sensor connected, same with the connection lost message.
#96
BETAS / Re: New beta 10.6.x
Last post by orux - April 19, 2024, 10:57:28 AMQuote from: Starfighter on April 17, 2024, 02:54:28 PMHola, Orux!
Recientemente he visto que en "DEM based maps" se ha añadido una nueva propiedad configurable llamada "Shadows exageration" para controlar la gama de grises empleada en el sombreado del relieve.
Mi propuesta es que se duplique esa propiedad, una para el visor tradicional y otra para el VTM por una razón obvia cuando se analizan los dos pantallazos que adjunto, ambos con valor de 99 (el más claro es el VTM; el visor de siempre para igualarlo le basta con 40), con el fin de que se puedan establecer valores independientes para cada uno de los visores.
https://photos.google.com/share/AF1QipMepIAETZVe-L7XM1P9aNrdmMbkqPlJyZFCDRsYMgEoUmTL0N4oliY_MPdYXRv6Jg/photo/AF1QipMtOJ6SSJrulU0NH4Gd-FbjBbgPbdlQzZwOEDbv?key=b2xpU3pvVU1lTnlMUzU0NGxDQy0zSDZmUDNEM3F3
https://photos.google.com/share/AF1QipMepIAETZVe-L7XM1P9aNrdmMbkqPlJyZFCDRsYMgEoUmTL0N4oliY_MPdYXRv6Jg/photo/AF1QipNi0baxF1NWXj0FE5JEWpdbIJqAa1RrkntWiSfU?key=b2xpU3pvVU1lTnlMUzU0NGxDQy0zSDZmUDNEM3F3
Los ajustes son, en teoría separados, para los visores que usan tecnología diferente (superposición vs multiplicación de colores).
Debes poder ajustar con diferentes valores para uno u otro tipo de mapa.
Prueba a cargar un mapa mapsforge, por ejemplo, con uno y otro visor, verás que los ajustes de opacidad pueden ser diferentes,
orux
#97
BETAS / Re: New beta 10.6.x
Last post by orux - April 19, 2024, 10:48:13 AMQuote from: IBERO on April 15, 2024, 09:18:35 AMBuenos días Orux:
Estoy teniendo problemas con los controles por voz, que tienen "," en su texto:
- Continuar, centro.
- Continuar, desvío derecha.
- Continuar, desvío izquierda.
no me los reconoce o cuando me los reconoce me crea el símbolo de "lugar-waypoint" general, en lugar de su icono especifico. He probado a nombrar la coma también y lo que hace la app es reconocerla pero con un espacio posterior a la palabra continuar: ejemp: Continuar , centro. y ya no lo reconoce.
¿Se podría eliminar la coma, para que se ejecutará correctamente? He probado a crear un comando "propio" con una imagen diferente y el texto sin la coma: ejemplo: Continuar centro y va perfectamente.
Otra cuestión: Los siguientes comandos referidos a las salidas en las glorietas. ¿Cómo los dicto por voz, que no tengo manera de crearlos, al no reconocérmelos la app?:
- 1º Salida.
- 2º Salida.
- 3º Salida.
- 4º Salida.
- 5º Salida.
Gracias y un saludo
Buenas!
Probaremos a probar coincidencias sin los signos de puntuación, y a reemplazar los números con textos,
orux
#98
GENERAL / Re: Remove "S" from track data...
Last post by capoccia - April 18, 2024, 09:56:58 PMHi orux,
today I updated to 10.6.0 GP. I have the same problem.
In new account Kap3 I synced only last 43 track. I logged to old account and delete all track from sicami, then I returned to new account but It syncked only 43 track.
The only way to solved the problem is logged to old account and in the track select: property-delete from oruxmaps. In this way when Logged in new account it syncronise a track. But I have a lot of traces for do this work by hand.
Is there a system to automatize its?
Can you add a property "Remove from Orxumaps" when I select all tracks?
today I updated to 10.6.0 GP. I have the same problem.
In new account Kap3 I synced only last 43 track. I logged to old account and delete all track from sicami, then I returned to new account but It syncked only 43 track.
The only way to solved the problem is logged to old account and in the track select: property-delete from oruxmaps. In this way when Logged in new account it syncronise a track. But I have a lot of traces for do this work by hand.
Is there a system to automatize its?
Can you add a property "Remove from Orxumaps" when I select all tracks?
#99
BETAS / Re: New beta 10.6.x
Last post by Starfighter - April 17, 2024, 02:54:28 PMHola, Orux!
Recientemente he visto que en "DEM based maps" se ha añadido una nueva propiedad configurable llamada "Shadows exageration" para controlar la gama de grises empleada en el sombreado del relieve.
Mi propuesta es que se duplique esa propiedad, una para el visor tradicional y otra para el VTM por una razón obvia cuando se analizan los dos pantallazos que adjunto, ambos con valor de 99 (el más claro es el VTM; el visor de siempre para igualarlo le basta con 40), con el fin de que se puedan establecer valores independientes para cada uno de los visores.
https://photos.google.com/share/AF1QipMepIAETZVe-L7XM1P9aNrdmMbkqPlJyZFCDRsYMgEoUmTL0N4oliY_MPdYXRv6Jg/photo/AF1QipMtOJ6SSJrulU0NH4Gd-FbjBbgPbdlQzZwOEDbv?key=b2xpU3pvVU1lTnlMUzU0NGxDQy0zSDZmUDNEM3F3
https://photos.google.com/share/AF1QipMepIAETZVe-L7XM1P9aNrdmMbkqPlJyZFCDRsYMgEoUmTL0N4oliY_MPdYXRv6Jg/photo/AF1QipNi0baxF1NWXj0FE5JEWpdbIJqAa1RrkntWiSfU?key=b2xpU3pvVU1lTnlMUzU0NGxDQy0zSDZmUDNEM3F3
Recientemente he visto que en "DEM based maps" se ha añadido una nueva propiedad configurable llamada "Shadows exageration" para controlar la gama de grises empleada en el sombreado del relieve.
Mi propuesta es que se duplique esa propiedad, una para el visor tradicional y otra para el VTM por una razón obvia cuando se analizan los dos pantallazos que adjunto, ambos con valor de 99 (el más claro es el VTM; el visor de siempre para igualarlo le basta con 40), con el fin de que se puedan establecer valores independientes para cada uno de los visores.
https://photos.google.com/share/AF1QipMepIAETZVe-L7XM1P9aNrdmMbkqPlJyZFCDRsYMgEoUmTL0N4oliY_MPdYXRv6Jg/photo/AF1QipMtOJ6SSJrulU0NH4Gd-FbjBbgPbdlQzZwOEDbv?key=b2xpU3pvVU1lTnlMUzU0NGxDQy0zSDZmUDNEM3F3
https://photos.google.com/share/AF1QipMepIAETZVe-L7XM1P9aNrdmMbkqPlJyZFCDRsYMgEoUmTL0N4oliY_MPdYXRv6Jg/photo/AF1QipNi0baxF1NWXj0FE5JEWpdbIJqAa1RrkntWiSfU?key=b2xpU3pvVU1lTnlMUzU0NGxDQy0zSDZmUDNEM3F3
#100
MAPAS/MAPS / Re: Mapas WMS (Solved)
Last post by jespa - April 17, 2024, 01:42:01 PMJust to clarify...
In version Oruxmaps version 10.5 GP the WMS, WMTS and composite maps are stored in a internal database that is imported from files
oruxmaps/mapfiles/.wms_data, oruxmaps/mapfiles/.wmts_data and oruxmaps/mapfiles/.mms_data
When you export the WMS, WMTS data (using the "💾 Save Maps" option in the menu of maps screen), oruxmaps will ask you for one directory to save the files. You can use oruxmaps/mapfiles if you want, but this does not mean making the maps permanent. You can copy these files in your computer or sdcard and use later to restore the data using the "Restore Maps" option in the same maps screen menu.
The app will save three files: wms_data , wmts_data and mms_data file format is this:
.wms_data:
.wmts_data:
.mms_data:
As you see, this is not XML but a direct dump of sqlite database. First line is a header, and next lines contains values for the database.
First number in each line is an identifier (you don't want two of these numbers repeated)
If you are brave enough, you can edit those files using a text editor and import then again, but you run the risk of breaking the oruxmaps internal database.
In version Oruxmaps version 10.5 GP the WMS, WMTS and composite maps are stored in a internal database that is imported from files
oruxmaps/mapfiles/.wms_data, oruxmaps/mapfiles/.wmts_data and oruxmaps/mapfiles/.mms_data
When you export the WMS, WMTS data (using the "💾 Save Maps" option in the menu of maps screen), oruxmaps will ask you for one directory to save the files. You can use oruxmaps/mapfiles if you want, but this does not mean making the maps permanent. You can copy these files in your computer or sdcard and use later to restore the data using the "Restore Maps" option in the same maps screen menu.
The app will save three files: wms_data , wmts_data and mms_data file format is this:
.wms_data:
Code Select
#42
_id||name||descr||url||maxz||minz||addons||format||srs||cache||down||layers||version||maxtiles||minx||miny||maxx||maxy||tilesize||maxthread
16046||PNOA 2021||||https://www.ign.es/wms/pnoa-historico?SERVICE=WMS&||19||3||&styles=||image/png||EPSG:4326||1||1||PNOA2021||||-1||-19||27||5||44||256||4
16047||PNOA 2018||||https://www.ign.es/wms/pnoa-historico?SERVICE=WMS&||19||3||&styles=||image/png||EPSG:4326||1||1||PNOA2018||||-1||-19||27||5||44||256||4
16049||PNOA 2012||||https://www.ign.es/wms/pnoa-historico?SERVICE=WMS&||19||3||&styles=||image/png||EPSG:4326||1||1||PNOA2012||||-1||-19||27||5||44||256||4
16050||PNOA 2009 ||||https://www.ign.es/wms/pnoa-historico?SERVICE=WMS&||19||4||&styles=||image/png||EPSG:4326||1||1||PNOA2009||||-1||-19||27||5||44||256||4
16051||PNOA 2006||||https://www.ign.es/wms/pnoa-historico?SERVICE=WMS&||19||3||&styles=||image/png||EPSG:4326||1||1||PNOA2006||||-1||-19||27||5||44||256||4
16053||SIGPAC 1997-2003||||https://www.ign.es/wms/pnoa-historico?SERVICE=WMS&||19||3||&styles=||image/png||EPSG:4326||1||1||SIGPAC||||-1||-19||27||5||44||256||4
16054||AMSB 1956-57||||https://www.ign.es/wms/pnoa-historico?SERVICE=WMS&||19||3||&styles=||image/png||EPSG:4326||1||1||AMS_1956-1957||||-1||-19||27||5||44||256||4
.wmts_data:
Code Select
#42
_id||name||user||pass||heads||url||cache||down||tsize||maxtiles||minx||miny||maxx||maxy||layer||layerid||layersetid||urltemp||format||style||srs||zids||scales||maxys||minxs||xtiles||ytiles||maxthreads
1||LIDAR ||||||User-Agent=OruxMaps v.10.5.0 GP||https://wmts-mapa-lidar.idee.es/lidar?||1||1||256||||-40||10||26||61||Modelo Digital de Superficies LiDAR||EL.GridCoverageDSM||EPSG:4326||||image/png||default||EPSG:32662||EPSG:4326:0;EPSG:4326:1;EPSG:4326:2;EPSG:4326:3;EPSG:4326:4;EPSG:4326:5;EPSG:4326:6;EPSG:4326:7;EPSG:4326:8;EPSG:4326:9;EPSG:4326:10;EPSG:4326:11;EPSG:4326:12;EPSG:4326:13;EPSG:4326:14;EPSG:4326:15;EPSG:4326:16;EPSG:4326:17;EPSG:4326:18;EPSG:4326:19;||2.795411320143589E8;1.3977056600717944E8;6.988528300358972E7;3.494264150179486E7;1.747132075089743E7;8735660.375448715;4367830.1877243575;2183915.0938621787;1091957.5469310894;545978.7734655447;272989.38673277234;136494.69336638617;68247.34668319309;34123.67334159654;17061.83667079827;8530.918335399136;4265.459167699568;2132.729583849784;1066.364791924892;533.182395962446;||1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;1.0018754171394622E7;||-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;-2.0037508342789244E7;||2;4;8;16;32;64;128;256;512;1024;2048;4096;8192;16384;32768;65536;131072;262144;524288;1048576;||1;2;4;8;16;32;64;128;256;512;1024;2048;4096;8192;16384;32768;65536;131072;262144;524288;||4
.mms_data:
Code Select
#42
_id||maps||names||trasp||off||mult||zooms||type
1||4,104||OpenSeaMap & Base map||1.,1.||0||0,0||||As you see, this is not XML but a direct dump of sqlite database. First line is a header, and next lines contains values for the database.
First number in each line is an identifier (you don't want two of these numbers repeated)
If you are brave enough, you can edit those files using a text editor and import then again, but you run the risk of breaking the oruxmaps internal database.