Elevate - Openandromaps hiking, cycling, sightseeing themes

[eartrumpet]

Elevate 4 and Elevate 2 have been updated. Some new map features are rendered, and the theme is ready for some internal transition of sac_scale processing. Also the special buildings overlay has been renamed to "special buildings + orientation" and guidepost has been moved to this overlay.



4.1.7 10/07/17

- added man_made=cutline, man_made=cairn, support for sac_scale=T5/T6 (for maps August 2017 and later)

- removed yes-value from via_ferrata_flag, changed name of special buildings overlay to "special buildings + orientation", moved guidepost to this overlay



2.7.6 10/07/17

- added man_made=cutline, man_made=cairn, support for sac_scale=T5/T6 (for maps August 2017 and later)

- removed yes-value from via_ferrata_flag

[orux]

Elevate 4 and Elevate 2 have been updated. Some new map features are rendered, and the theme is ready for some internal transition of sac_scale processing. Also the special buildings overlay has been renamed to "special buildings + orientation" and guidepost has been moved to this overlay.



4.1.7 10/07/17

- added man_made=cutline, man_made=cairn, support for sac_scale=T5/T6 (for maps August 2017 and later)

- removed yes-value from via_ferrata_flag, changed name of special buildings overlay to "special buildings + orientation", moved guidepost to this overlay



2.7.6 10/07/17

- added man_made=cutline, man_made=cairn, support for sac_scale=T5/T6 (for maps August 2017 and later)

- removed yes-value from via_ferrata_flag

Hi!



I am working with mapsforge 0.8.0 libraries, that support hillshading.



But I do not get it to work, because I think hillshading attributes should be included in the theme. Can you confirm that?



orux

[eartrumpet]

But I do not get it to work, because I think hillshading attributes should be included in the theme. Can you confirm that?

As far as I get it there's a element to be positioned where you think it fits in the theme (those are the default values):

<hillShading zoom-min="5" zoom-max="17" magnitude="64" layer="5" />

All resources I found:

https://github.com/mapsforge/mapsforge/pull/922">https://github.com/mapsforge/mapsforge/pull/922

https://raw.githubusercontent.com/mapsforge/mapsforge/master/resources/renderTheme-v6.xsd">https://raw.githubusercontent.com/mapsf ... eme-v6.xsd">https://raw.githubusercontent.com/mapsforge/mapsforge/master/resources/renderTheme-v6.xsd

https://groups.google.com/d/msg/mapsforge-dev/Gq5pcoAEQwg/J2j_9UBYBwAJ">https://groups.google.com/d/msg/mapsfor ... j_9UBYBwAJ">https://groups.google.com/d/msg/mapsforge-dev/Gq5pcoAEQwg/J2j_9UBYBwAJ

[orux]

But I do not get it to work, because I think hillshading attributes should be included in the theme. Can you confirm that?

As far as I get it there's a element to be positioned where you think it fits in the theme (those are the default values):

<hillShading zoom-min="5" zoom-max="17" magnitude="64" layer="5" />

All resources I found:

https://github.com/mapsforge/mapsforge/pull/922">https://github.com/mapsforge/mapsforge/pull/922

https://raw.githubusercontent.com/mapsforge/mapsforge/master/resources/renderTheme-v6.xsd">https://raw.githubusercontent.com/mapsf ... eme-v6.xsd">https://raw.githubusercontent.com/mapsforge/mapsforge/master/resources/renderTheme-v6.xsd

https://groups.google.com/d/msg/mapsforge-dev/Gq5pcoAEQwg/J2j_9UBYBwAJ">https://groups.google.com/d/msg/mapsfor ... j_9UBYBwAJ">https://groups.google.com/d/msg/mapsforge-dev/Gq5pcoAEQwg/J2j_9UBYBwAJ

Thanks;



there was a bug in the library with negative longitudes, now is working with default theme.



added 0.8 mapsforge libraries to the last beta version.



I think that hillshading requires themes version v6.





orux

[maozetung]

