Dylan72 forum posts in last 60 days

I've spent the last few days looking at crazy tracks on ka72 and refining the data filters. (Along the way I discovered an anonymous user from Hong Kong who uploaded the identical same track around 20 times somehow expecting a different result when his/her/their cheap gps didn't store it's data in m/s but instead km/h.)

I'm pleased to report that the site is now more robust to ****ty data from cheap GPS devices, and the more observant amongst you may have already noticed that it now visibly complains when you try to upload a gpx file from Garmin Connect when the fit file is a much better source of data.

If you have the time and the inclination, feel free to use the "Report a track issue" link that appears on every single track details page on the site to let me know about ****ty results. I'm on a ****ty result hunt this weekend, and the more I stomp the better.

Also a reminder that there is actually a Moderator role on the site that grants access to Pro tools in exchange for your own efforts in tracking down ****ty data. If you are interested in becoming Ka72 moderator, let me know by email at [email protected] and I'll introduce you to the world of **** wrangling.

I'm actually happy as a pig in **** to be working on this. I've been busy with other stuff the last few weeks and the break to focus on data quality on the site is actually more refreshing that it sounds. (Or smells?)

Dylan.

Sorry all, a scheduled update I wasn't aware of at my webhost failed and broke the site for a period of time. Thanks to everyone who reached out. When I became aware of the outage, I had the site back up and running again ASAP, but it was unfortunately offline for some time.

I had to do some investigation just to ensure the outage wasn't malicious in nature (ka72, like most websites, has a constant stream of malicious activity attempting to break into the site) but it seems from my webhosts's response, that it was entirely their fault. I'll put something in place so I find out about this kind of disruption sooner next time it occurs.

Cheers,
Dylan

Thanks for pointing this out once again. Most browsers changed the way they operate back in 2022 to make it hard for you to post data to other sites without their explicit permission. GPSTC has not been updated since then. I've been in sporadic communication with the GPSTC devs about this issue since then, but so far we haven't resolved it. It's not hugely difficult to click the button twice, but obviously I'd prefer a more streamlined experience, and it's a big priority for me to resolve, but unfortunately not under my control.

We continue the conversation.

In the meantime, there is a workaround, and I promise it will be sorted out sooner or later.

Dylan