Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Show the car on an offline track map and time laps from GPS

Open
  • Is something wrong?
#850 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 4 days

@TheJeffreyKuo is already working on this.

Since Oct 13, 2026.

  • #851 by @TheJeffreyKuo — open

Assessment

This issue has not been assessed yet.

Description

backend by: ai-assisted dev work frontend
What

The map page shows the car's live position and driving trace on an offline OpenStreetMap background, and engineers place a start line and an optional finish line (two GPS points each) on it. scylla-server times laps from a Run's stored GPS data against those lines, so accel, autocross and endurance get lap times without trackside equipment.

Diagram
flowchart LR
  subgraph Before
    C1[Car GPS] -.->|not stored| S1[scylla-server]
    UI1[Map page] -.->|no data| S1
  end
  subgraph After
    C2[Car GPS or dev mock] -->|TPU/GPS/Location| S2[scylla-server]
    S2 --> DB[(Postgres: datapoints, tracks)]
    UI2[Map page] -->|live position and trace| S2
    UI2 -->|tracks and a Run's laps| S2
    UI2 -->|offline background| PM[(Local venue map file)]
  end
Requirements
  • The map page shows the live car position and trace for the current Run, and the full trace for a past Run, with no internet connection
  • Engineers can create and delete tracks, and place, drag, edit and clear each track's start line and optional finish line; tracks are stored in scylla-server
  • scylla-server returns a Run's laps for a track: a start line alone gives laps, a start and finish line give timed runs
  • Lap times show next to the map and update while the Run is live
  • Tests cover lap timing, track storage and line editing
Notes

No response

Context transfer
Dominant language
TypeScript
Stars
5
Forks
1
Avg merge
3d 12h
Merged PRs (30d)
33

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Northeastern-Electric-Racing/Argos

All issues in Northeastern-Electric-Racing/Argos

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.