Show page
Traveline Wiki

A PCRE internal error occured. This might be caused by a faulty plugin
This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
======TNDS issues======

 * Listed - most recent first *


=====Issue No: Copy this blank template, enter Issue number and brief description =====
 
  *Where detected (and date): 

  *Observation: 

  *Hypothesis:

  *Raised by:

  *Assigned to:
=====Issue No: 209 Missing WaitTimes for Layovers =====
 
  *Where detected (and date): SVRLAAO0650-20131109-9961.xml  from North West, 11 Dec 2013

  *Observation: WaitTimes are not in TNDS but are in source data (as submitted to ITOWorld). See VehicleJourney 88844 dep 0932 from Brierfield Chatburn Park Drive, should have 10 min WaitTime at Nelson Bus Station (Stand 6) 2500NEL0006. WaitTimes seem to be processed correctly on data from MDV.

  *Hypothesis: Basemap is either not expecting WaitTimes on both From and To stops, which is valid TXC, or is losing them on generating JourneyPatterns.

  *Raised by: John Prince / Peter Stoner 11 Dec 2013

  *Assigned to: Basemap
=====Issue No: 208 - Duplicate VehicleJourney elements in one file =====
  
  *Where detected(and date): TNDS export from 4 Dec 2013

  *Observation:  Some files in the SW region export contain identical 
   repeated VehicleJourney elements with the same VehicleJourney code.  

   Example file is: swe_38-1_-1-y10.xml

   *Hypothesis:  Duplicate VehicleJourneys have been included.
 
   *Raised by:  Carl Partridge, FatAttitude
  
   *Assigned to:


=====Issue No: 207 **CLOSED** No NE export to TNDS this week=====
  *Where detected (and date): Advised by Amy Armstrong 6 Dec 13

  *Observation: Christmas Holiday codes have caused the TXC export to TNDS from NE to fail

  *Hypothesis:

  *Raised by: John Prince 6 Dec 2013

  *Assigned to: Amy Armstrong 

  *John Prince 10 Dec 13: New software has been received and will be tested and used 11 or 12 Dec.
  *John Prince 16 Dec 13: NE data exported OK. 

=====Issue No: 206: Start date after end date =====
 
  *Where detected (and date): SVRYNAO042-20131223-26348 on 25/11/2013 

  *Observation:	Service 42 York - Selby start date (23/12/13) is after the end date (22/12/13)  

  *Hypothesis:	Export error originating with new registration at the beginning of Christmas holiday period defined by local SIS database.  

  *Raised by:	John Prince	

  *Assigned to:	John Prince
  
*John Prince 6 Dec 2013: The error on North Yorks' service 42 has been addressed by completely re-entering the data. A similar problem in SY has no such solution and is on a list of issues within SYPTE for review.


=====Issue No: 205 - 43A or 5A, Plymouth region =====
 
  *Where detected (and date): User feedback on NextBuses API results

  *Observation:
Stop: 1180PLA10022
Service: 43A to Saltash, Oaklands Green
Details: is now 5A service

  *Hypothesis:

  *Raised by: Tim Millington

  *Assigned to:


=====Issue No: 204 **CLOSED** Large number of services expiring this week  =====
 
  *Where detected (and date): TNDS export on 25 November 2013

  *Observation:  We're finding a lot of bus routes (around 570 of them, I believe) with services that have an end date of 30th November 2013.  This means that these services will effectively disappear from our timetables after this Saturday.  We suspect this is just an issue with the SW region but have not investigated further.

  *Hypothesis: Service end dates are incorrect, or news services are missing from export.

  *Raised by: Carl Partridge, FatAttitude

  *Assigned to:
  
   *Peter Stoner (ito) comments: Having spoken to Traveline SW it seems this was because the Christmas holiday dates had not been set.  Next week's data will correct this, but unfortunately this leaves a few days gap.  It seems the dates on the vehicle journeys do look ahead, so it is the global operating period end date which is the problem.  

===== Issue No: 203 missing stop call in LCB2 (SE: 5-LCB-2-y08-1) =====

  *Where detected (and date): set_5-LCB2-1-y08.xml

  *Observation: A passenger reports that this service stops at atcoCode 150035049005, but the journey pattern sections indicate a jump from 1500IM1035 direct to 1500IM2614. Viewing the route on a map suggests that 150035049005 is en-route, between these other two stops.

  *Hypothesis: 150035049005 should be in the route?

  *Raised by: Tim Millington

  *Assigned to:
  
  *Roger Slevin comments:  I have checked this out and forwarded the information to colleagues in Essex to make the correction.
 

=====Issue No: 202 Stop missing on some journies service 52B Honiton =====
 
  *Where detected (and date): swe_33-52B_-1-y10.xml 15/11/2013

  *Observation: From operator PDF http://www.stagecoachbus.com/PdfUploads/Timetable_26168_52A,%2052B,%2052C.pdf?onbusleafletid=186033 all journies from Honiton start from Lace Walk.

From the XML the 09:10 departure appears to start from the station at 09:13 not Lace Walk. See:

JPS_33-52B-_-y10-1-17-17-R

JP_33-52B-_-y10-1-17-R-17

VJ_33-52B-_-y10-1-13-T0

In the other direction the journey loop round the town varies. See note D in the PDF. This may not be relevant but can be a point of confusion.

  *Hypothesis:

  *Raised by: Brainforge

  *Assigned to:
Issue No: 201 NCSD - National Express 538, 544 services on same route but different stops - CLOSED
 
  *Where detected (and date): NCSD Data 15/11/2013

  *Observation: Searching for Carlisle on the National Express website shows service 538 serving Carlisle but the NCSD data has both 538 and 544 (plus others).


The NX website provides a link to the 538 timetable at 538.pdf - this also includes the 544. However, they do not provide a separate 544.pdf so possibility of NCSD user confusion.


According the NX this is because 538 and 544 travel on the same route but serve different stops.


This is not immediately obvious from NCSD. Could this link between the 538 and 544 be included in the NCSD data somehow - say a 'parent' the other 'child' service relationship?


I assume this is a generic issue and affects other NX services, and maybe even other operators.

  *Hypothesis:

  *Raised by: Brainforge

  *Assigned to:

	SP: The 538 and 544 are very distinct services. 544 is express service from Manchester to Glasgow while 538 is a regular stopping service from Coventry to Inverness.

=====Issue No: 200 Peculiar note on route 74 to Bedford =====
 
  *Where detected (and date): bed_1-74_-2-y08.xml 14/11/2013

  *Observation: Journey VJ_1-74-_-y08-2-32-T2 has a strange note attached.

In operator PDF http://www.stagecoachbus.com/PdfUploads/Timetable_40434_74.pdf?onbusleafletid=184590 there is no obvious explanation!

  *Hypothesis: John Prince 10 Dec 2013: This looks like a note to the driver "Pay in at 0830 in Bedford bus station", NoteCode ra008. It is a Stagecoach Bedford service.

  *Raised by: Brainforge

  *Assigned to (John Prince 10 Dec 2013): Stuart Reynolds

=====Issue No: 199 NCSD Missing national operator codes =====
 
  *Where detected (and date): NCSD/TXC/NX_532.xml 13/11/2013

  *Observation: Looks like this is missing in all NCSD files.

  *Hypothesis:

  *Raised by: Brainforge

  *Assigned to:
  *Peter Stoner (ito) comment: The NCSD data does not have the National Operator Codes but a NCSD column has been added to the NOC file. At the moment it only lists those operators whose data in NCSD is NOT a copy of the data which is already included in the datasets for the Traveline regions.  
=====Issue No: 100 - Blank Serviced Organisations in South region =====
 
  *Where detected (and date): TNDS on 5/11/2013

  *Observation: Many files within the export contain redundant, empty ServicedOrganisation elements with no working days, or holidays.  Despite being empty, these organisations are actually referenced by vehicle journeys within the XML file.  This is ambiguous and might be invalid TransXChange, since it could be interpreted as saying that the vehicles on these journeys do not run at all. 

Additional information - the ServicedOrganisations in question have strange names such as 'QE0 bus.cif' :-

''<ServicedOrganisation>
      <OrganisationCode>1</OrganisationCode>
      <Name>
QE0 : Bus.cif
</Name>
    </ServicedOrganisation>'' 

Example files with this issue are:
SVRABAO001-20130920-38.xml
SVRABAA002B-20130910-2.xml


  *Hypothesis:  Redundant ServicedOrganisation elements exist that ought to be deleted.

  *Raised by:  Carl Partridge, FatAttitude

  *Assigned to:
  *Peter Stoner(ITO) comments: These files are from Scotland. AB - Aberdeen.  In the files quoted, the Serviced Organisation is listed, albeit with rather a strange reference, but as far as I can see, is not applied to any journeys, therefore it has no effect. 

=====Issue No: 198 NW Incorrect running times (PT0M) =====
  *Where detected (and date): SVRLAMO0100-20130204-6285.xml, 29/10/2013
  *Observation: PTOM running time for the first 11 links. This is not realistic.
  *Hypothesis: Incorrect 0 timings or perhaps timings accurate to the second are required?
  *Raised by: Tim Millington
  *Assigned to:
  *Peter Stoner(ito) comments: in this week's data the file is probably SVRLAMO0100-20130204-8551.xml and I note there is a StartDeadRun.  It is likely therefore that the part of the pattern that has the PT0M timings is that part of the pattern that is not shown as in public service.  If correct then the coding may be correct if inelegant. 
 Issue No: 197 CLOSED NW running times incorrect 
  *Where detected (and date): SVRLABO0760-20130609-5211.xml (21 October 2013)
  *Observation: running times in TNDS does not match other published timetables
  *Hypothesis: Vehicle Journey overrides may not have been processed correctedly
  *Raised by: Carl Partridge/Peter Stoner
  *Assigned to: BaseMap
  *Peter Stoner comments: The cause seems to be that the 5 minute wait time at Abingdon Street in Blackpool Town Centre is not being communicated correctly in TNDS.  This is covered in Issue 186.
  *Peter Stoner comments: LABO0760 does not appear to be in current data.  Need to find another example.
  *Peter Stoner comments:  Issue 209 takes this issue forward with a current example.


=====Issue No: 196 NE Serviced Organisations =====
  *Where detected (and date): all NE.zip data (15 October 2013)
  *Observation: Holiday date ranges are listed in the Serviced Organisations but the references to serviced organisation in the vehicle journeys are in terms of "working days".
  *Hypothesis: journey days of operation or non operation should be expressed as "holidays" if that is what is listed for the serviced organisation
  *Raised by: Carl Partridge
  *Assigned to: Amy Armstrong (24 October 2013)
  *Peter Stoner comments: see issue 192 for the XML extracts that illustrate this.
  *Carl comments: 

instead of writing:

<ServicedOrganisationDayType>
<DaysOfOperation>
<WorkingDays>
<ServicedOrganisationRef>0000</ServicedOrganisationRef>
</WorkingDays>
</DaysOfOperation>
</ServicedOrganisationDayType>


they should write:

<ServicedOrganisationDayType>
<DaysOfNonOperation>
<Holidays>
<ServicedOrganisationRef>0000</ServicedOrganisationRef>
</Holidays>
</DaysOfOperation>
</ServicedOrganisationDayType>




=====Issue No: 195 WM Differences in EM and WM data for service 8 Burton on Trent =====
  *Where detected (and date): em_11-8C-1-y08.xml twm_4-8A-1-y11.xml 24/10/2013
  *Observation: This serves New St in Burton On Trent. The EM and WM regions give different stoppointrefs for New St. Can cause duplication in timetable information returned to user.

See for instance:

http://nextbuses.mobi/WebView/BusStopSearch/BusStopSearchResults/dbsjapmd?searchType=route&searchFilter=8
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Keith Sabin (Burton on Trent being in Staffordshire) (24 October 2013)


=====Issue No: 194 Two National Operator Codes for NN Cresswell =====
 
  *Where detected (and date): SW/swe_45-973_-2-y10.xml and WM/twm_9-973_-1-y11.xml 22/10/2013

  *Observation: I recall reporting similar elsewhere. Maybe there are other instances. Data consistency check needed somewhere? Happened to spot this by chance manually, should be able to find a way to automatically pull out other instances another day (assuming enough other information is consistent!).

  *Hypothesis:

  *Raised by: Brainforge

  *Assigned to:
  *John Prince comments 6 Dec 13: You will notice that there are two local codes in use for this operator and therefore two lines are required in NOC database. If two local codes are not required, Keith Sabin should ask for one to be removed and if there is no reason to have two NOC codes, Keith Sabin should ask for one to be removed.
  *Assigned to Keith Sabin 6 Dec 13


=====Issue No: 193 Service 15 Bath University Tue-Sun Night Journeys =====
 
  *Where detected (and date): swe_40-15_-1-y10.xml 22/10/2013

  *Observation: Operating profile of day / evening services have non-opdays of Bath Spa University holidays. The jrouneys after midnight do not have this flag. Is this an omission?

  *Hypothesis:

  *Raised by: Brainforge

  *Assigned to:


Issue No: 192 NE CLOSED Possible ambiguity in TNDS VehicleJourney elements
 
  *Where detected (and date): TNDS, 15th October
  *Observation: VehicleJourney references working days that don't exist
  *Hypothesis:  The document may be incorrect
  *Raised by:  Carl Partridge, FatAttitude
  *Assigned to: see issue 196

In file NE_090_PC2407_75.xml, there are VehicleJourney elements which reference 'Working Days' of a ServicedOrganisation as follows: 

       <ServicedOrganisationDayType>
          <DaysOfOperation>
            <WorkingDays>
              <ServicedOrganisationRef>0000</ServicedOrganisationRef>
            </WorkingDays>
          </DaysOfOperation>
        </ServicedOrganisationDayType>


However, the ServicedOrganisation in question has no working days defined, it only has holidays:

  <ServicedOrganisations>
    <ServicedOrganisation>
      <OrganisationCode>0000</OrganisationCode>
      <Name>School*Holidays</Name>
      <Holidays>
        <DateRange>
          <StartDate>2013-07-20</StartDate>
          <EndDate>2013-09-01</EndDate>
        </DateRange>
        ...edited for brevity
      </Holidays>
    </ServicedOrganisation>
  </ServicedOrganisations>


How are we to interpret this XML?  The TransXChange Schema guide does not seem to give any clear guidance.  If the service runs in term time, I would expect it to be represented by 

    <ServicedOrganisationDayType>
    <DaysOfNonOperation>
    <Holidays>
    ...


Issue No: 191 CLOSED SW service 484 in Truro in TNDS but not appearing in Nextbuses
  *Where detected (and date): TNDS, NextBuses (21 October 2013)
  *Observation: not appearing in the NextBuses scheduled times API
  *Hypothesis: incorrect times for some buses
  *Raised by: Carl Partridge
  *Assigned to: Peter Stoner
  *Peter comments: The 484 is still showing in the current data but with an end date of 8 October 2013.  However there seems to have been a delay in notifying
the withdrawal of the service as it was in the data on 4 October with
an end date of 29 November 2013.
  *Julie Williams comments:  The service was withdrawn by Cornwall Council at very short notice. It was registered to operate from 30.09.13 but never actually started operation. Notice was given of cancellation of the service after the date it was actually registered to start.
  *Peter comments: Where a service is withdrawn earlier than previously stated it is best that the data remains available with the new date until the previous date has passed. 

  

Issue No: 190 CLOSED SW Handling of planned road closures and associated temporary timetables
  *Where detected (and date): Stops dvngagag, dvngagaj Newton Poppleford area 12/10/2013
  *Observation: The other day the Traveline SW site showed the standard 52A,52B,157 timetables plus a notice about the planned 3 week road closure and link to temporary timetable information.
Could notices of such pre-planned works be cascaded as a note against the service in the TNDS XML? Ideally as soon as publicly announced, even if the temporary timetable is not finalised.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: The facilities for some regions to incorporate temporary timetables will be enhanced in a few weeks time.  However there are no plans to make the incident notes available that some regions generate.


Issue No: 189 RESOLVED SW Wessex Bus - Missing National Operator Code
  *Where detected (and date): swe_38-3A_-1-y10.xml 02/10/2013
  *Observation: In operator details the National Operator Code is missing.
Its not the only instance this, but I thought I had a few minutes to add Wessex Red to part of my processing which uses the Nat Op code... and I try to add more of the larger operators to the process when I have the opportunity.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: Wessex Red was one of several SW region operators that were missing codes.  These are now added.  Wessex Red appearing as FHMR converting from SW local code FH1.

Issue No: 188 CLOSED SW TimingLinks contain an incorrect Activity element
  *Where detected (and date): File **swe_30-596_-1-y10.xml** from the most recent TNDS (24 Sep 2013)
  *Observation: 

TransXChange file swe_30-596_-1-y10.xml defines a circular bus route with Published Line Name 596.

I would expect the final Timing Link on this route to have an Activity element with value 'setDown', however it is set to 'pickUpAndSetDown'.  (see XML fragment below)

Is this correct?  I may be wrong but it would be odd if the bus picked up passengers at the end of its trip.

If this is incorrect, could the rest of the TNDS also be integrity checked in case there is a problem, as our systems rely on the Activity element being correctly populated.

       <JourneyPatternTimingLink id="JPL_30-596-_-y10-1-1-H-1-15">
        <From SequenceNumber="14">
          <Activity>pickUpAndSetDown</Activity>
          <StopPointRef>0800COC30048</StopPointRef>
          <TimingStatus>OTH</TimingStatus>
        </From>
        <To SequenceNumber="15">
         <Activity>pickUpAndSetDown</Activity>  <!-- SHOULD THIS BE setDown ? -->
          <StopPointRef>0800COC30049</StopPointRef>
          <TimingStatus>PTP</TimingStatus>
        </To>
        <RouteLinkRef>RL_30-596-_-y10-1-H-1-14</RouteLinkRef>
        <RunTime>PT1M3S</RunTime>
      </JourneyPatternTimingLink>


  *Hypothesis: On its final stop, the Activity should be set to 'setDown'.
  *Raised by: Carl Partridge, FatAttitude
  *Assigned to: Peter Stoner
  *Peter Stoner comments: This has some aspects similar to issue 94 where we answered that "Pickup and Set down" is the default for normal operation, including the arrival at an interchange point where there is a wait, or a terminus.

 =====Issue No: 186 Resolved Y W NW S Wait times not appearing =====
  *Where detected (and date):  Wetherby bus station on route 770 (23 Sept 2013)
  *Observation: There is zero time at the bus station and subsequent times on the jouneys are early but the amount of the missing wait.
  *Hypothesis: That WaitTime has been incorrectly coded in the export in TXC2
  *Raised by: MXdata
  *Assigned to: John Prince (26 September 2013)
  *John Prince: Trapeze have been notified. (27 September 2013)
  *Trapeze report: Testing of revised software nearly complete (30 September 2013)
  *John Prince comments 6 Dec 2013: The correction which has been implemented removed duplicate timing links. The issue regarding missing Wait times has not been logged yet. Inconsistencies between the schema and the notes regarding the recording of Wait times and the computation of passing times are with Nick Knowles.
  *John Prince 10 Dec 2013: Nick Knowles says schema comment that WaitTimes are duplicated is wrong and will be removed. Martin Sizckowski (VIX Technology) says that TXC 1.2.1 allowed redundant TimingLinks from B to B to hold the WaitTime as RunTime.
  *10 Dec 2013 Resolved
Issue No: 185 CLOSED NE Common Names and Locality Names in NaPTAN and TNDS Stoppointref Data mismatch
  *Where detected (and date): Stoppoint ref 410000004936
  *Observation: I was aware of something like this going on with discrepancies between the NaPTAN and TNDS data but today decided to have a good look.

Searching my site for Meadow Well stops also returns the West Monkseaton stops. Reasonable result, but not seeing the name 'Meadow Well' in some stop titles is confusing. Combining both locality names could help, but which one should be first? It would make the name display crowdier. By the same token there maybe cases where the same applies to the common names!

Any suggestions?

Also if two or more routes share the same stop then there are several copies of the TNDS Stoppoint Data - one in each file. Can this information be relied upon as being identical in all cases? My internal data handling assumes this may not be the case - if it can be relied upon as being identical (in a single download) then some simplification is possible. But what about stops on routes which span regions?

Separate download file containing just the current snapshot of the TNDS Stoppoint Data?
Would still need to be in each XML for those who want just one complete file.
__**NAPTAN Data**__
 AtcoCode = 410000004936
 NaptanCode = twrgtmgt
CommonName = Newsteads Drive-Chathill Close
Indicator = E-Bound
LocalityName = West Monkseaton
ParentLocalityName = NT
__**TNDS Stoppoint Data**__
stoppointref = 410000004936
CommonName = Newsteads Drive E (04936)
LocalityName = Meadow Well
localityqualifier = NT
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Peter Stoner (27 September 2013)
  *Peter comments: If there is a variation between the stop information within the TXC2 and the centrally downloaded NaPTAN, please go via the central file. The names in the TXC2 files should be the same but may not have been kept up to date.

Issue No: 184 CLOSED NE Routes 62 Carlisle Bank Holidays (See also issue 156)
  *Where detected (and date): NE_090_PC2407_62.xml 26/09/2013
  *Observation: Should MonFRI vehicle journey VJC_O53 only run on bank holidays?
See also VJC_054. Could these vehicle journies be combined into one Sundays + special op days on bank holidays?
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: This is a further example of the issue being dealt with under issue 114.
Issue No: 183 CLOSED SE Saturday journeys on 135 at Wallingford
  *Where detected (and date): set_2-135C-1-y08.xml 26/09/2013
  *Observation: The XML shows some Saturday journies.
The operator PDF does not show these - http://www.thames-travel.co.uk/timetables-fares/oxfordshire-and-reading/135/

Is this an error in operating / non-operating dates? - compare with Tuesday journeys.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: The PDF is now showing Saturday journeys.

