Skip to content

Fix location of Hergenrath station#2268

Open
dancojocaru2000 wants to merge 1 commit into
public-transport:mainfrom
dancojocaru2000:be-fix-hergenrath-location
Open

Fix location of Hergenrath station#2268
dancojocaru2000 wants to merge 1 commit into
public-transport:mainfrom
dancojocaru2000:be-fix-hergenrath-location

Conversation

@dancojocaru2000

Copy link
Copy Markdown
Contributor

Location in the SNCB/NMBS dataset is 1 km away from the real location. The distance is too significant not to fix.

The new locations are taken from the OSM nodes.

@dancojocaru2000
dancojocaru2000 force-pushed the be-fix-hergenrath-location branch from 17e4f14 to dd2732a Compare June 29, 2026 14:53
@jbruechert

Copy link
Copy Markdown
Collaborator

Sorry, this is really not the right place to fix this. Please report it to SNCB.

@dancojocaru2000

Copy link
Copy Markdown
Contributor Author

Why not both? When SNCB fixes their data, this fix can be removed as well. But I thought the point of scripting was to fix issues in the datasets in the first place.

@jbruechert

Copy link
Copy Markdown
Collaborator

Scripts are currently not CI tested, can break the import process and hard to review without looking at the data. As soon as they reference ids from the dataset they are also prone to breaking at some random point.

So I want to keep the amount of script changes as little as possible, usually restricted to reshuffling existing data.

@dancojocaru2000

Copy link
Copy Markdown
Contributor Author

Generally speaking, I agree. I think it would be unsustainable to use a script to, for example, modify the location of all stations to match OSM.

I think in this particular case it is justified as a stop-gap measure until SNCB/NMBS fixed the dataset in order to not direct people 1 km (straight line) / 1.8km (walking) wrongly. I've had a look at all other border stations and this is the only one that's horribly misaligned.

I would also argue that the code is written in such a way that, if IDs change for example, it just does nothing (as opposed to crashing the import). I could change it to use the name though if that's a big concern.


Ultimately it's indeed your call. I just feel like this is a more important correction than adding line colours (not that I have anything against those either).

@dancojocaru2000

Copy link
Copy Markdown
Contributor Author

I've sent an email to Belgian Mobility Company (since they're who SNCB/NMBS point to here) and I'll see how it unfolds from there.

Location in the SNCB/NMBS dataset is 1 km away from the real location.
The distance is too significant not to fix.
@dancojocaru2000
dancojocaru2000 force-pushed the be-fix-hergenrath-location branch from dd2732a to 047d9ee Compare June 30, 2026 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants