Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - sonny

Pages: 1 2 [3] 4
Troubles & Questions / Re: option to dim/darken the map layer?
« on: January 26, 2017, 11:20:49 »

black background, opacity of map: 30%

You can see that the waypoints in the map are not very easy to recognize, the contrast will be even worse if you're out under sunlight. Now if we could quickly dim the map (by using a slider or a button to apply a predefined opacity value), you can see how easy the waypoints now could be seen.

I simulated the dimmed screenshot by choosing "Blank maps > Dark variant" as basemap, the original street map as Overlay and set it's opacity to 30%. Much to complicated for the average user, to many clicks for just to dim the current map.
But if you would really implement such a feature that's would be the method to implent the dimming   :D

Troubles & Questions / option to dim/darken the map layer?
« on: January 25, 2017, 15:34:31 »
on some maps it is very difficult so recognize point icons. They are very good "camouflaged" within the layout consisting of streets, paths, landmarks etc of the map. So is there an option within Locus quickly to dim/darken the map by a fixed value (e.g. 50%) or by the use of a slider but not darken the point icons?
So the point icons would be better contrast the the map's layer.

Hi, I'm using the GSAK-database addon for Locus. It's a pity that it seems to be that its delelopment was stopped.

I noticed the following little bug. When opening a cache from a GSAK-databse using this addon in Locus and looking at the Logs tab of the Cache:
Each logtype has its correct icon left of the logtext. But NOT "Archive" logs. When loading the same cache online with Geocaching4Locus addon, then this "Archive" log has the correct icon.

Would it be posssible for Locus to recognize even  this maybe "malformed" Archive logs of GSAK-addon and put an icon next to the log and below in the Quickinfo-window of a cache?

Troubles & Questions / Sunrise/Sunset Values for Dashboard?
« on: September 15, 2016, 22:02:53 »
Sometimes I want to know what time the Sunrise is when hiking outdoors. I know, I can use the Weather-function of Locus. But just if an Internet connection is available which is not always true outdoors.

The only offline sunset-info in Locus I found, is the "Sunrise/Sunset"-entry in the large, top text field. But I have to switch to this entry first cause usually I'm displaying other stuff there. And not the (for me prefered) time OF sunrise (e.g. 19:24h) is displayed, but the time TO (e.g. 1:58h) sunrise, which is changing every minute. 

Wouldn't it be possible to provide both, a sunrise- and sunset- item for the use within dashboard? That would be an ideal, offline solution!

I want to clearly identify the Navigation route an the map, therefor I can adjust Settings > Navigation > Style on map.

But this Style right now is just used for Navigation mode "Navifation". Not for "Guidance (commands)" and "Guidance (no commands)". Please use the line style also for these 2 Guide Modes.

First of all:
- Just download the 1"-sec versions of the DTMs (or if you have little available memory on your phone: 3"-sec).
Not the 20m and 50m-versions, Locus can not use them.

- Yes, copy the .hgt-files into data/srtm folder of Locus.

- If there are already equal named files in this directory, just overwrite them (they have been automatically downloaded by Locus before and are based on less accurate SRTM-data)

You don't have to copy each .hgt-file of a country, just for the areas you are interested in.
Each elevation file (.hgt) represends exactly 1° x 1°, which could automatically derived from the filename. The filename specifies the southwest corner, e.g. "N47E014.hgt" represends an area from N47° to N48° latitude and E14° to E15° longitude.

- If you copied them I recommend to start Locus and once execute
Menu > Settings > Miscellaneous > Clear temporary data > (check all points)
to make sure, no old cached elevation or shading remain.

If the country's Lidar-elevation data is Opendata, then maybe. But those of Switzerland, France are not available free. And for Italy (exempt South Tyrol) I'm unsure about the situation. And if Opendata - where to find LiDAR sources of the whole country.

Maps / LiDAR- Digital Terrain Models (DTM) of European countries
« on: September 11, 2016, 21:17:19 »
Dear Locus map creators and users!

I want to tell you, that I've created several Digital Terrain Models (DTMs), which are based on precise Opendata LiDAR-elevation data of the country's Geographical Institutes. Right now these are:
The improvements in accuracy, quality and fine details of my model's elevations compared to those of the popular SRTM-datasets are enormous. Especially in mountainous terrain. Take a look at the following Map comparisons: Maps based on LiDAR-DTMs to maps based on SRTM-DTMs:

You can use these new DTMs to create improved, more accurate contour lines in maps. Or you can copy the files for the area of your interest into the correct folder of Locus to improve dynamic elavation values and the shading of the maps in these areas.

I spent many, many Hundreds of hours during my leisure time to search for new Opendata source files, get in contact with national public authorities. To download those giant amounts of source data. To search for errors, plug gaps within the data, compile, resample it and create files in useful formats. To finally provide them to you, FOR FREE.

It would make me very happy, if you honor this work by supporting me with a Donation. I’ve created a DONATIONLINK via PAYPAL:


I just controlled bicubic interpolation using Global mapper. Same result here, also Global mappers maximum is even 1213 m for the 1206 peak. And funny detail: The 1213m maximum is at a position, where in the .hgt file the edge of the peak-pixel is about 50 meters away :o

I also looked at the result using bilinear interrpolation: Using this method, each map-pixel is <=1206 m

Just for interest: Is there a reason why bicubic is better for elevation files than bilinear?


I'm using Global Mapper for the creation of the .hgt files. i can define any raster width i like. For my test-hgt for example I used 2200x2200 values which equals about 50m x 35m. (By the way: Does a .hgt file for use in Locus have to be same amount of rows and colums? Or is it possible e.g. to create files 1600 x 2200 - which equals about 50m x 50m - which suits much better to the original 10x10 m elevation files, which are free available for Austria.

Global Mapper has several options to resample the elevation values of the new, wider raster. One is: take the maximum elevation within a box of e.g 5x5 elevation pixel of the source file. So I can make sure that each maxiumum elevation of a peak is still in the new .hgt file for Locus.

But I have to see if this is really the best method now I know that Locus is adding some meters in altitude in the center. I have to take care the resampling method of Global Mapper as well as these of Locus to get optimum offline elevation files. Some tests following  ;)

But how can it be that if a peaks' elevation-pixel of the .hgt file has an elevation for example of 1500 m.
And every elevation pixels around in a 4x4 raster (which are used for bicubic interpolation) are much meters lower.
So in my opinion just the map-pixel which is in the middle of the elevation pixel should have an exact altitude of 1500 m

Each map-pixel around should be lower, shouldn't they? Or am I wrong that the map-pixel which is exactly in the center of an elevation-pixel should have the same elevation values (1500 m). Or in other words: How can a map-pixel be higher than the highest elevation-pixel?

But maybe I'm not quite understanding bicubic interpolation, and I've to read some sites about this filter method in detail ;)

I'm experimenting in producing more accurate .hgt elevation files compared to the ones downloaded with Locus especially for mountain terrain in Austria.

For example there'e a mountain peak with true elevation=1206 m
The highest peak of this mountain in the original .hgt-file of Locus=1185 m
The highest peak of my new created .hgt-file of this mountain=1206 m

But now the strange thing: When using my new .hgt-file in Locus, the map show me a maximum of 1210 m at the location of the peak. How can this be, since the highest spot in the .hgt file is 1206 m and each point on the map should be <=1206 m?  :o
What method of filter is Locus using to calculate the high at the exact cursor's location out of the elevation-values around this location of .hgt-file?


I usually have the option "Hold map center" on when guiding to a Waypoint or Geocache. But there's the following annoying behaviour:
When opening the infosite of this waypoint and then clicking onto the map-icon on the buttom to return to the map screen, the "Hold map center" is suddenly switched off! (I could alternatively press the "back"-Button of my phone. Here the hold-option is still turned on. But I do not always remember this and just click the more intuitive Locus "map-icon" on the bottom.

A satisfying solution would be: If pressing the "map-icon", jump to the waypoint's coordinates. But keep the "Hold map center" option switched on. Because of that the map would jump to the actual GPS-position after 5 seconds.


I noticed that a few of the Locus-Waypoint icons having a wrong or missleading Hotspot (the pixel that is exactely marking the coordinates an icon's waypoint on the map).

These are the "x"-icon, the ring-icon, and the circle-icon of each color. Their optical hotspot is in the center of these icons. But Locus uses a Pixel at the bottom of these icons as the coordinate hotspot

Look at following example Screenshot:

you can see, there is a difference of about 60 Meters in reality between the center of the icon and the real coordinates of the icon's waypoint indicated by the cross-hair. In extreme cases somebody could by mistake think that the waypoint is somewhere within the parallel street of a town.

Please correct the Hotspots of these icons.

The other Locus icons (arrows and marker-like icons) as well as the Garmin-icons, which having their optical hotspot in their center, are already treated correctly in Locus.

Pages: 1 2 [3] 4