Issue No: 182 CLOSED L TFL duplicate <VehicleJourney>s
  *Where detected (and date): tfl_54-139_-23543-y05.xml 2013-09-24
  *Observation: The VehicleJourney objects appear to be duplicated, they run from VJ_54-139-_-y05-23543-1-MF to VJ_54-139-_-y05-23543-292-MF twice, seemingly containing the same data. We noticed as this triggered a minor bug in our parser. 
  *Hypothesis: 
  *Raised by: Tom at TransportAPI
  *Assigned to: Peter Stoner (27 September 2013)
  *Peter comments: Reported to TfL but resolved in the next data.

Issue No: 181 RESOLVED SW Data Supplier codes in Operator Field
  *Where detected (and date): BaseMap reports (19 September 2013)
  *Observation: Codes CO DE DO GL PL WF
  *Hypothesis: Data Suppliers should replace these with codes for the operators of the services
  *Raised by: Peter Stoner
  *Assigned to: Andy Hole (19 September 2013)
  *Awaiting report from BaseMap to locate the use of these codes.
  *Andy Hole comments: These codes are used in files that should not have been exported and are removed from the current data.

Issue No: 180 CLOSED Empty JourneyPatternSection
  *Where detected (and date): 11/09/2013; L/tfl_59-99_-34037-y05.xml
  *Observation: <JourneyPatternSection id="JPS_59-99-_-y05-34037-118-3-I"/>
  *Hypothesis: 
  *Raised by: Tim Millington
  *Assigned to:
  *Peter Stoner comments: This could have been a teething problem with a change in processes at TfL. The file is now provided with no emply JourneyPatterSections.

=====Issue No: 179 NE Incorrect detection of duplicate journeys  =====
  *Where detected (and date): Servic 100 Alston to Crook, (7.9.2013)
  *Observation: Partial duplication shown in ITOquality
  *Hypothesis: that there is an error in the detection of bank holiday journeys
  *Raised by: Simon Day
  *Assigned to: Peter Stoner
  *Peter Stoner comments: NE checking the operation of their BTD to TXC converter.  (September 2013)
=====Issue No: 178 L Wembley Park bus stop in Jubilee Metro Line Journey =====
  *Where detected (and date): output_txc_01JUB_.xml file downloaded 18/06/2013
  *Observation: Journey Pattern Timing links use incorrect stop references - using bus stop reference for a metro journey on Jubilee line
  *Hypothesis: Stop reference 490000257374 should be one of 9400ZZLUWYP1,9400ZZLUWYP2,9400ZZLUWYP3,9400ZZLUWYP4
  *Raised by: Rohaan Thavarajan
  *Assigned to: Gerard Butler (21 September 2013)
  *Peter Stoner comments: There has been a gap in publishing TfL data but issue still present in data published 20 September 2013. 

Issue No: 177 RESOLVED SE.zip won't decompress
  *Where detected (and date): 2013-09-03 SE.zip
  *Observation: Unzip fails:
"[download/SE.zip]
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive."
  *Hypothesis: Something going wrong with the zipping - the log file notes three separate SE files possibly overwriting each other on upload? 

"Region: SE, File: SE2_TXC_130829.zip, Uploaded: 29/08/2013 07:55:40 State: Pass
Region: SE, File: SE3_TXC_130829.zip, Uploaded: 29/08/2013 08:22:04 State: Pass
Region: SE, File: SE_TXC_130829.zip, Uploaded: 29/08/2013 08:56:58 State: Pass"
  *Raised by: Tom @ TransportAPI
  *Assigned to: Peter Stoner (3 September 2013)
  *Peter comments: Apologies.  We hope this will be rectified tomorrow.
  *Peter comments: the zip file has been reloaded and should now download correctly. 



