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
I have access to the UDOT Atspm API and I've noticed that for methods that return detector configuration information, Detection Type IDs fields (and Detection Types) are always null in the response. Is this intentional?
Specifically, when querying a signal config (api/data/SignalConfig) or even an explicit detector config (api/data/DetectorConfig), I see useful information about the detector (e.g. channel, distance from stop bar) but DetectionTypeIDs are always null. Without this information, it's difficult to know what kind of detector I'm dealing with (stop bar vs lane-by-lane count).
There are some comments in the SignalRepository.cs code that makes me wonder if detector support is still in-progress?
Either way, if there is some other way of getting detection type information using the existing APIs, I'd be interested to know. Right now, I'm manually inspecting it from https://udottraffic.utah.gov/ATSPM/Signals/SignalDetail
The text was updated successfully, but these errors were encountered:
I have access to the UDOT Atspm API and I've noticed that for methods that return detector configuration information, Detection Type IDs fields (and Detection Types) are always null in the response. Is this intentional?
Specifically, when querying a signal config (api/data/SignalConfig) or even an explicit detector config (api/data/DetectorConfig), I see useful information about the detector (e.g. channel, distance from stop bar) but DetectionTypeIDs are always null. Without this information, it's difficult to know what kind of detector I'm dealing with (stop bar vs lane-by-lane count).
There are some comments in the SignalRepository.cs code that makes me wonder if detector support is still in-progress?
https://github.com/udotdevelopment/ATSPM/blob/master/AtspmApi/Repositories/SignalsRepository.cs#L390
Either way, if there is some other way of getting detection type information using the existing APIs, I'd be interested to know. Right now, I'm manually inspecting it from https://udottraffic.utah.gov/ATSPM/Signals/SignalDetail
The text was updated successfully, but these errors were encountered: