derhuerst/match-gtfs-rt-to-gtfs

matching: option to configure tolerable time differences

Open

#4 opened on Oct 22, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (1 fork)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (5 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

With some realtime data sources (such as some HAFAS endpoints) and some GTFS datasets, there are minor discrepancies between the realtime data and the plan data, e.g. 1m for a departure of a specific trip.

We could introduce an option to allow such time differences when matching.

  • In the respective SQL queries, the time range would have to include the tolerance.
  • There should be logic in JS that fails if there are >1 matches, because in these cases, the matching can be wrong.

as reported by @hbruch

Contributor guide

Research direction
Investigate current SQL queries and JavaScript logic for time comparisons, then add a configurable tolerance parameter and adjust matching to avoid multiple matches.
Tech stack
javascript
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitSQLJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65