...
Custom Location Formatting
Custom Location Formatting uses REGEX to reformat specific Location Types while building the Enhanced 911 reports. It is configured by adding entries into the pcr360.ini file.
The settings are in the following format:
e911.type.<LOCATION_TYPE>.match = <REGEX_STRING>
e911.type.<<LOCATION_TYPE>.replace = '$1'
LOCATION_TYPE refers to any of the following:
- The List RECID of a Location Type, example: 178
- The List Code (in all caps) of a Location Type, example: FLOOR
- BUILDING_NUMBER, the building number of an address
- BUILDING_NAME, the building name of an address
- SERVICE_LOCATION, the Service Location of the Service
The REGEX strings use a standard REGEX find and replace format: https://regex101.com/.
| Expand | ||
|---|---|---|
| ||
Example UsageLet's say you have a Location like this: 1234 Example Building > 2 > 12 The Location Type for each part is BUILDING_NUMBER BUILDING_NAME > FLOOR > ROOM If the Example INI settings below are used on the e911 report, the location will be formatted as: #1234 > Flr: 2 > Rm: 12 # Floors # Example: A location type Floor is named "123" # It would appear on the report as "Flr: 123" # The config option uses the name (all in caps) of the location type e911.type.FLOOR.match = '/(.*)/' e911.type.FLOOR.replace = 'Flr: $1' # Rooms # Prepend "Rm: " to all room numbers # The config option can also use the list ID of the location type e911.type.178.match = '/(.*)/' e911.type.178.replace = 'Rm: $1' # Buildings # Clear the building names e911.type.BUILDING.match = '/(.*)/' e911.type.BUILDING.replace = '' # Building Numbers # prepend the number symbol to all Building Numbers e911.type.BUILDING_NUMBER.match = '/(.*)/' e911.type.BUILDING_NUMBER.replace = '#$1' |
...