PC [app] - Thirdrails Live Multiplayer Radar

Yes, there is a minimum threshold.

Rides need to be at least 2 miles long to be logged and published to WhistleBoard. This helps filter out very short test runs, setup movements, or accidental starts.

If your shunting operations were around 3–4 miles total they should normally qualify, but if they were just under 2 miles they won’t be published.

 

Yes, you’re right, apparently the world decided it was a good idea to reuse station names across continents

There is a temporary workaround:
Since stations are harvested directly from the timetable’s “Calling At” entries, the system treats the station name exactly as written there. So if you manually rename it in your timetable to something like:

Chatham (US)
Dover (US)

The Station Network will treat those as separate entries and they will register correctly.
It’s not ideal, and I don’t expect everyone to modify their timetables, but it does work as a short-term solution.

I’m currently refactoring the radar engine as part of RadarX to support upcoming features like the timetable layer, which will also enable a more location-based approach to station matching.

 

3.57 according to the log, but in spite of my attempts to upload it, no dice..

 

Oh yeah, you are right about that.

I looked into it a bit deeper.

Rides under 2 miles are not logged at all, neither locally nor on WhistleBoard.
However, the WhistleBoard server only accepts uploads for rides over 5 miles.

So your 3.57 mile shunting run was logged locally, but it doesn’t meet the 5 mile threshold required for publication.
Why 5 miles? Please don’t ask… it’s one of those “historic design decisions” that stuck

 

Cool, good to know.