Shifdr Routes

Map-first driving routes for car clubs. One static page (index.html, deployed on Vercel) plus a Supabase project for accounts and the shared route library.

Route library (Phase 2)

• Build / Discover tabs. Discover shows public routes that cross the map view, with search and a distance filter. Click a card or a line on the map for the route's page: stops with mile markers, roads, Export GPX, Copy link, and Open in builder.
• Hide routes: each card has a Hide/Show toggle so you can see only the routes you want on the map; Show all and Hide all above the list. Remembered in your browser.
• Share links: ?r=<route id> opens straight to a route.
• Accounts: sign in with Google or a 6-digit email code. The Google button shows only when the Google provider is on in Supabase. Saving while signed in stores the route in your library; tick Public to list it in Discover. Opening someone else's route and saving makes your own copy.
• Backend: Supabase project Shifdr Routes. Schema in supabase/migrations/. Row-level security lets anyone read public routes; only the owner can read private ones or change anything. A PostGIS trigger stores each route's line so routes_in_view can find routes by map area.

How to use it

• Opens on your location if the browser allows it; otherwise on your last view, or Marble Falls. The target button jumps back to you.
• Satellite button (top right) switches between the street map and satellite imagery with road names. The choice is remembered.
• Draw mode (default): click a starting point, then hold and drag along the roads you want. The route snaps to the road network as you go.
• Click anywhere to extend the route to that point.
• Drag an anchor to move it; only the two segments touching it re-route.
• Drag the route line onto a different road; a new anchor is inserted there.
• Pan: right-click and drag, switch to Pan mode, or hold Space while drawing. Scroll or pinch to zoom.
• Undo / Redo: buttons or Ctrl/Cmd+Z and Shift+Ctrl/Cmd+Z.
• Reverse drives the same roads the other way (stored geometry is flipped, not re-routed). A one-way route swaps Start and Finish; a loop keeps its start and runs the other way round. Route pages in Discover have the same option, and GPX export and Open in builder use the reversed direction.
• Loop routes the end back to the start.
• Clean up detours drops points that pulled the route onto side streets. It only removes a point if the simpler path still passes where your finger was and isn't any longer. Undo restores the original.
• Stops: name the Start and Finish, and add numbered pit stops. Find searches places and addresses near the map view, or you can tap the map instead. Searching a Start or Finish moves that end of the route there. A pit stop is routed through and shows its mile marker. Clean up and loop trimming never remove a pit stop.
• Test drive: a car drives the route at the router's speed for each stretch, sped up 15–300×. It shows the current road, mile, clock and speed, pauses at pit stops, and flags possible U-turns, gaps and unsnapped pieces in red. Drag the slider to scrub; next jumps to the next issue. Drag the map to stop following.
• Save keeps routes in this browser; Export GPX saves the exact path as a GPX track for nav apps, with the named stops as waypoints; Export JSON gives the full Shifdr route file. Import opens a GPX (tracks keep their exact path; route-point files are routed between the points; waypoints on the route become Start, Finish and pit stops) or a Shifdr JSON file. A reopened route uses its stored geometry and is never re-routed.

Road work check

Check road work (in Build, and on any route page) looks for construction, lane closures and closures on the route for a chosen drive date. Each issue shows its mile along the route, dates, a short description, and links to the source and the map location; markers appear on the map.

