BRSTAP3 and the Weston-Super-Mare to Worle service?

163 views
Skip to first unread message

David Mountain

unread,
May 23, 2025, 6:18:47 AMMay 23
to A gathering place for the Open Rail Data community
Hi

I'm investigating a station with name/tiploc "BRSTAP3" and CRS "BWE" which looks to be a bus stop for a service that connects Weston-Super-Mare to Worle, and possibly continues to Bristol Airport. 

Example from  National Rail below



Screenshot 2025-05-23 at 10.32.36.png


Screenshot 2025-05-23 at 10.36.09.png


Clearly the name isn't very user friendly, so a fix on that (in the corpus?) is needed.

But weirdly there appears to be some ambiguity in different sources about whether this service runs  (A) Weston-Super-Mare to Worle, or (B) Weston-Super-Mare to Bristol Airport via Worle. Network Rail sources are consistent in (B) but Darwin looks to be less consistent.

Any thoughts about who best to report this to to get the name fixed and schedules consistent at source?

Thanks
Dave




Ian Sargent

unread,
May 23, 2025, 7:59:51 AMMay 23
to openrail...@googlegroups.com
It's a bus service from Bristol Airport with through ticketing via Weston super Mare. It's using a different CRS code and TIPLOC at the airport to those used for the bus to Bristol Temple Meads as the tickets are not interavailable on the two different buses.

That the codes are not being displayed properly in the journey planners is either an issue with those planners not properly interpreting the source data, or that the source data has been incorrectly edited.



From: openrail...@googlegroups.com <openrail...@googlegroups.com> on behalf of David Mountain <dmmou...@gmail.com>
Sent: Friday, May 23, 2025 11:18:46 AM
To: A gathering place for the Open Rail Data community <openrail...@googlegroups.com>
Subject: [openraildata-talk] BRSTAP3 and the Weston-Super-Mare to Worle service?
 
--
You received this message because you are subscribed to the Google Groups "A gathering place for the Open Rail Data community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openraildata-t...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/openraildata-talk/6f67ba83-a3fe-4eeb-b6fd-a53e1107a283n%40googlegroups.com.

David Mountain

unread,
May 28, 2025, 12:03:05 PMMay 28
to A gathering place for the Open Rail Data community
The problem appears to be this record in the Darwin location reference data.

 LocationRef tpl="BRSTAP3" crs="BWE" locname="BRSTAP3"

The location name is the same as the tiploc code which isn't user friendly. Other bus/rail stops in the reference data have more descriptive names.

It appears that Network Rail Corpus has a better name, but rather than chopping and changing station by station, it looks to me like it would be best to fix the locname in Darwin location reference data. Is this the best place to request that, or is there a more specific contact? I can see lots of reliable services propagating this tiploc code as the station/stop name https://www.opentraintimes.com/schedule/C21052/2025-05-28

Many thanks
Dave Mountain

Peter Hicks

unread,
May 28, 2025, 12:11:22 PMMay 28
to A gathering place for the Open Rail Data community
Hi David

If it’s not already been picked up by anyone reading this from RDG, I’ll log a support ticket so it gets picked up.


Peter 

David Mountain

unread,
Jun 27, 2025, 4:40:41 AMJun 27
to A gathering place for the Open Rail Data community
This issue is still presenting in all sources. I reported it to network rail but didn't get a response. 

Peter if you are able to raise it with RDG, that would be appreciated

Thanks
Dave

Peter Hicks

unread,
Jun 28, 2025, 6:44:41 AMJun 28
to openrail...@googlegroups.com
Hi Dave

On Friday, 27 June 2025 at 09:40, David Mountain <dmmou...@gmail.com> wrote:

Peter if you are able to raise it with RDG, that would be appreciated

Logged under case CS00287574 - I'm anticipating it'll be next week before somebody looks at it.


Peter

Peter Hicks

unread,
Jul 8, 2025, 6:17:36 AMJul 8
to openrail...@googlegroups.com
Hi Dave

On Saturday, 28 June 2025 at 11:44, 'Peter Hicks' via A gathering place for the Open Rail Data community <openrail...@googlegroups.com> wrote:

Logged under case CS00287574 - I'm anticipating it'll be next week before somebody looks at it.

This should be resolved in tomorrow's reference data update.

Best wishes,


Peter

Reply all
Reply to author
Forward
0 new messages