Movescount export button grayed out

djibarian

@mff73 yes when I said I opened the thread I was referring to the feature request to be able to export POIs from the new Suunto app. That’s somewhere in the forum. And you’re right about the developers answering, but that means nothing. They don’t have voice in the company’s direction, as they already stated. But good to hear from them anyway! Let’s hope that the request stirs. I guess one way or another they have to add that functionality in the Suunto app.

Mff73

@djibarian
Let’s hope, but I am pretty sure it will come. When? That is the question.
If you have Android rooted phone, POI are not so hidden in SA database.
text alternatif

djibarian

@mff73 I had a quick look at rooting an android phone but it looks pretty complicated at first sight, if I’m not wrong. I have a few of spare android phones to try. But I can see in your screenshot that data is truncated, or is only a display issue?

Mff73

@djibarian said in Movescount export button grayed out:

But I can see in your screenshot that data is truncated, or is only a display issue?

No, I hide coordinate for privacy reasons.

If you speak about altitude, I hope you really don’t care about 10 digits for altitude point

margusl

@djibarian said in Movescount export button grayed out:

If you look into them, you’ll see that the elevation is something like “1648.98374982374942” (same for location), but in Movescount you see only “1649”.

POIs recorded with Ambits never had elevation so can’t argue with that, but all the POIs I have saved with my Ambits and are still in my MC web POI table share exactly the same precision for lat/lon as POIs in GPX files from exported dataset - 6 decimal places for decimal degrees. And it doesn’t make sense to go beyond that.

Anyway, scarping MC POI table and formatting it into GPX, WPTs with just lat/lon, time & description, only tested with Chrome - https://gist.github.com/marguslt/4ad715ae43475cd90031c29f9ff1f039

Dimitrios Kanellopoulos

@margusl 6decimals is the precision most of the cases.

Fenr1r

@dimitrios-kanellopoulos What’s that (notional) precision in metres on the ground?

Dimitrios Kanellopoulos

@fenr1r notional from GNSS? Maybe 3.5 meters at best for commercial usage. But I cannot say this with confidence.

Many documents report less but from many phones (with double frqs etc) I never got less.

Maybe I am wrong. I am not sure.

But there is also software on top…

6 decimals on lat long I think you can have meter or less precision. I have a link for that

Fenr1r

@dimitrios-kanellopoulos said in Movescount export button grayed out:

6 decimals on lat long I think you can have meter or less precision

Seems like a reasonable stopping point. Thanks.

margusl

For latitude 1 degree is about 111 km ==> 0.000001 decimal degrees is 0.000111 km (11.1 cm). Same for longitude at equator.

margusl

@mff73 said in Movescount export button grayed out:

If you have Android rooted phone, POI are not so hidden in SA database.

Not sure if something has changed or has this been always the case, but apparently there’s no need to root to get access to SA db and pois table, it’s all included in stt-dump (taping on Settings >> Version).

$ sqlite3 -header amer_app.db "select * from pois"
creation|modified|longitude|latitude|altitude|name|type|activityId|country|locality|watchEnabled|key|syncState|deleted|remoteSyncErrorCode|watchSyncErrorCode
1611574952|1611574952|25.4796848796365|65.0148620160951|15.42|Heikinkatu 9, 90130 Oulu, Finland|40||||0|600eaea82608154740f27006|PENDING_WATCH|0||
1611574969|1611574969|17.8476172592436|59.3023613607754|11.82|Lindöbrovägen 6, 178 93 Drottningholm, Swe...|0||||0|600eaeb92608154740f27007|PENDING_WATCH|0||
1611574989|1611574989|24.8601936378492|59.379607477896|47.39|Rannakivi Tee 23, Rae, Estonia|20||||0|600eaecc2608154740f27008|PENDING_WATCH|0||

Mff73

@margusl
Effectively. I never had a look at this dumb content