For nostr-ava I think I'm going to lean into a DVM model to analyze gpx files. Here's the flow I'm thinking 1) user uploads a gpx file in a client and adds relevant metadata around it (name, description, etc...) 2) GPX files is uploaded to a blossom server and the location is stored in the original note 3) user can then request analysis of the gpx file by creating a DVM job request. This will allow multiple ways to analyze (there's a lot of cool python libraries to transform GPX files), and also allows DVMs to use output from previous DVMs to do meta analysis. Clients can pull in the original notes + any DVM results per activity and display them as they see fit. I'm envisioning DVMs for run matching, analyzing your progress throughout the year, comparing with other similar routes (e.g. segments and KOM stuff) #nostrava #running
Yeah I was using the python-garminconnect in a crude way to pull the data for the garmin, clean the gpx to not dox the location and other units, clean the json, plot it to look pretty and post it on nostr from time to time, could be automatic but don't like time correlations either, so to have something when I manage to do an activity, awefull pow I get it 🤣 Looking forward to nostr-ava and blossom support would be great. It will be good if some sort of extension nip7 ties up the gadgets login with the nostr one, fancier than just the current script. nostr:nevent1qqspzdjpt074pyy34zvev44q0yneupwl99v03ze047p3l0ghz44m20spzpmhxue69uhkztnwdaejumr0dshsygy42sesjm72ygljnt0a22sv9hs850zjad5qlx6dn6mvgmv3jmz5pcpsgqqqqqqszmx092