Metadata reference for license plate reads - Genetec Patroller™ | SharpV | SharpZ3 | Security Center

Exporting License Plate Reads in AutoVu™ and Security Center
Applies to
Genetec Patroller™ | SharpV | SharpZ3 | Security Center
Last updated
2022-04-11
Content type
Guides > Deployment guides
Language
English
Product
Genetec Patroller™
SharpV
SharpZ3

For AutoVu™ users who are already familiar with the different scenarios for exporting license plate reads, this section allows you to quickly reference the metadata tags associated with each scenario.

This section includes metadata tags for the following export scenarios:

  • Exporting reads from SharpV using FTP
  • Exporting reads from SharpV using HTTP
  • Exporting reads from Genetec Patroller™ using Hit export
  • License plate read metadata in Security Desk reports
  • Exporting reads from Security Center using XML export
  • Exporting reads from Security Center using AutoVu™ third-party data exporter

Scenario: Exporting reads from SharpV using FTP

FTP template:


<?xml version="1.0" encoding="utf-8"?>
<AutoVu>
   <Plate>#PLATE_READ#</Plate>
   <State>#CUSTOM_FIELDS#{State Name}</State>
   <UTCDate>#DATE_UTC#{yyyy:MM:dd}</UTCDate>
   <UTCTime>#TIME_UTC#{HH:mm:ss.fff}</UTCTime>
   <CameraName>#CAMERA_NAME#</CameraName>
   <SourceName>#SHARP_NAME#</SourceName>
   <ContextImage>#CONTEXT_IMAGE#</ContextImage>
   <PlateImage>#PLATE_IMAGE#</PlateImage>
   <LongitudeX>#LONGITUDE#</LongitudeX>
   <LatitudeY>#LATITUDE#</LatitudeY>
   <Guid>#GUID#</Guid>
</AutoVu>

Additional XML tags:

Confidence score
The Sharp assigns a confidence score percentage to each license plate read. This value indicates how confident the Sharp is in the accuracy of the read. You can add the confidence score associated with the plate read to the XML using the following field:

<ConfidenceScore>#CUSTOM_FIELDS#{Confidence Score}</ConfidenceScore>

Lane
If dual-lane monitoring is configured for the Sharp, you can add the lane name associated with the plate read to the XML using the following field:

<Lane>#CUSTOM_FIELDS#{Lane}</Lane>

Relative Motion
When the Sharp reads a plate, it detects and displays if the vehicle is approaching or moving away.
To use this field, add the following line to the XML:

<RelativeMotion>#CUSTOM_FIELDS#{Relative Motion}</RelativeMotion>.

Speed
For systems that include a fixed Sharp camera, you can configure the camera to export the vehicle’s estimated speed. You can add the speed of the vehicle associated with the plate read to the XML using the following field:

<Speed>#CUSTOM_FIELDS#{Speed}</Speed>

State Name
The Sharp attempts to read the plate’s origin in addition to the plate number (some plates include the issuing state or province). This may not be possible for all types of license plates.
To use this field, add <State>#CUSTOM_FIELDS#{State Name}</State> to the XML, and then select State on the Analytics page of the Configuration menu in the Sharp Portal.
NOTE: The ALPR context you are using must support the state name feature.
Vehicle Type
Certain license plates include character symbols that identify specific vehicle types (for example, taxi, transport, and so on). If the Sharp can read these symbols, it displays the vehicle type along with the other read and hit information.
To use this field, add the following line to the XML:

<VehicleType>#CUSTOM_FIELDS#{Vehicle Type}</VehicleType>.

Scenario: Exporting reads from SharpV using HTTP

HTTP template: JSON format


{ "ContextCameraName" : "Context Camera",
  "ContextImage" : "",
  "Id" : "32cf870a-46aa-4cfd-914b-00062d98e93a",
  "Latitude" : 0.0,
  "Longitude" : 0.0,
  "LprCameraName" : "Lpr Camera",
  "PlateAnalytics" : [ { "Key" : "State Name",
        "Score" : -1.0,
        "Value" : "-"
      },
      { "Key" : "Vehicle Type",
        "Score" : 1.0,
        "Value" : "-"
      },
      { "Key" : "Relative Motion",
        "Score" : -1.0,
        "Value" : "-"
      },
      { "Key" : "Context",
        "Score" : 1.0,
        "Value" : "US"
      },
      { "Key" : "Characters Height",
        "Score" : 1.0,
        "Value" : "70"
      }
    ],
  "PlateImage" : "",
  "PlateRead" : "AA7D2",
  "SourceUrl" : "SHARPV12345",
  "Timestamp" : "2016-08-29T08:42:45.797"
}

