Topics

Hi,

I was wondering if it is possible to have the distance line* text positioned at the bottom (just above the dashboard, or maybe *in* the dashboard) like it was before. It seemed a good idea at first, but honestly it become annoying fast. It's not that every time I pan the map I'm interested in knowing the distance, sometimes I'm just looking at the map searching for a road or something, and the damn text covers the map. A smartphone screen isn't that big anyway, even if the text is at the bottom is plenty reachable and readable.

I haven't found any option in the preferences, but maybe I missed it.

* I mean, the line drawn from map center to GPS position that shows distance, elevation difference and slope

[Bugianen]

(English version below)

Ciao,

vorrei annunciare due mappe che ho realizzato per l'arco alpino di Piemonte e Valle d'Aosta. Non sono progetti nuovi, se ne era già parlato da queste parti in fase di prototipazione, poi mi sono dimenticato di annunciare i prodotti finiti.

Bugianen
La prima in ordine cronologico è Bugianen, mappa escursionistica estiva delle zone alpine, pubblicata già da qualche anno.
Per i livelli di zoom alti utilizza la base CTR raster 10k del Piemonte e della Val d'Aosta sulla quale sono riportati i sentieri con classificazione pedonale e ciclistica, punti acqua, rifugi e vegetazione presi da OpenStreetMap. "Un taccone" come diciamo da queste parti, ma funziona piuttosto bene.
I livelli di zoom bassi sono creati da me con un mix di dati OpenStreetMap e dati vettoriali delle regioni.
https://tartamillo.wordpress.com/bugianen/

Sorbetto
La seconda è Sorbetto, mappa per attività invernali in montagna
Riporta su una base essenziale la classificazione delle pendenze oltre i 30° per pianificare meglio gli itinerari e applicare con più facilità e maggior precisione i vari metodi di riduzione del rischio valanghe.
Nata insieme a Bugianen su base CTR, nel 2021 è stata completamente ridisegnata da zero, curve di livello comprese, per sfruttare al massimo la qualità dei modelli del terreno LIDAR più recenti. I calcoli delle pendenze sono fatti con applicazioni GIS a partire dai dati altimetrici istituzionali originali, quindi sono molto più precisi delle analoghe funzioni presenti in varie app che usano dati rimaneggiati od obsoleti. Per i nostalgici è ancora disponibile la vecchia versione, ma a questo punto la sconsiglio. Dopo due anni di utilizzo trovo decisamente meglio la nuova in accoppiata con Bugianen.
https://tartamillo.wordpress.com/sorbetto/

Grazie per l'attenzione


------ English version -----------

Hi,

I would like to announce some maps I made for Piemonte and Valle d'Aosta (alpine area only). They are not really new but I never announced them properly here.

Bugianen
The first in chronological order is Bugianen, a summer hiking map of the Alpine areas, published a few years ago.
It uses, for high zoom levels, the 10k raster technical regional map (CTR) base of Piedmont and Val d'Aosta with overlayed the paths with pedestrian and cycling classification, water points, shelters and vegetation taken from OpenStreetMap. "A kludge" apparently, but one that works amazingly well.
The low zoom levels are created by me with a mix of OpenStreetMap data and vector data from the regions.
https://tartamillo.wordpress.com/bugianen/

Sorbetto
The second project is Sorbetto, a map for winter activities in the mountains
It brings back the classification of slopes over 30° overlaid on an basic map in order to better plan itineraries and apply the various methods of reducing the avalanche risk more easily and with greater precision.
Born together with Bugianen, in 2021 it was completely redesigned from scratch, including the contour lines to make the most of the quality of the most recent LIDAR terrain models. The slope calculations are made with GIS applications starting from the original institutional altimetric data, so they are much more precise than the similar functions found in various apps that use reworked or obsolete data. For the nostalgic, the old version is still available, but at this point I do not recommend it. The new one coupled with Bugianen is way better.
https://tartamillo.wordpress.com/sorbetto/

Thanks for your attention

Hi Orux, since the last update from the Play Store half of the time I launch OruxMaps panning doesn't work. I can however zoom (and pan with two fingers which isn't really comfortable but saves the day). I noticed that when that happens I also see the status bar or sometimes even the whole interface, looks like Immersive Mode doesn't load completely or at all. I'm using a stock Samsung S8.