is there a way to download only a portion of a map? how?



I would like to reproduce the online map/offline map creation behavior where you can select a very restricted area.



thank you

[eartrumpet]

is there a way to download only a portion of a map? how?



I would like to reproduce the online map/offline map creation behavior where you can select a very restricted area.



thank you

Only full download of OAM is possible.

It is possible to download individual extracts in mapsforge format here, but various OAM features are missing:

https://extract.bbbike.org/">https://extract.bbbike.org/

[eartrumpet]

There are new versions of Elevate 4 and Elevate 2 available. It is recommended to use maps at least August 2017 or later with these, and they work best with October 2017 or later.

Big changes are a new overlay for extended road surface information, new via ferrata rendering, solid/dashed borders for cycleways and changed visibility information for paths without sac_scale. Check out the map key for further information. And lots of smaller changes, too:



4.2.0 06/10/17

- new optional overlay for extended road surface information of primary/secondary/tertiary/track roads and missing surface in cycling/MTB/hiking map style

- new via ferrata rendering: added non-switchable via_ferrata marking and highway=via_ferrata (for maps starting October 2017 and later)

- added dashed borders for non-paved cycleways (cycling/MTB), leisure=swimming_area, leisure=beach_resort, separate symbol for leisure=water_park, bboxweight for archipelagos and islands (for maps starting October 2017 and later), patterns for camp_site/caravan_site/golf_course (in case symbols for accomodation/sports are switched off), surface for turning circles

- changed administrative borders, all areas with strokes to areas with separate line for VTM compatibility

- removed "no trail_visibility available" marking for paths/footways without sac_scale/mtb_scale, old raw_sac_scale values (which were used in maps earlier than August 2017)



2.8.0 06/10/17

- added dashed borders for non-paved cycleways (cycling), leisure=swimming_area, leisure=beach_resort, separate symbol for leisure=water_park, bboxweight for archipelagos and islands (for maps starting October 2017 and later), surface for turning circles

- new via ferrata rendering: added non-switchable via_ferrata marking and highway=via_ferrata (for maps starting October 2017 and later)

- removed "no trail_visibility available" marking for paths/footways without sac_scale, old raw_sac_scale values (which were used in maps earlier than August 2017)

- changed administrative borders

[Anonymous]

Very much appreciate your work however...



I have mentioned this to you before. I find all the many different track types incredibly confusing and hard to remember.



You have 6 different track types! for a simple hiking trail!  then its further segmented by 3 different visibility of trail indicators marked by how dashed the lines are !



Who can remember all this unless they bring a paper copy of the map key with them when walking...... your map key is 21 pages! https://www.openandromaps.org/wp-content/users/tobias/Elevate_map_key.pdf">https://www.openandromaps.org/wp-conten ... ap_key.pdf">https://www.openandromaps.org/wp-content/users/tobias/Elevate_map_key.pdf



PLEASE PLEASE RELEASE A VERSION WITHOUT ALL THE TRACK TYPES !!



For the hiking style you have



Yellow - Hiking]Blue[/color]  - Mountain hiking: partially steep, fall hazard possible



Red -  - Demanding mountain hiking]Black[/color] - (Difficult/demanding)Alpine hiking/Via Ferrata: no trail, very exposed, climbing, glaciers



Then you also have further segmentation by broken and dashed lines or two thin dashed lines !



and then you have regular uncategorized trails



