New beta 5.5.23betaXX

[eartrumpet]

Thanks Orux, hillshading looks much better now.



A different issue:



I just realized that zoom level behavior for mapsforge maps has changed in comparison to earlier betas.



I thinks it's a good idea to have them at equivalent level as tileserver maps so it's easier to switch between those, so I find this a great thing and solves problems discussed earlier.



But I think it's confusing to change the zoom level label to a fake equivalent label (so that it seems that mapsforge maps use the same zl number even if they don't), as under the hood (mapsforge maps/themes) the real zoom level number is still used.



It makes it harder for theme developers, but also for advanced users who have a look at the themes or tag-mapping at openandromaps.

But also with normal users ZL is often discussed, e.g. when they ask when which POI is visible, or which level is best for viewing place names.



So the real zoom level number has a real usage in those cases, so it would be good to have it still visible.

[chobkwon]

Thank you for your effort new version



The strings in the [Setting-TTS/Sounds] aren't localised.

I checked both the strings and the array files, and I cannot find the corresponding Text.



[Max. Wpt. alarm warnings]



Can you check that the files are current?



http://cfile257.uf.daum.net/image/2308403E54600F752F8F62">http://cfile257.uf.daum.net/image/23084 ... 0F752F8F62">http://cfile257.uf.daum.net/image/2308403E54600F752F8F62



http://cfile257.uf.daum.net/image/2308403E54600F752F8F62">

[6745th@web.de]

I played a bit with the mapforge settings.

If I set the factor for the text and symbols to 1.5 text and symbols are bigger as expected.

But when I increase the "scale factor"

Everything becomes smaller.

Is that wanted, or is it a bug?



Text, symbols 1.5, scale 1

http://tapatalk.imageshack.com/v2/14/11/14/851cae593a69af1fd5f1887fa96a376f.jpg">



Text and symbols 1.5 scale 2

http://tapatalk.imageshack.com/v2/14/11/14/956f627df266c4e9d1d1082bf055f9f8.jpg">



Greetings,

 Thomas

[Quercus.JB]

I played a bit with the mapforge settings.

If I set the factor for the text and symbols to 1.5 text and symbols are bigger as expected.

But when I increase the "scale factor"

Everything becomes smaller.

Is that wanted, or is it a bug?



Text, symbols 1.5, scale 1

http://tapatalk.imageshack.com/v2/14/11/14/851cae593a69af1fd5f1887fa96a376f.jpg">



Text and symbols 1.5 scale 2

http://tapatalk.imageshack.com/v2/14/11/14/956f627df266c4e9d1d1082bf055f9f8.jpg">



Greetings,

 Thomas

+1



Enviado desde mi LG-E460 mediante Tapatalk

[Maki]

I can't answer for Jose, but maybe a few notes about Mapsforge can help.



MF 0.3 used a fixed tile size of 256x256px. It meant that on displays with higher density things were actually smaller (because pixels are smaller). But a pixel level, regardless of the device, tiles were identical.



MF 0.4 uses a variable tile size with an automatic scale factor that is proportional to the display density, plus one "user scale factor" that the app can expose to the user or not. This means that at any given zoom level things look the same (except for PNG symbols that are not scaled). That's the theory. In practice, as explained before, Oruxmaps cannot work with a variable tile size, so Jose forced a 512x512 px tile size (which BTW is the natural tile size for 300 dpi devices). The Mapsforge library allows that, but with some problems, because the feature was never really meant for vector maps and weird things happen.



The biggest problem is that even is the tile size is fixed some things are still scaled according to the device screen, namely line widths and labels. So, if you look at the same map at the same ZL on a 233 dpi device and on a 450 one you'll see that text labels are roughly the same size, but lines are shorter and (proportionally) thicker. One possible side effect of this is that some symbols/labels can be killed by the collision detector on some devices and not on others.

So while tiles will have the same size on any device, tile content will vary and there is very little Jose can do about that, other than giving us access to a user scaling parameter that is built in Mapsforge for fine tuning.



In my experience if a theme is built for 300 dpi it sales acceptably well from 233 to 480 without touching anything in the settings except for the symbol scale factor. If one wants to keep things to exact proportions than playing with the other parameters is useful.



I'm not sure why the user scale factor for map works in such a way, but I believe it's a conflict between the fixed tile size and MF scaling mechanism.



MF 0.5 will bring a lot of new stuff that will solve most of the problems we are facing now. For starters there should not be clipped labels at tile boundaries anymore. Then a lot of things will be defined in a flexible way, which should make symbol and labels display more reliable. The scaling problem in itself will remain, however, unless Jose finds a way to modify OM to use variable tile sizes.

[orux]

I played a bit with the mapforge settings.

If I set the factor for the text and symbols to 1.5 text and symbols are bigger as expected.

But when I increase the "scale factor"

Everything becomes smaller.

Is that wanted, or is it a bug?





Greetings,

 Thomas

Hi, Thomas,



It is correct.