Issue No: 176 CLOSED NE Arriva 50 service, Evenwood to Durham timings inaccurate
  *Where detected (and date): NE_130_PB2717_50 30/08/2013 
  *Observation: Some of the timings do not match the on-line timetable (http://www.arrivabus.co.uk/serviceInformation.aspx?id=20820) and indicates departures different to those returned by NextBuses API. Example VJC_I11 (start time 17:10) refers to JPS_I3 which indicates a cumulative run-time of 34 minutes to 13004000G (Bishop Auckland Bus Station G), i.e., 17:44, whereas the timetable shows 17:45. The timetable indicated a wait time at the bus station with a departure time of 17:47, but there is no wait time indicated in the file. All subsequent stop times according to the file are consequently earlier than those according to the published timetable.
  *Hypothesis: Timing inaccuracies? Missing wait times?
  *Raised by: Tim Millington
  *Assigned to: Amy Armstrong (3 September 2013)
  *Amy reports: this service no longer operates from 1 September.

Issue No: 175 CLOSED Service 5 Whitby Monday journeys
  *Where detected (and date): NE_Tees_PB2087_5.xml 28/08/2013
  *Observation: Journeys such as VJC_I171 are shown in the XML as operating every Monday.  They only operate on bank holiday mondays.

See http://www.arrivabus.co.uk/uploadedfiles/Services/North_East/nesk5,5a,5b_090712_160712.pdf
  *Hypothesis:
  *Raised by: brainforge
  *Assigned to:
  *Peter Stoner comments: same issue as 114 

=====Issue No: 174 Resolved W Consistency of NationalOperatorCode in XML data =====
 
  *Where detected (and date): SVRPWAO088-20121011-4111.xml and related 26/08/2013

  *Observation: The NationalOperatorCode for route 88 of this operator is OWEN. Files for other routes (71, 86) by the same operator have NationalOperatorCode of OWNC.

I have seen similar with regional subsidiaries of the larger operators, but first time I have seen it with a small one.

I use the NationalOperatorCode to drive a new part of my functionality. At one level I can use one of the codes as an alias - but then I would have to manually check all XML files relating to every operator to detect instances of this (but it is supposed to be an automatic process!).

  *Hypothesis:

  *Raised by: Brainforge

  *Assigned to: Martyn Dunn (5 September 2013)
  *John Prince 6 Dec 13: You will see that the operators have different VOSA names and licence numbers because they are not the same; Wales have re-allocated some local operator codes to services to remove the confusion. 
  *Resolved 10 Dec 2013 John Prince

Issue No: 173 RESOLVED SE Route 615 Hatfield / Stanmore Operating Dates
  *Where detected (and date):  	set_7-615A-1-y08.xml 16/08/2013
  *Observation: In Operating Profiles both journeys VJ_7-615-A-y08-1-75-T0 and VJ_7-615-A-y08-1-22-T0 appear to operate after 1st Sept. From operator site http://www.unobus.info/service.shtml?serviceid=1684 I think VJ_7-615-A-y08-1-22-T0 does not operate after that date.

In addition notice that the current XML file contains both the current and the September timetables. Would be easier to manage as 2 separate files with appropriate service operating dates.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Stuart Reynolds (3 September 2013)
  *Stuart reports: No issue found. The trips which cease are correctly - although messily - coded. In particular, the VJ that he quotes (ending -22-T0) is the 0905 trip that runs AFTER 1 Sep and matches what the operator shows.

Issue No: 172 RESOLVED SVRYSFO027-20130827-34148.xml incomplete in download
  *Where detected (and date): 14/08/20113
  *Observation: File SVRYSFO027-20130827-34148.xml, extracted from Y.zip is corrupt/incomplete
  *Hypothesis: 
  *Raised by: Tim Millington
  *Assigned to:
  *Dan comments: one of the TXC files in the Y.ZIP had not compressed properly, so I've just re-zipped and uploaded the data.
  

Issue No: 171 RESOLVED Y  CoastLiner Line 20 not in TNDS
 
  *Where detected (and date): http://www.yorkbus.co.uk/cmsUploads/route/files/20ttWEB250213.pdf (13 August 2013)
  *Observation: I can sometimes see this service in live departures but not in TNDS
  *Hypothesis: Missing from TNDS
  *Raised by: Tim Millington
  *Assigned to: John Prince (13 August 2013)
  *Peter Stoner comments: It has been in the data since September.  Not sure why it was missing before that.
=====Issue No: 170 SW Cremyll Ferry Atcocode and Stoppointref mismatch =====
  *Where detected (and date): swe_30-2_-1-y10.xml swe_30-2_-2-y10.xml 11/08/2013
  *Observation: The Cremyll end stoppoint code is 9300CRE1. The equivalent Atcocode from NaPTAN is 9300CRE. From http://www.dft.gov.uk/transxchange/schema/2.4/TransXChange_registration.xsd I expect it to be the same.

Is one of these wrong or have I missed something.

I think it applies to other ferry points in the Plymouth area, but I have not checked all of them. See list here http://www.plymouth.gov.uk/homepage/transportandroads/publictransport/ferryservices.htm
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: DfT
  *Peter Stoner comments: SW data seems to be referring to FBT (ferry berth) points eg 9300CRE1 which have not been set up in NaPTAN, under the FER (Ferry or Port Interchange Area) codes eg 9300CRE

=====Issue No: 169 WM Route 746 Pixley - Vehicle summer Sunday journeys give 2012 dates =====
*Where detected (and date): twm_3-476_-1-y11.xml 09/08/2013

*Observation: Might only have been an issue on 19th May 2013, but still confusing. Looks like the operator PDF dates are a day out as well...
http://www.drmbus.com/pdfs/476_ledbury_bartestree_hereford.pdf

*Hypothesis:

*Raised by: Brainforge

*Assigned to: Keith Sabin (12 August 2013)


Issue No: 168 CLOSED Duplicate Routes/Journeys/Sections with different details
 
  *Where detected (and date): em_13-101_-1-y08.xml set_13-101_-1-y08.xml 02/08/2013

  *Observation: Route/Journey/Section IDs are duplicated across files but have different details. EG. RouteID R_13-101-_-y08-1-H-1 is in both files above, but have description 'Bus Station - Queensgate Bus Station' and 'Central Railway Station - War Memorial' respectively. Which one should be deemed as correct? This phenomenon occurs for other IDs too.

  *Hypothesis:

  *Raised by: rthavarajan

  *Assigned to:
  *Peter Stoner comments: These elements are not the same.  The references may only be unique within the file where they occur or possibly within the same regional zip file.  The only references which unique and peristent across all the data are the NaPTAN number and National Operator Code.  


Issue No: 167 CLOSED Route 462,463 Woking school holiday journeys
  *Where detected (and date): set_6-463D-1-y08.xml set_6-462D-1-y08.xml 29/07/2013
  *Observation: Service details and operating profiles for VJ_6-462-D-y08-1-8-T0 and VJ_6-463-D-y08-1-5-T0 do not appear to match operator PDF.
http://www.arrivabus.co.uk/serviceInformation.aspx?id=15625&r=South+East
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: assumed to be another example of the operation profile problem raised with issue 128

Issue No: 166 CLOSED Route 6 Newbury Days of operation
  *Where detected (and date): set_4-6C-1-y08.xml 26/07/2013
  *Observation: For 06:55 from Newbury XML gives two vehicle journeys with different notes, one schooldays the other school holidays.

The operating days for the non-schoolday journey appear not to be reflected in the operator PDF.

http://www.newburyanddistrict.co.uk/pdf/jan13/connect-service-6-and-6A-%28effective-from-18-Feb-2013%29.pdf
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: The PDF shows the 0655 journey extends to Newbury College and Park House School on schooldays only.   This is shown as a note on the line rather than a separate column.
Issue No: 165 CLOSED Route 71 Sheffield Different AtcoCodes for same stop
 
  *Where detected (and date): SVRYSEO071-20130721-39461.xml, em_11-71_-1-y08.xml : 26/07/2013

  *Observation: For Sheffield Interchange Yorkshire data has stop point ref 37070005, East Midland data has 37010121. 

  *Hypothesis: 

  *Raised by: Brainforge

  *Assigned to:
  *Peter Stoner comments: This is the same as issue 138
Issue No: 164 CLOSED SW Route X1 to Lymington missing Tue-Fri journeys
 
  *Where detected (and date): swe_42-X1_-1-y10.xml 26/07/13
  *Observation: Most Mon-Fri journeys appear as Monday only in XML.

Initially spotted as Mon only on VJ_42-X1-_-y10-1-28-T0 which should be MonFri.
VJ_42-X1-_-y10-1-49-T0 is correct with MonFri
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Andy Hole (12 August 2013)
  *Andy Hole replies:  The data is correct, the X1 has a different route on a Monday than the rest of the week due to road closures for the Christchurch Market, this only affects intermediate stops so is not reflected on the more bus website. 


Issue No: 163 CLOSED Route 81 Bolsover Unexpected Sunday Journey
  *Where detected (and date): em_11-81A-1-y08.xml 25/07/2013
  *Observation: Vehicle journey VJ_11-81-A-y08-1-19-T0 has some special op days ranges which overlap with Sundays.
According to http://www.derbysbus.info/times/timetables/081M_121028.pdf there are no Sunday journeys.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: 
  *Peter Stoner comments: this is thought to be another example of issue 128 which has already been raised with MDV.
=====Issue No: 162 SE Too many timing points ===== 
  *Where detected (and date): Surrey data Set_6-34D-1-y08.xml (17.7.2013) 
  *Observation: example 2041 line 34 from St Johns (Woking, Raglan Road (adj) to Working Railway Station.  TimingStatus PTP at Ragland Road, Post Office, St James Close, The Triangle, Bridge Barn Lane, Cawsey Way.  ie 5 timing points in 6 minutes.  TimingStatus of 4 remaining stops is OTH. 
  *Hypothesis: Were these PTP timings in the registration or added afterwards?
  *Raised by: Omnitimes
  *Assigned to: Stuart Reynolds (25 July 2013)
  *Stuart comments (23 August 2013): The data in the system uses OTH, but is exporting as a mix of OTH and PTP. This is a new issue, and I have raised it with MDV.


Issue No: 161 RESOLVED Blandford to Dorchester 09:00 Not Wed / Wed Only
  *Where detected (and date): swe_42-311_-1-y10.xml 24/07/2013
  *Observation: See http://www.morebus.co.uk/service.shtml?serviceid=1664

Vehicle journey VJ_42-311-_-y10-1-3-T0 is Wed only, appears to be correct.

Vehicle journey JP_42-311-_-y10-1-10-H-10 has no days of week specified.
Should this be Mon,Tue,Thu,Fri? - there is no other 09:00:00 departure.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Andy Hole
  *Peter Stoner comments: According to the operators website the Wednesday journey terminates at Dorchester Market instead of Trinity Street C1.

 <DaysOfWeek> <NotWednesday /> </DaysOfWeek> is not being recognised by BaseMap.  Is it valid?

  *Peter Stoner comments: NotWednesday is valid in the schema, despite the TXC schema guidance not listing it.  BaseMap are now exporting the NotWednesday status correctly.


 
=====Issue No: 160 EA SE Correspondence address =====
  *Where detected (and date): Suffolk data eg suf_18-196_-2-y08.xml (20 July 2013)
  *Observation: Fails to pass schema check
  *Hypothesis: The element 'CorrespondenceAddress' in namespace 'http://www.transxchange.org.uk/' has invalid child element 'Line' in namespace 'http://www.govtalk.gov.uk/people/AddressAndPersonalDetails'. List of possible elements expected: 'PostCode' in namespace 'http://www.govtalk.gov.uk/people/AddressAndPersonalDetails'. (Line 2607)
  *Raised by: BaseMap 
  *Assigned to: Stuart Reynolds (25 July 2013)
  *Stuart reports (23 August 2013):  Still an issue - MDV have been prompted to fix urgently.


Issue No: 159 RESOLVED SW Route 102 EAST HUNTSPILL – King Alfred School – BURNHAM-ON-SEA
  *Where detected (and date): swe_41-102_-5-y10.xml 22/07/2013  
  *Observation: No separate XML file or mention of Hatch Green Coaches service. See Hatch Green website:
http://www.hatchgreencoaches.co.uk/somerset1bus-services/east-huntspill_burnham-on-sea.html

However, there is a First 102 service at Burnham but again I could not find a  mention that Hatch Green operate any of the journeys.

Other Hatch Green services appear in the TNDS data correctly.

I checked TNDS data for 22/06/2013 as I still had it in case it was an end of school term issue, but again no mention of Hatch Green.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Andy Hole (25 July 2013)
  *Andy Hole replies: The Hatch Green 102 service is not open to the public so not included in traveline data.
  *Andy Hole updates: The operator confirms that the service is open to the public and it will appear in the data soon.


Issue No: 158 CLOSED Route 301 Welwyn GC Operating Profile Date
  *Where detected (and date): set_7-301A-1-y08.xml 20/07/2013  
  *Observation: Vehicle journeys VJ_7-301-A-y08-1-2-T0, VJ_7-301-A-y08-1-8-T0
 
From operator PDF looks like these are Mon-Fri journeys (ignoring school hols).

The XML operating profile appears to show them as Thurs/Fri with extra special days INCLUDING SUNDAYS!
See for instance special operating range starting Saturday 2013-07-27
See operator PDF http://www.arrivabus.co.uk/uploadedfiles/Services/South_East/SESV300,301_160412_090412.pdf
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: This is another example of operating profile errors being addressed under issue 136.
Issue No: 157 RESOLVED SE Route 171 Bracknell Circular
 
  *Where detected (and date): set_4-171B-1-y08.xml 18/07/2013
  
  *Observation: I cannot match VJ_4-171-B-y08-1-48-T2 to any of the journeys in the operator PDF.
  http://www.courtneybuses.com/files/171T-NEW.pdf
  
  Looks like there are journeys with similar issue, could be circular route related.
  Route 171 is also operated by First to a different pattern. 

  *Hypothesis:
 
  *Raised by: Brainforge

  *Assigned to:
  *Peter Stoner comment: This might be another example of the region having created overlapping sections on the loop in order to ensure the data works better in the jorney planner.  I want to establish that the data is incorrect before asking the region to investigate further.
  *Stuart Reynolds reports (23 August 2013): an underlying data error has now been rectified.

Issue No: 156 CLOSED Routes 103, 104 Carlisle Issues 
  *Where detected (and date): NE_090_PC2407_104.xml NE_090_PC2407_103.xml 16/07/2013
  *Observation: (a) From operator PDF looks like vehicle journey VJC_I95 should only run Bank Holidays. Currently XML shows it runs every Mon and Fri.
  Problem also appears with other Sunday / bank holiday times, but the others don't appear to make much difference.

  See: http://www.stagecoachbus.com/PdfUploads/Timetable_28629_103,%20104%20%28Carlisle%29.pdf

  (b) Operator PDF also shows various notes re school / university days. I cannot see these notes in the XML.
  
  (c) There seems to be some confusion as to whether 07:55 from Carlisle is a 103 or 104.
  Is the operator PDF link out of date? - quick look and I either got errors or could not find later one! 
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: This is a further example of the issue being dealt with under issue 114.

Issue No: 155 CLOSED Route 215 Chatsworth House - East Midland Region dates of operation
  *Where detected (and date): EM/em_15-350_-1-y08.xml 15/07/2013 
  *Observation: The XML file appears to have the Sunday services repeated for everyday.
  Looks similar to issue 143.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: This is another example of operating profile errors being addressed under issue 136.
=====Issue No: 154 EA SE Brightlingsea and East Mersea Ferry=====
 
  *Where detected (and date): http://brightlingseaharbour.org (June 2013) 
  *Observation: Can't find this ferry in the data or the Traveline journey planner. 
  *Hypothesis:  Data may not have been updated for 2013.
  *Raised by: Peter Stoner 
  *Assigned to: Roger Slevin
  *Stuart reports (23 August 2013): Essex has been asked to create the ferry data

Issue No: 153 CLOSED Route 350 Scunthorpe - East Midland Region and York Region disagree
  *Where detected (and date): Y/SVRYHAO350-*.xml EM/em_15-350_-1-y08.xml 11/07/2013
  *Observation: The East Midland files appear to have the Sunday services repeated for everyday.
  The Yorkshire files appear to match the operator information.
  
  Looks similar to issue 155.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: this is another example of profile errors being addressed under issue 136.

Issue No: 152 Route 193 CLOSED Buxton / Taddington
 
  *Where detected (and date): EM/em_11-193_-1-y08.xml 11/07/2013
  
  *Observation: For vehicle journey VJ_11-193-_-y08-1-2-T0 the note refers to this being a School Holiday Mon-Fri service.
  However, only Mon, Wed, Thurs and Fri showed in my application.

  The operator information agrees with the note which suggests a problem in the XML operating profile.
  http://tmtravel.co.uk/app/download/5777033274/193.pdf
  
  On further investigation found the operating profile has a regular Mon,Wed,Thu,Fri but not Tuesday.
  Tuesdays are added in as special operating days, confusing but not unreasonable.
  However, Saturdays and Sundays are also added in as special operating days!
	Saturdays have a different journey pattern.
	There is no Sunday service. 

  *Hypothesis:
 
  *Raised by: Brainforge

  *Assigned to:
  *Peter Stoner comments: a further but useful example of issue 128

Issue No: 151 CLOSED Route 30 Whitehaven Mon, Fri, Sun Journeys
  *Where detected (and date): NE_090_PC2407_30.xml 11/07/2013
  *Observation: Vehicle journey VJC_I110 (as similar) shows as running every Monday and Friday.
  Is special specialOpDays / specialNonOpDays information missing?
  Should this journey information be combined with VJC_I111 Sunday journey?
  
  See http://www.stagecoachbus.com/PdfUploads/Timetable_29356_30%2031%2031A%20%28West%20Cumbria%29.pdf 
  *Hypothesis:
  *Raised by: Brainforge 
  *Assigned to:
  *Peter Stoner comments: another example of issue 114.
=====Issue No: 150 L Duplicate NaPTAN code confusion =====
  *Where detected (and date): 11/07/2013, NextBus API / L.output_txc_48011p / SE.set_5-741A-1-y08 
  *Observation: 490015048T / 490015048F appear to refer to the same physical stop (Westminster, Parliament Square, Stop F). Both codes are referred to in TNDS vehicle journeys. As a result, both stops show up in various delivery tools (eg Google Maps) and this is likely to cause passenger confusion.
  *Hypothesis: 490015048T / 490015048F are duplicates, each being used by different authorities.
  *Raised by: Tim Millington
  *Assigned to: Gerard Butler (23 July 2013)

Issue No: 149 CLOSED Monday to Sunday Journies on 313 Potters Bar
  *Where detected (and date):  set_7-313A-1-y08.xml 09/07/2013  
  *Observation: There are a number of Sunday / Bank Holiday journeys shown incorrectly in the XML as Monday to Sunday.
See for instance: VJ_7-313-A-y08-1-301-UL, VJ_7-313-A-y08-1-302-UL

The L region data does seem to have the same problem.
Issue 136 is a similar issue, so it could be a general SE region problem.

My program does not prioritize one region over another and I suspect it could be changeable over time as to which is the more reliable.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: This is another example of operating profile errors being addressed under issues 128/136.
Issue No: 148 CLOSED Route 65 Rossendale, Rawtenstall, All Saints confused by JourneyPatternTimingLink
  *Where detected (and date): SVRLABO0650-20120729-5394.xml 09/07/2013
  *Observation: The first 2 stops (250012922, 2500IMG2515) in JourneyPatternTimingLink JPS_LABO0650-2 have runtime of PT0M.
 In JourneyPatternTimingLink JPS_LABO0650-3 they have a runtime of PT480S.
 Could not correlate this journey with operator / metro information.
 From Google maps the longer runtime appears more appropriate.
 But what is going on might be obvious for someone with local knowledge!
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: This service is no longer in the NW data.
  

Issue No: 147 RESOLVED Service 128A in Royston is duplicated
  *Where detected (and date): Data from SE and EA (8 July 2013)
  *Observation: Similar versions of the same service are available from branches 7 and 20 
  *Hypothesis: That only one version needs to be submitted to TNDS 
  *Raised by: Peter Stoner 
  *Assigned to: Stuart Reynolds
  *Stuart replies: "I have suppressed the Cambs one for now, but will get the discrepancies checked out."



=====Issue No: 146 NE Route 14/X14 Morpeth=====
 
  *Where detected (and date): NE_310_PB2032_14.xml and NE_310_PB2032_X14.xml 05/07/2013
  
  *Observation: From note in the operator's timetables some X14 journeys operate through to Thropton as 14.
See http://www.arrivabus.co.uk/ServiceSearchResults.aspx?txt=x14&stype=service&reg=North%20East

I cannot see this information reflected in the XML files. 
 
For instance if trying to plan a journey from Morpeth Cottage Hospital to Newcastle Haymarket the XML indicates that there is both a 14 and an X14 at the same time - whereas the operator's note says they are the same vehicle.

Some way of providing that same note in the XML would be helpful and quicker / easier to implement than using something like the VehicleJourneyInterchange element 
  *Hypothesis: that set down only restrictions in the data are not being exported.
  *Raised by: Brainforge 
  *Assigned to: Amy Armstrong
  *Peter Stoner comments: it seems that the service 14 journeys are in the source data as set down only south of Morpeth, but that the export of the data is not including the set down only restrictions, meaning that both journeys appear. 
  *Peter comments: Setdown activity status is in the vehicle journeys of 14 and X14 data but not at sufficient stops.

=====Issue No: 145 S NE Bezier curve errors =====
 
  *Where detected (and date): ITOquality (2 July 2013)
  
  *Observation: North of Berwick upon Tweed

  *Hypothesis: stop bearings may be wrong or services allocated to the wrong stops.
 
  *Raised by: Peter Stoner

  *Assigned to
Issue No: 144 CLOSED Route X13 Abingdon - Oxford
  *Where detected (and date): set_2-X13_-1-y08.xml 01/07/2013
  *Observation: Comparing with operator's timetable
I am unable to match the 07:39:00 departures shown for VehicleJourneyCodes VJ_2-X13-_-y08-1-317-UL and VJ_2-X13-_-y08-1-253-UG with the operator's timetable at http://assets.goaheadbus.com/media/route_pdf/city13_X13_X3_23_Timetable_Web_2013.pdf
  *Hypothesis:
  *Raised by: Brainforge 
  *Assigned to:
  *Peter Stoner comments: Looks as if there is a loop in Abingdon which is not fully explained in the leaflet.
 
Issue No: 143 CLOSED Routes 517 Sunday Journeys
  *Where detected (and date):  	twm_4-T584-1-y11.xml 29/06/2013 
  *Observation: Vehicle journey VJ_2-517-_-y11-1-4-01 is listed in the XML as operating on Saturdays and Sundays.
  The council website PDF shows this particular journey as operating Mon-Wed only:
  http://www.worcestershirebus.info/timetables/Bus-services-512-517-and-519-from-08-04-2013.pdf
  There maybe other similar issues with other journies and also routes 512, 519.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: This is another example of operating profile errors being addressed under issue 136.
 
Issue No: 142 CLOSED Routes 584, 585, 588 Wolverhampton Sth Staffs rural Sunday Journeys
  *Where detected (and date):  	twm_4-T584-1-y11.xml and related 29/06/2013  
  *Observation: Various vehicle journies are listed in the XML as operating on Sundays.
  No Sunday journies are shown in operator website PDFs:
  http://www.codsallcars.co.uk/RuralLink.aspx
  http://www.arrivabus.co.uk/uploadedfiles/Services/Midlands/MDSL584,585,586,587,588_040911_150811.pdf

  *Hypothesis: 
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: This is another example of operating profile errors being addressed under issue 136.

 
Issue No: 141 CLOSED Route 7 Milton Keynes
  *Where detected (and date): set_13-7A-1-y08.xml 29/06/2013  
  *Observation: Vehicle journey VJ_13-7-A-y08-1-289-UL is shown in operating profile as MondayToSunday.

  From operator PDF http://www.arrivabus.co.uk/uploadedfiles/Services/South_East/SEMK7_020613_110413.pdf this looks like it should be Sundays and BankHolidays.
	
	Same issue applies to some of the other Vehicle Journeys. 
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to:
  *Peter Stoner comments: This is another example of operating profile errors being addressed under issue 136.
 
=====Issue No: 140 S StopPointRef and related AtcoCode / NaptanCode in NaPTAN.xml =====
 *Where detected (and date):SVRFSCW004-20130329-15237.xml 27/06/2013
 *Observation: This XML file contains a StopPointRef = 601031.
 
 A quick look and I cannot see any correspondence with data in NapTAN.xml.
 
 Should this be caught by a TNDS data sanity check?   
 *Hypothesis:
 *Raised by: Brainforge 
 *Assigned to: Peter Stoner
 *Peter comments: The stop is in the Western Isles.  There are also stops in Glasgow and Shetland which have not been added to the official NaPTAN.  These are the only Transport Authorities in the UK which are not updating their NapTAN information on a regular basis.
=====Issue No: 139 S Missing notes - W4 Stornoway =====
 *Where detected (and date):SVRFSCW004-20130329-15237.xml and similar 27/06/2013
 *Observation: PDF on council website http://www.cne-siar.gov.uk/travel/busservice/current/documents/lewisandharris/W4%20Stornoway%20to%20Uig.pdf shows various notes for this service.
 These notes do not appear in the TNDS data. 
 *Hypothesis: 
 *Raised by: Brainforge 
 *Assigned to: Fraser Leith (4 July 2013)
 *Peter Stoner comments: The absence of notes may be because the detail has been built into the electronic data.  We need to identify a specific example of some detail in the notes that would mislead a passenger if it were not in the data. 
=====Issue No: 138 Y Indicators Missing at Sheffield Interchange =====
  *Where detected (and date): NaPTAN (26 June 2013) 
  *Observation: NaPTAN Indicator field is blank in SY data 
  *Hypothesis: Loss of useful detail for passengers. Makes it very difficult for passengers to enquire of the right stand in NextBuses.
  *Raised by: Peter Stoner
  *Assigned to: John Prince 
  *John replies: Operators will include the correct stand in the schedule data they send to ACIS for real time and if real time is working an enquiry on a stand in the bus station will get a correct real time response. But if real time is not working they will get nothing.
  *Peter comments: still seems to be a problem then (August 2013)



Issue No: 137 CLOSED Vehicle journeys departing after midnight causing confusion
 
  *Where detected (and date): Service 40 Bristol swe_38-40_-2-y10.xml 25/06/2013
  
  *Observation: Vehicle journey VJ_38-40-_-y10-2-122-T2 departs at 01:00 on Sundays.
  This is correct but from the operator's PDF timetables this journey is a continuation of the Saturday timetable.
  I.E. it appears at the end of Saturday not at the beginning of Sunday.
  See: http://www.firstgroup.com/ukbus/bristol_bath/journey_planning/timetables/index.php?operator=3&service=40/40A/41&page=1&redirect=no
  
  Ditto the 00:00 and 02:00 departures except that on the website they show the Saturday 00:00 as 24:00.
  
  Would like to have some way of indicating the Sunday 00:00, 01:00 and 02:00 journeys are a continuation of the Saturday timetable and not part of the Sunday timetable.
  One way would be to show them as 24:00, 25:00 and 26:00 but that will probably throw up problems elsewhere...

  *Hypothesis:
 
  *Raised by: Brainforge 

  *Assigned to: Andy Hole
  *Peter Stoner comments: I believe TransXchange v 2.4 (we currently use v 2.1), has a facility to say that early morning journeys should be presented as part of the previous day's operation.  It is a presentational issue and some software will display the journey at the end of the previous day as well as the start of the new day. 
  *Peter comments: we discourage journeys starting at 00:00 because of the confusion that can be caused.  It is better that they are in the data as 23:59 or 00:01.  Andy might wish to take that up with the operator. 
  *Andy Hole comments: We have many operators that have services that depart at 00:00 and unfortunately they do actually depart at this time, so we can not change the time.

Issue No: 136 RESOLVED SE Sunday journeys - 84 St Albans and 78 Slough
  *Where detected (and date): se/set_7-84A-1-y08.xml se/set_1-78B-1-y08.xml 23/06/2013  
  *Observation: Noticed first on 84 at St Albans - there appear to be operating profile errors for Sunday and Bank Holiday journeys. For example:

VJ_7-84-A-y08-1-282-UL
Has RegularDayType of MondayToSunday - Error, should be Sunday.
Should also have special op day on Bank Hols.

VJ_7-84-A-y08-1-180-T2
Has RegularDayType of Saturday - OK.
Should also have special op day on Good Friday.

Compare with http://www.intalink.org.uk/timetables/tt/84_a_atg.pdf

+++++++++++++++++++++++++++++++++++++++++++++++

Later on noticed same effect on 78 at Slough.
See for instance vehicle journey VJ_1-78-B-y08-1-185-UL
No time to check in more detail.

+++++++++++++++++++++++++++++++++++++++++++++++

Issue 149 seems similar.

  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Stuart Reynolds
  *Stuart comments: "I have only looked at the 84, but I agree with the assessment. The trip first listed is inheriting the RegularDayType from the Service element - but the 1030 trip is only on Sundays, so this is incorrect."  This is a further example of data not being reflected correctly in TXC and is being followed up. 
 * Stuart comments: 
My original contention (on the 84) was slightly incorrect, in that the -UL vehicle journey is one that only runs on August Bank Holiday. It should therefore have been set to HOLIDAYSONLY and have bank holiday operation - which it now does. The data has changed so that the VJ references are no longer valid, but it appears to be structured correctly from what I can see.
FYI, T0 is Monday-Friday, T2 is Saturday, UG is Sunday, and then UH through UL are the bank holidays in order from Good Friday to Summer BH. Christmas is then a continuous set of individual dates from UM (Christmas Eve) to UU (New Years Day), with occasional UV and UW as needed in January.

   
Issue No: 135 RESOLVED Route 685 Brampton to Carlisle Sundays
  *Where detected (and date): NE_310_PC2407_685.xml 11/06/2013 
  *Observation: In the XML there are some XX:10 journeys from Brampton to Carlisle for which I cannot find any reference elsewhere See: http://www.arrivabus.co.uk/serviceInformation.aspx?id=10514 and http://www.arrivabus.co.uk/north-east/bus-timetables/685-X85/bus-times-in-newcastle and http://www.stagecoachbus.com/GetUpload.ashx?Id=6832

For the 10:10 departure the journey / pattern section refs are: JPS_O9 JP_O9 VJC_O13

As an aside neither of the documents referred to above indicate a validate date - Google could have pointed me at an obsolete page which had not been removed!
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Richard Hall
  *Peter Stoner comments: the Sunday journeys can be found on the Cumbria County Council website where the times from Brampton Market Place are 1115, 1415, 1715 and 1935.  From Carlisle they are shown as 0905 1128 1428 1728. Operated by Stagecoach.  As 685 service data comes from Northumberland I am assigning the issue to Richard to check.
  *Peter Stoner reports: The cause of the confusion seems to be an error in the bus registration which contains old as well as new journeys. The operator(s) are sorting this out.

Issue No: 134 RESOLVED NCSD file thandicoaches route 1 timing query
  *Where detected (and date): NCSD-atco.xml 10/06/2013 
  *Observation: See 08:45 Wolverhampton http://www.thandicoaches.com/route1.html 
  In the XML this service includes JPSection-28746
	JourneyPatternTimingLink id="JPSection-11349-SEC6532-POS35261" shows a runtime of 45 minutes.
	This equates to the Handsworth to Coventry section.
  Assuming the thandi website is correct should the runtime for this be 30 minutes?  
  The 15:45 departure timings look OK.
	
	Just started looking at NCSD data and this happened to be the first one I looked at!
	
  Would make it easier to handle if the NCSD data was supplied as small separate files one for each route. e.g. NCSD_1_THAN.xml etc.. 
  *Hypothesis: Looks like I got muddled up earlier - not an issue, but would still like my last comment considered for the future. Thanks.
  *Raised by: Brainforge
  *Assigned to:

Issue No: 133 CLOSED Service 44 Newcastle (see also issue2 114 and 131)
  *Where detected (and date): NE/NE_130_PB3954_44.xml 06/06/2013  
  *Observation: Various journeys, such as VJC_O116, appear in XML to run every Monday and Friday. 

A random check indicates there may be some more examples of this which I have not looked at it detail. I cannot spot, in this case, an error in my XML processing. Can you confirm that this operating date information is indeed missing from the XML.
  *Hypothesis: Should this be only Bank Holidays / Good Friday?
  *Raised by: Brainforge
  *Assigned to: Amy Armstrong
  *Peter Stoner: timetable is at http://durham.pindarcreative.co.uk/tt/rr_Go.pdf and shows a Sunday and Bank holiday operation for this journey.  The Bank holiday status of journeys is not showing in these exports. 
  *Same as Issue 114.

Issue No 132: RESOLVED  NCSD line names are not the public facing line names
  *Where detected (and date): NCSD files, 05/06/2013  
  *Observation: <LineName> elements in the NCSD files do not describe the  service / line as known by the public, or as described in published materials. For example ... <ServiceCode>201_FK</ServiceCode> ... <Lines> <Line id="l_201_FK"> <LineName>L201_FK</LineName> </Line> </Lines> ...

This service is normally represented as "201" (see http://coachtracker.nationalexpress.com/routes/201/O/Swansea-Gatwick_Airport_Sth )
  *Hypothesis:  
  *Raised by: Tim Millington
  *Assigned to: BaseMap
  *BaseMap respond: We have now updated the code so the Line name should now only contain 201 in your example.

Issue No: 131 CLOSED Service 28 at Beamish Museum (see also issues 114 and 133)
  *Where detected (and date): NE_130_PB2400_28.xml 04/06/2013 
  *Observation: Various journeys, such as VJC_O74, appear in XML to run every Monday and Friday. 
  *Hypothesis: Should this be only Bank Holidays / Good Friday? 
  *Raised by: Brainforge
  *Assigned to: Amy Armstrong
  *Same as issue 114

Issue No: 130 RESOLVED Sheffield Services 273/274 in EM and Y region data
  *Where detected (and date): SVRYSGO274-20130528-53947.xml 03/06/2013  
  *Observation: Summer Sunday 273 service at 18:15 appears correct in the EM data. However the Y data shows the corresponding winter Sunday 274. The Y data date ranges appear not to cater for the timetable change.

See http://www.derbysbus.info/times/timetables/273H_111030.pdf

Also the EM and Y data appear to show different stoppointrefs at Sheffield Centre Interchange which is confusing.
  *Hypothesis: 
  *Raised by: Brainforge
  *Assigned to: John Prince
  *John comments: Yorkshire timetable version has now been corrected.
  *Peter Stoner comments: EM version still departs from stand 370010131 whereas Yorkshire version departs from 370070005
  *Stand allocation at Sheffield interchange being pursued under Issue 138. 

Issue No: 129 RESOLVED Missing Sidmouth Summer Sunday Journeys 157 and 56B (
  *Where detected (and date): swe_33-157_-1-y10.xml 29/05/2013 
  *Observation: 157 journeys are shown on http://www.stagecoachbus.com/PdfUploads/Timetable_39447_157,%20357.pdf but cannot find them in the XML.

File swe_33-56B_-1-y10.xml missing for 56B.
Shown on http://www.stagecoachbus.com/PdfUploads/Timetable_29921_56,%2056A,%2056B.pdf

07/06/2013 Data now appears, looks like it was few days late!

  *Hypothesis: 
  *Raised by: Brainforge
  *Assigned to: 
=====Issue No: 128 SE EM EA MDV SpecialDaysofOperation =====
  *Where detected (and date): set_7-388E-1-y08.xml 28/05/2013 
  *Observation: Vehicle journey VJ_7-388-E-y08-1-2-T0 has regular days of operation on Thursday / Friday during school holidays. It also has special days of operation date ranges which include Sundays.  PDF timetable http://www.intalink.org.uk/Timetables/tt/388_B_ATG.PDF makes no mention of this Sunday service.  Is the XML wrong or am I misunderstanding the documentation?
  *Hypothesis: 
  *Raised by: Brainforge
  *Assigned to: Stuart Reynolds (20 June 2013)
  *Stuart Reynolds comments:  Issues 99, 121, 122, 128 - These are all examples of the same error. The non-schoolday operation is coded as an apparently random selection of regular days, with additional dates in SpecialDaysOfOperation filling in the missing gaps in the school holidays. But there appears to be an underlying data error, since these date ranges often include Sundays when the trips do not run.  Raised with MDV 20 June 2013. 
  *Stuart comments (23 August 2013): . This appears to be fixed, by and large. Certainly the gross errors that we were seeing are now correct. I have two remaining issues which I will raise as new issues with MDV so that it is clear what we are talking about. The errors are on the 388 service and the 0735 school holiday tip, as before - we have a dual declaration of 1 Jan 2014, both as operating and not operating which is clearly incorrect, and we also have bank holidays declared as operational days which is also wrong. For both these, I don’t know whether it relates just to the 388 or to the wider data set - I suspect the latter.


Issue No: 127 RESOLVED Scarborough 64 out of date
  *Where detected (and date): 29/05/13 SVRYNAO064-20130329-57282, SVRYNAO064 
  *Observation: NextBusAPI reports departures for line 64 from stop 3200YNA96545 (St Thomas St Scarborough, stand C) to Weaponess Car Park. I have been informed that 64 services no longer run to that destination. The on-line resource http://www.scarboroughparkandride.co.uk/ indicates this is the case. A similar question has been raised regarding the 165 from the same stop. 
  *Hypothesis: Routes and journey patterns need to be updated for 64 and 165?
  *Raised by: Tim Millington
  *Assigned to: John Prince
  *This has been investigated by John and North Yorkshire CC.  The timetable data is correct but the naming of some stops makes it look as if it is still going to the former park and ride site.  These names will be adjusted to improve the situation.
  *Peter Stoner comments: Stop has been renamed to "Weaponness, Park & Ride" to try and make it clearer.

Issue No: 126 RESOLVED  Circle Line missing
  *Where detected (and date): L.zip (21 May 2013)
  *Observation: the Circle-Line of the London Underground doesn't appear in the data
  *Hypothesis:  Is that service still running?
  *Raised by: Simon, Moovit 
  *Assigned to: Peter Stoner
  *Peter Stoner comments: the usual file output_txc_01CIR_.xml was missing from the data received from TfL.  It is now restored and will be in this week's update. 

Issue No: 125 RESOLVED Unknown operator
 
  *Where detected (and date): NE_090_Unknown_564A.xml  (20 May 2013) 
  *Observation: no Operator section exists for line number 564A 
  *Hypothesis:  Are xml files like these simply duplicates? 
  *Raised by: Simon, Moovit 
  *Assigned to: Mark Hodgkiss (Cumbria)
  *Mark Hodgkiss comments: The service is operated by Western Dales Community Transport.  
  *John Prince has allocated code WDCB
  *Brian Marshall is adding the operator into the data. 

=====Issue No: 124 WM Incorrect Coodinates=====
  *Where detected (and date):  twm_8-86_-1-y11.xml (20 May 2013) 
  *Observation: in vehicle journey "VJ_8-86-_-y11-1-22-T0", the stop with id "260010806" seems to have incorrect coordinates far away from the rest of the path. 
  *Hypothesis: A problem in the source data, or misinterpretation, leading to overly-fast-travel errors in some areas.
  *Raised by: Simon, Moovit 
  *Assigned to: Keith Sabin
  *Peter Stoner comments: This seems to be a Leicestershire stop that has been deleted but it is still referred to in Warwick data that crosses into Leicestershire.
  *Peter comments: DEL stop still in the data (August 2013)


Issue No: 123 RESOLVED  Windermere Ferry
  *Where detected (and date): NE_090_WF01_F3.xml (20 May 2013) 
  *Observation: journeys such as "VJC_O7" include a stop with code "9300KWS1" which according to Naptan is "Kirkwall Shapinsay Ferry Terminal" in the Shetland Islands.
  *Hypothesis: in the xml file it is called "Brockhole landing stage, Troutbeck Bridge" and should be in the Lake District. In these journeys we get travel of 500km in 20 minutes.  
  *Raised by: Simon, Moovit 
  *Assigned to: Mark Hodgkiss (Cumbria)
  *Amy Armstrong replies: This is an error in our local resources. I have amended the lookup and all being well it will show correct in this week's TXC feed.  Mark - Nothing for you to do.

 
Issue No: 122 CLOSED see issue 128
  *Where detected (and date): 11.05.2013 set_6-42I-1-y08.xml 
  *Observation: 0805 from Dunsford Mon/Wed school hols appear to be missing in the XML (0730/0740 from Ewhurst)

JPS_6-42-I-y08-1-8-5-H
JP_6-42-I-y08-1-8-H-5
VJ_6-42-I-y08-1-9-T0

Compare with http://www.compass-travel.co.uk/timetables/service_42.html
Mix of 'Sch', 'S & H' and 'N' notes make things a bit complicated.

  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Stuart Reynolds
  *Peter Stoner comments: The 0730 journeys seems to be in the data as a Monday to Friday journey with Schoolday only operation only indicated by a note.  The 0740 journey is shown in the leaflet as Monday to Friday school holidays it is in the data as Tuesday, Thursday and Friday, with the school holiday only operation only shown as a note.  The Saturday journey at 0805 from Dunsfold is in the data. 
  *Stuart Reynolds comments:Issues 99, 121, 122, 128 - These are all examples of the same error. 
Issue No: 121 CLOSED 84 see issue 128
  *Where detected (and date): SE/set_7-84A-1-y08.xml 10/05/2013 
  *Observation: Services to St Albans appear to show as most mon-fri journeys being schooldays only with the school holiday journeys running Thu-Fri only. 
  *Hypothesis:  This is not correct.  
  Mon-fri journeys run all schooldays / school hoidays except for a few schoolday journey adjustments. 
  *Raised by: Brainforge
  *Assigned to: Stuart Reynolds
  *Peter Stoner comments: journeys at 1433,1453, 1513, 0707, 0728, 0750, 0813, 0833, 1555, 1615, 1413, 1535, 0653, 0901, 1603, 1705, 1727, 1749, 1830, 0720, 0737... showing as Thursday and Friday only during school holidays.  The holidays are dated, but there do not seem to be equivalent journeys for Monday - Wednesday.
  *Stuart Reynolds comments: Issues 99, 121, 122, 128 - These are all examples of the same error. 

Issue No: 120 RESOLVED Ilkeston Flyer journies missing / additional
  *Where detected (and date): em_11-IFA-1-y08.xml 10/05/2013 
  *Observation: Additional journey in XML Mon-Fri from Derby 06:30 
  Not shown here:
  https://www.trentbarton.co.uk/services/IlkestonFlyer/maps-and-times 
  Could not see in the XML the Fri-Sat 00:45, 01:45 and 02:45 journies from Derby.
  There appear to be 2 other XML files for this route, but again could not spot them. 
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Peter Stoner
  *Peter Stoner comments: the night journeys are now in the data. Those starting after midnight as Saturday, Sunday, Monday mornings, but Monday journeys have Non-Operating days which cancel all instances of them.  This may accord with the leaflet.  The 0630 journey now seems to have been removed.  

Issue No: 119 CLOSED London Undergroud missing regular days of week
  *Where detected (and date): output_txc_01HAM_.xml Hammersmith & City 09/05/2013 
  *Observation: The following services run every night Tue-Fri JP_01HAM_H0_92 JP_01HAM_H0_93 JP_01HAM_H0_94 but not mon-tue.
  Equivalent services run sat-sun and sun-mon night. But there appears to be no Mon-Tue night equivalents. 
  I thought I noticed a similar thing happen on part of the Jubilee line, but did not investigate.   
  *Hypothesis:  Is this correct or is it an omission?
  *Raised by: Brainforge 
  *Assigned to: Gerard Butler (31 May 2013)
  *Peter Stoner comments: These look like early morning journeys ie after Midnight, so Monday will be an extension of the Sunday timetable operation and therefore the data seems to be as expected.  

Issue No: 118 RESOLVED WM operating profiles missing days of non operation?
  *Where detected (and date):06/05/2013 e.g. twm_4-SWIA-1-y11.xml 
  *Observation: VJ_4-SWI-A-y11-1-3-T0 has operating profile which includes Monday, but no days of non-operation. NextBus service does not show this departure running today (Monday 06/05/2013 - bank holiday).
  *Hypothesis: TNDS operating profiles are incorrect - missing days of non-operation. 
  *Raised by: Tim Millington
  *Assigned to: Keith Sabin (31 May 2013)
  *Peter Stoner comments: The Monday only journeys now have days of non operation which only leave them running on the August bank holiday.  Very inelegant but the correct operation dates.

Issue No: 117 CLOSED Additional information suggestion
  *Where detected (and date): Throughout 2013/05/06
  *Observation: It would be handy if the Services section of the XML contained the URL of any operator's PDF
  leaflet(s), if available, applicable for the service. Actual operator's official publications required, not a
  community groups publication. Need to indicate validity dates for the publication. Not just a basic
  timetable PDF, but if available a link to something like this:
  http://www.firstgroup.com/ukbus/new_service_updates/attach_1350985566_13751_X53%20X54%20winter%20TT%20FINAL%20Oct%202012.pdf

Just realised that is an out of date link! The current one is:
http://www.firstgroup.com/ukbus/new_news_initiatives/attach_1360164533_3881_X53%20timetable%20Summer%202013%20web.pdf

Just goes to illustrate that something which gives reliable up to date information is required.
Find that Google often points me at an out of date timetable PDF!
When doing a quick departure time spot check sometimes forget to look at the date.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Peter Stoner
  *Peter comments:  Useful suggestion but may be difficult to maintain this inforamation.

Issue No: 116 CLOSED Missing nonoperating date
  *Where detected (and date): SE/set_6-271A-1-y08.xml 2013/05/06
  *Observation: Vehicle Journey: VJ_6-271-A-y08-1-24-T0
  DaysOfNonOperation does not include 2013-05-06
  It includes 2013-05-27 and 2013-08-26
  
  From http://www.metrobus.co.uk/download/11466/route-271-and-273-timetable-010912/
  it does not run on public holidays.

  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Peter Stoner
  *Peter comments:  the earlier date has passed.  The bank holiday dating is a matter that Stuart Reynolds is continuing to discuss with MDV.

Issue No: 115 RESOLVED SW Missing stops on 157 Exmouth to Sidmouth
  *Where detected (and date): swe_33-157_-1-y10.xml JPS_33-157-_-y10-1-17-16-H 04/05/2013
  *Observation: The one Mon-Fri service which serves the unmarked stop (dvngamtd) at Old Railway Station, Sidmouth is not indicated as serving either Bulverton Camp (dvngdtmw) or Knowle (1100DEA09102), it passes these points and I thought it served them.
  
  The summer Sunday services also serve the umarked Old Railway Station stop (dvngamtd) and again I would expect them to serve the others points as well, but I have not checked these.
  
  All regular Mon-Fri services serve the Knowle but not the others as they do not pass Bulverton, and this information is correct.
  
  A quick look and I could not find a list of stop points for this route, other than a cryptic note that a few services operate via Bulverton!
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Andy Hole
  *Andy Hole comments: Stagecoach supplied a new EBSR record in August which should have corrected the routing.
  *Peter Stoner adds: The 0728 Monday to Friday journey does now show as serving the Bulverton Camp and Knowle

=====Issue No: 114 NE Missing holiday special op / nonop dates =====
  *Where detected (and date): NE_130_PB2717_76A.xml 02/05/13 
  *Observation: Looks like regular day Mon and Fri journies should have special op / nonop days specified as they appear to be bank holiday Mondays and Good Friday journies only.
See: JPS_I1 JP_I1 VJC_I32
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Amy Armstrong (5 May 2013)
  *Issues 131, 133 and 175 are the same.
  *NE reports: raised with JourneyPlan (August 2013) 

=====Issue No: 113 WM Combined timetables  =====
  *Where detected (and date): WM (2.5.2013) 
  *Observation: Services such as 74/75 in Staffordshire are in the data individually and in a combined file.
  *Hypothesis: Information that is used to group routes for presentation in matrix timetables is causing duplication of journeys. 
  *Raised by: Mark Taylor
  *Assigned to: Keith Sabin
  *Peter Stoner comments: issues 91 and 97 were related.
  *Peter Stoner comments: It looks as if this is still happening - August 2013.  For example file TWM_9-T001-1-y11.xml has lineName 351/361  

Issue No: 112  CLOSED  Missing 26A service (Darlington-Catterick Garrison/Colburn/Marne)
  *Where detected (and date): TNDS 01/05/2013 
  *Observation: Service 26A Darlington - Richmond - Catterick Garrison/Colburn/Marne appears to me missing from the TNDS. 26A departures are shown in Nextbuses API (eg stop 3200YNA90228), and 26A appears in the on-line timetable (Arriva).
  *Hypothesis: Data is missing
  *Raised by: Tim millington
  *Assigned to: Amy Armstrong
  *John Prince comments: 26A is in Yorkshire's data SVRYNAO026A and in Yorkshire journey planner.
  *also in NE journey planner.


Issue No: 111 CLOSED  Stop 3800C591701 appearing in both directions of 72  *Where detected (and date): 01/05/2013 twm_6-72_-1-y11 & NextBus API (affected) 
  *Observation: NextBus API reporting non-existent departures from stop Lyme Valley Road (3800C591701) or services 72 showing S/W bound services when the stop is on the N/E bound side of the road. File twm_6-72_-1-y11 has 3800C591701 in outbound and inbound JourneyPatternSections:
JPS_6-72-_-y11-1-1-1-O
JPS_6-72-_-y11-1-2-1-O
JPS_6-72-_-y11-1-5-1-O
JPS_6-72-_-y11-1-3-2-I
JPS_6-72-_-y11-1-4-2-I
JPS_6-72-_-y11-1-6-2-I
There is no physical stop on the S/W bound side of the road.
  *Hypothesis: The N/E bound direction is outbound for this service. The stop should not appear in the inbound JourneyPatternSections, i.e.
JPS_6-72-_-y11-1-3-2-I
JPS_6-72-_-y11-1-4-2-I
JPS_6-72-_-y11-1-6-2-I

  *Raised by: Tim Millington 
  *Assigned to: Mark Taylor
  *reply from Stoke and First: This is not "an error". Buses serve this stop in both directions.  This because Service 72 bus to Clayton from the bus station is routed via Hassell St, Friars St, Blackfriars Rd and Friarswood Rd, but at the end of Friarswood Rd you can not go straight ahead into Clayton Road, you have to turn left. Our bus towards Clayton serves the stop in question then does a 180 degree circle of Morrisons roundabout to head for Clayton.
 
=====Issue No: 110 L Access Area being used as a platform =====
  *Where detected (and date): output_txc_01PIC_.xml, 30/04/2013 
  *Observation: Stops.csv lists 9400ZZLUHR4 as having StopType = MET.  However this atcocode appears in the file output_txc_01PIC_.xml as a StopPointRef
  *Hypothesis: All StopPointRefs in output_txc_01PIC_.xml which currently have 9400ZZLUHR4 should be changed to 9400ZZLUHR41 (Which is the atcocode of the corresponding location in Stops.csv which has StopType = PLT.)
  *Raised by: Jeppesen
  *Assigned to: TfL (5 May 2013)
  *Stuart Reynolds comments:  I will talk to TfL about it, but it relates to how they import LUdata and might not be quite as straightforward as we think. In general, I think that all underground services are mapped to METs. 
  *Peter Stoner: followed up August 2013

Issue No: 109 RESOLVED Same place different stop point refs
  *Where detected (and date): Devon, Kingswear, (Paignton and Dartmouth Railway) 26/04/2013 
  *Observation: This has two stop point refs 1100ZZPDKGW0 and 9400ZZPDKGW1.
One provides departure times, the other arrivals. Bit confusing.
In the Naptan data they have the same longitude / latitude, so maybe that's the easiest way to detect this situation. Any other suggestions? Data cleanup needed somewhere in source?
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Andy Hole
  *Andy Hole replies:This issue has been identified and will be resolved in our export on or about 20th May.
 
Issue No: 108 CLOSED Steam/Diesel trains on Swanage Railway 
  *Where detected (and date): SW/swe_42-SR_-2-y10.xml 28/04/2013
  *Observation: There appears nothing in the XML to indicate whether a journey is steam or diesel hauled.
Would be useful to include a note about this against each journey. I.E. like school day / non school day journey notes provided elsewhere - such as route 84 in issue 107.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Peter Stoner
  *Peter comments: this is probably not referred in the current standards, but is a good suggestion and could be added in a note field.

Issue No: 107 CLOSED Missing school holiday notes
  *Where detected (and date): NE/NE_090_25455_11.xml 25/04/2013  
  *Observation: Vehicle journeys VJC_O0 and VJC_O5 appear to only operate on Saturdays and during school holidays.

See: http://www.cumbria.gov.uk/elibrary/Content/Internet/544/931/6266/40920163535.pdf

In the XML vehicle journeys there appears to be no note of this or link to a serviced organisation.
Compare with ServicedOrganisationDayType references in SW/swe_31-382_-1-y10.xml
and notes in SE/set_7-84A-1-y08.xml both of which allow a sensible warning to be raised.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Mark Hodgkiss (31 May 2013)
  *Peter Stoner comments: the 0740 is in the current data as operating all Monday to Saturdays.  The 1535 journey is in the data as separate Monday to Friday and Saturday journeys. 
  *Peter comments: PDF file is not longer available.

Issue No: 106 CLOSED Missing Operating Dates
  *Where detected (and date): X84 Leeds Y/SVRYWAX084-20130401-52253.xml 24/04/2013 
  *Observation: Difficult to determine operating dates for service. The implication from the XML implies it runs forever except for a few Saturdays in 2013! Be better if it matched the operating dates on the First web site. Comment also applies to other related files.
  *Hypothesis: 
  *Raised by: Brainforge
  *Assigned to: John Prince (31 May 2013)
  *Peter Stoner comments: John is looking at various data issues in data from West Yorkshire.  Services with an open end date is not necessarily a problem, as this is how most bus services are registered.
  *Peter comments: The inventory now mentions the short look ahead horizon for data in Yorkshire.  This is according to their policies.


Issue No: 105 CLOSED Handling of set down request stops
  *Where detected (and date): SW/swe_33-52B_-1-y10.xml 23/04/2013  
  *Observation: On some vehicle journies there is a note saying 'Sets down by request to driver only'. This usually applies to Honiton station (some journies only) which in JPS_33-52B-_-y10-1-28-8-H / JPL_33-52B-_-y10-1-28-H-8-68 has an activity of 'setdown'. Would be less confusing if the vehicle journey note was removed and the stop activity changed (when appropriate) to 'setdownonrequest'.

Also be more flexible if any journies have multiple set down on request points.
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Peter Stoner
  *Peter comments: The SetDown activity in TransXchange is different from the "by request" activity you mention.  Several stops are already marked as Set down only so it looks as if the "by request" is a supplementary note to passengers.  
 
Issue No: 104 CLOSED London Underground services
  *Where detected (and date): File output_txc_01HAM_.xml 20 April 2013 
  *Observation: No service mode specified in XML - ditto other London underground lines. Should it be Metro?
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Peter Stoner
  *covered by issue 18 which is still open.


Issue No: 103 RESOLVED XML handling error
  *Where detected (and date): Region NE File NE_090_Unknown_564A.xml 19/04/2013
  *Observation: Cannot handle the XML data for this file (excerpt from import log):

Processing: NE_090_Unknown_564A.xml

DOMDocument::loadXML(): Malformed declaration expecting version in Entity, line: 1

DOMDocument::loadXML(): Blank needed here in Entity, line: 1/components/com_timetablebrain/helpers/data.php on line 137

DOMDocument::loadXML(): parsing XML declaration: '?>' expected in Entity, line: 1

DOMDocument::loadXML(): Start tag expected, '<' not found in Entity, line: 1 

Quick visual comparison check and could not spot the issue.

Looks like its this: http://www.dalesbus.org/564A.html
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Peter Stoner
  *Peter comments: This "unknown  operator" has now been identified as Western Dales Community Transport and will be referenced as such in the data which is expeted to solve the XML problems.

Issue No: 102 CLOSED End date before start date in date range
  *Where detected (and date): 4 files in region L data 19/04/2013
  *Observation: Extract from import log file:
Processing: output_txc_08250f.xml
Date Range Error: Start date = 2013-04-17, End date = 2013-04-11
Failed: processVehicleJourneys('VehicleJourneys')

Processing: output_txc_24679j.xml
Date Range Error: Start date = 2013-04-12, End date = 2013-04-11
Failed: processVehicleJourneys('VehicleJourneys')

Processing: output_txc_60008_.xml
Date Range Error: Start date = 2013-04-15, End date = 2013-04-11
Failed: processVehicleJourneys('VehicleJourneys')

Processing: output_txc_61H10g.xml
Date Range Error: Start date = 2013-04-14, End date = 2013-04-11
Failed: processVehicleJourneys('VehicleJourneys')
  *Hypothesis:
  *Raised by: Brainforge
  *Assigned to: Peter Stoner
  *Peter comments: These dates have now passed.
=====Issue No: 101 SW Routes with loops at either end =====
  *Where detected (and date): SW/swe_33-52B_-1-y10.xml 17 April 2013  
  *Observation: Exeter to Honiton services on 52B loop through Honiton and then return to Exeter. The XML data shows, correctly, the end points in Honiton being either Lace Walk or the Job Centre.

The XML file does not make it obvious that one can either continue past Lace Walk to the station / hospital or join the service before Lace Walk when continuing in the Exeter direction.
  *Hypothesis: In the Journey Pattern Sections it would be better if the Lace Walk services showed a termination point of dvngmjwp (Joslin Rd) and a departure point when traveling to Exeter of dvngatwj (Holy Family Church). The routes information would continue to show the Lace Walk.

Presumably this is not an isolated incident.
Not too much bother if one has local knowledge, but no good if trying use the information generically.

---------------------------------------------------

On random check of my users spotted similar issue with Reading route 21 and then by chance happened to be there in person a few days later!

Operator's map explains it best but the loop between Chilcombe Way and Hawkedon Way is confusing in both the XML and the operator's timetable.

 http://www.reading-buses.co.uk/files/maps/24%20Sept%2012/claret%20routes%20map%2024%20sept%2012%20web.pdf

http://www.reading-buses.co.uk/files/timetables/24%20Sept%202012/claret%2021%20timetable%2024%20Sept%2012%20web.pdf

  *Raised by: Brainforge
  *Assigned to: Andy Hole (29 May 2013)
  *Peter Stoner comments: followed up August 2013
  *Andy Hole reports: Stagecoach supplied a new EBSR record in August which should have
corrected the routing.
  *Peter Stoner comments: There is a 3 minute wait at Lace Walk but the loop still appears to be broken in the data.  Overlapping section or guaranteed connection needed.


Issue No: 100 RESOLVED Odd data on 505 to Kendal
  *Where detected (and date): 	NE_090_PC2407_505.xml 17 April 2013 
  *Observation: Through services Coniston to Kendal bus station: 3 on mon-sat, 2 on sun
The mon-sat services appear OK.
In the xml data the sun services appear to terminate at Sandes Ave is this correct?
The XML also contains 2 additional Mon & Fri only services to Sandes Ave. at the same times as the Kendal bus station services.
  *Hypothesis:
Is this some data muddle with holiday Mondays, Good Friday and Sundays?
In the operating profile no mention is made of these holidays.
  *Raised by: Brainforge
  *Assigned to:Mark Hodgkiss
  *Peter Stoner comments: Sandes Avenue is probably correct.  If the bus can set down here it can proceed to the bus depot without entering the long Kendal one ways system!  There seems to be some duplication which Cumbria may be able to resolve in the data. 
  *Mark Hodgkiss comments:  Looking at the current timetable buses on the 505 which run to Kendal at the end of the day now terminate at Blackhall Road (Stand C) and not Sandes Avenue
 

Issue No: 99 CLOSED see issue 128
  *Where detected (and date): SE/set_7-304H-1-y08.xml 15th April 20:13
  *Observation: School holiday service 304 from Hitchin 15:55
File says:
Regular day service Thurs / Fri.
Special days Mon-Wed service at holiday times.
Note says Hertfordshire School Holidays only.
This matches http://www.intalink.org.uk/Timetables/tt/304_B_ATG.PDF but a bit messy to work out automatically.
Be better if it said something like regular Mon - Fri and note about school holidays.
Non-operating days could be shown as block of dates.

I just happened to spot this example on a random check on my site's visitors. 
  *Hypothesis:  
  *Raised by: brainforge
  *Assigned to: Stuart Reynolds
  *Stuart Reynolds comments: Issues 99, 121, 122, 128 - These are all examples of the same error. 



Issue No: 98 CLOSED Route tag missing
  *Where detected (and date): most Yorkshire data, and some NW routes, (15.4.13) 
  *Observation: the majority of files do not use the <Route> tag hence 
  *Hypothesis:  it is difficult to reconstruct the timetables for checking particularly given the large number of files associate with this area
  *Raised by: Bruce Ramsey
  *Assigned to: Peter Stoner
  *Peter comments: The export processes in Scotland, Yorkshire and North West, are not able to group journeys of the same service into a single file.  However the file referencing may help to group timetables together.  We are looking at ways of overcoming this problem.

Issue No: 97 CLOSED More duplication of services
  *Where detected (and date): TNDS 2013/04/09 
  *Observation: Duplicated times shown for Memorial Square, Coalville to  Leicester, St Margaret's Bus Station.
One says route 29, the other says 29 / 29A.
  *Hypothesis: Multiple data sources em_12-29_-1-y08.xml (EM), em_12-29A_-1-y08.xml (EM), twm_4-29A_-1-y11.xml (WM) twm_4-T29A-2-y11.xml (WM) and twm_4-29_-1-y11.xml (WM). Different linenames: 29, 29A and 29 / 29A.
  *Raised by: brainforge
  *Assigned to: Keith Sabin
  *Peter Stoner comments: There is a cross boundary duplication here between EM and WM data, but also a composite timetable (T29A).  Keith is investigating why these composite timetables are also being exported.  See issue 113.

Issue No: 96 CLOSED More duplication of services
  *Where detected (and date): TNDS 2013/04/09 
  *Observation: Two times shown (14:25 and 14:26) for service 377 from Maisemore, The White Hart.
  *Hypothesis: Two data sources twm_9-377_-1-y11.xml (WM) and swe_45-377_-1-y10.xml (SW).
Slight timing difference in RunTime of JourneyPatternTimingLink?
  *Raised by: brainforge
  *Assigned to: Peter Stoner
  *Peter comments: one minute variations are quite common between regional sources.  These are due to different methods of interpolating the intermediate times between timing points.


Issue No: 95 RESOLVED Duplicate Services
  *Where detected (and date): TNDS (27 March 2013)  
  *Observation:  Very similar but not identical services:
L/output_txc_08313i.xml     Metroline

SE/set_7-313A-1-y08.xml     Arriva

  *Hypothesis: Arriva is missing Mon-Fri non-holiday departures from Chingford   *Raised by: Jonathan Brain
  *Assigned to: Gerard Butler
  *Peter Stoner comments: Local operator codes: "MN" in London (which is not mapped to a National Operator Code, "27" in SE which is mapped to National Operator code ALNO (Arriva London North).
  *Peter Stoner adds: we have established that the Mon-Fri non-holiday departures are in the data, though there are some minor discrepancies in the timing between the Hertfordshire and London version of the same timetable.

Similar issue with route 298 (from Arnos Grove) operated by Sullivan buses.

L/output_txc_86298h.xml

SE/set_7-298B-1-y08.xml

They also serve different stops at Potters Bar station.

Peter Stoner comments: Finding that southbound at Potters Bar station SE is quoting stop C and TfL Stop D.  Referred to TSE. 

TfL respond: According to the stop sequences from London Buses both directions serve Stop C.  Data has been amended to reflect this. 

Issue No: 94 CLOSED Incorrect use of activities for JourneyTiminglinks 
  *Where detected (and date):  WM twm_6-25_-1-y11.xml (22/02/13) but likely to be widespread 
  *Observation: JourneyPatternSections with bus stations along the route can show an arrival stand and a separate departure stand, with the <Activity> in the timing links being "pickUpAndSetDown" (the default). I suspect this is incorrect - in the example below (extracted from the named file) the sencond link (JPL_6-25-_-y11-1-41-O-1-26) is a movement between two stands at the station. The only pickUp should probably be the last link (stop ref 3800C510105). Without the correct activities, it is extremely difficult do direct passengers to the correct departure stand for a particular service, as would be desirable in journey planning. 

<JourneyPatternTimingLink id="JPL_6-25-_-y11-1-41-O-1-25">
    <From SequenceNumber="24">
        <Activity>pickUpAndSetDown</Activity>
        <StopPointRef>3800C540101</StopPointRef>
        <TimingStatus>OTH</TimingStatus>
    </From>
    <To SequenceNumber="25">
        <Activity>pickUpAndSetDown</Activity>
        <StopPointRef>3800C510100</StopPointRef>
        <TimingStatus>PTP</TimingStatus>
    </To>
    <RouteLinkRef>RL_6-25-_-y11-1-O-1-24</RouteLinkRef>
    <RunTime>PT1M5S</RunTime>
</JourneyPatternTimingLink>

-<JourneyPatternTimingLink id="JPL_6-25-_-y11-1-41-O-1-26">
    <From SequenceNumber="25">
        <Activity>pickUpAndSetDown</Activity>
        <StopPointRef>3800C510100</StopPointRef>
        <TimingStatus>PTP</TimingStatus>
    </From>
    <To SequenceNumber="26">
        <Activity>pickUpAndSetDown</Activity>
        <StopPointRef>3800C510105</StopPointRef>
        <TimingStatus>PTP</TimingStatus>
    </To>
    <RouteLinkRef>RL_6-25-_-y11-1-O-1-25</RouteLinkRef>
    <RunTime>PT2M</RunTime>
</JourneyPatternTimingLink>

<JourneyPatternTimingLink id="JPL_6-25-_-y11-1-41-O-1-27">
    <From SequenceNumber="26">
        <Activity>pickUpAndSetDown</Activity>
        <StopPointRef>3800C510105</StopPointRef>
        <TimingStatus>PTP</TimingStatus>
    </From>
    <To SequenceNumber="27">
        <Activity>pickUpAndSetDown</Activity>
        <StopPointRef>3800C591302</StopPointRef>
        <TimingStatus>OTH</TimingStatus>
    </To> <RouteLinkRef>RL_6-25-_-y11-1-O-1-26</RouteLinkRef>
    <RunTime>PT1M43S</RunTime>
</JourneyPatternTimingLink>
  *Hypothesis: Incorrect / invalid use of activities for links. In fact, the whole usage of activities within links is confusing. Surely the activity of a <From> element should be "pickUp" while the activity of a <To> element should be "setDown"?
  *Raised by: Tim Millington
  *Assigned to: Mark Taylor
  *Peter Stoner comments:  the schema has "pick up and set down" as the default activity in both the From and To elements of the the link.  Whether the bus station has a set down only arrangement will be something we can establish with Staffordshire CC.
  *Peter Stoner adds: Staffordshire CC confirm that the first stop is a general arrival stop.  We have discussed changing that to a BCQ stop and placing it near the vehicle entrance.
  *Tim Millington adds: The on-site station manager confirmed that there is no general set-down stop on site and set-downs all take place at the designated bays. I would suggest that changing the stop type to BCQ in the TNDS would not fix the issue that the TNDS indicates that passengers can be picked up at this stop, as described above. 
  *Peter Stoner comments: On the general point a valid observation but it would be a lot of work to change all the activities which do seem in line with TXC guidance.  The treatment of the bus station in Saffordshire is one or several approaches which would be valid.

=====Issue No: 93 WM Bus Available on the Wrong Day =====
 
  *Where detected (and date): Found an error in the West Midlands data which can be found in the follwing file cen_41-6C-1-y11.xml
  
  *Observation: A bus service for travel from Pool Meadow Bus Station departing at 07:25 (Mon to Fri) is incorrectly made available for regular weekday travel. This bus service should only be available on Univeristy holidays. 

  *Hypothesis: Incorrect Data as per the following:
  

       <VehicleJourney>
       <PrivateCode>VJ_41-11-C-y11-1-58-01</PrivateCode>
       <Operational>
         <VehicleType>
           <VehicleTypeCode>02</VehicleTypeCode>
           <Description>Double Deck</Description>
         </VehicleType>
       </Operational>
       <OperatingProfile>
         <RegularDayType>
           <DaysOfWeek>
             <MondayToFriday />
           </DaysOfWeek>
         </RegularDayType>
         <ServicedOrganisationDayType>
           <DaysOfNonOperation>
             <Holidays>
               <ServicedOrganisationRef>SOId_XX-38_UH</ServicedOrganisationRef>
             </Holidays>
           </DaysOfNonOperation>
         </ServicedOrganisationDayType>
       </OperatingProfile>
       <VehicleJourneyCode>VJ_41-11-C-y11-1-58-01</VehicleJourneyCode>
       <ServiceRef>41-11-C-y11-1</ServiceRef>
       <LineRef>41-11-C-y11-1</LineRef>
       <JourneyPatternRef>JP_41-11-C-y11-1-20-O-2</JourneyPatternRef>
       <DepartureTime>07:25:00</DepartureTime>
     </VehicleJourney>
	 
It is believed that the ServicedOrganisationDayType data for this service should look like this:
	 
         <ServicedOrganisationDayType>
           <DaysOfOperation>
             <Holidays>
               <ServicedOrganisationRef>SOId_XX-38_UH</ServicedOrganisationRef>
             </Holidays>
           </DaysOfOperation>
         </ServicedOrganisationDayType>
 
  *Raised by: Jeppesen

  *Assigned to: Keith Sabin
  *Peter Stoner comments: looks as if the journey is still (August 2013) being run during the University terms rather than the holidays.


Issue No: 92 CLOSED Invalid RunTime values?
 
  *Where detected (and date): TNDS NW file SVRLABO0760-20110130-5019.xml
  
  *Observation:  Many of the JourneyPatternTimingLinks have a RunTime of zero  (i.e. PT0M)    We believe that these are supposed to be populated with the correct time taken to travel between the two stops.  The zero RunTime occurs for StopPoints of all different TimingStatus value, not just OTH.  According to the TransXChange schema guide, the RunTime value is a required field for a JourneyPatternTimingLink.

This is making it hard for us to produce timetables that show how long it takes a bus to travel to various stops along a route.

  *Hypothesis:  The RunTime values have not been correctly set and instead are at their default value of zero.
 
  *Raised by:  Carl Partridge, FatAttitude

  *Assigned to:

  * Further notes:   Since submitting this report, we are wondering whether the zero RunTime values are intentional and a result of rounding times to the nearest minute, or incorrect interpolation of route times.
  * Peter Stoner adds: It seems that the data is as intended.  There are rather a lot of stops over a short distance.
Issue No: 91 CLOSED Composite Routes
  *Where detected (and date): TNDS WM file twm_4-T74_1-y11.xml (1.2.2013)
  *Observation: there are some route pairs in the TNDS such as this one, with line name '74/75', which don't do anything. 
  *Hypothesis: The pairs correlate exactly to a requirement of MDV to group services explicitly in order to make them appear on the same timetable on Traveline.  There does not seem to be any way to distinguish these 'special routes' from others when importing and thus be able to skip them. 
  *Raised by: Carl Partridge and Mark Taylor
  *Assigned to:
  *see issue 113

Issue No: 90 CLOSED Invalid Origin and Destination
   *Where detected (and date): NE_Nexus_NEXUS_GYB.xml (03/01/13) but affects many other NE_Nexus_* files
  *Observation: XML gives ATCO codes for StandardService Origin and Destination, instead of stop description.
  *Hypothesis: Misunderstanding of what field contents should be.
  *Raised by: Niall Jackson
  *Assigned to: Ian Jopling
  *Tim Millington reports (10.2.2013): A number of NE services (e.g. X19, 496, all NE_NEXUS* files?) are showing Origin / Destination of 13003424E / 13003424E These are valid NaPTAN atco codes but not ones which represent endpoints for the relevant services. 
  *Peter Stoner adds: Nexus are expected to change their systems in the next few months so this is unlikely to be resolved before then.
Issue No: 89 CLOSED Missing Journey Dates
  *Where detected (and date): swe_41-519_-1-y10 (13 November 2012)  
  *Observation: In ITOquality this appears with special days of operation ie non-operating days 24/12/2012-28/12/2012 and 31/12/2012-02/01/2013 but these dates are missing in TNDS.
  *Hypothesis: Seems to have lost the dates by the time it got into TNDS.
  *Raised by: Shane Reynolds (ITOworld)
  *Assigned to: BaseMap
  *Peter Stoner added:  The 1645 journey was exported from the SW as

		<VehicleJourney>
			<PrivateCode>VJ_41-519-_-y10-1-2-T0</PrivateCode>
			<OperatingProfile>
				<RegularDayType>
					<DaysOfWeek>
						<MondayToFriday />
					</DaysOfWeek>
				</RegularDayType>
				<ServicedOrganisationDayType>
					<DaysOfNonOperation>
						<Holidays>
							<ServicedOrganisationRef>SOId_Default-SOStr</ServicedOrganisationRef>
						</Holidays>
					</DaysOfNonOperation>
				</ServicedOrganisationDayType>
				<SpecialDaysOperation>
					<DaysOfNonOperation>
						<DateRange>
							<StartDate>2012-12-24</StartDate>
							<EndDate>2012-12-28</EndDate>
						</DateRange>
						<DateRange>
							<StartDate>2012-12-31</StartDate>
							<EndDate>2013-01-02</EndDate>
						</DateRange>
					</DaysOfNonOperation>
				</SpecialDaysOperation>
				<BankHolidayOperation>
					<DaysOfNonOperation>
						<AllBankHolidays />
					</DaysOfNonOperation>
				</BankHolidayOperation>
			</OperatingProfile>
			<VehicleJourneyCode>VJ_41-519-_-y10-1-2-T0</VehicleJourneyCode>
			<ServiceRef>41-519-_-y10-1</ServiceRef>
			<LineRef>41-519-_-y10-1</LineRef>
			<JourneyPatternRef>JP_41-519-_-y10-1-2-R-2</JourneyPatternRef>
			<DepartureTime>16:45:00</DepartureTime>
		</VehicleJourney>
	</VehicleJourneys>

The TNDS export of the same journey is:


   <VehicleJourney>
      <PrivateCode>VJ_41-519-_-y10-1-2-T0</PrivateCode>
      <OperatingProfile>
        <RegularDayType>
          <DaysOfWeek>
            <MondayToFriday />
          </DaysOfWeek>
        </RegularDayType>
        <ServicedOrganisationDayType />
        <SpecialDaysOperation>
          <DaysOfNonOperation>
            <DateRange>
              <StartDate>2012-12-24</StartDate>
              <EndDate>2012-12-28</EndDate>
            </DateRange>
            <DateRange>
              <StartDate>2012-12-31</StartDate>
              <EndDate>2013-01-02</EndDate>
            </DateRange>
          </DaysOfNonOperation>
        </SpecialDaysOperation>
        <BankHolidayOperation>
          <DaysOfNonOperation />
        </BankHolidayOperation>
      </OperatingProfile>
      <VehicleJourneyCode>VJ_41-519-_-y10-1-2-T0</VehicleJourneyCode>
      <ServiceRef>41-519-_-y10-1</ServiceRef>
      <LineRef>41-519-_-y10-1</LineRef>
      <JourneyPatternRef>JP_41-519-_-y10-1-2-R-2</JourneyPatternRef>
      <DepartureTime>16:45:00</DepartureTime>
    </VehicleJourney>
  </VehicleJourneys>

It would seem that there are a number of Tags missing in the TNDS version.
It would seem that:
<ServicedOrganisationDayType>
    <DaysOfNonOperation>
     <Holidays>
      <ServicedOrganisationRef>SOId_Default-SOStr</ServicedOrganisationRef>
     </Holidays>
    </DaysOfNonOperation>
   </ServicedOrganisationDayType>
has been reduced to:
<ServicedOrganisationDayType />
    
The tag <AllBankHolidays /> is missing.

  *BaseMap report that this issue has been resolved.
Issue No: 88 CLOSED Ferry appearing as Mode Bus
  *Where detected (and date): TNDS Scottish dataset (23 November 2012 data)
  *Observation:  some ferry journeys eg CM18 via Cal Mac through the  Western Isles are marked in the data as being a bus.
  *Hypothesis: That the Ferry mode is not being exported properly and therefore downstream systems are reverting to the default mode which is bus.
  *Raised by: Shaun MacDonald (ITOworld)
  *Assigned to: Stuart McNeill (Traveline Scotland)
  *Traveline Scotland replies: The data is exported to TNDS showing vehicle mode 3 and that mode is defined as being a ferry.
  *Shane Reynolds adds <Mode> should be a child element of
<ServiceInfoGroup> ie..

<ServiceInfoGroup>
    ....
    <Mode>ferry</Mode>
</ServiceInfoGroup>

However in data from Scotland the <ServiceInfoGroup> tags are missing.

  * Peter Stoner comments:  ServiceInfoGroup on p 144 of the TXC2 schema guide, shows that <mode> can appear on its own and does not need to be enclosed in <ServiceInfoGroup>.  It seems therefore that <Mode> is being exported correctly, but is being interpretted incorrectly in some downstream systems.
Issue No: 87 RESOLVED Service appearing in NextBuses not found in TNDS
  *Where detected (and date): TNDS 25/11/2012  
  *Observation:  Next buses API shows live & scheduled departures from Godlington Tesco (AtcoCode 0200352271) for the number 10 service. However the TNDS contains no route or journey pattern with that stop included for the number 10 service. The Bedford Borough Council route map shows the 10 following a route to the stop, and not the route described in the TNDS.
  *Hypothesis: Missing incorrect date for No. 10 services from Bedford to Godlington. 
  *Raised by: Tim Millington
  *Peter Stoner comments:  I think this stop is  020035271 Goldington Tesco (bfsampjm)
  *Assigned to: Stuart Reynolds
  * Tim Millington Adds: (02/01/13) Stops '020035557','020035558' also do not appear in the TNDS for this service. Note, also that these stops are flagged as unused in the unused stops file, (presumably, because they do not figure in any TNDS routes). However, the Nextbuses API does report departures from these stops. End user bus travelers report to me that these are real departures.
  *Stuart Reynolds comments: (20 June 2013) The Stagecoach Bedford EBSR data has recently been refreshed. Can you please retest?
  *Tim Millington responds: All looks good. 


Issue No: 86 RESOLVED Invalid dates in some files
 
  *Where detected (and date): in NE_Nexus_PB1954_20A.xml (21 November 2012)
  *Observation: Several departure times in this file are invalid, for example: <DepartureTime>16:64:00</DepartureTime>
  *Hypothesis: Typo propagated by copy/paste? Previous versions of the file do not have this error.
  *Raised by: Niall Jackson
  *Assigned to: Amy Armstrong (NE)
  *Amy replies: This is a service that Durham leads on and last week Nexus include it as part of the Nexus feed.  It has been removed from this week's feed so the issue should no longer exist.  
  *Peter comments:  The correct data supplied will be in the live TNDS from 27 November.  

=====Issue No: 85 SE Anomaly within some of the 'DaysOfOperation' elements =====

  *Where detected (and date): in bed_1-2e-1-y08.xml (and most of the other files) in SE.zip. (19 November 2012)  
  *Observation: how do we interpret this:
<code>
        <SpecialDaysOperation>
          <DaysOfOperation>
            <DateRange>
              <StartDate>2013-01-01</StartDate>
              <EndDate>2013-01-01</EndDate>
              <Note>New Year's Day</Note>
            </DateRange>
          </DaysOfOperation>
          <DaysOfNonOperation>
            <DateRange>
              <StartDate>2012-12-27</StartDate>
              <EndDate>2012-12-28</EndDate>
            </DateRange>
            <DateRange>
              <StartDate>2013-04-01</StartDate>
              <EndDate>2013-04-01</EndDate>
            </DateRange>
            <DateRange>
              <StartDate>2013-01-01</StartDate>
              <EndDate>2013-01-01</EndDate>
              <Note>New Year's Day</Note>
            </DateRange>
          </DaysOfNonOperation>
        </SpecialDaysOperation>
</code>
...and this:
<code>
        <BankHolidayOperation>
          <DaysOfOperation>
            <GoodFriday />
            <ChristmasDay />
            <BoxingDay />
          </DaysOfOperation>
          <DaysOfNonOperation>
            <GoodFriday />
            <ChristmasDay />
            <BoxingDay />
          </DaysOfNonOperation>
        </BankHolidayOperation>
</code>
  *Hypothesis: The dates are contradictory.
  *Raised by: Tony O'Grady
  *Assigned to: Roger Slevin
  *Stuart Reynolds: Current TXC2 guidance (v52) 3.18.3 (p119) "Special Days override Bank Holidays".  So if we say it does (or doesn't) run <Boxing Days> but we also say that it does (or doesn't) fun 26th December, it is the 26th December entry that you use. ....  and, also see 3.18.5 (point 5, p122) "Non operation overrides operation".  So the data is certainly interpretable - it's just that I haven't confirmed  yet that the data, when interpreted that way, is correct!
  *Stuart comments: Has been raised with MDV. (20 June 2013)
Issue No: 84 RESOLVED EA Service Description field does not describe where a service runs
 
  *Where detected (and date): suf_1-75_-5-y08.xml, ea_21-12F-1-y08.xml, ea_21-1B-1-y08.xml, ea_21-53_-1-y08.xml, ea_21-X29B-1-y08.xml, ea_20-125A-1-y08.xml, ea_20-407B-1-y08.xml, ea_21-29A_-1-y08.xml and around 200 files in the SW.zip including swe_30-218_-1-y10.xml (29/10/2012)
  
  *Observation: These files have the following service descriptions :
"Data Provided by South West Public Transport Information (SWPTI)  -  46  -  10/04/12", "The information on this timetable is expected to be valid until at least 17th October 2012. Where we know of variations,", "Please see First services 76/77 for journeys from Old Felixstowe and Landguard Fort", "before or after this date, then we show these at the top of each affected column in the table." We would expect this field to have a customer facing name that could be used to identify the service, e.g. "Feock - Pilleigh"
  *Hypothesis: An issue with the creation of the export files
  *Raised by: Jeppesen
  *Assigned to: Roger Slevin
  *now resolved for EA but may still be affecting Suffolk ones and possibly SW ones.  Issue being raised with mdv to resolve the problem fully.
  *Michael Clary: More examples from download on 22 January in files such as set_6-131C-1-y08.xml
  *Peter Stoner: will forward these examples to Stuart Reynolds. 
  *Carl Partridge: This is still present in some files in the most recent TNDS export, e.g. ea_20-3A-1-y08.xml
  *Peter Stoner comments: believed to be significant improvement, but not sure if the problem entirely eliminated(May 2013)
  *Stuart Reynolds comments: has apparently been fixed in the next release of DIVA.
  *Peter asks (August 2013): When in the next release expected?
  *Stuart:  Believe this is now fixed.
=====Issue No: 83 Serviced Organisations and Holiday Tables=====
  *Where detected (and date): in Table3.xls (22/10/2012)
  *Observation: No data available for 2013. LateSummerBankHolidayNotScotland is referenced as LateSummerHolidayNotScotland.
  *Hypothesis: Reference is inconsistent with the TransXchange specifications.
  *Raised by: Jeppesen
  *Assigned to: Peter Stoner
  *Peter Stoner comments: dealing with dating anomalies in the data, where exported are explicitly dated, is taking a higher priority over updating the central Service Data and Holidays file which is not yet being used. (August 2013)
=====Issue No: 82 EA DRT services=====
 
  *Where detected (and date): suf_18-DRT2-3-y08.xml (17/10/2012) 
  *Observation: There are a number of bus services that require booking which are incorrectly entered in the TXC data.  These bus services have a mode of “rail”.  Also they are described as Standard Services should they be Flexible Services?  There needs to be a consistent way of identifying these on demand services in the data other than parsing the note text.  Example line names (can provide a more extensive list if required):
- East Anglia (Suffolk Links Alde, Suffolk Links 3 Towns, Suffolk Links Wilford)
- East Midlands (C96, 16S|Spalding CallConnect, 4R|Stamford &amp; Rutland CallConnect)
  *Hypothesis: (from Roger:) Codes for modes in Suffolk map to different modes in the system creating the export to TNDS
  *Raised by: Jeppesen
  *Assigned to: Roger Slevin
  *Stuart Reynolds comments:  They aren't all from Suffolk, some in the list are also from EM, but that ties in with Suffolk appearing to have hte same settings as EM.  There would therefore seem to be something deeper in the TXC export process that will have to be raised with MDV.
  *Peter comments: This is believed to be one of the issues that Stuart Reynolds is continuing to discuss with MDV. (May 2013)
  *Stuart comments:Suffolk have advised that they are not using FLX stops in the system, which may be part of the problem.  Low priority. 

Issue No: 81 CLOSED Vehicle Journeys in TNDS not showing in NextBus API scheduled departures
 
  *Where detected (and date): 10/10/2012. twm_6-72_-1-y11.xml (4/10).
  *Observation: Vehicle journeys VJ_6-72-_-y11-1-*-UP (e.g. VJ_6-72-_-y11-1-430-UP) do not figure in the NextBuses API scheduled departures list. The operating profile shows Monday-Sunday operation with no special days. Journeys VJ_6-72-_-y11-1-*-T0 (e.g. VJ_6-72-_-y11-1-44-T0) do figure. These journeys have Monday-Friday operation.
  *Hypothesis: Perhaps the operating profile specified for journeys VJ_6-72-_-y11-1-*-UP (Monday-Sunday) is not correct.
  *Raised by: Tim Millington
  *Assigned to: Keith Sabin
  *Peter Stoner comments: All vehicle journeys on the quoted service are now Mondays only or Monday to Friday.
=====Issue No: 80 WM Multiple <VehicleJourney>s, same <DepartureTime>=====

  *Where detected (and date): WM, file twm_6-25_-1-y11.xml, 21/09/2012
  *Observation: Multiple <VehicleJourney>s, e.g. VJ_6-25-_-y11-1-35-T0 and VJ_6-25-_-y11-1-73-T0, for the same <Service> but referring to different <JourneyPattern>s, have the same <DepartureTime> (21:25:00). Both have operating profiles showing Monday to Friday operation (excepting a few days each).
  *Hypothesis:  On a given day, the <DepartureTime> should uniquely identify a <VehicleJourney> for a particular <Service>. (Otherwise, which journey pattern will the 21:25:00 follow?)
  *Raised by: Tim Millington
  *Assigned to: Keith Sabin
  *Peter Stoner comments: a solution to referencing errors is awaited from MDV (August 2013)


Issue No: 79 CLOSED  Y Data - same JPS with different links
 
  *Where detected (and date): Y data, 14/09/2012
  *Observation: Different files define the same JourneyPatternSection (by id), with a different set of TimingLinks. E.g. compare JPS_YWAX084-2 in files SVRYWAX084-20121029-31699.xml  and SVRYWAX084-20120730-31501.xml
  *Hypothesis: Should a different set of links not be a different JourneyPatternSection?
  *Raised by: Tim Millington
  *Assigned to: John Prince
  *Peter Stoner comments: there is no guarantee that references in one file will be unique across all files.

Issue No: 78 RESOLVED  Layover at Alston on service 888 missing
 
  *Where detected (and date): schedules_NE_Data_Northumberland_888.xml (12 September 2012)
  *Observation: layover is in northeast_CF_NorthumberlandData120830.cif but not found in the TXC2 version. 
  *Hypothesis: layovers are not being exported correctly.
  *Raised by: Bruce Ramsey
  *Assigned to: Ian Jopling
  *NE have tested their TXC2 output in Publisher and find that wait times are being exported correctly.
  *This is the Timing link in the NE TXC2 export 9 Sept of service 888 that includes the 35 min wait time at Alston Henderson Garage, before the 13 minute run time to Hartside cafe.
			<JourneyPatternTimingLink id = "JPTL_O0_69" >
				<From >
					<WaitTime>PT35M</WaitTime>
					<StopPointRef>090074022147</StopPointRef>
					<TimingStatus>PTP</TimingStatus>
				</From>
				<To>
					<WaitTime>PT00M</WaitTime>
					<StopPointRef>090074231557</StopPointRef>
					<TimingStatus>PTP</TimingStatus>
				</To>
				<RouteLinkRef>RL_O0_69</RouteLinkRef>
				<Direction>outbound</Direction>
				<RunTime>PT13M</RunTime>
			</JourneyPatternTimingLink>
  *This shows the NE were sending the waiting time.  However the current TNDS export does not include it:
<JourneyPatternTimingLink id="JPTL_O1_69">
        <From>
          <StopPointRef>090074022147</StopPointRef>
          <TimingStatus>PTP</TimingStatus>
        </From>
        <To>
          <WaitTime>PT00M</WaitTime>
          <StopPointRef>090074231557</StopPointRef>
          <TimingStatus>PTP</TimingStatus>
        </To>
        <RouteLinkRef>RL_O1_69</RouteLinkRef>
        <Direction>outbound</Direction>
        <RunTime>PT13M</RunTime>
      </JourneyPatternTimingLink>
  *So did NE send it in the recent data?  It seems they did:

			<JourneyPatternTimingLink id = "JPTL_O1_69" >
				<From >
					<WaitTime>PT35M</WaitTime>
					<StopPointRef>090074022147</StopPointRef>
					<TimingStatus>PTP</TimingStatus>
				</From>
				<To>
					<WaitTime>PT00M</WaitTime>
					<StopPointRef>090074231557</StopPointRef>
					<TimingStatus>PTP</TimingStatus>
				</To>
				<RouteLinkRef>RL_O1_69</RouteLinkRef>
				<Direction>outbound</Direction>
				<RunTime>PT13M</RunTime>
			</JourneyPatternTimingLink>
  *Hypothesis now is that the wait time is being dropped in the final processing of the NE TXC2 to produce TNDS.
  *Assigned to: BaseMap
  *BaseMap report this as resolved.  (TNDS-91 on 23 November 2012)

 =====Issue No: 77 NE Empty JourneyPatternSection element=====
 
  *Where detected (and date):  NE_Data_Cumbria_73A.xml  (12 September 2012)
  *Observation: "JPS_07" is empty and imports failure.
  *Hypothesis: That this is a mandatory element and the failure to import is indeed correct. 
  *Raised by: Shane Reynolds
  *Assigned to: Ian Jopling
  *Peter Stoner comments:  30 files listed, all Cumbria data, in the current error reports that "Sequence contains no elements"
  *Peter comments: follow up (August 2013)
Issue No: 76 RESOLVED SW missing RouteLinks
  *Where detected: SW.zip (11/09/2012) Specifically 'swe_30-10_-1-y10.xml'
but many other files in the same download exhibit the same issue.
  *Observation: Missing RouteLinks, Route Sections exist as empty elements.
KeyRef constraints fail as other parts of the document reference RouteLink
IDs that do not exist.
  <RouteSections>
    <RouteSection id="RS_30-10-_-y10-1-R-1" />
    <RouteSection id="RS_30-10-_-y10-1-H-2" />
  </RouteSections>
  *Hypothesis: 
 The export is failing to output the RouteLink records
  *Raised by: Edward Wohlman (Omnibus)
  *Assigned to: Stuart Reynolds
  *Stuart Reynolds reports: This is to be corrected in the next edition of the DIVA software from MDV.
  *Andy Hole reports: The 30-10_1-y10.xml does include RouteLinks.


Issue No: 75 CLOSED times rounded to whole minutes
  *Where detected (and date): NW data (previously stated as Yorkshire) (e.g. SVR60019548-20090201-22.xml) (6 Sep 2012)  Can also be observed in Y data (e.g. SVRYWAO033A-20120828-12873.xml)
  *Observation: the timing links in much of the NW & Y data appear to have <RunTime>s rounded to the nearest minutes.
  *Hypothesis:  rounding to whole minutes prevents matching of NextBuses scheduled departures to the TNDS timetable information.
  *Raised by: Tim Millington
  *Assigned to: John Gardner
  *Peter Stoner comments: rounding and different methods of interpolating intermediate stops can lead to minor differences between duplicate versions of the same journey and between scheduled and real time.


Issue No: 74 RESOLVED Service 67-68 missing in Cumbria
 
  *Where detected: TNDS download NE/zip on 28 August 2012 
  *Observation: Services 67 and 68 which are in the Journey Planner are not found in TNDS
  *Hypothesis: Failure in the conversion of the TXC2 data from NE
  *Raised by: Peter Stoner
  *Assigned to: Stuart Woods
  *Simon Day comments: the reason for this omission has been identified and should be resolved within a couple of weeks
  *Peter Stoner comments:  seems to be resolved now.

Issue No: 73 CLOSED No unique ID for a 'service', as a commuter would understand it

  *Where detected (and date): TNDS export download on 22 Aug: throughout TNDS, with  SW/swe_43-4_-1-y10.xml and SW/swe_43-4_-2-y10.xml used to illustrate.
  *Observation: There is often no single, unique identifier for bus services at a level of aggregation that is intuitive for commuters. For example there is no single ID for the service that represents 'the Wilts and Dorset Bus no 4 in Poole'. This service is stored across two files (SW/swe_43-4_-1-y10.xml and SW/swe_43-4_-2-y10.xml) with two distinct ServiceCodes (43-4-_-y10-1 and 43-4-_-y10-2). A composite ID of operator (WD) and LineName (4) would not uniquely reference this route, since there is another bus service operated by WD with the LineName '4' that is based in Salisbury (as represented in file SW/swe_47-4_-1-y10.xml)
  *Hypothesis: Minor variations in the 'same' service, result in this service being represented by multiple ServiceCodes.
  *Raised by: David Mountain
  *Assigned to: Peter Stoner
  *Peter Stoner comments:  "If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck".  There may be no substitute for looking at the general shape of journey patterns and the line number they run under to associate them with what has gone before, and some manual intervention may be necessary and recourse to those that supply the data.  This is not offered under TNDS at the moment but could be considered, and we know that several users could find it of assistance.
  *Roger Slevin - these separate identities will be found in all mdv sourced data and they refer to different "versions" where a version has a start and end date. so in this example it is probable that there are two versions of the data, one for "now" and the other starting at some future date.
  *Peter Stoner comments:  we know there are local and regional schemes to reference services uniquely but there is no UK wide scheme which seems to be what several users are requesting.
Issue No: 72 RESOLVED Short Working in Deadrun
 
  *Where detected (and date): Yorkshire data 0700 departure in YEB0746 in Y-YEYHYN120801.zip
  
  *Observation 1: The vehicle journey in the source from Yorkshire shows that it is a short working start at Pocklington 2200YEA0037 yet this appears in the export as a journey startin in Market Weighton and travelling at zero minutes to Pocklington which is normally a journey of about 30 minutes.

  *Observation 2: The export from the Traveline Yorkshire software creates a journey pattern, references the journey pattern but puts zeros in if a stop is missed in that journey pattern rather than create new journey pattern. This results in the TNDS import process currently reading these as zero timing sections.

  *Hypothesis:  That Short Working in Deadrun, possibly found in all Trapeze data, is not being imported correctly and/or the export from the Traveline region could be made more elegant.
 
  *Raised by: Peter Stoner
  *Assigned to: BaseMap (Jira)
  *Short working tags are now being passed correctly into TNDS
Issue No: 71  CLOSED Short notice changes in TfL data 
  *Where detected: TNDS exports in July 
  *Observation: Not including the special Underground timetables for the Olympic Games
  *Hypothesis: That these are being distributed separately by TfL
  *Raised by: Peter Stoner 
  *Assigned to: Peter Stoner
  *Peter Stoner comments:  TfL confirm that the Open data is the base timetable and is not updated for short term changes, which included revised schedules for the Underground.  These are available from the TfL website but if used you will need to suspend the base timetable.
  *TfL have agreed that Traveline can include in TNDS the data with includes short term changes that TfL provide for the Traveline journey planners.  We are working on including this as soon as possible - once the Olympics are over.
  *Peter Stoner comments: there are continuing problems in exporting temporary timetables so more details than originally expected.
  *Peter adds: this issue is not restricted to the Olypics and is represented by Issue 16 which remains open.

Issue No: 70 RESOLVED  Annotated Stop points missing in Centro data
 
  *Where detected (and date): all XML files (6493 xml files) (WM.zip CreationDateTime="2012-05-22T11:45:00-00:00")
  *Observation:All files are missing the StopPoints section.
  *Hypothesis:The files contain no "StopPointRef" and "CommonName"
  *Raised by:Sigrid van Veen / Dilip Mistry (Nokia L&C)
  *Assigned to: BaseMap
  *Peter Stoner comments - this is data from the new WM source and the format seems to be causing some difficulty.  All the StopPoints should be as listed in the NaPTAN national data.
  *Annotated stop points are now appearing in the TWN the files but not the CEN files.  This is being followed up.
  *Roger Slevin - the sources used for TWM files are CIF, whilst the CEN data is managed in mdv's DIVA database. This probably at least explains why there are these differences.
  *Peter Stoner comments:  My understanding is that it is only a matter of setting the export options and we hope that in the next export we get from Centro that this will be corrected.
  *Peter Stoner comments:  The Annotated stop points are now coming through in some of the WM.zip data ie that sourced from the Shire Counties.  As of 4 Septebmer 2012, we are waiting for an update of the Centro data which we hope will have the annotated stop references listed.
  *Annotated Stop points are showing in all Centro data now.
Issue No: 69 CLOSED More work needed on National Operator Codes 
  *Where detected (and date): TNDS, NOC (downloaded 2012-06-18) 
  *Observation: Even in regions that largely include NOC codes, there are still references to operators that do not include NOC codes, and are therefore difficult to match to NOC operators unambiguously. See eclipse.ukcod.org.uk/~louise/tnds/missing_2012-07-09_with_fixes.tsv for a list of all references to operators in files that can't simply be matched, plus a suggested match to a NOC code, where one could be made by name. 
  *Hypothesis: No region's files are yet completely populated with NOC codes.
  *Raised by: Louise Crow (mySociety) 
  *Assigned to: Peter Stoner
  *Peter Stoner comments: EA, EM and SE codes are now in NOC.  Good progress is being made to get remaining codes from other regions.



Issue No: 68 RESOLVED JourneyPatternTimingLink IDs duplicated
  *Where detected (and date): NW.zip File:SVRGM005820-20120305-2572.xml CreationDate:2012-06-26
  *Observation: Non-unique JourneyPatternTimingLink ids
  *Hypothesis: All 19 JourneyPatternSections contain JourneyPatternTimingLinks with the same 45 different ids. JourneyPatternTimingLink ids should be unique within a file.
  *Raised by: Edward Wohlman (Omnibus)
  *Assigned to: BaseMap
  *Similar issues have now been found in some Scottish data, where the problem is in the processing of the data for TNDS rather than the export from Scotland.  Therefore this issue has been reassigned to BaseMap.
  *This issue is now believed to be resolved.  (4 September 2012)
Issue No: 67 RESOLVED  Faulty file in TfL data
  *Where detected (and date): output_txc_49965d.xml (L.zip CreationDateTime:2012-06-21T08:12:58)
  *Observation: This file is missing the 'Services' section
  *Hypothesis: The file contains no 'Services' or 'JourneyPatternSections' (but there are two VehicleJourneys that reference non-existant, Services, Lines and JourneyPatterns)
  *Raised by: Edward Wohlman (Omnibus)
  *Assigned to: BaseMap
  *Peter Stoner comments: this seems to be a continuing error in the <Services> element of the source file from TfL so we should be rejecting this file for further processing in TNDS.
  *the problem in the original data has been raised with Source London
  *a reminder sent to Tfl January 2013
  *Peter Stoner: seems to be fixed (Feb 2013)
Issue No: 66 RESOLVED Faulty file in TfL data
  *Where detected (and date): output_txc_49965d.xml (L.zip CreationDateTime:2012-06-21T08:12:58)
  *Observation: Schema validation error due to missing RegularDayType (Line 476)
  *Hypothesis: VehicleJourney/OperatingProfile contains 'SpecialDaysOperation' but not 'RegularDayType' which is mandatory in all OperatingProfiles.
  *Raised by: Edward Wohlman (Omnibus)
  *Assigned to: BaseMap
  *Peter Stoner comments: Same incomplete source file as Issue 67.
  *the problem in the source data has been raised with Source London
  *the file has not been corrected in the latest data so has been removed from the TNDS.
  *Peter Stoner adds: it has not been excluded in a subsequent week and is still incorrect, so a note quoting this file will be added to the inventory.
Issue No: 65  Backwards dates in NE data  CLOSED
  *Where detected (and date): NE TXC2 exports 120615.zip
  *Observation: OperatingPeriod dates are backwards on a few routes eg 352
  *Hypothesis: That there is something wrong in the TXC2 exports
  *Raised by: Peter Stoner
  *Assigned to: Stuart Woods/Simon Day
  *Peter Stoner comments:  This is now believed to be resolved  (4 September 2012)
  *Peter Stoner:  Seems to be fixed (Feb 2013)
Issue No: 64 CLOSED Multiple files for a single Line
  *Where detected (and date): TNDS data 3 June 2012
  *Observation: a single route can have multiple files
  *Hypothesis: An explanation would be beneficial  
  *Raised by: Alan 
  *Assigned to: Peter Stoner
  *Peter Stoner comments: The incidences of multiple files will mostly be found, though not necessarily exclusively, in the NW, Wales, Yorkshire and Scottish data.  The data in these areas, tends to be held with separate tables for different periods, rather than holding the changes in a single file.  The highest number of files we have found is over 100 for a single route.  The causes for such a high number of files are being investigated.
  *Roger Slevin - as noted in issue 73, mdv system also holds data in dated versions, so multiple files exist when service changes are imminent.  The Trapeze export also used to have multiple files for days of the week - but maybe this is no longer the case.
  *Peter Stoner comments -this is still the case. (May 2013)  Trapeze outputs are not groups into the same file unless Trapeze's extra CIF records are maintained.  
  *see also Issue 32.
  *Stuart comments: there is an easy way to tell as
the filename contains the version number. For example, in this week's SUF
data (EA2), you will find two files SUF_56-FRY-1-7-y08 and
SUF_56-FRY-1-8-y08. The service is defined by SUF_56-FRY-1, and the versions
are 7 and 8 respectively. In SW, this may lead to two different operators
(e.g. a change in a contracted service) as their equivalent to the "56" part
is mostly authority based, but the services can still be grouped on this
basis. However, the final comment to be aware of is that higher version
numbers will supersede lower version numbers when they overlap - so it would
be feasible to create a new version which covered Christmas only, say, while
leaving the original version there but apparently running through. This is
one of the things that I am asking them to change in the outputs so that it
is clear.
  *Peter Stoner comments: A note to explain multiple files has been added to the inventory. http://traveline.info/inventory-tnds.html


Issue No: 63 CLOSED
  *Where detected (and date): 'SVRACAO001-20100228-217.xml' and other files from 'W.zip' 29/05/2012
  *Observation: Non-unique JourneyPatternTimingLink ids, violates schema uniqueness constraint
  *Hypothesis: This file contains two JourneyPatternSections, with ids 'JPSection2' and 'JPSection3' the ids of the links in both these sections are the same, numbers 9850 to 9895. This means there 92 TimingLinks but only 46 unique IDs.
  *Raised by: Edward Wohlman (Omnibus)
  *Assigned to: Peter Stoner
  *Peter Stoner comments: the current data does not seem to contain JPSection references so the issue needs to be raised again with a current example.

Issue No: 62 CLOSED
  *Where detected (and date): File NE_Darington_Data.20 in NE.ZIP, downloaded 2012-05-29
  *Observation: I noticed that this bus service has an OperatingPeriod element with StartDate of 3rd June, i.e. the future.  However, when calling the Nextbuses API (e.g. for StopPoint with atcoCode 07605043), it shows this service is scheduled to arrive at the stop every hour today.  (at xx:54)  Both of these cannot be correct.
  *Hypothesis: Either the NextBuses API is producing incorrect schedules, or Bus Service with lineName '20' is marked with a start date in the future, but should have a start date in the past.
  *Raised by: Carl Partridge
  *Assigned to: Simon Day
  *Simon Day comments: service changed on 3rd June, and the version of the service expiring on 2d June was not included in the data set created on 29/5/12.
  *Peter Stoner comments: this would have been an error as the usual practice is to include expiring and new services.
Issue No: 61 CLOSED  No Description sub-element in NE data
  *Where detected (and date): In TNDS files downloaded on 16th May 2012, e.g. NE_Cumbria_Data_1.xml
  *Observation:  In some files (such as NE_Cumbria_Data_1.xml) the Service elements have no Description sub-element.  I haven't checked if this element is mandatory, but it exists in around 90% the national data.  It's obviously a very helpful element to have in the data set, since it providers a quick, user-facing description of a bus service.  The affected Service elements are mostly in  London, Cumbria or Durham.
  *Hypothesis: Description element of some Service elements is missing.
  *Raised by:  Carl Partridge
  *Assigned to: Peter stoner
  *Peter Stoner comments:  Issue 53 also concerns Service Descriptions.  While the field may be desirable, it is not just that it is populated, but what it is populated with.
  *Simon Day adds: Issue generic in all NE+C data.  We appreciate the value (of a Service Description) but at present cannot readily populate (unless you can suggest a method?)
  *Peter Stoner comments: Unless they can be handcrafted names for each service, I suggest look for the longest JourneyPattern and quote the locality name of the first and last points.


Issue No: 60  CLOSED
Where detected (and date): In London files downloaded on 16th May 2012, e.g.  output_txc_54C11j.xml
Observation:  In many (if not all) of the files for the London area (such as output_txc_54C11j.xml) various sub-nodes of the Operator element appear to be abbreviated forms of what they are meant to be.  For example, 'OperatorNameOnLicence' is set to ML, which is unlikely to be what is on the actual licence.  Could these perhaps be correctly populated with the correct operator name?
Hypothesis: The OperatorNameOnLicence,  OperatorTradingName and OperatorShortName elements are abbreviated the same as the operator short code instead of their long-form equivalents.
Raised by:  Carl Partridge
Assigned to: Peter Stoner
Peter Stoner comments: These fields are intended for Electronic Bus Registration which will not necessarily be being used, and certainly not in London, where bus registration does not apply.  Better indentification of operators will come as we improve the National Operator Code dataset and get it working in all regions.



Issue No: 59 RESOLVED
  *Where detected (and date):set_6-26B-1-y08.xml 12/05/12
  *Observation: TransXchange 2.4 reports 
PublishingException: Problem with input document: couldn't find RouteLinkRef element for 
JourneyPatternTimingLink with id: JPL_6-26-B-y08-1-UL-196-0-2 .
  *Hypothesis: Each Journey pattern link does not have an actual or inherited link to the route scheme.
This prevents mapping and appears to be a conversion error. If the mapping is turned off a matrix is 
produced which is significantly different from the actual timetable. The source of this difference 
is not yet obvious.
  *Raised by: Philip Mart
  *Assigned to: Peter Stoner
  *Peter Stoner comments: The file quoted was not quoting <RouteLinkRef> in <JourneyPatternTimingLink> records but now is.

Issue No: 58 RESOLVED
  *Where detected (and date):set_6-26B-1-y08.xml 12/05/12
  *Observation: TransXchange 2.4 reports Line 16768, column 46: Duplicate unique value [6-26-B-y08-1] declared for identity constraint of element
  *Hypothesis: The &lt;PrivateCode&gt; child element of each &lt;Service&gt; is not unique. When amended to be unique the fault is removed. It would appear to be a conversion error. I found that  the error occurs in all of the files I checked in the SE.zip
  *Raised by: Philip Mart
  *Assigned to: Peter Stoner
  *Peter Stoner comments: the latest version of this file does not repeat the <PrivateCode> reference in the <Service> section and this is believed to reflect changes that the SE have made to address the problem.
Issue No: 57  CLOSED
  *Where detected (and date): SVRSKAO041-20120124-1105.xml, 12/05
  *Observation: Having uploaded all files I find there is no route for the reverse of SKAO041_003. While the service 'hasMirror', this cannot be strictly true as the reverse route uses the a different set of stops (on the other side of the road). Have seen other similar examples from the WM.zip archive.
  *Hypothesis:
  *Raised by: Tim Millington.
  *Assigned to: Keith Sabin (WM)
  *Peter Stoner comments: the source of the WM data is about to change and it is unlikely that a "hasMirror" indicator will be in the new data in the same way.  That said we do need to consider how such labels arise and what their definition is.  The mirror is unlikely to use exactly the same stops.
  *WM has moved to new data source.
Issue No: 56  CLOSED
  *Where detected (and date): WM.zip downloaded 05/05, observed 11/05
  *Observation: Seems to be a lot of duplicate information. E.g., the information in SVRSKAO041-20120124-1104.xml seems to be repeated in SVRSKAO041-20120124-1105.xml.Should I be assumin that the information on the file with the higher number it the end of the file name supercedes that with the lower?
EDIT: I have noticed that the latter file is Weekend Operation, while the first Weekday, so there is a difference. Since both files reference the same set of JourneyPatternSections (ref issue 55, below), is it safe to assume the JourneyPatternSections information is duplicate?
  *Hypothesis:
  *Raised by: Tim Millington
  *Assigned to: Keith Sabin (WM)
  *Peter Stoner comments: the source of the WM data is about to change and when it does so the data is likely to come through as one file per service. 
  *WM has moved to new data source. 
Issue No: 55  CLOSED
  *Where detected (and date): WM.zip downloaded 05/05, observed 10/05
  *Observation: All the files in WM.zip (e.g. SVRSKAO041-20120124-1104.xml) seem to use generic &lt;JourneyPatternSection&gt; ids, e.g., &quot;JPSection2&quot;. According to the schema guide, this element is a top level element -- so should these ids be unique across the system?
  *Hypothesis:
  *Raised by: Tim Millington
  *Assigned to: Keith Sabin (WM)
  *WM has moved to new data source.


Issue No: 54 CLOSED
  *Where detected (and date): eg. SVRSKAO041-20120124-1104.xml 08/05/2012
  *Observation: Some &lt;Service&gt;&lt;StandardService&gt;&lt;JourneyPattern&gt; elements do not contain a &lt;RouteRef&gt; element.
  *Hypothesis:
  *Raised by: Tim Mllington
  *Assigned to:
  *WM have moved to a new data source.
Issue No: 53 CLOSED
  *Where detected (and date):  Spotted in several files, e.g. em_11-152_-1-y08.xml
  *Observation: An incorrect service description is present in some files, for example in file em_11-152_-1-y08.xml, the service description for the Service with ServiceCode 11-152-_-y08-1-T2 is as follows:

&lt;Description&gt;to the normal timetables. The Bank Holiday timetables are subject to change at short notice - please check again&lt;/Description&gt;
  *Hypothesis: An incorrect service description is present in some files - perhaps an auto-import script populated the wrong data?
  *Raised by: Carl Partridge (FatAttitude)
  *Assigned to: Stuart Reynolds
  *Peter Stoner comments:  This appears to be resolved.


Issue No: 52  RESOLVED
Where detected: I've seen this in a large number of files in different ares
For Example &quot;SVRWREO010A-20090126-5297.xml&quot; from W.zip (02/05/2012)
Observation: Schema validation issue due to incorrect element ordering
Hypothesis: 'JourneyPatternTimingLinkGroup' elements are xsd:sequence
Should be 'From' -&gt; 'To' -&gt; 'RouteLinkRef' -&gt; 'Direction' -&gt; 'RunTime'
I'm seeing 'Direction' -&gt; 'RouteLinkRef' -&gt; 'From' -&gt; 'To' -&gt; 'RunTime'
which occurs on all of the JourneyPatternTimingLinks
Raised by: Edward Wohlman (Omnibus)
Assigned to: Peter Stoner
Peter Stoner comments:  This should be resolved now.


Issue No: 51  RESOLVED
Where detected: TNDS 1 May 
Observation:  34 files in Scotland have not loaded 
Hypothesis: TXC files supplied are incomplete
Raised by: BaseMap
Assigned to: Stuart McNeill (Scotland)
Peter Stoner comments: Tracing the cause back it seems that the Trapeze TXC export stopped because of a missing or incorrect NaPTAN point for Ballycastle ferry terminal.
Stuart McNeill comments: These services will not be exported in future, because they relate to Non NaPTAN points, such as in Northern Ireland.

RouteLinkRef
=====Issue No: 50  Converting TNDS to GTFS=====
  *Where detected: THDS data 27 April 2012 from all regions
  *Observation: data fails to convert
  *Hypothesis: data is not supported by current GTFS converters
  *Raised by: Colin
  *Assigned to: Peter Stoner
  *Peter Stoner comments:  This may work now that the xsd:sequence has been sorted out.



Issue No: 49  RESOLVED

  *Where detected: 'swe_32-26_-1-y10.xml'
  *Observation: Schema validation issue due to multiple occurrence of 'VehicleType' in VehicleJourney/Operational.

&lt;PrivateCode&gt;VJ_32-26-_-y10-1-1-T0&lt;/PrivateCode&gt;
&lt;Operational&gt;
	&lt;VehicleType&gt;
		&lt;VehicleTypeCode&gt;DDLF&lt;/VehicleTypeCode&gt;
		&lt;Description&gt;Double Decker Low Floor &lt;/Description&gt;
	&lt;/VehicleType&gt;
	&lt;VehicleType&gt;
		&lt;VehicleTypeCode&gt;LD&lt;/VehicleTypeCode&gt;
		&lt;Description&gt;Double Decker Low Floor &lt;/Description&gt;
	&lt;/VehicleType&gt;
&lt;/Operational&gt;

  *Hypothesis: The schema specifies 
&lt;xsd:element name=&quot;VehicleType&quot; type=&quot;VehicleTypeStructure&quot; minOccurs=&quot;0&quot;&gt;
'maxOccurs' defaults to '1' as it has not been overridden here

  *Raised by: Edward Wohlman (Omnibus)
  *Assigned to: Andy Hole (SW)
  *Andy Hole comments:  There was a type mismatch between internal and external codes.  This will be corrected in this week's data export.



Issue No: 48 CLOSED Schema invalid footnote
  *Where detected: 'swe_30-225_-2_y10.xml'
  *Observation: Last journey (VJ_30-225-_-y10-2-4-T0) missing DepartureTime, having a schema-invalid footnote with just the text 'R' rather than separate 'NodeCode' and 'NoteText' elements.
  *Hypothesis:  Journey repetition record
  *Raised by: Edward Wohlman (Omnibus)
  *Assigned to: Andy Hole (SW)
  *Peter Stoner comments: SWE file is no longer in the data.


Issue No: 47   RESOLVED
Where detected: 'swe_30-1_-1y10.xml'
Observation: Conflicting bank holiday flags. 
The same element names appear both in both the 'DaysOfOperation' and 'DaysOfNonOperation' groups of 'BankHolidayOperation'

XPath Expressions:
count(//BankHolidayOperation[[DaysOfOperation/EasterMonday and DaysOfNonOperation/EasterMonday])
= 182
count(//BankHolidayOperation[[DaysOfOperation/GoodFriday and DaysOfNonOperation/GoodFriday])
= 185

Hypothesis: Data issue
Raised by: Edward Wohlman (Omnibus)
Assigned to: Andy Hole (SW)
Peter Stoner comments:  These holidays are no longer exported in the quoted file.
Andy Hole comments:  The issue is no longer present.  I amended the way I do Bank Holidays.

Issue No: 46  RESOLVED
Where detected: 'swe_30-1_-1y10.xml'
Observation: Schema validation issue due to sequence ordering of BankHoliday flag elements.
Hypothesis: 'HolidayMondaysDaysGroup' elements are an 'xsd:sequence'
The elements are all optional but where they occur they should be ordered.
LateSummerBankHolidaysNotScotland -&gt; MayDay -&gt; EasterMonday -&gt; SpringBank -&gt; AugustBankHolidayScotland
The file contains 
          &lt;DaysOfNonOperation&gt;
            &lt;GoodFriday /&gt;
            &lt;EasterMonday /&gt;
            &lt;SpringBank /&gt;
            &lt;LateSummerBankHolidayNotScotland /&gt;
          &lt;/DaysOfNonOperation&gt;

Raised by: Edward Wohlman (Omnibus)
Assigned to: Andy Hole (SW)
BaseMap comment: The order remains as supplied by the regional source data.
Peter Stoner comments:  These days are no longer quoted in the export file which may be an issue in itself.
Andy Hole comments:  Issue is no longer present.  I amended the way I do Bank Holidays.


Issue No: 45  RESOLVED
Where detected: several of the SW xml files, probably all of them
Observation: Schema validation issue due to sequence ordering of Operator elements
Hypothesis: OperatorStructure elements belong to an 'xsd:sequence'
In the data files NationalOperatorCode appears after OperatorNameOnLicence, 
it should appear first in the Operator, before OperatorCode.
Raised by: Edward Wohlman (Omnibus)
Assigned to: Peter Stoner
Peter Stoner comments: this is expected to be corrected in the data release on 1 May.



Issue No: 44  RESOLVED
Where detected: National Operator Codes April 2012
Observation: There are some codes which are not 4 characters long, and they are not rail or air mode: AUSTP, ECCHS, EXCEL, HMV, HMPTN, WPH, 
Hypothesis: They may have been created in error.
Raised by: John Prince
Assigned to: The regional owners of the codes concerned.
Peter Stoner comments:  The bus codes listed above have now been amended so all bus operator codes are 4 characters.


Issue No: 43 RESOLVED National Operator Codes
  *Where detected: Prerelease TNDS data, NOC
  *Observation: There are around 450 operators referenced in TNDS that cannot be simply matched in NOC from their region and operator code, and an additional 160 that don't seem to have records in NOC at all. See http://eclipse.ukcod.org.uk/~louise/tnds/missing_2012-04-16_with_fixes.tsv for a list of all the TNDS files that contain references to operators that can't currently be simply matched, plus a suggested matched to a NOC code, where some match could be made based on the name.
  *Hypothesis: NOC is missing some regional codes, and also some records.
  *Raised by: Louise Crow / mySociety
  *Assigned to:  Traveline Regional Managers
  *PJS: West Midlands should be ok now in latest version of NOC.  Other regions to follow.
  *Peter Stoner comments:  SE, EM, EA issues now understood.  Working on a solution.
  *SE, EM and EA now substantially complete in NOC.


Issue No: 42   RESOLVED
Where detected: TNDS test data swe_48-329A-1-y10.xml
Observation: Negative run time of -PT2M
Hypothesis: seems to cancel a wait time of PT2M
Raised by: Eduard Tulp
Assigned to: Andy Hole
Andy comments: surprised that the -ve time got through.  Data will be checked.
Peter Stoner comments:  This seems to be corrected in the file quoted.


Issue No: 41  CLOSED
Where detected: TNDS test data SUF_7-1_-1-y08.xml
Observation: &lt;Description&gt;Nowton Ã¯Â¿Â½ Bury St. Edmunds Town Centre Ã¯Â¿Â½ Mildenhall Rd Est&lt;/Description&gt;
Hypothesis: Not entirely sure whether that is formally allowed and it is not a big issue, but our sofwtare was unhappy with it.
Raised by: Eduard Tulp
Assigned to: Stuart Reynolds
Peter comments: This file is not in the latest data supplied.
Stuart comments: I think that this was caused by Suffolk copying and pasting something that Microsoft Word had auto-corrected. It has a habit of turning a perfectly respectable hyphen into a longer em dash, that then falls apart as soon  as the character set changes. I did tell them about some, and it may be  that it is fixed already.
Peter comments: So we will try and avoid this happening but no auto checks in place yet.


Issue No: 40  RESOLVED
Where detected: TNDS test data
Observation: Files are not zipped
Hypothesis: Is it possible to have this data provided in a zip file to improve the download time?
Raised by: Jeppesen, JourneyPlan, ITOworld
Assigned to: Peter Stoner
Peter comments:  The files are expected (soon) to be in separate zip folders relating to the (regional) source of the data.  A test file of London data has been zipped.
Peter comments:  The files are now zipped.


Issue No: 39  RESOLVED
Where detected:  TNDS NPTDR format sample data
Observation: Sample files in a single directory
Hypothesis: an index file mapping file names to region
names will be useful - as this allow automated referential integrity
checks with other data sources that reference regions eg. NOC
Raised by: Louise Crow
Assigned to: Peter Stoner
Peter comments:  The files are expected to be in separate zip folders relating to the (regional) source of the data.


Issue No: 38 RESOLVED Mandatory ID missing
  *Where detected: TNDS NPTDR format sample data
  *Observation:  JourneyPatternTimingLink elements don't have id attributes as they do in the beta data set.
  *Hypothesis:  may not make any difference to downstream loading processes
  *Raised by: Louise Crow
  *Assigned to: Peter Stoner
  *Eduard Tulp adds: In both the Wales and the YK sets the mandatory Id in the JourneyPatternTimingLink elements are all missing.
  *Peter Stoner comments: Wales and YK now pass the schema checks.



Issue No: 37 CLOSED
  *Where detected: TNDS NPTDR format sample data
  *Observation: The operator code &quot;554TMT&quot; used in em_11-112_-1-y08.xml isn't an operator code listed for any region in NOC - looks like maybe it should be just &quot;TMT&quot;. Also if this is the &quot;T M Travel Ltd&quot; in NOC, the OperatorNameOnLicence value of &quot;TM Travel&quot; doesn't exactly match the VOSA_PSVLicenseName field in NOC - which has &quot;T M Travel Ltd&quot;
  *Hypothesis: 
  *Raised by: Louise Crow
  *Assigned to: Peter Stoner


Issue No: 36  CLOSED
  *Where detected:  TNDS NPTDR format sample data
  *Observation: The operator code &quot;JT&quot; used in swe_30-218_-1-y10.xml  and swe_30-219_-1-y10.xml isn't an operator code listed for any region in NOC and the name &quot;Jacketts Coaches&quot; doesn't appear in NOC
  *Hypothesis: a missing entry in NOC?
  *Raised by: Louise Crow
  *Assigned to: Peter stoner
  *Peter Stoner:  Good progress now on NOC, with regions actively managing.


Issue No: 35 RESOVED  Schooldays not current
  *Where detected:  Comparison of Service 79 Barnard C to Richmond supplied to TNDS by Yorkshire and NE.
  *Observation: Yorkshire has &quot;Schooldays&quot; but no dates.  NE has &quot;English shooldays only&quot; and &quot;Schooldays only&quot; both with dates but they are not current.
  *Hypothesis: This should not be a problem as a user of the data should apply more rec  ent dates from the central         Services Organisation file.
  *Raised by: Peter Stoner
  *Assigned to: Peter Stoner
  *Peter comments: NE has updated their holiday dates file.

Issue No: 34 CLOSED Serviced Organisation Codes
  *Where detected: Comparison of Service 79 Barnard C to Richmond supplied to TNDS by Yorkshire and NE.
  *Observation: Differences in Organisation codes.  Yorkshrie quotes &quot;11&quot;, Durham quotes 1000, 1011, 1002 and 0000.
  *Hypothesis: These may be local organisation codes.  Need to check with main Serviced Organisations file.
  *Raised by: Peter Stoner
  *Assigned to: John Prince
  *John Prince: I am querying the source of the &quot;11&quot; code from Trapeze.
  *"11" is understood to be an internal reference only.
  * no current plans to adopt the national serviced organisations referencing. 


Issue No: 33   CLOSED
Where detected: NOC_DB120329.xls
Observation: There are two NOC codes for the Huddersfield Bus Company - HUDB and HBSY, and for East Yorkshire Motor Services (SDMS, EYMS, same VOSA license number), The A &amp; M Group (AMMG, AAMG), Harrogate Coach Travel (HCTY, HGCT)
Hypothesis: One's a duplicate, or NOC codes are not supposed to be nationally unique and represent a license holder uniquely?
Raised by: Louise Crow / mySociety
Assigned to: John Prince
John Prince replies to say: 
There are public name differences in the local dataset which should perhaps be added to NOC so that the reason for their being two codes is made clear.  
Peter Stoner comments:  We have agreed to include an entry for each PSV number and more than one entry if the public name needs to be different in use in different places.
Louise Crow comments: In this case, it will be important to be able to identify in NOC cases where two entries refer to the same entity - is the reliable way to do this by looking for duplicated VOSA license numbers?
Peter Stoner comments:  Yes, comparing the VOSA licence numbers should be a reliable method of finding which operator is the same, but the public name and feedback channels may vary.


Issue No: 32 CLOSED Bus route spread across multiple files
  *Where detected: travelineFullSet14032012.zip
  *Observation: There are instances where journeys for what appears to be a single service are distributed across multiple files with no simple way to relate them back together - e.g. SVRLAAX0600-20110919-10555.xml and SVRGM00X600-20110919-6209.xml appear to describe outbound and inbound journeys on one route - the X60 run by Stagecoach in Lancashire - but they don't share ServiceCodes or OperatorCodes
  *Hypothesis: Not all services whose data are distributed across files share a ServiceCode or OperatorCode.
  *Raised by: Louise Crow / mySociety
  *Assigned to: Peter Stoner
  *Peter Stoner comments:  We are considering merging journeys into files for the moment find it helps match to the source file if we keep them as they came in.  What do you think is the best way to group journeys?  By operator and line eg 79, 79A, N79 in separate files, by operator and service ie 79 (includes 79, 79A and N79). Would you include the journeys of another operator eg if they provided the evening service under contract?  Of course this implies we have got issue 31 resolved.
  *Louise Crow comments: For my purposes, operator and line are the most useful ways to group journeys as this maps to what the public would understand as a bus route. If you can reliably include the journeys of another operator that runs the same service under contact, that would be ideal.
  *Peter Stoner comments: in some regions a route may be spread over 100 or more files.  Trapeze are investigating the reasons this happens, which is thought to be related to the way the data comes in.
  *issue continues under no 64

Issue No: 31  RESOLVED
Where detected: travelineFullSet14032012.zip
Observation: There are differences in the interpretation of TransXChange elements in the dataset that make it difficult to interpret consistently - e.g. in what is considered a Line - most files contain as the line name one identifier but swe_41-SO10-1-y10.xml contains the line name &quot;154/54/54A/54B/54C&quot; and there doesn't appear to be specific information that would map the journey patterns included to a specific one of these lines.
Hypothesis: 
Raised by: Louise Crow / mySociety
Assigned to: Andy Hole - given the example quoted is in SW data.
Peter Stoner comments:  Useful tutoring from Nick Knowles suggests that there could be more than one line used in a given TXC timetable - eg there might be 21a and 21B for different branches, or 98 and N98 for a day and night bus, or 21C and 21A for a clockwise anticlockweise journeys on a circular route.  However these should be listed separately so that each journey gets the number shown on the front of the bus.
Andy Hole replies:  This (the example quoted) is a fairly easy one to explain as it should not have been included in the export as it is a composite route.  I will try and make sure that composite routes are not included in future TNDS exports.
Peter Stoner comments: The observed file is no longer included in the SW export.


Issue No: 30  RESOLVED
Where detected: travelineFullSet14032012.zip
Observation: There are services whose mode is given as &quot;air&quot; in the dataset.  See http://eclipse.ukcod.org.uk/~louise/tnds/files_with_air_as_mode.txt
Hypothesis: These are either air services mistakenly included, or services incorrectly assigned the mode air.
Raised by: Louise Crow / mySociety
Assigned to: Stuart Reynolds - given the number of Bedfordshire, Suffolk, EM and EA references.
SR responds: &quot;Air&quot; should probably be wheelchair accessbile bus.  MDV are being asked to fix this.
PS: SVRFAAHWY0-20100707-5411.xml SVRFAAHWY0-20100707-5412.xml are the Anglesey to Cardiff air service so is correct.  Air can be included in Traveline but we do not undertake to include all air services.
Stuart Reynolds responds:  That this problem has been resolved and the data he processes should not normally refer to &quot;air&quot; mode.  




Issue No: 29 CLOSED  Missing NaPTAN Points
  *Where detected: travelineFullSet14032012.zip
  *Observation: There are StopPoints with a StopPointRef missing from the latest NaPTAN database. There is no way to determine the location of these stops. For a full list of affected stops, see http://www.rome2rio.com/extras/Traveline14032012.xlsx
  *Hypothesis: Maybe I'm using an old NaPTAN database? I downloaded from http://www.dft.gov.uk/public-transportdatamanagement/DataUser_Login.aspx on 20/03/2012.
  *Raised by: Bernie Tschirren / rome2rio
  *Assigned to: Peter Stoner 
  *Comment from Peter Stoner: We expect at any one time for their to be a certain number of NaPTAN stops that cannot be found.  Some may have come through more quickly to TNDS than to the NaPTAN downloads, and a later download of NaPTAN will enable them to be matched.  Others may be errors that need to be corrected at the regional or operator data sources.  The analysis you have supplied is useful.  The regions already have reporting tools to help them match up the missing NaPTAN points.



Issue No: 28 CLOSED Missing NaPTAN points
  *Where detected: travelineFullSet14032012.zip
  *Observation: There are JourneyPatternTimingLinks where From/To StopPointRef is not a defined StopPoint in XML file. For a full list of affected files, see http://www.rome2rio.com/extras/Traveline14032012.xlsx
  *Hypothesis:
  *Raised by: Bernie Tschirren / rome2rio
  *Assigned to: Peter Stoner
  *Peter Stoner comments: We are proposing to provide integrity reports so all the NaPTAN points that are not found are listed in one place.  This was the method prefered by PTIC.  It may be helpful if these reports list the preceding and following NaPTAN points, as found in the journeys.  The individual NapTAN files we process will include a list of NaPTAN points and we need to ensure that we have a consistent way of listing a point that is not found in NaPTAN.
  *PJS:  Now able to check suf_18-DRT6-1-y08.xml and NaPTAN 390040482 is still listed as a &lt;StopPointRef&gt; but is not listed in the &lt;StopPoints&gt; even though it is a valid NaPTAN points.  This can be pointed out as an error to the source of the data, but also raises the question about whether in republishing the data the list of &lt;StopPoints&gt; should be refreshed against the latest NaPTAN.
  *PJS: suffolk data example is no longer in the data


Issue No: 27   RESOLVED
Where detected:  Testing of 21-02-2012 TNDS data
Observation: Parsing the full dataset does not reveal any schedule information for Greater London
Hypothesis:  Data for the London area is missing from the set.
Raised by:  Carl Partridge
Assigned to:  Peter Stoner
Peter Stoner comments: The London data is now included.


Issue No: 26 RESOLVED Coach Stops
  *Where detected: Testing of January 2012 TNDS data
  *Observation: The TNDS data references stops that are not defined in the NAPTAN stops data and we then have no way of determining the coordinates for those stops. We would suggest it should be an essential requirement that all stops used in TNDS timetable data exist in the base NAPTAN reference database. In particular, the North East region refers to the following stops: 900098292 900069092 900077134 900070172 900077134
  *Closer inspection has found that these stops are present in the CoachReferences.csv file, and that the codes above are the NationalCoachCodes. Each of these stops also has a corresponding ATCOCode and it is our understanding that this is the code that should be used in the TXC timetable data (instead of the NationalCoachCode). 
  *Hypothesis: That regions should use the NaPTAN references to stops not the NationalCoachCodes.
  *Raised by: Andrew Steele - Jeppesen
  *Assigned to: Peter Stoner
  *Peter comments:  I have asked NE (Simon Day) for their comments.
  *Stuart Woods comments:  NE recollection (admitted hazey) that Coach Exchange Points weren't functioning correctly in the TD environment.
  *Peter comments:  I have asked TD if there are still reasons why the NaPTAN point codes can't be used.
  *Roger Slevin : Coach Exchange Points are not stops - they are a form of "cluster" code and therefore should never appear in timetable data in TNDS. 
  *Peter Stoner: NE have updated their data to use the NaPTAN point codes

Issue No: 25  RESOLVED
Where detected: Testing of January 2012 TNDS data
Observation: The data supplied in the London region is out of date. All services appear to have an end date of 29/11/2010
Data downloaded directly from the TfL site is up to date. 
Hypothesis: The London data in TNDS needs to be updated
Raised by: Andrew Steele
Assigned to: Peter Stoner
Peter comments: London data now included each week.


Issue No: 24 CLOSED
  *Where detected: Testing of January 2012 TNDS data
  *Observation: We have been using Â http://80.168.14.244/transxchange/schemaDoc.htm. Is this the correct place to look for the latest documentation? We have had some problems with this documentation. The page talks about 2.1 and 2.4 interchangeably, and it is not clear which is being described. For example clicking on the 2.1 Schema link on the left page takes you to the same place as the 2.4 Schema link. The guide itself is comprehensive; however, it still contains some confusing information. For example, TXC 2.4 supports â€œDeltaâ€ files, however, there isnâ€™t a single example or description of how a delta is applied onto an existing file.
  *Hypothesis: That clarification is needed of the correct version of the schema to use
  *Raised by: Andrew Steele Jeppesen
  *Assigned to: Peter Stoner
  *Peter comments: We are NOT set up to use any of the delta records yet in TNDS.  


Issue No: 23  CLOSED Timing Backwards
  *Where detected: Testing of February 2011 TNDS data
  *Observation: WrongXmlSchema â€“ The data is not as we expect it to be.  For example, a trip segment in TXC_47-C11_-1-y10.xml has duration â€œ-PT22Mâ€.   
  *Hypothesis: Timing backwards is possible in TXC2
  *Raised by: Andrew Steele - Jeppesen
  *Assigned to: PJS
  *PJS: There will be a test for &quot;timing backwards&quot;.  It is thought to arise from certain timetable editing systems or issues about timing over midnight.
  *PJS: regions can test for timing backwards in ITOquality.  20 in NW at the moment 1 in NE.




Issue No: 22 CLOSED  Unknown data elements
  *Where detected: Testing of February 2011 TNDS data
  *Observation: Found unknown Operators, Stops and Services.
  *Hypothesis: That there is a referential integrity problem.
  *Raised by: Andrew Steele - Jeppesen
  *Assigned to: Project Management
  *PJS: there will be tests for unknown data elements.  The problem can be one of timing with data being supplied by different routes.  There are ongoing discussions of how best to deal with these issues.
  *Peter Stoner comments (May 2012):  Some progress is being made. 
  *Peter Stoner comments: Regions now have various tests to identify missing data elements. 


Issue No: 21 RESOLVED  Multiple link overrides
  *Where detected: Testing of February 2011 TNDS data
  *Observation: MultipleLinkOverrides â€“ This is a data sanity issue.  Trips have multiple definitions for a single link (i.e. the part of the trips between 2 consecutive stops).  Each link has different values, leaving our system not knowing what the correct data is, if either.
  *Hypothesis: That we need a test for multiple link overrides
  *Raised by: Andrew Steele - Jeppesen, and BaseMap
  *Assigned to: Trapeze
  *Peter Stoner comments:  examples given recently are in vehicle journey overrides in regional data supplied by Trapeze.  It seems probably that one of the values is usually zero and should be ignored.
  *Toni Jenkinson of Trapeze comments: The developer can now see that there is a fault with the export... We believe the issue occurs when there is a double-row (for separate arrive/depart times).  Until this is fixed we suggest tht the second time is more likely to be correct.
  *Peter Stoner comments:  BaseMap have implemented a fix which overcomes the problem.  However we still need the fix from Trapeze in case the assumptions that BaseMap are making do not hold in all instances.
  *Colin Thompson provides counts of the problem (June 2012): NE- 2/1117, NW - 2636/7822, S - 170/20745, W - 1761/5275, WM - 926/6493, Y - 316/16934
  *Trapeze have indicated (November 2012) that this has been resolved.


Issue No: 20  CLOSED
Where detected: Testing of February 2011 TNDS data
Observation:BadXml â€“ Input is malformed XML.  Looks like your export tool crashed, and output an error message half way through the XML file.
Hypothesis: Looks like your export tool crashed, and output an error message half way through the XML file.
Raised by: Andrew Steele - Jeppesen
Assigned to: PJS
PJS: We need to pick this up if it occurs again.  The exports from BaseMap will be a different process.


Issue No: 19  CLOSED
Where detected: Testing of Feb 2011 TNDS dataset
Observation:The TransXChange schema supports polyline data via the Track attribute of a Route.  This is present in 30% of the input files (i.e. there is at least some mapping data in 30% of input file).
For all routes that do not include Track data, the consumer must create the polyline using the location of stops along the route. This produces a lower quality polyline.
Hypothesis:
Raised by: Andrew Steele - Jeppesen
Assigned to:  Peter Stoner
Peter Stoner comments:  The TNDS exports do not now include the Tracking information.


=====Issue No: 18 L Some datasets are using VehicleType and not Service Mode=====
  *Where detected: Testing of Feb 2011 TNDS dataset
  *Observation:  It appears that the data in the London region does not utilise the ServiceInfoGroup / Mode attributed (as described in section 6.6.3 of the TransXChangeSchemaGuide-2.1-v46.pdf) to describe the mode of service. Instead, the mode is specified in the VehicleType element. This is not ideal as the VehicleType does not require that the vehicle fall into pre-defined transport modes. This makes the processing of the data more difficult as the consumer has to maintain a mapping between the VehicleType and the ServiceInfoGroup / Mode to ensure each service is tagged with the correct mode. 
  *Additionally, the TransXChange Schema Guide indicates that if the Mode is not present for a Service that the mode should default to â€œBusâ€. In the case of London Underground services, this would mean that all London Underground services should be identified as mode â€œBusâ€.
  *Hypothesis: The assumption that No Mode = Bus does not apply to London data
  *Raised by: Andrew Steele - Jeppersen
  *Assigned to: Peter
  *Andrew adds 12/1/2012: Further investigation of the latest data set has found that the number of regions that are not using the Mode tag has increased (eg., East Anglia, East Midlands and North East no longer use this). 
This is a point which needs urgent clarification. As the data stands it is incredibly difficult to tell what transport mode is used for a service. In London we are attempting to derive the type from the &lt;VehicleTypeCode&gt; identifier, however, this is not always consistent and there is no definitive reference data defining what mode (ie., Bus, Tube, Ferry, etc) a vehicle code maps to. 
We have also observed that other regions such as East Anglia use the VehicleTypeCode as well, but with different values. 
In short, there appears to be no consistent way of deriving the transport mode of a service from the TNDS data. Without this, the usefulness of the TNDS is severely limited, especially for users who are attempting to process it as an amalgamated set. 
Our key points on this are:
Is the ServiceInfoGroup/Mode still supported?
If this element is not present, can we default to a mode of Bus (as is defined in the TXC schema)
If instead the VehicleTypeCode should be used, can we obtain a definitive list of Codes that should be used across all regions? 
If the answer to each of above is â€œNoâ€ then it will be incredibly difficult to process the TNDS consistently. On the other hand, if the TNDS is intended to be a consistent set of data that can be processed easily, agreement needs to be made on how the transport modes for services are defined.
  *Peter Stoner comments: there may still be differences in the way different sources refer to mode. (May 2013)
  *Stuart Reynolds comments: random samples of all our data sets (EA2 and SE2 included) show Mode being correctly populated. (June 2013)
  *Peter comments: London Underground files seem still not to have Mode tags in them.  Bus, ferry and Metro modes detected in NE data. (August 2013)

Issue No: 17 RESOLVED TfL frequency methodology
  *Where detected: background information
  *Observation: Journey planning in London does not use the conventional approach adopted everywhere else in UK - in that bus services do not run to a timetable; they are controlled by frequency, and there is a special frequency journey planning method which TfL requires traveline to use.  Unclear what they expect third parties to do with the data they publish in the LDS - as they have not published the frequency methodology for journey planning (as far as I am aware)
  *Hypothesis:  Issue will be that journey plans will look quite different on journey planners which use the conventional journey planning method - and could be significantly slower
  *Raised by: Roger Slevin
  *Assigned to: Peter Stoner
  *Peter Stoner comments: it will be good to find some examples of this.
  *Roger Slevin - it appears that TfL is now accepting that journey planning using the raw data made available by them will be done using conventional journey planning formulae rather than any special "frequency based algorithm"


=====Issue No: 16 L SE EA EM Missing Short term service variations=====
  *Where detected: NDS
  *Observation: Need to be aware that any data for London taken from the London Data Store does not include short/medium term service variations related to engineering works or similar .... which makes the data very unsatisfactory for journey planning on a day to day basis as at any one time there will be a significant number of special timetables in use which are not in the LDS data.
  *Hypothesis: TXC2 exports from MDV do not include temporary timetables.
  *Raised by: Roger Slevin
  *Assigned to: Peter Stoner
  *Peter Stoner comments:  It will be good to find some examples of the problem.
  *Peter Stoner comments: We understand that the temporary timetable needs to be included in the export and a not operating period set for the journeys in the main timetable for the period of the temporary timetable.
  *Peter comments: This is believed to be included in the ongoing discussions Stuart is having with MDV (May 2013)
  *Peter comments: see also issue 64
  *Stuart comments (23 August): MDV have agreed in principle how this is to be handled and a spec will be put together in early September.

Issue No: 15 CLOSED
Where detected: JourneyPlan UKjourneyplanner
Observation: Service 60 in Buckinghamshire, Sunday schedule showing on Monday to Saturday as well
Hypothesis: Could be a Bank Holiday service not coded, or interpretted correctly.
Raised by: Peter Stoner
Assigned to: Peter Stoner
Response: ITOqualityUK show Aylesbury to Buckingham service 60, the  Monday to Saturday timetable is contained in  uk_SE_01060.xml whereas the Sunday service, and the extra (holiday?) journeys are on  uk_SE_01060A.xml  

Eduard replies - Thanks for the additional information!  We found the cause and it has been
fixed.  A next NDS processing run will be correct.


=====Issue No: 14 EM Missing Serviced Organisations info=====
  *Where detected: ITO Quality
  *Observation: A number of journeys duplicates are being shown in ITO Quality that are journeys that run in school-term/school holidays. This was reported by Andrew from Lincolnshire. This information is provided in the CIF file - however once it is converted into TXC there seems to be no corresponding DaysOfOperation stuff - therefore the information on running on school-term/holidays is lost. I have emailed Stuart Reynolds from the South East for his opinion but so far have had nothing back
  *Hypothesis: This affects the stats of ITO Quality but will have more serious issues on journey planners etc.
  *Raised by: Shane Reynolds (first reported by Andrew Addo-Smith)
  *Assigned to:  Peter Stoner
  *Response:  This seems to relate to MDV data and Stuart Reynolds suggests this may be resolved now.  Need to retest.
  *Shane - After retesting with help from Andrew this issues seems to remain.
  *Peter Stoner comments:  The TNDS exports may be relying in some areas on the Serviced Organisations file which is neither up to date nor fully in use yet across the regions.  Some regions explicitly date the journeys so the serviced organisation just becomes a helpful label eg &quot;Sch&quot; meaning schooldays.  but if elsewhere the journey is only has a long duration but quotes a serviced organisation, then the dates of operation of that organisation should kick in.
  *Peter comments: Not sure we can progress this issue easily until we have issue 128 cleared.   I doubt if the schema checks will allow a serviced organisation to be referenced unless it is declared in the file with some dates attached to it.  The dates may be historic but it is up to the downstream user to source the current dates for the particular Serviced Organisation.  In due course we hope to update to the current dates in TNDS. 


Issue No: 13 CLOSED
Where detected: ITOquality
Observation: Blackpool trams departure times are not shown at PLT stops but are coded at PLT in ITOqualityUK
Hypothesis: Something amiss in the NW ATCO cif export
Raised by: Peter Stoner
Assigned to: Darren Guest
Response:  We have waited until 21 March 2011 when Blackpool tram data should be restored in the Journey Planner for operation from Easter onwards.  The problem seems still to be there so referred back to Daren for comment.
PJS: Blackpool trams now showing correctly in NextBuses as PLT stops so we think that this issue is now resolved.


Issue No: 12  RESOLVED
Where detected: (anticipated) in ITOqualityUk
Observation: Sheffield Supertram is showing as Bus.
Hypothesis:the Trapeze export has only been designed to support bus registration and the TXC mode default is Bus.  The TXC export needs to add a mode record for the services to appear as Trams.  See Closed Issue 2
Raised by: Peter Stoner
Assigned to: John Prince
Response: Something not quite right here.  SuperTram is not appearing in ITOqualityUK because all South Yorkshire data is not available in TXC2.  Therefore this is an anticipated problem.  When TXC2 data becomes the non bus mode will need to be identified. In addition there is difficultly in transport authorities detecting tram issues because the stops trams user are 9400 and therefore errors appear as DfT.
PJS: Trams appearing as Tram mode.


Issue No: 11 CLOSED
Where detected: ITOqualityUK in early November 2010
Observation: Multiple stops greater in Scotland in ITOqualityUK than ITOquality
Hypothesis:
Raised by: Peter Stoner
Assigned to: Stuart McNeill
Response:
PJS: ITOqualityUK is no longer available to the comparison can't be made now.  In ITOquality Scotland has only 2 multiple stop warnings and these are for looping town services.



Issue No: 10 CLOSED
Where detected:  ITOqualityUK in early November 2010
Observation: Scotland have a lot of fast timing sections in ITOqualityUK than in ITOquality
Hypothesis:
Raised by: Peter Stoner
Assigned to: Stuart McNeill
Response: ITOqualityUK is no longer available so the comparison can't be made any more.  In ITOquality fast timings in Scotland are among the lowest in UK, only two other regions have lower, - and half of them are in Shetland!



Issue No: 9 CLOSED
Where detected: ITOqualityUK in early November 2010
Observation: WM have high numbers of Stops missing from NaPTAN in ITOqualityUK compared to ITOquality
Hypothesis: 
Raised by: Peter Stoner
Assigned to: Keith Sabin
Response: 
PJS: ITOqualityUK is no longer avaiable so the disparity is not currently visible. December 2012 - ITOquality has 28 stops not in NaPTAN.  2 other regions have more.



Issue No: 8  RESOLVED
Where detected: ITO Systems but will be everywhere
Observation: Journey Notes are not being output in the TXC files
Hypothesis: Journey notes do not seem to be output in the XML files - I noticed this when I received TXC files from the South East but I assume it will affect the NDS as well. Stuart R. from the South east explained that this was a bug in the MDV exporter and that they were planning to address it.
Raised by: Shane Reynolds
Assigned to: Stuart Reynolds
Response: Stuart Reynolds reports that the outputs from MDV will now include notes.



Issue No: 7     CLOSED
Observation: that computer processing is slow even on high spec computers 
Raised by: Peter Miller



Issue No: 6 RESOLVED
Where detected: ITOqualityUK
Observation: Simon Day
Hypothesis: That too many records/journeys/services are being rejected, not just the ones affected by the error reports. System needs to be more robust rather than all or nothing.
Raised by: Simon Day .



Issue No: 5  RESOLVED
Observation: Failure to import NETIS TXC
Raised by: Andy Hole



Issue No: 4  CLOSED
Where detected: In NDS
Observation: West Yorkshire and York data not available.
PJS: Yorkshire data now available in TXC2


Issue No: 3  CLOSED
Where detected: In NDS
Observation: South Yorkshire data not available.
PJS: Yorkshire data now available in TXC2.


Issue No: 2 CLOSED
Observation: Non mode buses appearing as buses throughout UK
Response:

Kieran - In V2.1 (Section 6.6.2) one of the attributes of the Service element is ServiceInfoGroup.  Within this group there is the element &quot;Mode&quot; in which the various modes are defined via a set of allowed values.  (This is the same in V2.4)  The default value is bus.  It may be that the data providers are not populating this field correctly for all modes.

Peter - this does seem to be the explanation. Opening isuses with the affected regions.



Issue No: 1   RESOLVED
Observation: TXC routes provided by NETIS has not appeared
Raised by: Simon Day"
tndsissues.txt · Last modified: 2024/01/31 09:48 (external edit)