OruxMaps

Quote from: eartrumpet post_id=12896 time=1519075975 user_id=518
The new hillshade map looks better, but is hardly usable. At this speed I would prefer the old algorithm, and, if possible, the above mentioned idea of adding zoom level min/max settings.

Quote from: "orux"

Quote from: eartrumpet post_id=12896 time=1519075975 user_id=518
The new hillshade map looks better, but is hardly usable. At this speed I would prefer the old algorithm, and, if possible, the above mentioned idea of adding zoom level min/max settings.

Hello,



There is a new beta.



I want to keep the new one. With modern devices (one plus5 for example), the entire screen is painted in 2-4 seconds. The old one is the default, but I added a new setting in maps--relief maps settings.



There is already a setting for composite maps in settings - maps - zoom settings. Limits the maximum zoom level to the maximum of the minimums. In this case, relief maps have a maximum level of 16.



orux

Quote from: eartrumpet post_id=12906 time=1519160162 user_id=518
Strange, with a BQ X5+ which isn't that old it takes one whole minute at ZL14 with the new algorithm and just hillshade. Old algorithm, all else equal 2 seconds.



The zoom limit option you mentioned doesn't do what I would like: I want to have a mapsforge map with all ZL that are available with this map, and added hillshades at only some levels, e.g. 12-15. That would make the map render much faster at low levels, also I find shading distracting there. And again at high levels, where map details and contour lines are more important.

Quote from: Maki post_id=12917 time=1519246004 user_id=100
I briefly tried beta8 on a GPad 8.3, so not exactly a high end device nowadays and the new algorithm is plenty usable wit 1 arcsec DEMs. I just have sometimes some random tiles that take a few seconds to appear. I suppose that some things are strongly device-dependent.

The new algorithm is much better but I still see errors at tile borders. Looks like the calculations are vectorised, looks nice but there are arguments in favour to use the raw pixels with nearest neighbour interpolation (mostly not to give the user the impression of a higher than real precision): I'm agnostic in this, my maps use a 5 m grid and a continuous tone variation so I just don't have the problem. Maybe let the user choose between the two if possible.



Please, pretty please, do not tell the user "if you touch this you need to flush the cache", just do it as soon as the preference change is confirmed.



The measure tool is exactly what I expected, except for the use of % as slope unit. % works well when dealing with low inclines and as such is used on roads, but on slopes we commonly use degrees, at least in the ski touring/alpine world where the request was born.



Please also have a look at the dedicated thread about slope map request.



Thanks,

Maki

Quote from: Maki post_id=12965 time=1520086272 user_id=100
Beta 11 multimaps are broken for me. The old ones I had created disappeared and I can't create new ones, they are not saved. Or they are saved but not shown, in any case I don't see them.

I don't understand the zoom limits in the multimap creation phase. Why am I limited to ZL 16 for the slope map and hillshade? Makes no sense, it's common to upsize hillshading.

Quote from: Maki post_id=12969 time=1520099568 user_id=100
I came from Beta 10, but I really didn't use it, due to lack of time I just tried a couple of minutes the degree option with measure tool. Anyway I cleared app data and started from scratch, it works now. The multiply option is still broken, it only works when opacity is set to 1.0 which generally has a too strong effect: if you set it to 0.5 you should just weaken the effect but you actually lighten the whole map. Try it in any image editor.



When activating the slope maps you said we have to also set the dem resolution to the highest setting, which isn't the default. Anybody who isn't reading the forums wouldn't know. Automatically doing it (with a warning) as usually would be the best option.



I also noticed that I had to manually refresh the map list to see these special maps.

Quote from: Maki post_id=12972 time=1520105808 user_id=100
I'm not sure what alpha channels have to do with this, they are usually used to manage transparency.

The "multiply" thingy I'm referring to is the one explained here:

//https://tilemill-project.github.io/tilemill/docs/guides/comp-op/

or here:

//https://docs.gimp.org/en/gimp-concepts-layer-modes.html



How are you applying opacity?

Quote from: orux post_id=12927 time=1519400241 user_id=2


That device has a good CPU, strange.



Midium level devices, like huawei p8, takes 8-10 seconds the entire display.

Quote
About zoom levels; it is easy, I will add that feature.

Quote from: Maki post_id=12976 time=1520114088 user_id=100
If I understand correctly you are multiplying alpha channels by themselves. That's not the way to do it. Source alpha should be applied to source image, destination alpha to destination image. Then you multiply the results. In other words if one image is fully opaque the result has to be fully opaque.

Quote from: Mapper-Alps12 post_id=12979 time=1520149492 user_id=5155
Hello Orux,



as I mentioned here http://www.oruxmaps.com/foro/viewtopic.php?p=12932#p12932 it takes with beta11 too long to show the relief map when I use the high precision DEM. Here a solution would be very welcome.



With beta11 the "Center map dialog" function with all type coordinates (degrees, utm, swiss grid, mgrs,...) doesn't work for me, same problem like I told you here http://www.oruxmaps.com/foro/viewtopic.php?f=4&t=4477&start=100#p12460. I've sent several bug reports.



Also I have the same problem as Maki wrote with Multimaps. In beta10 it worked fine. But in beta11 I'm not able to create any Multimap. Also I can't see the zoom numbers in the map creation dialogue for Multimaps. This worked well in beta10.

Quote from: eartrumpet post_id=12975 time=1520113973 user_id=518

Quote from: orux post_id=12927 time=1519400241 user_id=2


That device has a good CPU, strange.



Midium level devices, like huawei p8, takes 8-10 seconds the entire display.

I tested with other DEM files, as I too use the high quality mentioned here. (//http) But still painfully slow with new algorithm, also with different relief map resolution settings. BTW, it would be about time to change the title of nearly all settings here from "relief map" to "DEM based maps" or similar.

Quote
About zoom levels; it is easy, I will add that feature.

Thanks, that's good to have, although I would prefer to have this setting not in the composite maps (also some probably like it there), but in the relief map settings, because then it would be applied also to the "apply hill shadows" setting in the "Mapsforge settings". Having it in composite maps results in two problems: I have to generate composite maps for every mapsforge map, instead of just applying one setting, and also cluttering the available maps menu. The other - mapsforge tiles are not at native device ppi size with composite maps (probably 512px instead of 768px with my device). The results are similar as before this was fixed:

http://www.oruxmaps.com/foro/viewtopic.php?p=10842#p10842

So I would suggest to zoom other maps to the tile size of mapsforge maps when they are used in composite maps. And also to add a zoom-min/max setting in the relief maps settings.

Best regards,

Tobias

Quote from: Mapper-Alps12 post_id=12983 time=1520184583 user_id=5155
Hi,



I use .hgt-files with more Resolution. The format is the same like the 1', but the files are much larger, ca. 25 MB. You can download the high resolution DEM files in .hgt-format for Spain here http://data.opendataportal.at/dataset/dtm-spain, just choose the "DTM Spain Mainland,1 sec" then you will find the .hgt-files here https://drive.google.com/drive/folders/0BxphPoRgwhnoRVVwT1N4bzc2RnM. They're created of LIDAR, more details and a discussion you will find in the OAM-Forums here https://www.openandromaps.org/oam-forums/topic/neues-genaueres-hoehenmodell-fuer-oesterreich (in German). The reason why we prefer to get this much better DTM working with your app is that you get these high precision LIDAR files for many European countries, e.g. Austria, Germany, Itlaly, Luxemburg, Slovenia und Spain.

Quote from: Mapper-Alps12 post_id=12983 time=1520184583 user_id=5155
Thanks for trying to find a solution for the Center map dialogue. It worked well up to beta10, it also works fine in the current version 7.2.7 you can download on your Homepage.

Quote from: Mapper-Alps12 post_id=12983 time=1520184583 user_id=5155
The Multimaps I try to create are 2 MBTiles maps. I can add them in the multimaps creation dialogue but after that they're not in the map list, as a user described before me here. This worked well in last beta10 and ever before. I never had any problems, neither to combine a mapsforge-map and a raster map nor 2 raster maps. Everything worked fine.

Quote from: orux post_id=12982 time=1520176696 user_id=2


where can I download high resolution DEM files in HGT format? I only see them in tiff format. I would like to test them.

Quote
It is possible to add a new setting in DEM based maps to adjust min/max zoom levels.

QuoteThere are maps that can be used at different tile sizes (not all), but yes shadows/slopes/relief. When a composite map is created, the base map tile size should be used, but you are right it is not working fine if it is using 512px if base map is a mapsforge map.

Quote from: orux post_id=12980 time=1520174242 user_id=2
What am I missing?