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 - tapio

Pages: [1] 2 3
Versions / Re: [APP] - version 3.35.+ ( 7. 12. 2018 )
« on: January 24, 2019, 13:17:05 »
Glad to hear it, perfect.

I've made some final improvements and just published the new Beta version, so if anyone interested ... feel free to try it.

We will publish a new final version most probably on Tuesday, so if there will be any problems that worth it to fix, please let me know.
The following users thanked this post: tapio

Versions / Re: [APP] - version 3.35.+ ( 7. 12. 2018 )
« on: January 22, 2019, 10:07:35 »
New version with search V2 in preparation, give me day or two, thanks :).

And @tapio, no, no optimization on the database is done in app. SQLite re-use empty spaces in DB after removing content, so some kind of "VACUUM" should not be needed. I have tested it on my maybe 5 year old DB and the result was > size reduced from 250 MB to 240 MB and DB benchmark: no result.
The following users thanked this post: tapio

Versions / Re: [APP] - version 3.35.+ ( 7. 12. 2018 )
« on: January 21, 2019, 00:25:14 »
search in the current folder is currently not possible
@menion - I think this is where there is confusion for the user (or at least me) - a simple sort is performed purely within the current folder, but your new advanced sorting methods are across all folders. I can appreciate it will take a lot of time to sort all tracks across all folders, something not possible before now, but the user shouldn't have to incur this time cost if the current folder only has a smaller number of tracks.
The following users thanked this post: tapio

Versions / Re: [APP] - version 3.35.+ ( 7. 12. 2018 )
« on: January 13, 2019, 16:23:03 »
Hi guys, nice feedback, thanks.

I've just today highly improved search in tracks (by distance) and also added "sort by nearest" option for track folders, so hope this helps better handle own imported tracks.

About filtering: I agree that filter for tracks is a lot less powerful then filter for points (mainly caches), but reason: I do not see any useful simply and exactly defined idea on help desk related to this problem, which means for me: no serious interest. And as usually: if I do not need & no interest = not implemented, sorry :).

@Andrew Heard
hehe, I know about the problem with the tap on "Start/Stop" button. I have the same and I just forget to test it more. Just click it more than once and it will work.
Link to attach the image ... hmm you are correct. Probably result of the update of this forum system? Fortunately seems that attachment below as you did, works correctly.

notification about more than one point will do not contain info about distance & angle. Not sure if this is wanted. I think that more than one point simply need a map. Notification just helps to find the right moment, when to look on the map.

The following users thanked this post: tapio

Versions / Re: [APP] - version 3.35.+ ( 7. 12. 2018 )
« on: January 12, 2019, 16:16:06 »
I hope the new version is out soon. I SO MUCH can't wait to the "sort by elevation gain" feature
What about an advanced filter for tracks ?
Now there is just name and date.
I think that distance and elevation gain are very important too.
Something to find out:
How many tracks wirh more then 20 km and more than 1000 mt of elevation I did this year?

Inviato dal mio SM-A520F utilizzando Tapatalk

The following users thanked this post: tapio

Troubles & Questions / Re: No share after manual backup
« on: January 02, 2019, 12:09:51 »
Thanks Tapio,
the issue will be fixed in the next version.
The following users thanked this post: tapio

Themes - Vector maps / Re: [Theme] Voluntary UK
« on: January 02, 2019, 00:38:58 »
New version available in the first post in this thread.
The most significant changes are revisions to dashed lines for better compatibility with devices with later Android versions and the incorporation of Mapsforge v4 (multilingual) versions.
Plus, of course, numerous other small tweaks and improvements.
The following users thanked this post: tapio

Good day Tapio,

rather check latest version:

Facebook tracker was not possible to disable before, but I've found a way so in the latest version, it is already disabled.

Google Analytics is step by step changing to Firebase Analytics, so it will be during 2019 completely removed. So the only tracking system should be "Firebase Analytics", which I hope is safe and secure. It's purpose is to monitor usage of some functions and usage of app.

Wish a good coming year as well ;).
The following users thanked this post: tapio

das einzige was nicht optimal ist. Die Theme von OAM kann man nicht optimal in Presets einbinden. Man kann zwar Elevate wählen aber nicht ob man Wandern, Radfahren, MTB will.
Dazu gibt es einen Vorschlag, bei Bedarf hier voten:
The following users thanked this post: tapio

Themes - Vector maps / Re: mapsforge v4 themes for Openandromaps
« on: December 15, 2018, 15:37:26 »
Well, some of that lies in Locus and can be replicated by Menion once he gets serious to move ahead with V4 (incl. MF POI DBs - address DB would stay Locus "private" in any case, I suppose).
Some other useful stuff from your list Menion should contribute to Mapsforge base, which has been a kickstart for Asamm initially ...
The following users thanked this post: tapio

