ViewTripWeb v0.50.0

ViewTripWeb v0.50.0

20 changes since v0.49.0

🚀 New

In the app

• Sharing — Public and shared trip links now load only as much map detail as the current zoom can show, instead of the whole trip at full resolution — far less data to download and far less memory held, which is the difference between a long trip opening on a phone and not. (#321)

Server & deployment

• Rail — Train routes drawn by an older version of the route finder are now redrawn quietly in the background, so an improvement to how routes are traced reaches trips you already planned instead of only new ones. A few are redone per hour rather than all at once, and routes you edited by hand are never touched. (#364)

🐛 Fixed

In the app

• Web app — Importing a trip's photos no longer saturates the connection. While the photos download in the background, the app now checks for them with a small request instead of re-downloading the entire trip every three seconds — on a long trip that was tens of megabytes a time, for three minutes. (#308)
• Trip stats — Climb totals on hand-edited activities and GPX imports were counting GPS wobble as ascent, sometimes several times over, while hills on imported planned routes could vanish entirely. Both are fixed, and existing trips are corrected when the server next starts. (#260)
• Settings — Setting a trip end date now really removes the days after it — they used to reappear right after you confirmed. The warning also tells you when a later day has an activity or a memory on it and will stay put. (#358, #362)
• Web app — Offline maps keep their detailed tracks again. A trip you have opened once on a device now keeps its full-detail route for the next time you open it without a connection. Exported and shared images are drawn from that full-detail route too, so a single-day export no longer comes out angular. (#317)
• Days — A day whose only content is a journal entry, an encounter or a segment now shows up in the day strip, is offered by the add button and counts towards the trip's day numbering. The day list already showed it, but the rest of the app behaved as though the day were not there. (#370)
• Map — Zooming into a shared trip, or into a trip someone shared with you, now brings the finer map detail it asks the server for instead of leaving the track as coarse as it first loaded. (#321)
• Settings — Moving a shared trip's end date earlier no longer deletes the notes, tags and sleeping entry of a day one of your travel companions has a journal entry on — those days stay, and the warning now says so. If the app cannot reach the server to check, it keeps every day past the new end date rather than deleting any. (#372)
• Trip stats — Climb totals are more accurate on tracks that are recorded sparsely, or whose altitude readings update more slowly than their position — flat ground on those could previously be reported as hundreds of metres of climbing. Gentle rolling terrain on imported routes is also counted properly instead of being flattened away. (#376)
• GPX import — Activities imported from a GPX file with some points missing elevation no longer show a drop to sea level on the elevation chart, and their total climb is no longer overstated. Existing activities are corrected automatically. (#374)
• Sharing — Renaming a trip no longer breaks its shared link. Visitors could briefly get an error, or be sent the full-detail map instead of the lighter one built for their zoom level, for about a minute after a rename. (#321)
• Trip stats — Editing or splitting an activity no longer rewrites how much climb it had. The figure your tracking app recorded is kept, split proportionally between the pieces, and restored in full if you reset the track. (#386)

Server & deployment

• Rail — Train routes now start and end at the right station. Some legs were drawn from a point several kilometres away — Paris Gare de l'Est to Strasbourg began 14 km south of the city — because the map data's platform outlines were being mistaken for track. (#359)
• Rail — Train routes now start at the station rather than at the edge of town where the map data leaves a gap. Paris Montparnasse to Bordeaux began 3.5 kilometres out, on the ring line south of the station. Nantes to Rennes is also drawn along the direct line it runs on instead of a detour via Le Mans. (#363)
• Day-Meta — On a shared trip, the notes on a day can no longer be deleted by someone whose app cannot see what is still keeping that day in the trip. (#387, #388)

⚠️ Upgrade notes

• Rail — Rail data must be refreshed after this release — run scripts/fetch_rail_data.py --dest /app/data/rail on the box. It rebuilds all regions rather than skipping them, since the store format changed while the published extracts did not. There is no window to plan around: the reader serves the existing stores until each is replaced.

Internal changes (7)

• judge the elevation sentinel per run, not by the median (#374)
• detect the elevation sentinel by grade, not by altitude (#374)
• adversarial-review follow-ups to #370/#372 (#384)
• refresh the code graph after the #359 fix
• cover the candidate day a only the server can see
• refresh the code graph after the #308/#317/#321 wave
• pin elevation gain against the classes it keeps breaking

Full changelog: v0.49.0...v0.50.0