Messages

Tracks and/or waypoints folders names created in the past may contain non-alphanumeric characters (spaces, dots, underscores, etc.), e.g. tracks folder name "My favorite tracks", and are still accessible. But within recent version 10.6.3 as well as within some versions before, unfortunately keyboard input of those characters is ignored when creating a new tracks/waypoints folder. Only alphanumeric characters are accepted. Bug or feature?

Issue still exists in version v.9.6.1 GP.

First of all, I really appreciate OruxMaps  .

But I have noticed some issues when adding turn instructions to imported track,
either using version 9.0.3GP or using version 9.0.4beta4.

Steps to reproduce:

• Install offline maps, amongst others OAM Alps.map and Germany.map
• Select offline map Germany.map
• Import attached GPX track "Regen-Zwiesel.gpx" into database.
  Track was generated by QMapShack and does not yet contain turn instructions!
  -> Track shows nice with Germany map (Screenshot 1)
• Open "Tracks verwalten -> Eigenschaften" (in German), probably "Manage tracks -> Properties" (in English) (Screenshot 2)
• Select "ÜBEREINSTIMMUNG IN BROUTER" (in German), probably "MATCH IN BROUTER" (in English) (Screenshot 3)
• Select vehicle "by foot" (Screenshot 4)
  -> track with turn instructions gets created
  Minor typo:
  German message on blue background is flashing "Eine neue Route wurde in Ihrer Datenbak gespeichert"
  -> Word "Datenbak" should be replaced by "Datenbank" (Screenshot 5)
  Issue:
  It sometimes happens that the spinning wheel seems to spin endlessly,
  showing "Verarbeitung, bitte warten" (in German), probably "Processing, please wait" (in English)
  -> In that case it may help to interrupt and to restart processing.
• After creation of new track, confirm to compare original track with new one.
  Issue:
  Comparison of original and new track are shown sidy by side,
  unfortunately not using currently selected Germany map as expected (Screenshot 6)
  but using Alps map as you will notice when zooming out (Screenshot 7)
  -> Seems first map in alphabetical order gets used, does it?
• After all, new track contains turn instructions.
  -> Back in map view, track shows nice with still active Germany map 

Regards,
Fritzle

Hello Orux,

as already noticed with earlier betas, pedestrian areas rendered with Mapsforge default theme still look strange in latest beta: with version 7.4.22 shown as hatched pattern  - currently shown as fat black lines. Bug or feature?

Regards

Update:
Seems I found the reason. Mapsforge default theme "default.xml" references patterns contained in jar file "mapsforge-themes-<version>.jar" by xml elements like "<line src="jar:patterns/access-private.png" stroke-width="1.0" />. If subfolder "assets/patterns" is not found within jar file or png file is not contained in subfolder, pattern gets rendered solid black.

Fat black filled pedestrian areas are back in v7.5.9beta43. (See item 1b in initial post)

[beta29]

Great, issue no longer reproducible with v7.5.9beta29
Thank you.

Attachment shows what I mean with "Mapsforge standard theme", i.e german "Mapsforge-Standardthema" translated to english.

When first locating map position in v7.4.22 and afterwards starting v7.5.9beta28 and navigating there to same location, I too see identical map contents. It seems that it is because the map tile is still cached and beta version displays cached tile. But after refreshing map segments in v7.5.9beta28, identically displayed map tile becomes rendered differently with pedestrian areas filled black as previously reported, public toilet POIs disappear and restaurants get shown by name and no longer by symbol "spoon & fork". When starting v7.4.22 later again, I also see pedestrian areas filled black as long as I do not refesh refresh map segments.

By the way, themes Elements and Elevate render correctly independent of zooming level. Osmarender theme shows pedestrian areas filled black too, when zooming in deep enough.

When rendering with Mapsforge standard theme, there is a different and strange behaviour between v7.4.22 and v7.5.9beta28:

1a) pedestrian areas get fine hatched by v7.4.22
1b) pedestrian areas get fat filled black by v7.5.9beta28
2a) more POIs get shown by v7.4.22 (e.g. public toilets)
2b) less POIs get shown by v7.5.9beta28

See attached screenshots located at Stuttgart main station with map recently downloaded from
http://download.openandromaps.org/mapsV4/Germany/baden-wuerttemberg.zip

Maybe, I was not able to find appropriate switches to achieve same look and feel in beta version.

I notice following rendering issue after upgrading to version 7.2.9:



When switching between renderthemes, e.g. between Mapsforge "Elevate" and "Elements",

or when switching between "Hiking" and "Cycling" layers,

rendering to screen does not correctly reflect changed settings.

Sometimes none and sometimes only part of screen gets updated correctly.



After layer switching in a region containing hiking and cycling routes and shifting map position,

upper half of screen shows cycling routes remaining from previous layer "Cycling" and

lower half of screen shows hiking routes reflecting change to layer "Hiking".

Seems only previously uncached data gets rendered correctly.



By downgrading, I verified that issue does not yet occur with version 7.2.7.



Nevertheless, thank you so much for this wonderful app   .