I'm running the agent on Linux in Docker so I don't even have that menu. I have to control the agent from the Dashboard.I have been adjusting it in the UI, but it seems to sync up as my web page says the same
View attachment 80203
That's inside the container though for me and not meant to be accessible to most people. I had to enable the webserver from there to get pictures working.you can control the agent through thealprd.conf
file
/etc/openalpr/
folder and modify it outside. Watchman Quick Start — openalpr 2.8.101 documentationAhh I did not know that!you can map the/etc/openalpr/
folder and modify it outside. Watchman Quick Start — openalpr 2.8.101 documentation
Edit the configuration file
sudo nano /etc/openalpr/alprd.conf
Configure the following properties:
Test the daemon from the CLI to make sure your settings are correct. Press CTRL+C once you see that the video stream is connected.
- company_id (using the value found on the web server)
- site_id (a unique text value that identifies this agent)
- stream (The mjpeg URL for the camera stream. Multiple streams are added as additional stream entries)
- analysis_threads (number of CPU cores dedicated to OpenALPR processing)
- upload_address (set this to http:///[Web_server_IP]/push/)
- store_plates_maxsize_mb (amount of space used for storing license plate images)
alprd -f
Are you guys storing video? I'm not even sure what that could be used for...
I have 5000ish plates which is taking up 5GB, but 30GB is video, which I'm not even sure what is being used for
i bet there's a way to get that plate data since it's still stored in the agent, and the agent isn't aware of what your subscription is.
But those plate "records" aren't on your local service DB since I had collected those plates before I ever started running your service. So your service doesn't even know about them. The hydrator would have taken care of pulling plates off the OpenALPR cloud service that weren't stored on the local webhook service, but as we found out, they require a commercial license to pull them down.i bet there's a way to get that plate data since it's still stored in the agent, and the agent isn't aware of what your subscription is.
i bet the data is in there somewhere, might need to crack the client's db open and take a look.But those plate "records" aren't on your local service DB since I had collected those plates before I ever started running your service. So your service doesn't even know about them. The hydrator would have taken care of pulling plates off the OpenALPR cloud service that weren't stored on the local webhook service, but as we found out, they require a commercial license to pull them down.
v3.2.0-alpha5
is out with preliminary search abilities. there are probably issues with timezone when searching with date/time filters, and the plate search is case sensitive right now.I have ~3500 plates stored on the local Webhook service. That corresponds to 1.6GB of plate pictures on the client or about 450KB per picture.
You can specify the quality of the .jpgs in the .conf file. I never tinkered with it so its set for whatever the default is. It only takes the snapshot when it detects a plate. The agent is always analyzing the video stream. You configure your camera in the agent settings so the agent has a direct connection to the camera. When it detects that a plate comes into the scene that is when it reads it and takes the snapshot.Wow - using the snapshot from BI for Plate Recognizer, my plate pictures are 75KB per picture.
Can you specify a resolution or size for the pics using OpenALPR or is it a direct relation to the resolution of the videostream that you are using?
Does this system take a snapshot of any vehicle or motion or just when it has a plate?
Does this system take the videostream and truly look for a plate and then take a pic only of plates or does it take a pic early like a large semi or bus enters the frame but the plate isn't visible yet?
Sorry for all the questions! I am just trying to figure out as much as I can before I start the trial period of OpenALPR and get my system as close as possible from the start to be usable.