Update detection type "Radar" to "Radar - Manufacturer"

[atdservicebot]

What application are you using?

Data Tracker

Describe the problem.

Request to update detection type "Radar" to "Radar - Manufacturer". Manufacturers include: Wavetronix, Iteris, and SmartMicro

Describe the outcome you'd like to see when this feature is implemented.

Ability to delineate radar type

Describe any workarounds you currently have in place or alternative solutions you've considered.

None - local knowledge only

Requested By Allyson R.

Request ID: DTS22-103340

[amenity]

@dianamartin @johnclary - any concerns about changing this?

[dianamartin]

@amenity question is are they requesting a new field or changing adding new choices to the field?

[amenity]

@dianamartin they want to replace "Radar" with

• Radar - Iteris
• Radar - SmartMicro
• Radar - Wavetronix in this list

[dianamartin]

@amenity okay, so change the choice fields.. got it

[dianamartin]

I'm assigning myself to this issue and will do it today if you don't mind

[amenity]

@dianamartin - sure, super, thanks!

[dianamartin]

On signal_detector object (CHILD), field "DETECTOR_TYPE" - Radar exists

1. GRIDSMART
2. LOOP
3. RADAR
4. SENSYS
5. VIDEO
6. FLIR
7. MIOVISION
8. PRE-TIMED
9. NO DETECTORS

On signal object (PARENT), field "DETECTOR_TYPE" - Radar do NOT exist

1. LOOP
2. VIDEO
3. NO DETECTION
4. MIXED
5. GRIDSMART

[johnclary]

@dianamartin did you end up making this change? If you haven't, I believe it may impact some data old data processing scripts and it would be good to hold off. If you have, we will find it out shortly...

[dianamartin]

@johnclary I did not do the change because I wanted to talk to you about it first. I also thought there might've been some automation on this. (Data going from Child to Parent)

[johnclary]

@dianamartin go ahead and make this change. I checked the detection status script and it will not be impacted. We may have an older ETL that will break but I'm comfortable seeing what happens.

[dianamartin]

Current Configuration

On signal_detector object (CHILD), field "DETECTOR_TYPE" - Radar exists

1. GRIDSMART
2. LOOP
3. ~RADAR~
   • [x] Remove Radar
4. SENSYS
5. VIDEO
6. FLIR
7. MIOVISION
8. PRE-TIMED
9. NO DETECTORS
   • [x] Add these:
10. Radar - Iteris
11. Radar - SmartMicro
12. Radar - Wavetronix

On signal object (PARENT), field "DETECTOR_TYPE" - Radar do NOT exist

1. LOOP - on signal_detector
2. VIDEO - on signal_detector
3. NO DETECTION - on signal_detector as "NO DETECTORS"
4. MIXED - CURRENTLY NOT on signal_detector
5. GRIDSMART - on signal_detector

Proposed Configuration

@johnclary Will I have to add the missing choices that are on the signal_detector table and add it to the signal object?

• FLIR
• SENSYS
• MIOVISION
• PRE-TIMED
• Radar - Iteris
• Radar - SmartMicro
• Radar - Wavetronix

[johnclary]

Ah, right. @dianamartin, yes, on the signal object please add the three radar types as well. Will need to update an ETL script when you're done—lemme know 🙏

[dianamartin]

Made backup copy of signals_detectors - bc removing "RADAR" as Detector Type. Maybe MMC would want to have this list to QC. on signal_detector

• [x] Removed RADAR
• [x] Added `RADAR- Iteris
• [x] Added `RADAR- SmartMicro
• [x] Added `RADAR- Wavetronix

on signals

• [x] Added FLIR
• [x] Added SENSYS
• [x] Added MIOVISION
• [x] Added PRE-TIMED
• [x] Added RADAR - Iteris
• [x] Added RADAR - SmartMicro
• [x] Added RADAR - Wavetronix

@johnclary these update have been made, ready for the ETL to be updated

[amenity]

@johnclary - do you want an issue for updating this ETL?

[amenity]

The ETL that calculates and populates the Data Tracker signal "Status" report is working fine.