HTTP template: XML format


<Plate>
  <ContextCameraName>Context Camera</ContextCameraName>
  <ContextImage/>
  <Id>32cf870a-46aa-4cfd-914b-00062d98e93a</Id>
  <Latitude>0.0</Latitude>
  <Longitude>0.0</Longitude>
  <LprCameraName>Lpr Camera</LprCameraName>
  <PlateAnalytics>
    <PlateAnalytics>
      <Key>State Name</Key>
      <Score>-1.0</Score>
      <Value>-</Value>
    </PlateAnalytics>
    <PlateAnalytics>
      <Key>Confidence Score</Key>
      <Score>1</Score>
    <Value>100</Value>
    </PlateAnalytics>
  </PlateAnalytics>
  <PlateImage/>
  <PlateRead>AA7D2</PlateRead>
  <SourceUrl>SHARPV12345</SourceUrl>
  <Timestamp>2016-10-21T21:35:04.8627622+00:00</Timestamp>
</Plate>

Plate read event parameters:

Parameter Value type Description
ContextCameraName String Name of the color context camera that generated the read event.
ContextImage Binary Color context image of the scene. Base64 encoded JPEG image.
Id Guid Unique identifier for the read event.
Latitude Double Decimal latitude of the SharpV camera.
Longitude Double Decimal longitude of the SharpV camera.
LprCameraName String Name of the license plate recognition camera that generated the read event.
PlateAnalytics Array of analytics Each analytic object is composed of a data triplet. This array is of variable size. The amount of analytic objects received depends on the SharpV camera’s configuration.
Key (analytic triplet) String Name of the analytic.
Score (analytic triplet) Float

(-1.0 or 1.0)

 Indicates if the analytic value is reliable (1.0) or not (-1.0).
Value (analytic triplet) String Value of the analytic.
PlateImage Binary Black and white cropped license plate image. Base64 encoded JPEG image.
PlateRead String Detected license plate number.
SourceUrl String Unique name of the SharpV camera.
Timestamp DateTime Date and time of the read event (UTC) in the following format: yyyy-MM-ddTHH:mm:ss:fff.

Scenario: Exporting reads from Genetec Patroller™ using Hit export

The following XML tags are available in HitExportTemplates.xml:

<?xml version="1.0" encoding="utf-8" ?>
<!-- 
      !!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORTANT !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
      This file is a sample of the available tags that you can use when creating a 
      template. Do not create a dependency on this file for it is subject to change.
      
      Instead, you must create a copy of this sample and use it for your own purposes.
      !!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORTANT !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  -->  
 
