You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
VeloPopuli and OpenBikeNet: real roads, rooms and a few questions
#4
I'm the person behind VeloPopuli, the one you opened the laps issue on. Thanks for that, by the way: it's a good proposal and I've said yes to it.
A bit of background so you know where I'm coming from. I'm a tinkerer who got fed up paying subscriptions to ride indoors, so I built my own: free, GPLv3, nothing to sign up for. I've no interest in turning it into a racing platform, but riding alongside other people is nice, and riding alongside people from other apps is even better. So I like what you're doing here, and I'd like VeloPopuli to join in once laps are done.
I've read the v0 spec. Mostly it just made me nod along, especially the privacy section. A few things came up while I was thinking about how it'd fit:
Real roads. This is the big one for me. VeloPopuli is built around riding real places: you load a GPX and it builds the world from the coordinates, OpenStreetMap and elevation data. A route that's only distance and height doesn't give it enough to go on. Could route files have an optional list of lat/lon points alongside the profile? Apps with their own world could ignore it. If that happened I'd happily send in route files for some of the classic climbs (Alpe d'Huez, Ventoux, the Stelvio, Box Hill and so on).
Further off: some way to share a route that isn't in the catalogue, maybe identified by a hash of its contents so it still can't change under anyone. That's how group rides work in VeloPopuli today. One person shares the GPX, everyone else downloads it.
Distances. Every app smooths and resamples a GPX a bit differently, so the "same" route comes out a few metres longer in one than another, and riders slowly drift apart. Maybe the spec could say the route file's length is the one that counts, and apps scale to it?
Private rides. I get that rooms in v0 are public, and that's fine. Group rides in VeloPopuli are meant for a few friends with a room code, though, so some kind of room password later on would be good.
The server. I'd make the server a setting in VeloPopuli, so people can run their own if they'd rather. For the public one, it'd help to have a short privacy note on openbikenet.cloud (basically section 10 of the spec) and a line saying who runs it. Have you thought about servers being able to talk to each other at some point? Otherwise people on different servers never meet.
Shared physics. Looking forward to that stage. VeloPopuli works out speed from power itself rather than trusting the trainer, so it'd be easy to switch over. It's probably worth deciding early what goes into the shared model: weight, drag, rolling resistance, drafting and wind.
None of this needs to hold up the velodrome. My rough plan would be: laps first, then a proper velodrome track in VeloPopuli, then riding on it with people from other apps, and real roads after that if route files ever get coordinates.
Good luck with it. I'll be keeping an eye on the repo.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi Ralf,
I'm the person behind VeloPopuli, the one you opened the laps issue on. Thanks for that, by the way: it's a good proposal and I've said yes to it.
A bit of background so you know where I'm coming from. I'm a tinkerer who got fed up paying subscriptions to ride indoors, so I built my own: free, GPLv3, nothing to sign up for. I've no interest in turning it into a racing platform, but riding alongside other people is nice, and riding alongside people from other apps is even better. So I like what you're doing here, and I'd like VeloPopuli to join in once laps are done.
I've read the v0 spec. Mostly it just made me nod along, especially the privacy section. A few things came up while I was thinking about how it'd fit:
Real roads. This is the big one for me. VeloPopuli is built around riding real places: you load a GPX and it builds the world from the coordinates, OpenStreetMap and elevation data. A route that's only distance and height doesn't give it enough to go on. Could route files have an optional list of lat/lon points alongside the profile? Apps with their own world could ignore it. If that happened I'd happily send in route files for some of the classic climbs (Alpe d'Huez, Ventoux, the Stelvio, Box Hill and so on).
Further off: some way to share a route that isn't in the catalogue, maybe identified by a hash of its contents so it still can't change under anyone. That's how group rides work in VeloPopuli today. One person shares the GPX, everyone else downloads it.
Distances. Every app smooths and resamples a GPX a bit differently, so the "same" route comes out a few metres longer in one than another, and riders slowly drift apart. Maybe the spec could say the route file's length is the one that counts, and apps scale to it?
Private rides. I get that rooms in v0 are public, and that's fine. Group rides in VeloPopuli are meant for a few friends with a room code, though, so some kind of room password later on would be good.
The server. I'd make the server a setting in VeloPopuli, so people can run their own if they'd rather. For the public one, it'd help to have a short privacy note on openbikenet.cloud (basically section 10 of the spec) and a line saying who runs it. Have you thought about servers being able to talk to each other at some point? Otherwise people on different servers never meet.
Shared physics. Looking forward to that stage. VeloPopuli works out speed from power itself rather than trusting the trainer, so it'd be easy to switch over. It's probably worth deciding early what goes into the shared model: weight, drag, rolling resistance, drafting and wind.
None of this needs to hold up the velodrome. My rough plan would be: laps first, then a proper velodrome track in VeloPopuli, then riding on it with people from other apps, and real roads after that if route files ever get coordinates.
Good luck with it. I'll be keeping an eye on the repo.
All reactions