Difference between revisions of "TrafficCam"
Jump to navigation
Jump to search
Line 15: | Line 15: | ||
Image volume calculation: | Image volume calculation: | ||
− | * 60 seconds/minute x 60 minutes/hour x 24 hours/day x 7 days/week x 4.5 weeks/month = | + | * 60 seconds/minute x 60 minutes/hour x 24 hours/day x 7 days/week x 4.5 weeks/month x 12 months/year = 32,659,200 seconds/year |
− | * 1 frame/second x 20 KB/frame x | + | * 1 frame/second x 20 KB/frame x 32,659,200 seconds/year = 653,184,000 KB/year or 637,875 MB/year or 623 GB/year |
Software architecture: | Software architecture: |
Revision as of 12:31, 11 August 2008
Gear to record video of the pedestrian crossing and the speed of Eastbound traffic in front of Earlham on National Road West.
To do (ordered):
- Test-drive current Axis camera "in-situ" on the wind geny's tripod. Use the PMP1 for the interface with the directional WiFi antenna. Location is likely to be the shrubbery near the East side of the entrance.
- Research all-in-one systems, see Alan's email.
- Research discrete speed sensors, pay close attention to the interface and data stream.
Possible technologies:
- Technologic Systems single-board computer
- WiFi interface with directional antenna
- DRS1000 Delta speed sensor
- Axis weatherproof camera
- Weatherproof case
- Mounting pole
Image volume calculation:
- 60 seconds/minute x 60 minutes/hour x 24 hours/day x 7 days/week x 4.5 weeks/month x 12 months/year = 32,659,200 seconds/year
- 1 frame/second x 20 KB/frame x 32,659,200 seconds/year = 653,184,000 KB/year or 637,875 MB/year or 623 GB/year
Software architecture:
- Cache 2 minutes locally
- Use infobomb stack to transfer and append to current day's movie
- 4a-3:59a movies, sync with infobomb and roll-over, simple trac or fancydir listing by year-month
Questions for Doug:
- Interface - 1 second frames, manual video review, automated video review, speed/video correlation,
- Overall duration, 1 year?
- Better density