Brown  - unpaved path/footway (alot of tracks are marked as this even very difficult ones because no user has categorized it



Grey  - paved path/footway.



and then their is roads,train lines etc etc.



Any competent hiker can use the contours to work out the steepness of the terrain..  and a number of the trail types are wrong or not marked.. some trails marked as red are just a gentle slope others are very technical steep slopes involving scrambling up cliffs..(not your fault or responsibility this is just openstreet map contributor error but it underscores the point that why have all these track types when a user cant rely on it to be reasonably accurate)



Sorry for this rant.  I love your maps and very much appreciate you do all this for free.  I just find this one thing very much reduces my safety (to confusing because oruxmaps also has different colours for sections of the route so easy to think im on the route but actually ive followed a different trail the same colour as the orux route) and enjoyment of using the map. If you just have an option to not show all the trail type and just mark all trail as brown then problem would be solved. If others want all the different types then it is still there.

[eartrumpet]

Who can remember all this unless they bring a paper copy of the map key with them when walking.

Everyone who is used to the way hiking paths are marked in the Eastern Alps, like this:

http://www.nationalpark-berchtesgaden.bayern.de/nationalpark/wandern/wandertipps/pic/schilderkonzept_15x10.jpg">//http://www.nationalpark-berchtesgaden.bayern.de/nationalpark/wandern/wandertipps/pic/schilderkonzept_15x10.jpg

..... your map key is 21 pages! https://www.openandromaps.org/wp-content/users/tobias/Elevate_map_key.pdf">https://www.openandromaps.org/wp-conten ... ap_key.pdf">https://www.openandromaps.org/wp-content/users/tobias/Elevate_map_key.pdf

It's formatted for on-screen-use on a smartphone, not for printing. The relevant section is just two pages, you could print this in credit card size and attach it to your phone :-)

PLEASE PLEASE RELEASE A VERSION WITHOUT ALL THE TRACK TYPES !!

Use city or cycling map style. Or a different theme:

https://www.openandromaps.org/en/oam-forums/topic/map-theme-link-collection">//https://www.openandromaps.org/en/oam-forums/topic/map-theme-link-collection

Yellow - Hiking]Blue[/color]  - Mountain hiking: partially steep, fall hazard possible



Red -  - Demanding mountain hiking]Black[/color] - (Difficult/demanding)Alpine hiking/Via Ferrata: no trail, very exposed, climbing, glaciers

That's just the short version, if you look http://wiki.openstreetmap.org/wiki/Key:sac_scale">here or at the original definition of the Swiss Alpine Club, you will see that they are well defined and definitely very different categories, which is essential to know.

Then you also have further segmentation by broken and dashed lines or two thin dashed lines !

Yes, by user demand, an in a way that is not very distracting if you're not interested, and quite logic as well - the more broken the dashes, the more difficult the trail.

and then you have regular uncategorized trails

Of course, should I not show them? Sac_scale should only be used in the mountains, so the majority of footways/paths will never have sac_scale. But showing them in the same color would be simply wrong, so there has to be a different one.

and then their is roads,train lines etc etc.

Yes, it's a map. Should be there.

Any competent hiker can use the contours to work out the steepness of the terrain..

As written above, steepness is only one of many variables that are part of sac_scale.

and a number of the trail types are wrong or not marked.. some trails marked as red are just a gentle slope others are very technical steep slopes involving scrambling up cliffs..(not your fault or responsibility this is just openstreet map contributor error but it underscores the point that why have all these track types when a user cant rely on it to be reasonably accurate)

Then it's up to you to correct the data, that's part of OSM. Here in the Eastern Alps the vast majority of markings is correct, this theme is made for this. Of course it can be used in every other area on this planet, and I do this as well. An my experience isn't that bad. Mostly it isn't marked, but then you have the brown paths you demand.

Sorry for this rant.

Have you ever achieved anything with something like this?

I love your maps and very much appreciate you do all this for free.

Thanks, and I have stated here and in the map legend why I do things I do:

https://www.openandromaps.org/en/oam-forums/topic/elevate-hiking-version">https://www.openandromaps.org/en/oam-fo ... ng-version">https://www.openandromaps.org/en/oam-forums/topic/elevate-hiking-version

If you're not satisfied, this theme might be not for you. That was my starting point for making Elevate, and that's why the license of Elevate allows everyone to modify it to fit their need and also publish it.

I just find this one thing very much reduces my safety (to confusing because oruxmaps also has different colours for sections of the route so easy to think im on the route but actually ive followed a different trail the same colour as the orux route) and enjoyment of using the map.

