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 - Andrew Heard

Pages: 1 2 [3] 4 5 ... 27
31
Troubles & Questions / Re: Search address without tap and hold?
« on: November 14, 2021, 08:51:16 »
This is really interesting topic.
We already have prepared a server-side feature for creating a completely new "long click" experience: "What is here", where should be united address search + search in nearest interesting poi categories.
This brings me close to removing this "disable long click" option.

And here comes a question: how does this happen @claesh1 that you trigger long click by accident? The slow device with lags? How we may solve this? Increase time necessary to trigger "long click" may help here?
The following users thanked this post: Andrew Heard

32
Locus Map (4+) / Re: Web planner / portal
« on: November 13, 2021, 16:37:32 »
By timestamp I mean that the tracks recorded by gps and imported into the planner have no time references. It is not possible to make simple assessments, for example: "What time was I on top of the mountain?" Or: "How long did it take me to go up and how long to go down?"
I always prefer to use my pc than my smartphone (although unfortunately they now have huge screens) to check my tracks and it would be very convenient to do so in the planner.
The following users thanked this post: Andrew Heard

33
Locus Map (4+) / Re: Web planner / portal
« on: November 13, 2021, 11:32:49 »
Hi there, I am sorry to miss your latest posts. As mentioned by @Menion I didn't receive or just overlooked notification in email.

First of all, thank you for your feedback! From now on I am not publishing release notes here - I have finally integrated it into web planner. You can access it here: https://web.locusmap.app/?show_changelog or by clicking version located in the bottom right of the map.

@francisco - via Points. Yes, it is on our list but not a priority right now. Please, feel free to create it as an idea and collect votes for it - https://help.locusmap.eu/topics/idea/status/all/category/30/sort/popular/page/1

@balloni - sorry, custom icons are not supported.

@lor74cas
1) timestamps - please, can you describe this in more detail? Importing via web planner is not supported ...
2) Undo button - it's on our list but not a priority for next months.
The following users thanked this post: Andrew Heard

34
Locus Map / Re: [APP] - version 4.4.+ ( 23. 9. 2021+ )
« on: November 11, 2021, 15:56:13 »
The pattern (at least) is 4 very experienced users now report the same issue. That's a good start.
I created a Helpdesk entry for it:
https://help.locusmap.eu/topic/26347-shaping-points-get-lost-from-saved-route-planner-tracks
The following users thanked this post: Andrew Heard

35
Locus Map / Re: [APP] - version 4.4.+ ( 23. 9. 2021+ )
« on: November 09, 2021, 09:21:22 »
Offline places ... this is small addition added on the push from @Michal
Problem is, you go into the offline places to add some POI from specific categories. Now the first step always is to go back from the overall search. I would remove the initial overall search when approaching the dialog from the toolbar.

Weird behaviour shaping points was more a question to the other users, I cannot force the behaviour reliably myself...

@tapio
what about settings "Points &tracks > Overwrite exported data"? It should solve the problem with overwriting of exported files ...
Yes. Menion, I explained the danger. User will be OK at first look with "overwrite data" because he thinks it just overwrites old with new versions. But user cannot see that Locus overwrites files created in the same export run - and so he gets less export files than tracks. Say 1000 same named tracks, 1000 different named. Will give you 1001 gpx files. In such a scenario data can silently get lost without noticing.

@tapio - shaping points correctly restored for me (although just recent route, not days before)
is the problem also there for recent route?
Very rarely. Problem is, this issue happens since many versions, but rarely and I can not find a hint why. I have reported it once but it does not seem to be a common problem. What's special about those tracks etc., not yet seeing a reason.
The following users thanked this post: Andrew Heard

36
Free chat / Have messy GPX filenames? Try to auto rename them.
« on: November 03, 2021, 16:04:25 »
Hi,

I created two Tasker scripts which help to rename GPX files to a more unified and timestamped form.

The script rnGPX analyses the gpx file and uses the first found trackpoint timestamp. It applies CEST corrections to that stamp! It uses and declutters the internally found name tag.
It automatically handles collisions (identical file names due to identical internal gpx names).

Backup is crucial here.

See below Reddit thread in the Tasker forum.

https://www.reddit.com/r/tasker/comments/qlw721/declutteringtimestamping_rename_gpx_files/?utm_medium=android_app&utm_source=share
The following users thanked this post: Andrew Heard

37
Locus Map / Re: [APP] - version 4.4.+ ( 23. 9. 2021+ )
« on: October 30, 2021, 23:06:02 »
@Viajero Perdido
thanks for the description. I'll try to simulate it and fix it.

@CabrioTourer
ah, small unfinished problem ... app may take quite a lot of time to compute currently used disk space. And this is the "stuck" you see. Just give it time and it will finish this compute :). Anyway, I've added it to to-do list and will improve it into the next version, thanks!

@Andrew Heard
Well ... this is in the app since begin and I never felt it is necessary to solve it. This page is visible only during recording when you directly display current track statistics. This is not a usual use-case because most often, you only check the side panel or use any dashboard. You are of course correct, that the current solution is not ideal ...
EDIT: will be removed in next version

The following users thanked this post: Andrew Heard

38
Locus Map / Re: [APP] - version 4.4.+ ( 23. 9. 2021+ )
« on: October 30, 2021, 09:56:03 »
@michaelbechtold
In case we never communicated with Google support, these should be definitely a try. But after 10+ years ... we know.
Sharing maps/srtm data between apps ... to be true, I really think that this is a geeky feature for us, people who communicate here about advanced features. 99% of app users don't care about this.

