Page 1 of 1
| Report invalid locations in XML 16/04/2018 at 07:56 #107549 | |
9pN1SEAp
1181 posts 
|
Hi, In creating XML's I've sometimes put an invalid TIPLOC in the Trips section. The loader does the right thing and ignores these. However, it would be nice if somewhere in the F4 tools, you could get a report of the Trip and EntryPoint (etc.) locations that are unrecognised for timetable analysis. Yes, I could type in the timetable by hand to avoid mistakes but generating the XML directly is easier :) Thanks Jamie Jamie S (JAMS) Log in to reply |
| Report invalid locations in XML 16/04/2018 at 18:22 #107571 | |
GeoffM
6376 posts |
No, because if I did an import of category ZZ in the Network Rail Open Data timetables I'd end up with thousands of locations from Penzance to Thurso and everywhere in between. The point of XML is to write one XML that covers multiple simulations. As you say, it correctly filters out locations not in the area which, for the ZZ trains, would be something like 95% of the data. SimSig Boss Log in to reply The following user said thank you: Meld |
| Report invalid locations in XML 16/04/2018 at 19:50 #107584 | |
|
9pN1SEAp
1181 posts
|
Fair point! Does the XML permit multiple entry points and then select only the one that it recognises, if you were using the same TT for chaining? Jamie S (JAMS) Log in to reply |
| Report invalid locations in XML 16/04/2018 at 21:51 #107585 | |
pedroathome
916 posts |
9pN1SEAp in post 107584 said:Fair point!Are you editing a timetable file directly, i.e. the XML within the .WTT file, or an XML file which you go Timetable, Import from XML? James Log in to reply |
| Report invalid locations in XML 16/04/2018 at 22:50 #107586 | |
|
9pN1SEAp
1181 posts
|
I'm using my own XSLT tools to generate them, then adding manual tweaks for routes that don't appear in WTT.
Jamie S (JAMS) Log in to reply |
| Report invalid locations in XML 16/04/2018 at 22:52 #107587 | |
|
GeoffM
6376 posts |
9pN1SEAp in post 107584 said:Fair point!James' point is valid - I assumed you meant the import XML, not the XML that the sim saves in. Now I'm not so sure. In terms of the import, it firstly finds trains running on the appropriate date (if selected). It then extracts schedules which contain at least 2 consecutive locations known to that simulation. Then, amongst other things, a set of rules determine how entry points are selected. For example, a yard/depot might have one location (TIPLOC), but exits at both ends so we need to check which direction it's going. Others might match a pair of locations but never enter the sim (usually on the approach fringes), so they need to be removed from the import. We also need to look back sometimes, when there are multiple lines (like fast/slow) as the line code is not entered for every location. SimSig Boss Log in to reply |
| Report invalid locations in XML 17/04/2018 at 10:42 #107590 | |
|
9pN1SEAp
1181 posts
|
Thanks for that answer, Geoff. Gives a good insight into the magic of the importer.
Jamie S (JAMS) Log in to reply |