Storage requirement for LPR images - Security Center 5.7 GA

Security Center Installation and Upgrade Guide 5.7 GA

series
Security Center 5.7 GA
revised_modified
2017-10-25

The images associated with the reads and hits are stored on disk in G64 files by an Archiver. You can estimate the disk space required to store these images if you know the average number of reads and hits processed by the LPR Manager per day.

For every license plate read or hit processed by the LPR Manager, the Archiver stores a set of four images:
  • One context camera image (in either high resolution or low resolution)
  • One LPR camera image (cropped to show only the license plate)
  • One context camera thumbnail image
  • One LPR camera thumbnail image

The size of the image set depends on the model of the Sharp camera and whether the context camera is configured to take images in high resolution or low resolution.

Use the following formula to estimate the disk space you need for the desired image retention periods.
Disk space = (ReadsPD x ImageSize x ReadIRP) + (HitsPD x ImageSize x HitIRP)
where:
ReadsPD
Average number of reads per day.
ImageSize
Estimated image size per read (depends on the Sharp model and configuration).
ReadIRP
Read image retention period (see LPR Manager's Properties tab).
HitsPD
Average number of hits per day.
HitIRP
Hit image retention period (see LPR Manager's Properties tab).

If your Patroller vehicles are equipped with wheel imaging cameras, double the number of hits per day in your formula (there are typically one wheel image per hit).

The following table gives you the rough estimates of the image size per read based on the Sharp model and configuration.
Type of image Sharp VGA or XGA SharpV
Context camera image (high res. config.) ~50 KB ~120 KB
Context camera image (low res. config.) ~18 KB -
LPR camera image (cropped) ~3 KB ~3 KB
Context camera thumbnail image ~3 KB ~3 KB
LPR camera thumbnail image ~1 KB ~1 KB
Image size per read (high res. config.) ~57 KB ~127 KB
Image size per read (low res. config.) ~25 KB -
NOTE: If a read or hit is protected and must be kept beyond its specified retention period, it will require more disk space for its associated images than what is calculated for a single event. Because the Archiver stores multiple LPR images in a single G64 file, if one image in the file is protected, then all other images in the file are also protected. This uses up more disk space over time. However, an image whose corresponding read or hit has been deleted can no longer be read because the G64 files are encrypted.

If the Archiver is assigned to more than one LPR Manager, add the numbers for all LPR Manager roles together.