Messages

Thanks for taking your time to look at this!

The correct draw order is what shows in GE. That is, draw order is from bottom up. However, in this case and using GE it doesn't matter because the layers is elevation enabled i ArcGIS. The layer that needs to be drawn on top have the elevation 3. The next layer have elevation 2 and the baselayer containing polygons have elevation 1. Locus draws layers based on the order in the KMZ, meaning the top layer draws first, then second, and lastly the bottom one overshadowing the other. This could easily be resolved by rearranging the layers in the program used for creating the maps and layers, but only if all layers are packaged in the same KMZ-file. This solution is less desirable however since it means breaking your workflow in the GIS program by starting to rearrange layers and making the map there inverted.

The draw order of multiple KMZ-files seem to be alphabetical however, meaning you need to rename your files to control the draw order.

With this said, and considering this for a bit i realize this is not that big of an issue. There is a solution and i can work with that. Especially considering most other things i need Locus to do, it does without any problem. Id be stuck with clumsy laptops in my fieldwork if there were no Locus! So keep up the great work!

Thank you! The dots disappeared, didnt even consider those settings would affect KMZ files.
I attached a file for testing, and a screenshot showing the problem.

Is there any possibility of changing or control the order in which locus draws KMZ layers? The files have elevation information placing the layers in the correct order ontop of eachother, but Locus wont draw them this way. The files contain polygons and polylines. The polylines needs to be drawn ontop of the polygons or the lines will be hidden.

The files are exported from ArcGIS without clamping the features to the ground.

Also, is there any way to implement the possibility to change the way Locus draws KMZ files or their symbology? As it is now Locus puts a point at each start or end of a line. Any option to hide or change this would be great.

Hello!
Im trying to find a way to use my high resolution elevation data i Locus. I have tried to convert my .asc-files to .hgt, but i seem to loose alot of data. My 2 meter grids turn into 30 meter grids. Is there any way to use another format that can handle those resolutions? Maybe anyone tried and found any solution or workaround regarding the srtm format?

Well, this is spot-on. I have been trying to come up with ways to make this type of map import/export to work but never got quite this far in the thinking I tried a quickie one-level map with this method and it seems to work nicely, but as you say, its not really userfriendly or streamlined... GIS-ok. webserver and that stuff-not so much, but i got it working. I will look into this method more for the advanced maps i want, and use the image cutter for the ones i need fast and easy.

Thank you very much for this!

This worked nicely! loaded and displayed with no problems. However im getting a serious loss of color information by this method. Have you see this problem too? Could this be due to source file, .png? Should i convert that first? I did not convert from ozi format, but rather made my own georeferenced raster image directly and ran through the image cutter.

Ah, nice. i must have missed this converter when i looked for a solution. I will try if out later, thanks
About the .shp, yes you are correct, its the arcGIS vector format. I use this in my work for isobaths for depth charts and such.

Adding a small suggestion to the list... How about considering implementing support for some type of georeferenced raster image format? or even better .shp support... Is this even doable?

Seems like the option to turn off logging when speed<0 is not working properly for some reason like you say. Neither did my suggestion. Even if i set the logging time to a huge amount of seconds and the distance for log entries to 10 meters to stop it logging the small movements of gps drifting the track was recorded anyway within a small area. As i imagine it it should just log a point every 10 meters (or 5 or whatever, setting based) and effectively ignore the time passed. (option to choose logging method might be good?).

I tried the new version and its a huge improvement for me with the adress searching! cseu:s idea to link the checking to "offline mode" sounds like a good idea and might be worth considering.

Thanks for incredibly fast replies and fix! Keep up the great work!

Small suggestion... Not sure if this works for your problem since i havnt tried it, but it may help to change the logging interval in meters to make up for the gps position drift while not moving.

There may be a simple fix that i missed, but i was wondering if its possible to turn off Locus searching for an adress on a long press on the screen? I use offline maps and have no use for it, instead i press by mistake alot and have to wait for the phone and program to realize that i have no connection. This get very annoying when i need to scroll back and forth fast and instead having to wait for this loading time.