Leave the date empty for a key that does not expire. The last day counts: a key set to expire on the 31st works through the 31st and is refused on the 1st.
| Site | Key | Status | Expires | Issued by | Requests | |
|---|---|---|---|---|---|---|
| no keys yet | ||||||
| Date | Requests | Recognized | Unrecognized | No plate | Read rate |
|---|---|---|---|---|---|
| no keys yet | |||||
| Username | Role | Created | By | |
|---|---|---|---|---|
| — | ||||
vehicle plate — boxes are what the models actually predicted, drawn on the image you sent.
Raw Carmen-shaped JSON
Read-only. All of this is fixed when the stack is deployed
(sam deploy), not from here — shown because when a customer is
being throttled or a reading looks wrong, the first question is what this
stack is actually configured to do, and reading the template in a repo is
not the same as asking the running process.
One timezone for the whole deployment, not one per browser. It sets the clock above and the day a request is counted in — a gate that runs until 02:00 would otherwise have its late traffic land on the next day's row, with every total still adding up and the day quietly wrong. Changing it moves numbers a customer may be billed against, so it takes a super admin.
A frame the engine could not read is the only kind that
can teach it anything, and it is gone the moment the response is
returned. The name says which half failed —
-anpr, -mmr, -anpr+mmr — so a
folder can be sorted by what is wrong with it.
No plate is off by default. An empty lane has not been misread, and keeping every empty frame from every camera would bury the failures this exists to collect.
Kept in this browser only. Unlike the timezone, these change what the console starts on rather than what the service does, so they need no round trip and are not shared with anyone else signing in.