You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From TrackAtlas point of view, there is only one output going to DMI containing speed profile information.
If there are differences in their interpretation, the source cannot be in TrackAtlas (the only data relevant to speed profiles emitted by TrackAtlas is the MRSP profile)
I assume that the flag and the planning area are both working on the MRSP info? Or is one of them using info from SDM?
We were a little bit surprise about the difference of the position on the DMI and the Loc_Abs position in the data from track atlas to DMI.
But @ShuangjiaoCao will check at monday again the files to the DMI t o be sure there is no issue in the controller. Can you please check your data as well?
We were a little bit surprise about the difference of the position on the DMI and the Loc_Abs position in the data from track atlas to DMI.
But @ShuangjiaoCaohttps://github.com/ShuangjiaoCao will check at monday again the files to the DMI t o be sure there is no issue in the controller. Can you please check your data as well?
Thank you very much
—
Reply to this email directly or view it on GitHub #987 (comment).
Speed reduction flag is not consistent with planning area speed reduction.
@JakobGartner @ShuangjiaoCao
The text was updated successfully, but these errors were encountered: