Site-Based Video System Design and Development (2012) / Chapter Skim
Currently Skimming:
Pages 21-24
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 21... ...
21 C h a p t e r 4 This chapter considers the broad range of performance and operational requirements expected of the "ideal" video tracking system. Given the unique importance of trajectory accuracy and resolution in both time and space, based on the need to compute accurate conflict metrics, Chapter 5 will consider these aspects in greater detail and discuss the likely applicability of these conflict metrics as surrogates for crash.
|
From page 22... ...
22 Sensitivity to lighting and weather conditions: It must be expected that in poor lighting and weather, the availability (percentage time of error-free operation) will drop.
|
From page 23... ...
23 system could go to the extreme operational mode of "capture by day, process by night," in which case-sufficient storage would be needed for approximately 12 h of uncompressed video for each camera station, something that is no concern for a hard drive but could be a challenge for solid state memory. Scalability and parallel processing: Once the system is developed and proved for an intersection of modest complexity, the same hardware and software should be capable of scaling up to a larger and more complex installation; to avoid processing bottlenecks, the major portion of the video processing should be parallelized (e.g., processing each video stream in parallel)
|
From page 24... ...
24 • Data access: Time history data should be stored in a standard database format, such as Microsoft SQL Server; • Analysis tools: Basic tools are needed to query the data to calculate a subset of conflict metrics, including time to collision and gap times for path-crossing conflicts; and • Visualization tools: A basic viewer should be provided so that events of interest, defined by event start and end time, can present video and time history data of that event. All such tools should be part of the prototype, with the expectation that future generations will offer increasing user-friendly interfaces.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.