The overall scale factor affects the scale factor of the text.



orux

[orux]

I can't answer for Jose, but maybe a few notes about Mapsforge can help.



MF 0.3 used a fixed tile size of 256x256px. It meant that on displays with higher density things were actually smaller (because pixels are smaller). But a pixel level, regardless of the device, tiles were identical.



MF 0.4 uses a variable tile size with an automatic scale factor that is proportional to the display density, plus one "user scale factor" that the app can expose to the user or not. This means that at any given zoom level things look the same (except for PNG symbols that are not scaled). That's the theory. In practice, as explained before, Oruxmaps cannot work with a variable tile size, so Jose forced a 512x512 px tile size (which BTW is the natural tile size for 300 dpi devices). The Mapsforge library allows that, but with some problems, because the feature was never really meant for vector maps and weird things happen.



The biggest problem is that even is the tile size is fixed some things are still scaled according to the device screen, namely line widths and labels. So, if you look at the same map at the same ZL on a 233 dpi device and on a 450 one you'll see that text labels are roughly the same size, but lines are shorter and (proportionally) thicker. One possible side effect of this is that some symbols/labels can be killed by the collision detector on some devices and not on others.

So while tiles will have the same size on any device, tile content will vary and there is very little Jose can do about that, other than giving us access to a user scaling parameter that is built in Mapsforge for fine tuning.



In my experience if a theme is built for 300 dpi it sales acceptably well from 233 to 480 without touching anything in the settings except for the symbol scale factor. If one wants to keep things to exact proportions than playing with the other parameters is useful.



I'm not sure why the user scale factor for map works in such a way, but I believe it's a conflict between the fixed tile size and MF scaling mechanism.



MF 0.5 will bring a lot of new stuff that will solve most of the problems we are facing now. For starters there should not be clipped labels at tile boundaries anymore. Then a lot of things will be defined in a flexible way, which should make symbol and labels display more reliable. The scaling problem in itself will remain, however, unless Jose finds a way to modify OM to use variable tile sizes.

Hi, Maki;



you are right.



In the next version we will play with the 0.5 mapsforge version.





orux

[mntr86]

OruxMaps,  when will be released the next version on play Store? Thanks

[Maki]

I just realized that zoom level behavior for mapsforge maps has changed in comparison to earlier betas.

[...]

So the real zoom level number has a real usage in those cases, so it would be good to have it still visible.

+1



In addition, I'm seeing an intermittent bug. It's not new, but previously I thought it was just my impression; today I've seen it clearly. Unfortunately I cannot reproduce it at will; fortunately it's not frequent. For the same area I have three maps installed, a raster one in mbtiles and two mapsforge. When switching from the raster to a vector one the map scale is kept correctly (OM internally switches to the previous zoom level). When I then switch to the other vector map there is a +1 ZL jump.

[6745th@web.de]

I just installed Orux maps 6.0donation from the play store.

Congratulation for releasing!!

[orux]

I just installed Orux maps 6.0donation from the play store.

Congratulation for releasing!!

Hi,



Yes, 6.0.0 is available in google play; I hope it doesn't have too much 'last minute' bugs



orux

[oleolafson]

Is it possible to import the settings and profiles from beta to final?



I just tested the 6.0.0 - the http://www.oruxmaps.com/foro/viewtopic.php?f=5&t=2031#p5269">bug with the echoed notification still persists. Any idea on this issue?

[orux]

Is it possible to import the settings and profiles from beta to final?



I just tested the 6.0.0 - the http://www.oruxmaps.com/foro/viewtopic.php?f=5&t=2031#p5269">bug with the echoed notification still persists. Any idea on this issue?

Hi,



Yes, you can use the beta configuration. Create a new profile, in the beta version with your settings. Open the new version, in configuration--profiles restore the saved profiles. Then you can select the previously saved profile from beta version.



About the double notification. It is due to using two or more versions, (free, donate or beta)





There is a new beta-->http://www.oruxmaps.com/foro/viewtopic.php?f=4&t=2475">//http://www.oruxmaps.com/foro/viewtopic.php?f=4&t=2475





orux

[oleolafson]

Hi and thanks for your answer!

Hi,



Yes, you can use the beta configuration. Create a new profile, in the beta version with your settings. Open the new version, in configuration--profiles restore the saved profiles. Then you can select the previously saved profile from beta version.

But the final doesn't "see" the profiles created in beta. Nevermind, I set up the profile manually.

About the double notification. It is due to using two or more versions, (free, donate or beta)

That can't be the reason, that issue also exists even tho there is - and always was - just one version installed.



Update: I did a tour last weekend and the notification for "GPS Signal lost" is played correctly, still the notification for "GPS Fix" is echoed.

[eartrumpet]

I just upgraded the beta, including a scale factor setting for mapsforge symbols. I have to try if properly scale the svg icons.



orux

I just realized that only PNGs with <symbol ...> are scaled, but not <lineSymbol ...>. Those should be included as well for proper scaling.

Best regards,

Tobias