2nd Edgware Road missing from Circle line orderedLineRoutes naptanIds

Open Data
1

Hey everyone

Have noticed that the second occurrence of Edgware Road is missing from https://api.tfl.gov.uk/Line/circle/Route/Sequence/[inbound|outbound].

Inbound data:

"naptanIds": [
                "940GZZLUERC", // Correct
                "940GZZLUPAC",
                "940GZZLUBWT",
                "940GZZLUNHG",
                "940GZZLUHSK",
                "940GZZLUGTR",
                "940GZZLUSKS",
                "940GZZLUSSQ",
                "940GZZLUVIC",
                "940GZZLUSJP",
                "940GZZLUWSM",
                "940GZZLUEMB",
                "940GZZLUTMP",
                "940GZZLUBKF",
                "940GZZLUMSH",
                "940GZZLUCST",
                "940GZZLUMMT",
                "940GZZLUTWH",
                "940GZZLUALD",
                "940GZZLULVT",
                "940GZZLUMGT",
                "940GZZLUBBN",
                "940GZZLUFCN",
                "940GZZLUKSX",
                "940GZZLUESQ",
                "940GZZLUGPS",
                "940GZZLUBST",
                *** missing ***
                "940GZZLUPAH",
                "940GZZLURYO",
                "940GZZLUWSP",
                "940GZZLULAD",
                "940GZZLULRD",
                "940GZZLUWLA",
                "940GZZLUSBM",
                "940GZZLUGHK",
                "940GZZLUHSC"
            ],

Outbound data:

"naptanIds": [
                "940GZZLUHSC",
                "940GZZLUGHK",
                "940GZZLUSBM",
                "940GZZLUWLA",
                "940GZZLULRD",
                "940GZZLULAD",
                "940GZZLUWSP",
                "940GZZLURYO",
                "940GZZLUPAH",
                "940GZZLUERC", // Correct
                "940GZZLUBST",
                "940GZZLUGPS",
                "940GZZLUESQ",
                "940GZZLUKSX",
                "940GZZLUFCN",
                "940GZZLUBBN",
                "940GZZLUMGT",
                "940GZZLULVT",
                "940GZZLUALD",
                "940GZZLUTWH",
                "940GZZLUMMT",
                "940GZZLUCST",
                "940GZZLUMSH",
                "940GZZLUBKF",
                "940GZZLUTMP",
                "940GZZLUEMB",
                "940GZZLUWSM",
                "940GZZLUSJP",
                "940GZZLUVIC",
                "940GZZLUSSQ",
                "940GZZLUSKS",
                "940GZZLUGTR",
                "940GZZLUHSK",
                "940GZZLUNHG",
                "940GZZLUBWT",
                "940GZZLUPAC"
                *** missing ***
            ],

Is this a known issue?

Many thanks

2

@freakyleaf Welcome.

Let’s ping @jamesevans - I think I’ve had to deal with this with a code correction myself. I guess with a single NAPTAN code it’s not possible to show the station appearing twice?

1 Like
3

@freakyleaf:

Interesting. As you say, the second occurrence of ERC is missing from the list of naptanIds in orderedLineRoutes, but, if you look in stopPointSequences, the stops are correctly shown as two branches for each direction, one circular one starting and finishing at ERC and one covering the ERC-HSC section of the line.

Personally, I always use the stopPointSequences section, since I recall having had a number of other problems with orderedLineRoutes (details now lost in the mists of time).

That said, stopPointSequences is not without its flaws: duplicate branchIds; dangling/mismatched nextBranchIds & prevBranchIds; an annoying process at the Tfl end that attempts, unsuccessfully, to eliminate duplicate branches and causes general mayhem on diverging/converging routes

1 Like
4

Thanks all, I’ll take a look into it. As @nickp says, the route sections do appear correctly other than in the orderedLineRoutes.

2 Likes