@Viajero Perdido
thanks for the test and precise report!!

  • "Working directories have been changed" .. hmm, this should not happen in this case and seems based on reactions below, you are not the only one. I'll look at it.
  • Reselecting of maps > hmm, absolute path to content has changed. Minor problem, but probably solvable.
  • (almost) empty dir after the move ... seems some maps were still loaded during the process. Damn ...

@tapio
Till Android 10 (include), all should in the end work as before. Thanks for the confirmation.

@balloni55
work with attached photos has to be heavily re-implemented, I know. Fortunately, the system of attachments is so bad, that not many people use it, not many people miss full attachment sync and so I hope, it won't be a problem for now. In 2022 I'll focus on this together with improved "search" and write it better from scratch.

@Andrew Heard
Values are visible during recording because I can't be 100% sure if value "0" means - "such data does not exist" or "currently value is 0".

Yes, the APK value is stuck on 1044. Why? You may easily update the version from the lower value to higher or from same to same. But! you can't downgrade from higher to lower. In this case, you have to un-install the app. So I generate a Beta version with the same ID as long as the downgrade is compatible. So in case of any problem, you may easily restore the previous Beta version.

And thanks for the update test!

@lor74cas
perfect, thanks!
The following users thanked this post: Andrew Heard

39
I've just finished the first draft of a theme that I use on my e-ink phone. The xml and svg files are on gitHub https://github.com/gauvins2/mapThemes

Attached is a comparison of the stock Hike/Bike theme (left) and the hcLayers (right).
 
The following users thanked this post: Andrew Heard

40
Locus Map / Re: [APP] - version 4.4.+ ( 23. 9. 2021+ )
« on: October 29, 2021, 14:14:39 »
TXs for the additional details, Menion.

I think you have to take the bull by the horns head-on!

The whole scoped storage thing is for the Instagram world, only good enough for images and videos.

All other big data sets suffer by deadly performance issues.

So, to summarize your (and similar apps) scenario:
- huge data sets
- random access needed (database and alike)
- shared between different apps
Forgot something?

If I were Asamm, I would create a dummy geo app with request for MANAGE_EXTERNAL_STORAGE, with above justification. Hence no danger to Locus itself, just for the battle with Google.

Quote from : https://support.google.com/googleplay/android-developer/answer/10467955#zippy=%2Cexceptions

Google Play may provide a temporary exception to apps that do not qualify as permitted use designated above, when;

    Use of the permission enables the app’s core functionality; and
    There is currently no alternative method to provide the core functionality; or

use of the privacy friendly alternatives (e.g., MediaStore API, or Storage Access Framework) has a substantially detrimental impact on the critical features of the app that are tied to the core functionality.

    The impact on user privacy is mitigated by security and privacy best practices

The developer must justify in their Console declaration why the Storage Access Framework or MediaStore API is not sufficient for their app’s purpose.

You can fulfil all three conditions. And if Google finally comes up with an enhanced framework that goes beyond Instagram (and alike) use cases, such exception can be ceeded. But not before!

Good luck and kind regards
Michael





The following users thanked this post: Andrew Heard

41
Have you tried OpenAndroMaps with the Elements (not Elevate) theme?

Elements is designed for sparsely-populated areas, and shows elements as soon as their data appears in the file, rather than keeping them selectively hidden until a higher zoom level.

https://www.openandromaps.org/en/legend/elevate-mountain-hike-theme

OAM are very similar to LoMaps, but - ironically - they render better in Locus than Locus' own maps.  That's because OAM and the Locus app both support MapsForge V4, but LoMaps are still stuck at V3.
The following users thanked this post: Andrew Heard

42
Locus Map / Re: [APP] - version 4.4.+ ( 23. 9. 2021+ )
« on: October 26, 2021, 16:53:43 »
Hmm... it doesn't show me those sensor stats (which is good).
The following users thanked this post: Andrew Heard

43
Locus Map / Re: [APP] - version 4.4.+ ( 23. 9. 2021+ )
« on: October 12, 2021, 10:45:09 »
And sorry if I warm up another old topic: The bottom and side bars are quite big using unnecessarily much map space while the zoom buttons that are used much more often are so small it happens repeatedly that I accidentally tap beside them.

I perfectly understand that bigger zoom buttons wouldn't look good, but is it maybe possible to make the surrounding transparent area touchable – to make the buttons in fact bigger without changing the look?
The following users thanked this post: Andrew Heard

44
Locus Map / Re: [APP] - version 4.4.+ ( 23. 9. 2021+ )
« on: October 06, 2021, 10:20:52 »
Menion, it has been mentioned before, there is inconsistencies in tap zones when it comes to points.

In screenshot, when I tap zone 1), it continues with point detail screen. It should do that only on 2) imo.

Everywhere else in the app, on tapping 1), it instantly displays (tracks) on map AND goes there. Which it should do here as well.

Btw., reasonable performance on big offline Geonames file: http://download.geonames.org/export/dump/allCountries.zip
Unpacked 1.4 GB, I was expecting Locus to crash, but I get results after 18 seconds, so it is usable.

I have a suggestion for offline Geonames. The window should pre-select the country file depending on map center, if it exists.
The following users thanked this post: Andrew Heard

45
@karlchick I think it may be better to test for tracktype first, then if grade is not specified (tracktype=~) test for surface.
<rule e="way" k="highway" v="track">
    <rule e="way" k="tracktype" v="grade3">
...
    </rule>
    <rule e="way" k="tracktype" v="~">
        <rule e="way" k="surface" v="gravel">
...
        </rule>
    </rule>
 </rule>

Also, I seem to recall that for OAM maps surfaces are combined in such a way that your rough equivalence of grade=3 and surface=gravel is OK.
The following users thanked this post: Andrew Heard

Pages: 1 2 [3] 4 5 ... 27