TSDE

Version	Type	Description	ID
21.4.1.0	CORR	The issue of TSDE failing when the Alert Trace Listener was selected (on the Listeners tab of the Trace Options dialog) has been fixed.	FX-11497
21.8.0.0	ENH	A new column labeled Revenue has been added to the trips file generated using TSDE Export.	FX-11974
21.11.0.0	ENH	The following changes have been made to fix issues in TSDE Export and TSDE Import: The context property, Exchange/TSDE/Export/Retain Legacy Pattern Point File Logic has been added. If selected, TSDE Export applies the legacy behavior, which is to increase the sequence in the pattern point file with every stop/node. If not selected, the stop/node pairs have the same sequence. TSDE Export now only populates the Stopnum on the Trip Times and Pattern Points files if the Line Points file is selected. (If the transit site does not use Line Point files, do not export the Line Point file.) The option, FX/TSDEExport/Log attribute errors has been added to the Trace Options in the Service Shell. If not selected, the warnings in the import log regarding attribute fields that cannot be found in the import database are suppressed. TSDE Import was modified to perform the following: Accept having the stops before nodes or nodes before stops in the pattern point files Use a single RunId in the MasterRun table for all TSDE Records with the same Service/Division/Run Number. Avoid Inserting the same relief opportunity more than once into the Trip Times table after a run with different exceptions has been cut at the same point to prevent errors. The error message, "Can't find matching pattern from source signup for pattern" now includes the pattern ID with the pattern name.	FX-12341
21.11.0.0	ENH	When using TSDE Export, users can now choose whether to export user-defined supplementary data.	FX-12317
21.12.0.0	ENH	After importing line stops and copying stops from another sign-up period, TSDE matches the patterns of the source sign-up period and now also merges the matching stops in a manner similar to how stop patterns are merged if you do not import line points.	FX-12420
21.14.0.0	ENH	Unused comments are no longer included when generating TSDE Export.	FX-12056
21.16.0.0	CORR	The issue of users getting an etime value of "-1" in the TSDE Export run file.	FX-12736
21.16.0.0	CORR	When running TSDE Export, files in XML format are now exported with UTF-8 encoding. Other formats use ANSI encoding.	FX-12690
21.18.0.0	CORR	The issue of the progress bar still appearing at the bottom of the TSDE screen after the TSDE Export or TSDE Import had been successfully completed has been fixed.	FX-12891
21.31.0.0	CORR	TSDE Export now reads the TP6 property for line-dependent deadheads.	FX-13798
21.39.0.0	CORR	An issue where the PI/PO/Interlined Deadheads were not appearing in the Blocking screen in the newly created imported sign-up period after completing a TSDE Import Run and Roster was fixed.	FX-14465

21.4.1.0

CORR

The issue of TSDE failing when the Alert Trace Listener was selected (on the Listeners tab of the Trace Options dialog) has been fixed.

FX-11497

21.8.0.0

ENH

A new column labeled Revenue has been added to the trips file generated using TSDE Export.

FX-11974

21.11.0.0

ENH

The following changes have been made to fix issues in TSDE Export and TSDE Import:

The context property, Exchange/TSDE/Export/Retain Legacy Pattern Point File Logic has been added. If selected, TSDE Export applies the legacy behavior, which is to increase the sequence in the pattern point file with every stop/node. If not selected, the stop/node pairs have the same sequence.
TSDE Export now only populates the Stopnum on the Trip Times and Pattern Points files if the Line Points file is selected. (If the transit site does not use Line Point files, do not export the Line Point file.)
The option, FX/TSDEExport/Log attribute errors has been added to the Trace Options in the Service Shell. If not selected, the warnings in the import log regarding attribute fields that cannot be found in the import database are suppressed.
TSDE Import was modified to perform the following:
1. Accept having the stops before nodes or nodes before stops in the pattern point files
2. Use a single RunId in the MasterRun table for all TSDE Records with the same Service/Division/Run Number.
3. Avoid Inserting the same relief opportunity more than once into the Trip Times table after a run with different exceptions has been cut at the same point to prevent errors.
The error message, "Can't find matching pattern from source signup for pattern" now includes the pattern ID with the pattern name.

FX-12341

21.11.0.0

ENH

When using TSDE Export, users can now choose whether to export user-defined supplementary data.

FX-12317

21.12.0.0

ENH

After importing line stops and copying stops from another sign-up period, TSDE matches the patterns of the source sign-up period and now also merges the matching stops in a manner similar to how stop patterns are merged if you do not import line points.

FX-12420

21.14.0.0

ENH

Unused comments are no longer included when generating TSDE Export.

FX-12056

21.16.0.0

CORR

The issue of users getting an etime value of "-1" in the TSDE Export run file.

FX-12736

21.16.0.0

CORR

When running TSDE Export, files in XML format are now exported with UTF-8 encoding. Other formats use ANSI encoding.

FX-12690

21.18.0.0

CORR

The issue of the progress bar still appearing at the bottom of the TSDE screen after the TSDE Export or TSDE Import had been successfully completed has been fixed.

FX-12891

21.31.0.0

CORR

TSDE Export now reads the TP6 property for line-dependent deadheads.

FX-13798

21.39.0.0

CORR

An issue where the PI/PO/Interlined Deadheads were not appearing in the Blocking screen in the newly created imported sign-up period after completing a TSDE Import Run and Roster was fixed.

FX-14465