STANOX code mapping

[Jonathon Hurley]

Has anyone come across a geographical mapping of STANOX codes?

For example:

12xxx codes are around Northumberland

13xxx codes are South of Tyne

14xxx are Durham Coast

etc

Is there an official reference as to which areas relate to which codes?

Cheers

Jonathon

[Peter Hicks]

Yup - http://dysgraphyk.madasafish.com/rail/stanox_areas.htm


Peter

[Matt Carlson]

This site is handy for TIPLOC / CRS / STANOX codes: http://deaves47.zxq.net/CRS/CRS0.htm

[Barry Carlyon]

I made a searchable/MySQL dump version of that very site/source at http://trains.barrycarlyon.co.uk/

I'm sure somewhere someone had it to long/lat?!

Sent from my iPhone

--
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 post to this group, send an email to openrail...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Jonathon Hurley]

I'll pitch in with a recommendation for Barry's data - I've recently combined his SQL dump with the CORPUS data available through the Reference Data feed. The location names and descriptions are much more useful in Barry / Phil's data than the NLCDESC given in CORPUS - e.g. CORPUS contains the ever-helpful description 'NLC NOT REQUIRED BY WAF2' for DALZBSC - which is actually Dalzell BSC!

Haven't yet found a source with location information in yet (other than NaPTaN which contains info for just stations.)

Regards,

Jonathon

[Peter Hicks]

On 24/05/13 18:09, Jonathon Hurley wrote:
> I'll pitch in with a recommendation for Barry's data - I've recently combined his SQL dump with the CORPUS data available through the Reference Data feed. The location names and descriptions are much more useful in Barry / Phil's data than the NLCDESC given in CORPUS - e.g. CORPUS contains the ever-helpful description 'NLC NOT REQUIRED BY WAF2' for DALZBSC - which is actually Dalzell BSC!

The CORPUS data is the single reference source of data - so if things
are missing or incorrect in it, let me know and I'll get 'em looked in to.


Peter

[Paul Kelly]

Peter Hicks wrote:
>
> The CORPUS data is the single reference source of data

Out of interest, where are the location descriptions and STANOX codes in
the "TIPLOC insert" records in the schedule data taken from? I use them
for everything and have always found them pretty accurate (although to
be fair I still haven't done a huge amount of work with the real-time
data feed, but haven't noticed anything missing when interpreting it
using the STANOX codes from the TI records).

Paul

[Peter Hicks]

On 25/05/13 10:52, Paul Kelly wrote:
> Out of interest, where are the location descriptions and STANOX codes
> in the "TIPLOC insert" records in the schedule data taken from? I use
> them for everything and have always found them pretty accurate
> (although to be fair I still haven't done a huge amount of work with
> the real-time data feed, but haven't noticed anything missing when
> interpreting it using the STANOX codes from the TI records).

They come from CORPUS, which feeds the data in to TPS, the Train
Planning System.


Peter

[Paul Kelly]

Oh that's good to hear. Looks like I'm not missing anything then. FWIW I
don't see the problem with DALZBSC in the schedule data (TI records) -
it is shown there as "DALZELL B.S.C.".

Paul

[Barry Carlyon]

I was looking at linking what I have with the CORPUS data.

Came across some oddities linking the two.

So I'm looking at taken CORPUS as golden.

And adding extra data from what I/Deaves has.

Anything that is in I/Deaves but not in CORPUS is extra data, as CORPUS only contains where trains currently go.

Just some of the Deaves is a bit more Human readable in place names I suppose (and is more of a historical resource in nature and was handy for when the CORPUS feed didn't exist).

But depends what you are using the entire Feeds for project wise :-D

--
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-talk+unsubscribe@googlegroups.com.
To post to this group, send an email to openraildata-talk@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--

Barry Carlyon

[bow...@interfleet.co.uk]

How do I access the CORPUS data ? ... or where can I find it 

I am looking at producing a map showing TSR,s and was wondering how to translate the 
Line route codes etc - to something that could be shown on a map 

[Peter Hicks]

On 5 Jun 2013, at 10:30, bow...@interfleet.co.uk <bow...@interfleet.co.uk> wrote:

How do I access the CORPUS data ? ... or where can I find it 

See http://nrodwiki.rockshore.net/index.php/ReferenceData - it's one of the reference data feeds

I am looking at producing a map showing TSR,s and was wondering how to translate the 
Line route codes etc - to something that could be shown on a map 

The LOR codes are listed in the Sectional Appendix - see the PDF links at the right of http://www.networkrail.co.uk/aspx/10563.aspx

Peter

[bow...@interfleet.co.uk]

Many thanks again Peter for your help

I'm looking for lat/long co-ordinates for the LOR or ELR 

I understand this is a massive exercise to produce this kind of data ... just wondering if anyone was doing this ?

[Prof Falken]

The NaPTAN dataset has Lat/Long for all stations (rail, bus, transit and ferry!), however it does not cover all TIPLOC/STANOX codes as far as I can tell.

Matt