2010-12-17T09:30:47.0Z SYS001 2010-12-17T09:30:47.0Z SYS002 2010-11-01T00:00:00Z REQUEST P1M Example of simple timetable frame with two journeys and service calendar, with detailed timings 1. OVERVIEW ============ The route has just three stops A - B - C with three intremediate timing points The route has just three stops A - t1 - t2 - B - t3 - C There are just two SERVICE JOURNEYs in a single DIRECTION hde:sj_24o_01 at 14:20 outbound hde:sj_24o_02 at 15:20 outbound And the timetable is thus sj_24o_01 sj_24o_02 A d 14:00 15:00 B a 14:30 15:30 B d 14:32 15:32 C a 15:10 16:10 In this example we include both detailed TIMING and JOURNEY PATTERN data as well as the SERVICE JOURNEY with CALLs. The CALLs are in effect derived from the other data and could be omitted Journey sj_24o_01 runs every day that is not a holiday and on Christmas day, New years day, Goodfriday and Easter monday Journey sj_24o_01 runs every monday to fridays that are not a holiday ================================== 2. DETAILS There are just two SERVICE JOURNEYs in the timetable for LINE 24 (i) SERVICE JOURNEY hde:sj_24o_01 Departs 14:00 on DAY TYPEs hde:DT_02-Everyday-NotHoliday hde:DT_ChristmasEve hde:DT_ChristmasDay hde:DT_ChristmasDayDisplacement hde:DT_NewYearsEve hde:DT_NewYearsDay hde:DT_2ndJanuary hde:DT_NewYearsDayDisplacement hde:DT_GoodFriday hde:DT_EasterSunday hde:DT_EasterMonday (ii) SERVICE JOURNEY hde:sj_24o_02 Departs 15:00 on DAY TYPEs hde:DT_01-MF-NotHoliday Connects with LINE 4 at stop B SCHEDULED STOP POINTs A) mybus:ssp_001 Alpha B) mybus:ssp_002 Bravo C) mybus:ssp_077 Charley SERVICE LINKS SERVICE LINK : A - B mybus:SSP_001_to_SSP_002 SERVICE LINK : B - C mybus:SSP_002_to_SSP_077 There is a single SERVICE PATTERN has three STOP POINTs IN JOURNEY PATTERN referencing the three SCHEDULED STOP POINTs which are connected by two SERVICE LINKs . SERVICE PATTERN: ServicePattern:svp_24o follows SERVICE JOURNEY PATTERN: ServiceJourneyPattern:sjp_24o 1 A STOP POINT IN JOURNEY PATTERN hde:spip_24o_01 SCHEDULED STOP POINT: A mybus:SSP_001 SERVICE LINK : A - B mybus:SSP_001_to_SSP_002 2 B STOP POINT IN JOURNEY PATTERN hde:spip_24o_02 SCHEDULED STOP POINT: B mybus:SSP_002 SERVICE LINK : B - C mybus:SSP_002_to_SSP_077 3 C STOP POINT IN JOURNEY PATTERN hde:spip_24o_03 SCHEDULED STOP POINT: C mybus:SSP_077 The TIMING PATTERN has three intermediate TIMING POINTs which are not SCHEDULED STOP POINTs, as well as the three SCHEDULED STOP POINTs A - a_t1 - a_t2 - B - b_t3 - C timing points TIMING POINT: mybus:SSP_001_t1 TIMING POINT: mybus:SSP_001_t2 TIMING POINT: mybus:SSP_002_t3 timing links TIMING LINK : A - a_t1 mybus:SSP_001_to_SSP_001_t1 TIMING LINK : a_t1 - a_t2 mybus:SSP_001_t1_to_SSP_001_t2 TIMING LINK : a_t2 - B mybus:SSP_001_t2_to_SSP_002 TIMING LINK : A - b_t3 mybus:SSP_002_to_SSP_002_t3 TIMING LINK : b_t3 - C mybus:SSP_002_t3_to_SSP_077 There is a single TIME DEMAND TYPE and one set of RUN TIMES 01 02 A d 14:00 15:00 t1 +10m RUN TIME t2 +10m RUN TIME B a 14:30 15:30 +10m RUN TIME B d 14:32 ... 15:32 +2m WAIT TIME t1 +180m RUN TIME . C d 15:10 16:10 .+20m RUN TIME +70m JOURNEY PATTERN RUN TIME JOURNEY RUN TIME mybus:tdtr_TD01_SSP_001_to_SSP_077 70M The TIMING PATTERN has thus six POINTs IN TIMING PATTERN, referencing the TIMING POINTs connected by five TIMING LINKs TIMING PATTERN: TimingPattern:tp_24o 1.TIMING POINT IN JOURNEY PATTERN : hde:tpip_24o_01 TIMING POINT: A mybus:SSP_001 TIMING LINK : A - a_t1 mybus:SSP_001_to_SSP_001_t1 JOURNEY RUN TIME mybus:tdtr_TD01_SSP_001_to_SSP_001_t1 4M Depart: 14:20, 15 20 2. TIMING POINT IN JOURNEY PATTERN : hde:tpip_24o_02 TIMING POINT: mybus:SSP_001_t1 TIMING LINK : a_t1 - a_t2 mybus:SSP_001_t1_to_SSP_001_t2 JOURNEY RUN TIME mybus:tdtr_TD01_SSP_001_t1_to_SSP_001_t2 10M 3. TIMING POINT IN JOURNEY PATTERN : hde:tpip_24o_03 TIMING POINT: mybus:SSP_001_t2 TIMING LINK : a_t2 - B mybus:SSP_001_t2_to_SSP_002 JOURNEY RUN TIME mybus:tdtr_TD01_SSP_001_t1_to_SSP_002 10M 4. TIMING POINT IN JOURNEY PATTERN : hde:tpip_24o_04 TIMING POINT: B mybus:SSP_002 JOURNEY WAIT TIME mybus:tdtr_TD01_SSP_002 2M TIMING LINK : A - b_t3 mybus:SSP_002_to_SSP_002_t3 JOURNEY RUN TIME mybus:tdtr_TD01_SSP_002_to_SSP_002_t3 18M Arrive14:30, 15 30 Depart14:32, 15 32 5. TIMING POINT IN JOURNEY PATTERN : hde:tpip_24o_05 TIMING POINT: mybus:SSP_002_t3 TIMING LINK : b_t3 - C mybus:SSP_002_t3_to_SSP_077 JOURNEY RUN TIME mybus:tdtr_TD01_SSP_002_t3_to_SSP_077 20M 6. TIMING POINT IN JOURNEY PATTERN : hde:tpip_24o_06 TIMING POINT: C mybus:SSP_077 Arrive: 15:10, 16 10 There is alink for the whole route as well TIMING LINK : A - C mybus:SSP_001_to_SSP_077 The SERVICE JOURNEY PATTERN has six POINT IN JOURNEY PATTERN referencing the three SCHEDULED STOP POINTs and three additional timing points which are connected by two SERVICE LINKs .and five TIMING LINKs SERVICE JOURNEY PATTERN: ServiceJourneyPattern:sjp_24o 1 POINT IN JOURNEY PATTERN hde:tpip_24o_01 SCHEDULED STOP POINT: A mybus:SSP_001 SERVICE LINK : A - B mybus:SSP_001_to_SSP_002 TIMING LINK : A - a_t1 mybus:SSP_001_to_SSP_001_t1 2. POINT IN JOURNEY PATTERN: hde:tpip_24o_02 TIMING POINT: mybus:SSP_001_t1 TIMING LINK : a_t1 - a_t2 mybus:SSP_001_t1_to_SSP_001_t2 3. POINT IN JOURNEY PATTERN: hde:tpip_24o_03 TIMING POINT: mybus:SSP_001_t2 TIMING LINK : a_t2 - B mybus:SSP_001_t2_to_SSP_002 4 POINT IN JOURNEY PATTERN: hde:tpip_24o_04 SCHEDULED STOP POINT: B mybus:SSP_002 SERVICE LINK : B - C mybus:SSP_002_to_SSP_077 TIMING LINK : A - b_t3 mybus:SSP_002_to_SSP_002_t3 JOURNEY RUN TIME 18M 5. POINT IN JOURNEY PATTERN: hde:tpip_24o_05 TIMING POINT: mybus:SSP_002_t3 TIMING LINK : b_t3 - C mybus:SSP_002_t3_to_SSP_077 JOURNEY RUN TIME 20M 6 POINT IN JOURNEY PATTERN: hde:tpip_24o_06 SCHEDULED STOP POINT: C mybus:SSP_077 The JOURNEY PATTERN has six POINT IN JOURNEY PATTERN referencing the three SCHEDULED STOP POINTs and three additional timing points which are connected by two SERVICE LINKs .and five TIMING LINKs SERVICE JOURNEY PATTERN: ServiceJourneyPattern:sjp_24o 1 POINT IN JOURNEY PATTERN hde:tpip_24o_01 SCHEDULED STOP POINT: A mybus:SSP_001 SERVICE LINK : A - B mybus:SSP_001_to_SSP_002 TIMING LINK : A - a_t1 mybus:SSP_001_to_SSP_001_t1 2. POINT IN JOURNEY PATTERN: hde:tpip_24o_02 TIMING POINT: mybus:SSP_001_t1 TIMING LINK : a_t1 - a_t2 mybus:SSP_001_t1_to_SSP_001_t2 3. POINT IN JOURNEY PATTERN: hde:tpip_24o_03 TIMING POINT: mybus:SSP_001_t2 TIMING LINK : a_t2 - B mybus:SSP_001_t2_to_SSP_002 4 POINT IN JOURNEY PATTERN: hde:tpip_24o_04 SCHEDULED STOP POINT: B mybus:SSP_002 SERVICE LINK : B - C mybus:SSP_002_to_SSP_077 TIMING LINK : A - b_t3 mybus:SSP_002_to_SSP_002_t3 JOURNEY RUN TIME 18M 5. POINT IN JOURNEY PATTERN: hde:tpip_24o_05 TIMING POINT: mybus:SSP_002_t3 TIMING LINK : b_t3 - C mybus:SSP_002_t3_to_SSP_077 JOURNEY RUN TIME 20M 6 POINT IN JOURNEY PATTERN: hde:tpip_24o_06 SCHEDULED STOP POINT: C mybus:SSP_077 There are Three NOTICes defining Stop Announcements These are associated with a POINT IN JOURNEY PATTERN using a NOTICE ASSIGNMENT mybus:Na_Nxa_SSP_001 = = > mybus:Nxa_SSP_001 Next stop is mybus:Na_Nxa_SSP_002 = = > mybus:Nxa_SSP_002 mybus:Na_Nxa_SSP_077 = = > mybus:Nxa_SSP_077 A COMPOSITE FRAME is used to group the component FRAMEs - It has a VALIDITY CONDITION that specifies it is valid from Sept to Matrch A SERVICE FRAME is used to contain the STOP POINT elements LINE, etc A TIMETABLE FRAME is used to contain the SERVICE JOURNEY elements a SERVICE CALENDAR FRAMEb A SERVICE CALENDAR FRAME is used to contain the DAY TYPEs etc The Calendar is shown coded as Compact : OPERATING DAYs are assumed for each calendar date within the period of the calendar mybus http://www.mybuses.eu/stuff My buses Stops for Winter timetable for route 24 hde http://www.halt.de/ Stop data data Westbound Eastbound Line 24 Alpha to Charley (Details not GIVEN) outbound Line 24 Alpha to Charley Line 24 bus 24 Red Bravo Bravo Bravo Charley Charley G Charley Alpha & Castle 53.0000 0.1000 timingPoint Alpha ALPH onstreetBus bus Bravo Street 53.2000 0.2000 timingPoint Bravo BRAV onstreetBus bus Charley Crescent 53.3000 0.3000 timingPoint Charley CHAS onstreetBus bus Alpha & Castle to Bravo Bravo to Charley Alpha to Charley outbound Redundant Information! false Next Stop Announcement for SSP_001 true Redundant Information! Next Stop Announcement for SSP_002 true false Next Stop Announcement for SSP_077 true Between Alpha and Bravo Point 1 53.2000 0.2000 timingPoint Between Alpha and Bravo Point 2 53.3000 0.3000 timingPoint Between Bravo and Charley Point 1 53.4000 0.4000 timingPoint Overall timing Alpha to Charley reen After Alpha t1 After Alpha t1 to After Alpha t2 After Alpha t2 to Bravo Bravo to After Bravo t1 After Bravo t1 to Charley Route 24 outbound Alpha to Charley - All POINTs outbound PT70M Next Stop Announcement for SSP_001 true Next Stop Announcement for SSP_002 true Next Stop Announcement for SSP_077 true Normal Day PT10M PT10M PT10M PT18M PT20M Wait at Stop B PT2M bogus group Next Stop Announcement for SSP_002 Welcome This service goes to Charley Crescent. Stopping everywhere textToSpeech Welcome This service goes to Charley Crescent. textToSpeech Willkommen Dieser Dienst fahrt nach Charley Crescent. Next Stop Announcement for SSP_002 Next Stop is Bravo Road. Alight here for Chocolate Museum textToSpeech Next Stop is Bravo Road textToSpeech Nachste Haltstelle Bravo Road. Next Stop Announcement for SSP_077 Next Stop is Charley Road. Service Terminates here textToSpeech Next Stop is Charley Crescent. All alight here. textToSpeech Nachste Haltstelle Charley Crescent. Aussteigen Sept to April 2010-11-01T00:00:00Z 2011-04-30T00:00:00Z Winter timetable for route 23 outbound bus subsidy false 20 contract false 20 14:20:00.0Z outbound Overall run time PT70M 14:00:00.0Z 14:10:00.0Z 14:20:00.0Z 14:30:00.0Z 14:50:00.0Z 15:10:00.0Z false PT2M Arrival at Terminus false 15:20:00.0Z outbound Overall run time PT70M 15:00:00.0Z 15:10:00.0Z 15:20:00.0Z 15:30:00.0Z 15:50:00.0Z 16:10:00.0Z false false PT2M false boardingAssistance conductor wheelchairAssistance standardClass stepFreeAccess suitableForWheelchairs noSmoking nextStopIndicator realTimeConnections stopAnnouncements purchase noBaggageStorage Service Calendar Nov to April 2010 (Compact Coding) 2010-11-01 2010-11-14 Weekdays unless a holiday Monday Tuesday Wednesday Thursday Friday NotHoliday Everyday unless a holiday Everyday NotHoliday Weekends unless a holiday Saturday Sunday NotHoliday Holidays Everyday AnyHoliday Christmas Ev e --12-24 EveOfHoliday Christmas Day --12-25 NationalHoliday Christmas Day Displacement holidday Monday Tuesday Wednesday Thursday Friday HolidayDisplacementDay NewYear's Eve --12-31 EveOfHoliday NewYear's Day --01-01 NationalHoliday 2nd January Holiday (Scotland) --02-01 RegionalHoliday NewYear's Day Displacement holiday Monday Tuesday Wednesday Thursday Friday HolidayDisplacementDay Good Friday Friday NationalHoliday Easter Sunday Sunday NationalHoliday Easter Monday Monday NationalHoliday 2010-11-01 Monday 2010-11-01 02:00:00 PT24H 2011-04-30 Saturday 2011-04-30 02:00:00 PT24H WInter 2011 NotHoliday Winter Monday 2010-11-01 Tuesday 2010-11-02 2010-11-02 Wednesday 2010-11-03 2010-11-03 Thusday 2010-11-04 2010-11-04 MFriday 2010-11-05 2010-11-05 Saturday 2010-11-06 2010-11-06 Sunday 2010-11-07 2010-11-07 Monday 2010-11-08 2010-11-08 Tuesday 2010-11-09 2010-11-09 Wednesday 2010-11-10 2010-11-10 Thusday 2010-11-11 2010-11-11 MFriday 2010-11-12 2010-11-12 Saturday 2010-11-13 2010-11-13 Sunday 2010-11-14 2010-11-14 Sunday 2010-12-24 2010-12-31 Saturday 2010-12-25 Christams Day 2010-12-25 Monday 2010-12-27 (Christjmas Day displacement holiday) 2010-12-27 Friday 2010-12-31 New Years eve 2010-12-31 Saturday 2011-01-01 New Years day 2011-01-01 Satuurday 2011-01-03 New Years day displacement 2011-01-03 Friday 2011-04-22 Good Friday 2011-04-22 Sunday 2011-04-24 Easter Sunday 2011-04-24 Monday 2011-04-25 Easter Monday 2011-04-25 Friday2011-04-29 2011-04-29 Saturday 2011-04-30 acs http://autocarssuperbe.fr Service data Autocars superbe fr +33-1-675-9876 http://autocarssuperbe.fr operator Sigma transport authority authority