<Enforce>

  <!--
    *************************************************************************
    NEWER
    The following section describe how to exploit the XML export to access
    the read Analytics fields using the generic #Analytics()# token.
    It can be used to access any Analytics field given its name.
    *************************************************************************
  -->
  <DoP>#Analytics(GeometricDop)#</DoP>
  <DoP>#Analytics(PositionDop)#</DoP>
  <DoP>#Analytics(TimeDop)#</DoP>
  <DoP>#Analytics(HorizontalDop)#</DoP>
  <DoP>#Analytics(VerticalDop)#</DoP>
  <DoP>#Analytics(EastingDop)#</DoP>
  <DoP>#Analytics(NorthingDop)#</DoP>
  <ReadWithDash>#Analytics(ReadWithSeparators)#</ReadWithDash>
  <Speed>#Analytics(Speed)#</Speed>
  <ConfidenceScore>#Analytics(Confidence Score)#</ConfidenceScore>
  
  <!--   
    *************************************************************************
    NEWER
    The following section describe how to exploit the XML export to access
    the read Analytics fields using the generic #Analytics()# token.
    It can be used to access any Analytics field given its name.
    *************************************************************************
  -->
  <GeometricDop>#Analytics(GeometricDop)#</GeometricDop>
  <PositionDop>#Analytics(PositionDop)#</PositionDop>
  <TimeDop>#Analytics(TimeDop)#</TimeDop>
  <HorizontalDop>#Analytics(HorizontalDop)#</HorizontalDop>
  <VerticalDop>#Analytics(VerticalDop)#</VerticalDop>
  <EastingDop>#Analytics(EastingDop)#</EastingDop>
  <NorthingDop>#Analytics(NorthingDop)#</NorthingDop>
  <Speed>#Analytics(Speed)#</Speed>
  <ConfidenceScore>#Analytics(Confidence Score)#</ConfidenceScore>
  <ReadWithDash>#Analytics(ReadWithSeparators)#</ReadWithDash>
  
  <ActualPlate>#ActualPlate#</ActualPlate>
  
  <!--   
    *************************************************************************
    NEW
    
    The following section describes the supported tags using the new format.
    
    *************************************************************************
  -->
  <IsPlateExpired>#ISPLATEEXPIRED#</IsPlateExpired>
  <IsPayZone>#ISPAYZONE#</IsPayZone>
  <PlateStatus>#PLATESTATUS#</PlateStatus>

  <HitId>#HIT_ID#</HitId>
  <HitType>#HIT_TYPE#</HitType>

  <ReadId>#READ_ID#</ReadId>
  <PlateRead>#PLATE_READ#</PlateRead>
  <PlateState>#PLATE_STATE#</PlateState>
  <ReadType>#READTYPE#</ReadType>
  <PermitName>#PERMIT_NAME#</PermitName>
  <RuleId>#RULE_ID#</RuleId>
  <RuleName>#RULE_NAME#</RuleName>
  <UnitName>#UNIT_NAME#</UnitName>
  <UnitId>#UNIT_ID#</UnitId>
  <UserName>#USER_NAME#</UserName>
  <UserLogin>#USER_LOGIN#</UserLogin>
  <UserId>#USERId#</UserId>
  <PermitId>#PERMIT_ID#</PermitId>
  <ParkingPermitId>#PARKING_PERMIT_ID#</ParkingPermitId>
  <Longitude>#LONGITUDE#</Longitude>
  <Latitude>#LATITUDE#</Latitude>
  <LprImagePath>#PLATE_IMAGE#</LprImagePath>
  <ContextImagePath>#CONTEXT_IMAGE#</ContextImagePath>
  <TireImagePath>#TIRE_IMAGE#</TireImagePath>
  <TimeStamp>#DATE_LOCAL#{yyyy-MM-dd} #TIME_LOCAL#{HH:mm:ss}</TimeStamp>
  <TimeStampUTC>#DATE_UTC#{yyyy-MM-dd} #TIME_UTC#{HH:mm:ss}</TimeStampUTC>

  <OvertimeVehicleId>#OVERTIME_READ_ID#</OvertimeVehicleId>
  <OvertimePlateRead>#OVERTIME_PLATE_READ#</OvertimePlateRead>
  <OvertimePlateState>#OVERTIME_PLATE_State#</OvertimePlateState>
  <OvertimeReadType>#OVERTIME_READTYPE#</OvertimeReadType>
  <OvertimePermitName>#OVERTIME_PERMIT_NAME#</OvertimePermitName>
  <OvertimeRuleId>#OVERTIME_RULE_ID#</OvertimeRuleId>
  <OvertimeRuleName>#OVERTIME_RULE_NAME#</OvertimeRuleName>
  <OvertimeUnitName>#OVERTIME_UNIT_NAME#</OvertimeUnitName>
  <OvertimeUnitId>#OVERTIME_UNIT_ID#</OvertimeUnitId>
  <OvertimeUserName>#OVERTIME_USER_NAME#</OvertimeUserName>
  <OvertimeUserLogin>#OVERTIME_USER_LOGIN#</OvertimeUserLogin>
  <OvertimeUserId>#OVERTIME_USER_ID#</OvertimeUserId>
  <OvertimePermitId>#OVERTIME_PERMIT_ID#</OvertimePermitId>
  <OvertimeLongitude>#OVERTIME_LONGITUDE#</OvertimeLongitude>
  <OvertimeLatitude>#OVERTIME_LATITUDE#</OvertimeLatitude>
  <OvertimeLprImagePath>#OVERTIME_PLATE_IMAGE#</OvertimeLprImagePath>
  <OvertimeContextImagePath>#OVERTIME_CONTEXT_IMAGE#</OvertimeContextImagePath>
  <OvertimeTireImagePath>#OVERTIME_TIRE_IMAGE#</OvertimeTireImagePath>
  <OvertimeTimeStamp>#OVERTIME_DATE_LOCAL#{yyyy-MM-dd} #OVERTIME_TIME_LOCAL#{HH:mm:ss}</OvertimeTimeStamp>
  <OvertimeTimeStampUTC>#OVERTIME_DATE_UTC#{yyyy-MM-dd} #OVERTIME_TIME_UTC#{HH:mm:ss}</OvertimeTimeStampUTC>

  <OvertimeElapseMinutes>#OVERTIME_ELAPSEMINUTES#</OvertimeElapseMinutes>
  <OvertimeElapseSeconds>#OVERTIME_ELAPSESECONDS#</OvertimeElapseSeconds>
  <OvertimeElapseHours>#OVERTIME_ELAPSEHOURS#</OvertimeElapseHours>
  
  <!-- 
    *************************************************************************
    LEGACY
    
    The following section describes the supported tags using the legacy format. 
    It can still be used but they have been deprecated since Patroller 6.2.
    
    *************************************************************************
  -->
  <IsPlateExpired>%IsPlateExpired%</IsPlateExpired>
  <IsPayZone>%IsPayZone%</IsPayZone>
  <PlateStatus>%PlateStatus%</PlateStatus>

  <HitId>%HitId%</HitId>
  <HitType>%HitType%</HitType>
  <UserAction>%UserAction%</UserAction>

  <VehicleId>%VehicleId%</VehicleId>
  <Plate>%Plate%</Plate>
  <State>%State%</State>
  <ReadType>%ReadType%</ReadType>
  <PermitName>%PermitName%</PermitName>
  <ZoneName>%ZoneName%</ZoneName>
  <UnitName>%UnitName%</UnitName>
  <UnitId>%UnitId%</UnitId>
  <UserName>%UserName%</UserName>
  <UserLogin>%UserLogin%</UserLogin>
  <UserId>%UserId%</UserId>
  <PermitId>%PermitId%</PermitId>
  <ParkingPermitId>%ParkingPermitId%</ParkingPermitId>
  <ZoneId>%ZoneId%</ZoneId>
  <GpsX>%GpsX%</GpsX>
  <GpsY>%GpsY%</GpsY>
  <LprImagePath>%LprImagePath%</LprImagePath>
  <ContextImagePath>%ContextImagePath%</ContextImagePath>
  <TireImagePath>%TireImagePath%</TireImagePath>
  <TimeStamp>%TimeStamp%</TimeStamp>
  <TimeStampUTC>%TimeStampUTC%</TimeStampUTC>

  <OvertimeVehicleId>%OvertimeVehicleId%</OvertimeVehicleId>
  <OvertimePlate>%OvertimePlate%</OvertimePlate>
  <OvertimeState>%OvertimeState%</OvertimeState>
  <OvertimeReadType>%OvertimeReadType%</OvertimeReadType>
  <OvertimePermitName>%OvertimePermitName%</OvertimePermitName>
  <OvertimeZoneName>%OvertimeZoneName%</OvertimeZoneName>
  <OvertimeUnitName>%OvertimeUnitName%</OvertimeUnitName>
  <OvertimeUnitId>%OvertimeUnitId%</OvertimeUnitId>
  <OvertimeUserName>%OvertimeUserName%</OvertimeUserName>
  <OvertimeUserLogin>%OvertimeUserLogin%</OvertimeUserLogin>
  <OvertimeUserId>%OvertimeUserId%</OvertimeUserId>
  <OvertimePermitId>%OvertimePermitId%</OvertimePermitId>
  <OvertimeZoneId>%OvertimeZoneId%</OvertimeZoneId>
  <OvertimeGpsX>%OvertimeGpsX%</OvertimeGpsX>
  <OvertimeGpsY>%OvertimeGpsY%</OvertimeGpsY>
  <OvertimeLprImagePath>%OvertimeLprImagePath%</OvertimeLprImagePath>
  <OvertimeContextImagePath>%OvertimeContextImagePath%</OvertimeContextImagePath>
  <OvertimeTireImagePath>%OvertimeTireImagePath%</OvertimeTireImagePath>
  <OvertimeTimeStamp>%OvertimeTimeStamp%</OvertimeTimeStamp>
  <OvertimeTimeStampUTC>%OvertimeTimeStampUTC%</OvertimeTimeStampUTC>

  <OvertimeElapseMinutes>%OvertimeElapseMinutes%</OvertimeElapseMinutes>
  <OvertimeElapseSeconds>%OvertimeElapseSeconds%</OvertimeElapseSeconds>
  <OvertimeElapseHours>%OvertimeElapseHours%</OvertimeElapseHours>

</Enforce>

Scenario: License plate read metadata in Security Desk reports

The following fields are available as search filters and report columns in Security Desk reports:

Accept reasons
Reason selected by the Genetec Patroller™ user when enforcing a hit. Accept reasons are created and configured in Config Tool.
Address
Location of the ALPR read.
Annotation fields
Any annotation field defined in System > ALPR Settings in the Config Tool. Shown in brackets.
Context image
Wide angle color image of the vehicle that was captured by the context camera.
Custom fields
Predefined custom fields for the entity. The columns only appear if custom fields are defined for the entity and were made visible to you when they were created or last configured.
Device
Device involved on the unit (reader, REX input, IO module, Strike relay, etc.).
Event timestamp
Date and time that the event occurred.
Latitude
The coordinates of where the ALPR event occurred.
Longitude
The coordinates of where the ALPR event occurred.
Offload timestamp
The date and time that the patrol vehicle offloaded the reads and hits to Security Center.
Patroller entity
Patroller entity name. The patroller entity name field is not populated for fixed SharpV cameras.
Plate image
The license plate image captured by the ALPR camera.
Plate origin
State that issued the license plate.
Plate read
The license plate read generated by the Sharp unit.
Protected
Indicates that the record will not be deleted from the database when the retention period (for this type of record) expires.
Protection expiration
Indicates when protection for the hit expires.
Reject reason
Reason selected by the Genetec Patroller™ user when rejecting a hit.
Rule
Hit rule that matched the plate read.
ALPR Unit
The ALPR unit that read the plate and populated for a patrol vehicle (for example, Patroller - Left, Patroller - Right, etc.), and for a fixed Sharp.
User
The Genetec Patroller™ user name. Not available at a Security Center Federation™ host for federated Genetec Patroller™ entities.
Wheel image
Image of the vehicle wheels. Used for virtual tire-chalking.

Scenario: Exporting reads from Security Center using XML export

The following XML tags are supported when using the XML export feature:
Supported XML hashtags
The following XML export hashtags are supported. Each hashtag must have an opening and closing XML tag (for example, to use the tag #CONTEXT_IMAGE# you must write <ContextImage>#CONTEXT_IMAGE#</ContextImage> in the XML).
#ACCEPT_REASON#
Reason hit was accepted.
#ADDRESS#
Address of the ALPR event.
#ATTRIBUTES#
Generate all Read and Hit attributes.
#CAMERA_NAME#
Name of the camera.
#CONTEXT_IMAGE#
Context image (Base64-encoded JPEG).
#DATE_LOCAL#
Local date of the ALPR event.
#DATE_UTC#
Date of the ALPR event in UTC time.
#ELAPSED_TIME#
For an overtime hit, this tag indicates the time difference between the two plate reads (displaying the number of days is optional).
FalseExportValue ???
"No"? - not sure about this
#FIRST_VEHICLE#
For a shared permit hit, this tag generates the content specified in ReadTemplate.xml for the first vehicle seen.
#FIRST_VEHICLE_FROM_STREET#
For an overtime hit, this tag retrieves the attribute From street from the first plate read.
#FIRST_VEHICLE_TO_STREET#
For an overtime hit, this tag retrieves the attribute To street from the first plate read.
#HOTLIST_CATEGORY#
Category field of the hotlist that generated the hit.
#GUID#
Unique identifier of the ALPR event.
#INVENTORY_LOCATION#
For MLPI installations, the location of the vehicle inventory.
#ISHIT#
This tag indicates if the ALPR event is a hit.
#LATITUDE#
Latitude of the ALPR event (in decimal degrees).
#LATITUDE#{dms}
Latitude of the ALPR event (in degrees, minutes, and seconds).
#LATITUDE#{dec}
Latitude of the ALPR event (in decimal degrees).
#LATITUDE_DEGREE#
Latitude of the ALPR event (degrees).
#LATITUDE_DMS#
Latitude of the ALPR event (in degrees, minutes, and seconds).
#LATITUDE_MINUTE#
Latitude of the ALPR event (minutes).
#LATITUDE_SECOND#
Latitude of the ALPR event (seconds).
#LONGITUDE#
Longitude of the ALPR event (in decimal degrees).
#LONGITUDE#{dec}
Longitude of the ALPR event (in decimal degrees).
#LONGITUDE#{dms}
Latitude of the ALPR event (in degrees, minutes, and seconds).
#LONGITUDE_DEGREE#
Longitude of the ALPR event (degrees).
#LONGITUDE_DMS#
Longitude of the ALPR event (in degrees, minutes, and seconds).
#LONGITUDE_MINUTE#
Longitude of the ALPR event (minutes).
#LONGITUDE_SECOND#
Longitude of the ALPR event (seconds).
#MATCHED_PLATE#
License plate against which the hit was generated.
#ORIGINAL#
For an overtime hit, this tag generates the content specified in ReadTemplate.xml for the first read of a given plate.
#OVERVIEW_IMAGE#
Overview image (Base64-encoded JPEG).
#PARKING_LOT#
Name of the park lot as configured in Security Center.
#PATROLLER_ID#
ID of patrol vehicle.
#PATROLLER_NAME#
Name of patrol vehicle.
#PERMIT_ID#
The ID defined for the Security Center permit.
#PERMIT_NAME#
Name of the permit that generated the ALPR event.
#PLATE_IMAGE#
License plate image (Base64-encoded JPEG).
#PLATE_READ#
License plate as read by the Sharp.
#PLATE_READ_MATCHED#
#PLATE_STATE#
License plate's issuing state or province, if read.
#REJECT_REASON#
Reason hit was rejected.
#READ#
Embed the contents of the ReadTemplate.xml inside another XML template (useful for hits).
#RULE_COLOR#
Color of the rule associated to the ALPR event.
#RULE_ID#
ID of the rule associated to the ALPR event.
#RULE_NAME#
Name of the rule associated to the ALPR event (hotlist, overtime, permit, or permit restriction).
#SECOND_VEHICLE#
For a shared permit hit, this tag generates the content specified in ReadTemplate.xml for the second vehicle seen.
#SECOND_VEHICLE_FROM_STREET#
For an overtime hit, this tag retrieves the attribute From street from the second plate read.
#SECOND_VEHICLE_TO_STREET#
For an overtime hit, this tag retrieves the attribute To street from the second plate read.
#SHARP_NAME#
Name of the Sharp that read the plate.
#STATE#
License plate's issuing state or province, if read.
#TIME_LOCAL#
Time of the ALPR event in local time.
#TIME_UTC#
Time of the ALPR event in UTC time.
#USER_ACTION#
User action related to the ALPR event.
#USER_ID#
ID of the user.
#USER_NAME#
Name of the user.
#VEHICLE#
Same as #READ#.
#ZONE_COLOR#
Color of the zone associated to the ALPR event.
#ZONE_ID#
ID of the zone associated to the ALPR event.
#ZONE_NAME#
Name of the zone associated to the ALPR event.

Scenario: Exporting reads from Security Center using AutoVu™ third-party data exporter

The following XML tags are supported when using the AutoVu™ third-party data exporter:

Supported hashtags
The following hashtags are supported in the XML and JSON templates.
NOTE: The XML and JSON templates are non-modifiable.
#ATTRIBUTES#
Generate all Read and Hit attributes.
#CAMERA_NAME#
Name of the camera.
#CONTEXT_IMAGE#
Context image (Base64-encoded JPEG).
#DATE_LOCAL#
Local date of the ALPR event.
#DATE_UTC#
Local date of the ALPR event.
#ELAPSED_TIME#
For an overtime hit, this tag indicates the time difference between the two plate reads (displaying the number of days is optional).
#FIRST_VEHICLE#
For a shared permit hit, this tag generates the content specified in ReadTemplate.xml for the first vehicle seen.
#FIRST_VEHICLE_FROM_STREET#
For an overtime hit, this tag retrieves the attribute From street from the first plate read.
#FIRST_VEHICLE_TO_STREET#
For an overtime hit, this tag retrieves the attribute To street from the first plate read.
#HOTLIST_CATEGORY#
Category field of the hotlist that generated the hit.
#GUID#
Unique identifier of the ALPR event.
#INVENTORY_LOCATION#
For MLPI installations, the location of the vehicle inventory.
#ISHIT#
This tag indicates if the ALPR event is a hit.
#LATITUDE#
Latitude of the ALPR event (in decimal degrees).
#LATITUDE#{dms}
Latitude of the ALPR event (in degrees, minutes, and seconds).
#LATITUDE#{dec}
Latitude of the ALPR event (in decimal degrees).
#LATITUDE_DEGREE#
Latitude of the ALPR event (degrees).
#LATITUDE_DMS#
Latitude of the ALPR event (in degrees, minutes, and seconds).
#LATITUDE_MINUTE#
Latitude of the ALPR event (minutes).
#LATITUDE_SECOND#
Latitude of the ALPR event (seconds).
#LONGITUDE#
Longitude of the ALPR event (in decimal degrees).
#LONGITUDE#{dec}
Longitude of the ALPR event (in decimal degrees).
#LONGITUDE#{dms}
Latitude of the ALPR event (in degrees, minutes, and seconds).
#LONGITUDE_DEGREE#
Longitude of the ALPR event (degrees).
#LONGITUDE_DMS#
Longitude of the ALPR event (in degrees, minutes, and seconds).
#LONGITUDE_MINUTE#
Longitude of the ALPR event (minutes).
#LONGITUDE_SECOND#
Longitude of the ALPR event (seconds).
#MATCHED_PLATE#
License plate against which the hit was generated.
#ORIGINAL#
For an overtime hit, this tag generates the content specified in ReadTemplate.xml for the first read of a given plate.
#OVERVIEW_IMAGE#
Overview image (Base64-encoded JPEG).
#PATROLLER_ID#
ID of patrol vehicle.
#PATROLLER_NAME#
Name of patrol vehicle.
#PERMIT_NAME#
Name of the permit that generated the ALPR event.
#PLATE_IMAGE#
License plate image (Base64-encoded JPEG).
#PLATE_READ#
License plate as read by the Sharp.
#PLATE_STATE#
License plate's issuing state or province, if read.
#REJECT_REASON#
Reason hit was rejected.
#READ#
Embed the contents of the ReadTemplate.xml inside another XML template (useful for hits).
#RULE_COLOR#
Color of the rule associated to the ALPR event.
#RULE_ID#
ID of the rule associated to the ALPR event.
#RULE_NAME#
Name of the rule associated to the ALPR event (hotlist, overtime, permit, or permit restriction).
#SECOND_VEHICLE#
For a shared permit hit, this tag generates the content specified in ReadTemplate.xml for the second vehicle seen.
#SECOND_VEHICLE_FROM_STREET#
For an overtime hit, this tag retrieves the attribute From street from the second plate read.
#SECOND_VEHICLE_TO_STREET#
For an overtime hit, this tag retrieves the attribute To street from the second plate read.
#SHARP_NAME#
Name of the Sharp that read the plate.
#STATE#
License plate's issuing state or province, if read.
#TIME_LOCAL#
Local time.
#USER_ACTION#
User action related to the ALPR event.
#USER_ID#
ID of the user.
#USER_NAME#
Name of the user.
#VEHICLE#
Same as #READ#.