I was doing some exercise today with the backtrack tool. While it works correctly I think it could be made quite a bit better with a simple modification. Currently it just warns you that are too far from the route. This works well on roads or paths, because when you get the alert you just need to go back and search for the missed bifurcation. However in an open field (ski-touring, desert, off-piste scrambling...) it doesn't work as well, because when you get the alert your only option is to stop and check the phone to correct your direction. It would be useful to have:

a) a "ok, you are on the route again" message

b) a progressive "out of route" message, on three levels: "you are going out of route" when the threshold is reached, "you are out of route" when you are at 1.5 times the threshold, and "you are really out of route" when you are at 2 times the threshold.



In this way when you see the error is increasing, you can correct your direction accordingly without the need to look at the phone every 10 seconds which in some situations (e.g. skiing) can be rather complicated.



Thanks,

Maki

Hi Orux,



apparently a lot of people isn't smart enough to understand the concept of sub-menus, nor they can investigate a bit before complaining. The italian Play store has quite a bit of negative comments about the latest version. The complain is always the same "they removed the ability to download maps". Of course  I lack the ability to answer to comments. I don't know exactly what to suggest between answering comments (I can write a standard answer in italian if you want), going back to simple menus, a welcome splash screen that illustrates the new features or...



Maki

Hi Jose,



I was playing with DEMs and I have a doubt. If I have multiple files covering the same area how is the conflict handled? This is obviously impossible with HGT files (file name is forced), but with HDR+DEM where the file name is free it may happen. Do we know which file is used in this case?



I ask this because if it is possible to determine the file that takes precedence we could do interesting things, like having detailed HDR+DEM files for critical areas and 90m HGT files as a fallback for nodata areas.



Thanks,

Maki

Hi all,



I have 5m DTMs stored as GeoTIFF that are much better than the common SRTM/ASTER DEMs we routinely use in Oruxmaps. Ideally I'd reduce them to 15 meters and then convert for use in OM, but I struggle to find the proper way to do the conversion, if at all possible. Anybody did already do this  and is willing to share the procedure? QGIS/GDAL preferred but I can evaluate other software.



Thanks

Hi Orux,



 I noticed that lately a folder called ".MF-cache" is showing up in the map list. Shouldn't it be hidden (dot at the beginning of the name)?



Maki

Non so a quanti possa intressare da queste parti, comunque ho pubblicato da poco una mappa derivata dalla CTR Piemonte, aggiungendo sfumo e calcolo delle pendenze superiori a 30°, più qualche cosina dai dati di OSM (sentieri e rifugi).



Per ora c'è solo parte della provincia di Cuneo (dalla Val Maira in giù).

Se volete è qui https://tartamillo.wordpress.com/sorbetto/">//https://tartamillo.wordpress.com/sorbetto/, con una descrizione dettagliata di cosa c'è.



Poi, ecco, se qualcuno facesse nevicare un po'...



Maki

ANNUNCIAZIO', ANNUNCIAZZIO'!!! [cit.]



...è ripresa la traduzione in italiano, a cura del sottoscritto. La situazione attuale non è male (grazie a chi ci ha lavorato prima di me) però mancano delle parti, c'è qualche piccola svista e a volte qualche incoerenza.



Il primo passo è tradurre le stringhe mancanti e correggere le sviste, in futuro vorrei uniformare la terminologia. Siccome però non uso tutte le funzionalità di OM a volte sono un po' in difficoltà per cui l'aiuto della comunità sarebbe gradito, postando commenti/suggerimenti/segnalazioni in questo thread.



Cosa servirebbe: nell'immediato un aiuto veloce su alcune terminologie con cui non ho familiarità (vedi sotto), poi una revisione del lavoro fatto. Per adesso non segnalate errori di ortografia o altre cose del genere perché ne ho già sistemati diversi e rischiate di perdere tempo per nulla.



Dunque cosa mi manca adesso? I seguenti termini:

ETA/ETE

Glide ratio

Compass heading

True track direction (GPS)

Magnetic track direction (GPS)

True bearing to target

Magnetic bearing to target

True heading

Compass heading

True track direction

HRM

XTE/Cross Track Error

TMG (Track Made Good)

Velocity Made Good



Qualcuno lo capisco, qualcuno no, ma soprattutto non so chi lo usa e se si traduce. Ad esempio "glide ratio" credo sia usato in aeronautica e ne capisco il significato, però magari normalmente non viene tradotto.



Commenti?

Hi,