Versions / Re: [APP] - version 3.35.+ ( 7. 12. 2018 )
« on: December 09, 2018, 15:39:59 »
Heh, oki. Confirmation message reduced to small toast visible over the map for a while, but not anymore caused delay in closing "Presets" screen.

I consider confirmation in Route as important. a) It is needed only rarely, b) function may cause a lot of tasks on background, log of internet request and a big delay in the workflow. Definitely bigger than simple on/cancel dialog.

Problem with GPSies? Cannot simulate, for me it works correctly. What settings should I use? Map center coordinates + screenshot of "search screen" may help. Thanks
The following users thanked this post: tapio

"Filterung der Höhendaten" - kann das nochmal jemand erklären - ist das zur Aufzeichnungszeit? Obwohl - er ermittelt doch die Höhendaten anhand der horizontalen Position, wenn ich "GPS-Daten ersetzen" nehme...

Also: Ich hatte immer "Kein Filter" eingestellt. Nun habe ich "Starker Filter" eingestellt. Ich dachte, wenn ich nun in einem Track die Höhen neu berechnen lasse, dass dann in der Statistik neue Werte entstehen. Passierte aber nicht, ich hatte bspw. vorher 1308 gewonnene Hm und nach der Neuberechnung auch. (Ein anstrengender Tag war das :-)

Ich habe mir das mit Filter selber mal anhand einer realen Runde im Freien ausgetestet. Die realistischten Höhen-Summenwerte bekam ich mit den Einstlellungen "GPS-Werte ersetzen" und "Starker Filter". gerade die zick-zack artigen Sprünge (entweder durch die GPS-Höhe oder auch dadurch, dass die horizontale Lage bei GPS-Empfang sagen wir +- 10 springt und dadurch auch die ermittlte Dateihöhe) sich doch ziemlich auf die Höhensumme auswirken.

Bestest Beispiel man geht immer eben horizontal entlang eines Flusstales, die Höhensumme sollte also 0m ergeben. Trotzdem wird die horizontale Lage der GPS-Koordinaten immer etwa um +/- 5-10 Meter schwanken und z.b. also auch öfters scheinbar an der Schrägkante zum Fluss hinunter sein. Schon hat man trotz bester Lidar-Höhendaten eine Höhe von zb. -2 Meter und danach wieder +2 Meter. Das wiederholt sich ständig und so hat man plötzlich +30 Meter trotz bester Höhendateien rechnerisch gemacht, obwohl man immer eben spazierte.  Und genau diesen (in der Realität nicht vorhandenen) Minisprünge soll die Filterung wegfiltern.

Soweit ich wird diese Filterung aber erst angewendet wenn ein Track gespeichert wird, also nicht schon live bei der Aufzeichnung. Bei der Speicherung wird ja bereits auf deine Lidar-Dateien zurückgegriffen, dadurch hat sich nachher mit "Höhen neu berechnen" nichts geändert, da dies ja genau dieselbe MEthode ist. Diese würde nur was ändern wenn du im Höhenmanager per per GPS (und nicht per Höhendateien) die Höhen aufgezeichnet hast. Oder wenn du von irgendwo im Internet einen Track her hast, der seine eigenen oder gar keine Höhen hatte.
The following users thanked this post: tapio

Versions / Re: [APP] - version 3.33.+ ( 26. 9. 2018 )
« on: September 28, 2018, 19:30:56 »
Weird, just today morning (GMT+1) I've published new 3.33.1 version

But if I see correctly, it is still not available for download :/. Most probably some issue on the Google server. So just for your information ... the version is out and the issue is not on our side. Thanks.

I thought it will be this issue ;).
The following users thanked this post: tapio

Versions / Re: [APP] - version 3.33.+ ( 26. 9. 2018 )
« on: September 27, 2018, 00:23:24 »
The issue with the start of navigation: found and fixed. Unfortunately, there is currently no workaround, except to use Route planner to create navigation route and avoid "Navigate to". The new version will be published most probably on Friday. I just want tomorrow collect some more problems (if any appear).

in case, the distance between points is less than 0.5m, app display breaks instead because there is the high risk of incorrect gradient values. And this is your case. You have defined in recording profile distance = 0m? Suggest to set there at least 1 (m) to avoid this issue.
The following users thanked this post: tapio

[DE] - deutschsprachiger Forumsbereich / Re: Mein subjektives Fazit
« on: August 31, 2018, 20:07:08 »
Ist jetzt auf meinem Handy. Bevor ich installiere, werde ich mir wohl erst eine SD -Karte kaufen müssen. Das war aber sowieso vorgesehen  ;D
The following users thanked this post: tapio

Pages: [1] 2 3