In my experience with SimSig Importer so far, I find I don't get to use the "simple" one-line timing points very often, where the TIPLOC is in column A and the description is in column B. For the majority of timing points I need to state Arr, Line, Plat, and/or Path explicitly and thus also Dep, and so I have the TIPLOC in column A, the activity code in column B, and the descriptive name in column C. So where I've put "ArrDep": true or "Line": true in the sim's .json file and I generate a spreadsheet, it doesn't include the whatever I've put for "Name":, and I have to manually put it into the spreadsheet.
It would be a non-breaking change to have the importer generate these spreadsheets with the names in column C and any Line/Plat/Path/Arr/Dep codes in column B:
But would it be agreeable in principle to make a breaking change, and move the activity codes to column C in both the generator and importer?
The benefit of this is that the spreadsheet would more closely match the arrangement of actual working timetables:
In my experience with SimSig Importer so far, I find I don't get to use the "simple" one-line timing points very often, where the TIPLOC is in column A and the description is in column B. For the majority of timing points I need to state
Arr,Line,Plat, and/orPathexplicitly and thus alsoDep, and so I have the TIPLOC in column A, the activity code in column B, and the descriptive name in column C. So where I've put"ArrDep": trueor"Line": truein the sim's .json file and I generate a spreadsheet, it doesn't include the whatever I've put for"Name":, and I have to manually put it into the spreadsheet.It would be a non-breaking change to have the importer generate these spreadsheets with the names in column C and any Line/Plat/Path/Arr/Dep codes in column B:
But would it be agreeable in principle to make a breaking change, and move the activity codes to column C in both the generator and importer?
The benefit of this is that the spreadsheet would more closely match the arrangement of actual working timetables: