Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detection Type IDs in Detector API responses? #75

Open
bdferris-v2 opened this issue Feb 18, 2020 · 0 comments
Open

Detection Type IDs in Detector API responses? #75

bdferris-v2 opened this issue Feb 18, 2020 · 0 comments

Comments

@bdferris-v2
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant