Change in the OpenALPR CSV Export

DLONG2

Known around here
Joined
May 17, 2017
Messages
763
Reaction score
454
This morning, the format of the exported OpenALPR CSV file has changed. There are a 14 new fields added to the export:

crop_location
gps_latitude
gps_longitude
img_height
img_width
plate_x1
plate_x2
plate_x3
plate_x4
plate_y1
plate_y2
plate_y3
plate_y4
processing_time_ms

This will require a bit or rework on the import-to-database process . . .
 

DLONG2

Known around here
Joined
May 17, 2017
Messages
763
Reaction score
454
Another change is the format of the 'epoch_time_end' and 'epoch_time_start' strings. The newer format looks much easier to parse:

Old:
2019-04-29T11:37:10.672Z,2019-04-29T11:37:03.866Z,

New:
2019-05-02 03:55:23.909000-07:00,2019-05-02 03:55:17.707000-07:00,
 

DLONG2

Known around here
Joined
May 17, 2017
Messages
763
Reaction score
454
Another change is the date time stamps as shown above are no longer in universal time, but local time.
 

tech101

Known around here
Joined
Mar 30, 2015
Messages
1,472
Reaction score
2,125
Location
SF BayArea, USA
Hi is there a script or a third party solution to download csv and process every 48 hours so we can retain data say in excel file ?
 

DLONG2

Known around here
Joined
May 17, 2017
Messages
763
Reaction score
454
Hi is there a script or a third party solution to download csv and process every 48 hours so we can retain data say in excel file ?
I wish I knew. My Windows application mostly automates by a one-click event using SendKeys in Visual Basic to effect the download from the website and import into my database, but wish there were a way to fully automate it and forget it.
 

DLONG2

Known around here
Joined
May 17, 2017
Messages
763
Reaction score
454
And of course the 'epoch_time_end' and 'start' fields have reverted back to UTC time rather than local time.
 
Top