Erik on Nostr: For nostr-ava I think I'm going to lean into a DVM model to analyze gpx files. Here's ...
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
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