Two stops in routeFareList.min.json carry names that aren't the stop's name. Both originate upstream of this project — kmb.py and lrtfeeder.py copy them through verbatim, which is correct behaviour — so I'm raising them here rather than sending a patch, since there's no stop-name override layer today and whether you want one is your call.
1. KMB 37477DA2524EA566 — "CHIRDHOOD" for "CHILDHOOD"
$ curl https://data.etabus.gov.hk/v1/transport/kmb/stop/37477DA2524EA566
{"stop":"37477DA2524EA566","name_en":"YEW CHUNG COLLEGE OF EARLY CHIRDHOOD EDUCATION",
"name_tc":"耀中幼教學院","lat":"22.250583","long":"114.147811"}
Tin Wan Hill Road, on route 107. CTB's record of the same kerb (002294) spells it correctly — "Yew Chung College of Early Childhood Education, Tin Wan Hill Road" — so within one merged joint route the two operators disagree, and the KMB side is the wrong one. name_tc (耀中幼教學院) is fine.
2. MTR Bus K52A-U015 — an operating-hours note inside the stop name
$ curl -s https://opendata.mtr.com.hk/data/mtr_bus_stops.csv | sed -n '275p'
K52A,O,2,K52A-U015,22.393937,113.973896,輕鐵屯門站 (請留意服務時間)*,LR Tuen Mun Stop (Please refer to Service Time)*,K52A
The stop is the Light Rail Tuen Mun stop; "(Please refer to Service Time)*" is a footnote about when the stop is served, not part of its name. It's the only stop of 15,265 in routeFareList.min.json whose name ends in *, and the only one carrying a service annotation — so it reads as a one-off authoring slip in MTR's CSV rather than a convention.
Consumers that render or search stop names have to special-case both. Happy to send a PR if you'd want a small errata table keyed by stop id (applied in mergeStopList.py or cleansing.py), but that's a new concept in the codebase, so I'd rather ask first. The alternative is that these get reported to KMB and MTR directly and you carry them until fixed.
Two stops in
routeFareList.min.jsoncarry names that aren't the stop's name. Both originate upstream of this project —kmb.pyandlrtfeeder.pycopy them through verbatim, which is correct behaviour — so I'm raising them here rather than sending a patch, since there's no stop-name override layer today and whether you want one is your call.1. KMB
37477DA2524EA566— "CHIRDHOOD" for "CHILDHOOD"Tin Wan Hill Road, on route 107. CTB's record of the same kerb (
002294) spells it correctly — "Yew Chung College of Early Childhood Education, Tin Wan Hill Road" — so within one merged joint route the two operators disagree, and the KMB side is the wrong one.name_tc(耀中幼教學院) is fine.2. MTR Bus
K52A-U015— an operating-hours note inside the stop nameThe stop is the Light Rail Tuen Mun stop; "(Please refer to Service Time)*" is a footnote about when the stop is served, not part of its name. It's the only stop of 15,265 in
routeFareList.min.jsonwhose name ends in*, and the only one carrying a service annotation — so it reads as a one-off authoring slip in MTR's CSV rather than a convention.Consumers that render or search stop names have to special-case both. Happy to send a PR if you'd want a small errata table keyed by stop id (applied in
mergeStopList.pyorcleansing.py), but that's a new concept in the codebase, so I'd rather ask first. The alternative is that these get reported to KMB and MTR directly and you carry them until fixed.