# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 17
# self = https://watcher.sour.is/conv/7bhzgaq
movq
www.uninformativ.de
View Thread
Wasted a good week fiddling with GPS but eventually found Sean Barbeau's database: gopher://uninformativ.de/0/phlog/2023-10/2023-10-26--smartphone-and-gps.txt
movq
www.uninformativ.de
View Thread
Wasted a good week fiddling with GPS but eventually found Sean Barbeau's database: gopher://uninformativ.de/0/phlog/2023-10/2023-10-26--smartphone-and-gps.txt
movq
www.uninformativ.de
View Thread
Wasted a good week fiddling with GPS but eventually found Sean Barbeau's database: gopher://uninformativ.de/0/phlog/2023-10/2023-10-26--smartphone-and-gps.txt
lyse
lyse.isobeef.org
View Thread
@movq How far off was your GPS location?
movq
www.uninformativ.de
View Thread
@lyse Depends, sometimes it’s within specs (you can expect something like 3 to 15m accuracy 68% of the time, IIUC), sometimes it’s 200m off (like in my test this morning) and doesn’t get better even if you wait and don’t move. But I admit that was an extreme case that I’ve only seen a couple of times.

Obviously I won’t share my real GPS tracks here. 😅 So I made a couple sketches. On a good day, it would look something like this:

https://movq.de/v/f95a556bed/sketch0.png

Green being a GPS track made with a good tracker. It’s already wobbly, even if you’re walking in straight lines, but it mostly matches your actual path. Red is the bad phone. Maybe I could have lived with this if it had been a cheap phone (which it wasn’t). In fact, my previous phone was *way* cheaper but had much better results, comparable to the green line, so this was quite a bit unexpected and disappointing.

On a bad day, it would look more like this:

https://movq.de/v/f95a556bed/sketch1.png

Basically useless.

And most of the time, it would take several minutes to get a “fix” in the first place. Meaning I was standing in front of my house for 5-10 minutes, waiting. The better phones get a fix within 5-30 seconds.

(I suspect that somehow A-GNSS was broken or partially broken on the bad phone, but no idea, really. The GPS hardware is a blackbox.)
movq
www.uninformativ.de
View Thread
@lyse Depends, sometimes it’s within specs (you can expect something like 3 to 15m accuracy 68% of the time, IIUC), sometimes it’s 200m off (like in my test this morning) and doesn’t get better even if you wait and don’t move. But I admit that was an extreme case that I’ve only seen a couple of times.

Obviously I won’t share my real GPS tracks here. 😅 So I made a couple sketches. On a good day, it would look something like this:

https://movq.de/v/f95a556bed/sketch0.png

Green being a GPS track made with a good tracker. It’s already wobbly, even if you’re walking in straight lines, but it mostly matches your actual path. Red is the bad phone. Maybe I could have lived with this if it had been a cheap phone (which it wasn’t). In fact, my previous phone was *way* cheaper but had much better results, comparable to the green line, so this was quite a bit unexpected and disappointing.

On a bad day, it would look more like this:

https://movq.de/v/f95a556bed/sketch1.png

Basically useless.

And most of the time, it would take several minutes to get a “fix” in the first place. Meaning I was standing in front of my house for 5-10 minutes, waiting. The better phones get a fix within 5-30 seconds.

(I suspect that somehow A-GNSS was broken or partially broken on the bad phone, but no idea, really. The GPS hardware is a blackbox.)
movq
www.uninformativ.de
View Thread
@lyse Depends, sometimes it’s within specs (you can expect something like 3 to 15m accuracy 68% of the time, IIUC), sometimes it’s 200m off (like in my test this morning) and doesn’t get better even if you wait and don’t move. But I admit that was an extreme case that I’ve only seen a couple of times.

Obviously I won’t share my real GPS tracks here. 😅 So I made a couple sketches. On a good day, it would look something like this:

https://movq.de/v/f95a556bed/sketch0.png

Green being a GPS track made with a good tracker. It’s already wobbly, even if you’re walking in straight lines, but it mostly matches your actual path. Red is the bad phone. Maybe I could have lived with this if it had been a cheap phone (which it wasn’t). In fact, my previous phone was *way* cheaper but had much better results, comparable to the green line, so this was quite a bit unexpected and disappointing.

On a bad day, it would look more like this:

https://movq.de/v/f95a556bed/sketch1.png

Basically useless.

And most of the time, it would take several minutes to get a “fix” in the first place. Meaning I was standing in front of my house for 5-10 minutes, waiting. The better phones get a fix within 5-30 seconds.

(I suspect that somehow A-GNSS was broken or partially broken on the bad phone, but no idea, really. The GPS hardware is a blackbox.)
movq
www.uninformativ.de
View Thread
Let’s see if I can dig through all this:

https://www.youtube.com/playlist?list=PLGvhNIiu1ubyEOJga50LJMzVXtbUq6CPo

🤔
movq
www.uninformativ.de
View Thread
Let’s see if I can dig through all this:

https://www.youtube.com/playlist?list=PLGvhNIiu1ubyEOJga50LJMzVXtbUq6CPo

🤔
movq
www.uninformativ.de
View Thread
Let’s see if I can dig through all this:

https://www.youtube.com/playlist?list=PLGvhNIiu1ubyEOJga50LJMzVXtbUq6CPo

🤔
lyse
lyse.isobeef.org
View Thread
@movq Indeed, that's terrible! Back in the days when my mate recorded the bike tours, we noticed that sometimes the reception was really poor. Whenever it took about three to five minutes or so until the location was found, we knew, the GPX is not going to be great that day. Sometimes there was a jump of several kilometers right after starting the track when we couldn't be bothered to wait for enough satellite contact. Our top speed was astronomically high. :-D
prologic
twtxt.net
View Thread
@movq Speaking of GPS stuf... I need to build (_hopefully open sourcing it_) a "Geocoder", is that what we call it? A way to auto-complete an address to a GPS coordinate.
prologic
twtxt.net
View Thread
@movq Speaking of GPS stuf... I need to build (_hopefully open sourcing it_) a "Geocoder", is that what we call it? A way to auto-complete an address to a GPS coordinate.
prologic
twtxt.net
View Thread
@movq Speaking of GPS stuf... I need to build (_hopefully open sourcing it_) a "Geocoder", is that what we call it? A way to auto-complete an address to a GPS coordinate.
prologic
twtxt.net
View Thread
And before anyone asks me why I need to build this, self hosting, privacy, etc. No I haven't found any good self-hosted solutions either i can just "borrow", so I'll have to build my own 🤣 Thinking of ingesting the data (addresses) into a Bleve database and using that to drive the "search"
prologic
twtxt.net
View Thread
And before anyone asks me why I need to build this, self hosting, privacy, etc. No I haven't found any good self-hosted solutions either i can just "borrow", so I'll have to build my own 🤣 Thinking of ingesting the data (addresses) into a Bleve database and using that to drive the "search"
prologic
twtxt.net
View Thread
And before anyone asks me why I need to build this, self hosting, privacy, etc. No I haven't found any good self-hosted solutions either i can just "borrow", so I'll have to build my own 🤣 Thinking of ingesting the data (addresses) into a Bleve database and using that to drive the "search"