You can define in OruxMaps the route that it looks nothing like anything contained in Elevate. Especially the "route path effect" helps. Also all paths in Elevate are dashed, so it's very easy to distinguish if you choose to have a solid route without "route path effect".

 If you just have an option to not show all the trail type and just mark all trail as brown then problem would be solved. If others want all the different types then it is still there.

The option would need an extra map style. I use map styles only for really major differences (hiking/cycling/mtb/city), so this won't happen.

[eartrumpet]

There are new versions of Elevate 4 and 2. Main changes are the support of new map contents (starting mid November 2017), higher peaks are now shown earlier and, if the app supports it, are prioritized. In Elevate 4 with waymarks also waycolor can be displayed, and the overlays contents have been rearranged a bit.



All changes:



4.2.1 28/11/17

- added zoom level visibility/priority per dominance for peaks/volcanos, osmc way colors (to waymarks overlay), blue/green/yellow arch waymark foregrounds, tower=windmill, bunker/bunker_disused, adit/adit_disused

- moved patterns for swimming areas/tourist attractions/golf courses/camping & caravan sites to special areas overlay, removed tourism=attraction from protected areas, tennis grounds/running tracks/swimming areas from sports overlay, limited tourism=attraction zoom level for Elements

- fixed ele for small volcano symbols, low zoom railway tunnels



2.8.1 28/11/17

- added zoom level visibility/priority per dominance for peaks/volcano, tower=windmill, bunker/bunker_disused, adit/adit_disused

- removed tourism=attraction symbol from various other pois, removed tourism=attraction from protected areas,

- fixed low zoom railway tunnels

[eartrumpet]

There are some new Elevate versions available. The biggest change is that now access limits are much more accurate to the mode of transportation the map style is made for, and with this the separate color for cycling prohibited was also removed. New map versions are needed for this to work properly.



All changes:



4.2.2 13/02/18

- new access rendering: private/no/destination/permit patterns now shown per transport mode the mapstyle implies (foot/general values for hiking, bicycle/vehicle/general values for cycling/MTB, general values only for city), removed separate pattern bicycle=no

- added seasonal for waterways, surface=winter, symbols for mountain passes with direction, building=construction

- removed house number display from peaks



2.8.2 13/02/18

- new access rendering for cycling: private/no/destination/permit patterns now additionally show cycling access limits, removed separate pattern bicycle=no

- added seasonal for waterways, surface=winter, building=construction

- removed house number display from peaks, fixed living_street rendering

[eartrumpet]

There's a new Elevate version available, biggest change is the addition of an overlay switch to turn the map background off (for a transparent map to overlay on satellite images e.g.)



4.2.3 23/04/18

- added the possibility to switch map background off (for composite maps), zoom min for area captions in Elements

- fixed tram stations, rough paved surfaces on highway=service

- changed zoom-min for playgrounds



2.8.3 23/04/18

- added zoom min for area captions in Elements

- fixed tram stations

[Maki]

Hi Tobias, there is a typo in the Italian strings.



"Percorsi accentato" should be "Percorsi accentuati"

[eartrumpet]

Hi Tobias, there is a typo in the Italian strings.



"Percorsi accentato" should be "Percorsi accentuati"

Thanks! As I don't speak Italian that helps a lot, I hope the other things make sense (those things are hard to get right even for languages you speak a bit)

[eartrumpet]

Elevate has been updated. Biggest changes include refinded redering of settlement names by population, better cycleway rendering and incline direction for MTB uphill scale.

All changes:



4.2.4 18/06/18

- added incline direction to MTB uphill scale, refs for ways without cycling/hiking routes (in cycling/hiking route overlays), refs for highway links, waterway=lock_gate, seperate rendering for minor aerialways, PopCat for city/town/village

- optimized cycleway rendering, cycling routes captions, waterway=dam, place rendering

- fixed Italian translation



2.8.4 18/06/18

- added incline direction to MTB uphill scale, PopCat for city/town/village, waterway=lock_gate, seperate rendering for minor aerialways

- optimized waterway=dam, place rendering