As mentioned earlier, to handle larger values in the data received for the primary key (PK) and Site_ID, a larger integer type had to be employed. Seems like new signs ups are getting a bit larger values
Another issue - Is there a way to correct the region_id? For example it listed a plate as us-ky and it should be us-nc
is there a way to manually change it in the viewer? I tried to find the column region but cant find itThat issue is an OpenALPR issue. The viewer simply shows what OpenALPR is providing.
You should reach out to them to investigate the AI on their end so that they are aware of the similarities between the plates that you are seeing.
is there a way to manually change it in the viewer? I tried to find the column region but cant find it
Anyone have issues where the license plate comes in - gets an error but when you manual check it the information is there? It happens on like 90% of the plates I capture and im not sure where to look.
So the region is correct. Only a few I have to change. I mean the lookup. Refresh plates for new and let’s say if I captured 10 only 5 have vins no matter what time they came in. Then on the 5 that are blank or error I hit manually check and it returns data.That sounds off. They should match.
I would go back thru the settings and configs of OpenALPR and the utility and ensure you selected the correct region.
I seem to recall there is a country and "home state" that you need to input in, so maybe you have one or both wrong?
So the region is correct. Only a few I have to change. I mean the lookup. Refresh plates for new and let’s say if I captured 10 only 5 have vins no matter what time they came in. Then on the 5 that are blank or error I hit manually check and it returns data.
Ahh ok - Ive thought there was an issue when its blank so Ive been manually updating it. The blanks are exactly what you said. First time hits.Oh ok I misunderstood.
I think that is simply "errors" in that you started without the VIN service, so some of the plates are showing an error since your subscription wasn't active.
So the VINs that are blank means the system hasn't seen that vehicle yet and will update at midnight. Or you can do the manual Check Forensics and it fills it in.
The ones that are error are more than likely the ones prior to when you signed up for the VIN service.
Because we only get so many lookups per month, we don't wanna waste a lookup on plates we already have or plates that didn't show up.
So any plate that has a VIN, the utility will not send that plate again to the VIN lookup. Same with the error plate as that is deemed to be a lookup and you don't want it to blow thru your monthly lookup for one of the few times that a plate isn't in the system.
So what this can mean on occasion is say my neighbor for example that has a plate in my system that identifies his VIN and vehicle. It isn't looking it up again. Two years later he sells the car but transfers the plate to the new vehicle. My system is still going to show the old vehicle and VIN. At some point, usually 6 months to a year later the VIN lookup service will update the vehicle, but it won't update in my system because it has already looked that plate up once. So I can hit the check forensics button to have it send the plate again and if the plate has been updated in the VIN system, then it will change to the current vehicle VIN.
So you will see that happen from time to time as well.
So you correct these errors as they pop up for the first couple of weeks, and then after it has flushed out those prior to the VIN service, you should only see it on the reasons I mentioned previously.
I didnt make any changes to the code. I built it as is. I think its working as intended and im not be patient. The service lookup has 25 an hour and when troubleshooting he upped mine to 100.Did you make any other changes to the code when loading Vin Data, especially concerning the timer? If not, it's odd because this process is supposed to happen overnight (Part of Daily Activity Routine)" , unless you manually click 'check forensics,' which is fine too. However, I recall a few months or even a year ago, the Vin Lookup service may have implemented some Denial of Service protection. If too many results are pulled at once, it may temporarily blocks the request. I have a feeling that this might be what you are experiencing.