• Sources: TxDOT DriveTexas (free key from api.drivetexas.org/request-key, kept in the server-only app_settings table or a DRIVETEXAS_KEY function secret; a work-zone key uses TxDOT's WZDx feed), WZDx work-zone feeds that need no key (City of Austin, Louisiana, Oklahoma, New Mexico, fetched only when the route passes through), and OpenStreetMap construction tags (fetched by the browser from Overpass).
• Only events that run along the route count; roads that merely cross it are ignored. Same-event duplicates per direction are merged.
• Code: supabase/functions/road-conditions/index.ts.

Events (group drives)

• Plan a drive on any route page (signed in). It keeps a copy of the route as it is now, normal or reversed, so later edits to the route don't change the drive. Set the date, departure time and time zone, up to two meetup points, a meal stop with its last seating, regroup points, a car limit, and co-organizers by email. Save as a draft, then Publish.
• Lunch clock: the form shows when group 1 reaches the meal stop (router drive time plus 10 minutes per regroup) against the last seating. Amber under 30 minutes, red under 15 or late. A second meetup's time follows group 1's arrival there unless you change it.
• Road work and plan B: check the drive's date for road work, then add plan B stretches (from mile, to mile, what to do instead). They show dashed amber on the map and on the event page.
• Invite: each drive gets a 6-character code (no 0/O or 1/I/L) and a link, /e/<CODE>; ?e=<CODE> and a dashed code like K7Q-4MZ work too. Copy link, Share, a QR code, and invite text. Nobody can find a drive without its code.
• Event page: the route on the map, meetups with directions, meal stop, regroups, plan B, Add to calendar (.ics) and Export GPX. Signed out it shows counts only; signed in, first names and cars as well.
• Join on the web: driver (car, extra passengers, seats open) or passenger (riding with a driver, or needs a ride), meetup, I'm in or Maybe. Your phone and car are remembered for next time. I can't make it takes you off the counts.
• Manage drive (organizers, from the event page or the Drives tab) has three tabs:
  • Overview: cars (against the car limit), people, maybes, need a ride, seats open and can't make it; drivers and passengers, new sign-ups this week, people added by hand, counts per meetup, the cars by make, the lunch clock and the headcount for the restaurant, the latest update, Close sign-ups and the invite.
  • Updates: post a message for everyone with the link or only for people on the roster, pin it, edit or delete it. Updates show near the top of the event page, pinned first. After posting, Copy message and Copy phone numbers let you text it; app alerts come with the Shifdr app. Saving a new time or meetup offers a ready-made update.
  • People: search names, phones and cars; filter by drivers, passengers, need a ride, maybe or can't make it; change who's coming, whose car a passenger rides in, or a driver's meetup right from the list; edit, remove or add people by hand; Need a ride and Seats open lists; Copy phone numbers and Download roster (CSV). Removing a driver moves their passengers to Need a ride.

Tests

• Database: tests/rls.sql runs in the Supabase SQL editor. Three throwaway users create, join, edit and cancel a drive, and each line of the result reads PASS or FAIL. The block rolls itself back, so nothing is kept.
• Pages and maths: run npm install once (it adds only playwright-core, and uses the Edge or Chrome already installed). Run tests/fixture.sql in the SQL editor for four [test] drives, then EVENT_CODES='<codes from the fixture>' ROUTE_ID=<route_id from the fixture> npm test. It checks the lunch clock and second-meetup times against hand sums, the Manage drive stats and change-of-plan text, the REST API as a signed-out visitor (updates included), invite links, unknown, draft, closed and cancelled drives, the event page at 360×740, and a pass over Discover, reverse, GPX export and import, the builder and the road check. Add BASE=https://<preview>.vercel.app to test a deployed copy. Run tests/cleanup.sql afterwards.

Search

• With a Mapbox token: Mapbox geocoding. Without: Photon (OpenStreetMap), with Nominatim as a backup. You can also paste coordinates like 30.5752, -98.2731.

Routing

• Without a key it uses Esri street map tiles and the free OSRM demo router. Good enough to test the interaction, but slow and rate-limited.
• Paste a Mapbox public token under Map & routing settings to switch to Mapbox Directions and Mapbox Outdoors tiles.
• The map is drawn with MapLibre GL, the open-source fork of Mapbox GL JS. The API is the same, so moving to Mapbox GL JS later is a small change.

How it preserves road choice

• Tracing drops an anchor roughly every 40 screen pixels. Each anchor pair is routed separately, so the router never gets a long enough gap to substitute a faster road.
• Where an anchor snaps just past an intersection, the router produces a short out-and-back spur. Those spurs are trimmed at the joints before distance is calculated.
• Small detour loops (the route leaving and returning to the same spot within 500 m) are cut out automatically.
• Distance comes from the final trimmed geometry. Drive time is the router's estimate, scaled to match.

Saved route format (shifdr.route/v1)

anchors (the ordered road-selection constraints), segments (per-segment geometry, distance, time, road names), geometry (MultiLineString, ready for a PostGIS column), plus start_name, finish_name, stops (type, name, location, mile), distance_m, duration_s, roads, is_loop, and router. Pit stops are anchors with a pit name.

Things to test in the Hill Country

• RR 1431 between Marble Falls and Kingsland: winding road with lake-side side streets.
• US 281 through Marble Falls: frontage roads and the bridge.
• Park Road 4 and the roads around Inks Lake.
• Deliberately take a slower road where a faster one runs parallel, then save, reload, and confirm the same path comes back.

Known limits

• Fast tracing on the OSRM demo server lags behind the cursor. Mapbox is noticeably quicker.
• Reverse keeps the original geometry, so on a divided highway it will show the opposite lane.
• Routes saved locally live only in that browser. Supabase storage comes in Phase 2.