I have several geotiffs of my area that I'd like to convert to OM format. So far I only managed to convert them one by one with OkGPS, but it's rather tedious and I end up with a lot of files. I'd like to batch process and possibly join some of them for an easier management on the phone. Is this possible in any way?



I link two example files:

http://www.regione.piemonte.it/risorseApplicative/GEOSCA/CTR/CTR_s244050.zip">http://www.regione.piemonte.it/risorseA ... 244050.zip">http://www.regione.piemonte.it/risorseApplicative/GEOSCA/CTR/CTR_s244050.zip

http://www.regione.piemonte.it/risorseApplicative/GEOSCA/CTR/CTR_s244010.zip">http://www.regione.piemonte.it/risorseA ... 244010.zip">http://www.regione.piemonte.it/risorseApplicative/GEOSCA/CTR/CTR_s244010.zip



Any help is appreciated, thanks in advance.

Hi, I tried to use some WMSs with Oruxmaps but without success. I use the same with JOSM and they work fine, so the server works, albeit slowly, especially the first one. On the other hand I managed to configure Oruxmaps with other WMSs successfully, so I don't understand what I'm doing wrong.

The URLs are:

http://webgis.arpa.piemonte.it/ags101free/services/topografia_dati_di_base/Topografica_Base_50K_Sfumo_Arpa_Piemonte/ImageServer/WMSServer?request=GetCapabilities&service=WMS">http://webgis.arpa.piemonte.it/ags101fr ... ervice=WMS">http://webgis.arpa.piemonte.it/ags101free/services/topografia_dati_di_base/Topografica_Base_50K_Sfumo_Arpa_Piemonte/ImageServer/WMSServer?request=GetCapabilities&service=WMS



http://webgis.arpa.piemonte.it/free/services/mappe_di_base/Topografica_CTR_10K_Regione_Piemonte/MapServer/WMSServer?request=GetCapabilities&service=WMS">http://webgis.arpa.piemonte.it/free/ser ... ervice=WMS">http://webgis.arpa.piemonte.it/free/services/mappe_di_base/Topografica_CTR_10K_Regione_Piemonte/MapServer/WMSServer?request=GetCapabilities&service=WMS





Any advice? thanks in advance.

[degrees]

Hi Jose,



I'd like to propose a couple of features that would find a lot of use in the ski touring community, possibly saving lives. And I mean that literally.



First a little background is necessary. One of the necessary conditions to trigger an avalanche is a minimum slope angle. That angle varies between 25° and 30° depending on snowpack humidification, usually the higher value is taken in account. The traditional approach is to measure that angle on a paper map using contour lines, but it is time consuming and imprecise. Some Swiss maps colour slopes above 30° in red, but it is a unique case. Please note that I'm talking about degrees and not percentages for the incline, and the relevant value is the maximum angle, not the average. The average angle between the current location and the top of the slope (known as alpha angle in some circles) is useful too, to estimate the maximum distance the avalanche can cover, but that's relatively less important.



Now the feature requests:

1) Enhance the measure tool. It currently only shows the distance, but using SRTM data it could calculate elevation gain and build an elevation profile. This would require some care from the user that has to chose the line in a proper way, but I suppose this is easy to implement, and could be interesting even outside the avalanche prevention scope.

2) This is the real one. Upon user request a variation of the relief map should be calculated on the fly for the currently shown area. Colour should show slope angle rather than absolute elevation, and should be overlaid semitransparent above the map. Below 25° green, 25-30° yellow, 30-35° orange, >35° red. (35° has a special importance, but I won't go into details now)

3) Same of above, but the angle is calculated from a single position in order to evaluate the alpha angle.



I've been intentionally brief, there would be quite a bit of details to discuss for an exact implementation but I think I gave you an idea. If you are willing to work on this stuff I can go deeper and hopefully involve some real avalanche experts.



Happy holidays.

hi Jose and all,



I just released a preliminary version of a new theme based on Tobias' Elevate. While it's still Elevate at the core (I changed very little in the XML) it is meant for high density displays in order to remove the need for digital zoom, and it looks quite different.



I built it on a Galaxy Nexus and tested on the alpine maps from OpenAndroMaps, I'd be interested to know how it works on other devices and other areas. I regularly read this forum, so comments here or on my website are the equivalent as far as I'm concerned.



A presentation, some screenshots and the download link here:

http://tartamillo.wordpress.com/tiramisu/">//http://tartamillo.wordpress.com/tiramisu/



Happy holidays.