V.15 UNIT Information Feature (COW Only)
Users have requested the ability to describe addresses more in more detail. Geosupport now allows users to specify UNIT information, e.g. APT 5, on COW address-processing functions
The UNIT feature enables users to keep better track of information specific to units within a building. For example, it will be useful for PECO (Post Emergency Canvassing Operations) to record which units in a building were canvassed, and which units required assistance. By allowing users to input apartment numbers it will help the users keep track of whom they saw when going into the field. They can print lists with apartment numbers and keep track of which apartments were seen and which still remain to be seen. The Unit information can also be used on mailing labels, etc.
Unit information may appear at the end of an input free-form address,
e.g. 120 BROADWAY STE 3102
Alternatively, unit information may also appear in the Unit Input field in Work Area 1,
e.g. STE 3102
Unit information consists of a Type and an Identifier . For example, ‘APT 5’ consists of a Unit Type of ‘APT’ (apartment) and a Unit Identifier of ‘5’. (Unit Type and Unit Identifier are similar to NENA (National Emergency Number Association) terminology.) NENA and USPS (US Postal Service) have defined Preferred Types with a length of up to 4 characters. Geosupport converts the input Type to the Preferred Type. See Table of Preferred Types later in this section. If the unit information does not have a recognized type, the Type will be set to a pound sign, viz. #, and the data will be considered as the Identifier. If the data is longer than the space available in the Unit fields, the identifier will be truncated and a warning message (Reason Code $) will be issued.
Unit information is supplied by the user in the Work Area 1 (WA1) Unit Input field for a length of 14, or at the end of a free-form address. In either case, the unit information is normalized and returned in the Output Area of WA1 in two formats – Display format and Sort format.
Display format for a length of 14, with Type and Identifier concatenated with one blank in between them.
Sort format for a length of 14, which is broken down into two consecutive fields
- Unit Type for a length of 4
- Unit Identifier for a length of 10
The following table indicates the size and location of the UNIT fields in the COW Work Area 1. These fields are defined in the Geosupport COPY library.
|UNIT Fields Work Area 1 (COW only)|
|---- The following Unit field is in the Input portion of Work Area 1 ----|
|---- The following Unit fields are in the Output portion of Work Area 1 ----|
|UNIT - SORT FORMAT||14||667||680||1*|
|Unit – Type||4||667||670||1*|
|Unit – Identifier||10||671||680||1*|
|Unit – Display Format||14||681||694||1*|
The normalization of Unit input includes recognizing the Unit Type and Identifier and converting all Unit Types to the Preferred Unit Types. In addition, the first instance of a Type is moved to the front of the Display Unit field. Some of the basics of normalization are mentioned here.
- All ordinals are removed
- All characters aside from A-Z, 0-9, -, / are removed
- All extraneous blanks and all blanks before and after / or – are removed
- The first instance of a Type is moved to the front of the unit field with the rest of the identifier following, e.g. 1st Floor will be output as FL 1.
- All instances of a Type are replaced by the Preferred Type
- In the absence of a Type, the software will return a pound sign (#).
- In Display format there will always be a blank between the Type and the Identifier, e.g.
MEZZAwill appear as
MEZZ Ain a Unit output field. (
MEZZis the preferred Type for Mezzanine.)
Note: In the following discussions, blanks appear as hyphens.
Consider an example where the Unit Input is '
4TH-FLOOR'. It will be normalized to: '
FL-4' in the Display format. The ordinal
'FLOOR'was replaced by the Preferred Type
'FL'was moved to the front of the Display Unit field.
The Sort format is similar except that it is composed of two fields. The Type is always 4 characters. The first instance of a Type is put into the Type field of the Sort format. The Identifier has 10 characters and any numeric may have extra spaces around them to ensure that they sort properly. In this case,
'4th-FLOOR'would be appear as
'FL--'in the Sort Type field and '---4------' in the Sort Identifier field. The extra blanks before the ‘4’ in the Sort Identifier field will ensure that if they are sorted, the sort version of
'10TH‑FLOOR'('--10------') will appear after the sort version of
If no Type at all is recognized in the input, then a pound sign ‘#’ is used as the Type in the Display and the Sort format. For example, if the Unit Input just had a ‘5’, Then the Display format would contain
'#-5'; the Sort format would contain Type: '#---' and Identifier:'---5------'.
If Unit Input is specified in the WA1 Unit Input field, and additional information also appears after the Street Name in a free-form call, then the WA1 Unit Input field is processed and the information appearing after the free-form address is ignored.
When the Unit information is supplied as part of the free-form address, Geosupport continues to give the Reason Code 'W' warning message
INPUT STREET NAME HAS BEEN MODIFIED
In rare instances, a Unit Identifier may be truncated in an output field. In that case, if the Unit Input was specified in the WA1 Unit Input field, then a warning message is issued. The warning message is:
|01||$||1*||UNIT IDENTIFIER HAS BEEN TRUNCATED|
When this situation occurs with a free-form address, the original warning message with Reason Code ‘W’: INPUT STREET NAME HAS BEEN MODIFIED is still given.
The following is a table of the Preferred Unit Types and the Alternate Types that are recognized as input. The Preferred Type will appear in the Unit Output fields.
|Table of PREFERRED UNIT TYPEs|
|Unit Type||Input 1||Input 2||Input 3||Input 4|
Mainframe GOAT (CICS) Support of Unit - Functions 1A and 1B
Input: Field labeled
'Unit'is available for input data.
Output: Field labeled
'Norm Unit Disp' displays the Normalized Display Format Unit Output field.
Input: Field labeled ‘Unit’ is available for input data.
Output: To save screen space, the Field labeled
'Unit'that was used for input is also used for output and displays the Normalized Display Format Unit Output field.
Mainframe GBAT Support - Functions 1A and 1B
Required GBAT Control Entries
RECTYPE=1A or 1B
Optional GBAT Control Entries
UNIT=S,L defines location of Unit input field(not required if input data is free-form only) GEOUNIT=YES or NO specifies if GBAT returns the Normalized Display Format Unit output field. GEOCODE=NO or ALL required if GEOUNIT=YES
Optional LRECL change
If GEOUNIT=YES is in effect, the LRECL of OUTFILE must be increased by 70.
For more detail on GBAT Unit processing, see Chapter IX, Appendix 9, and Appendix 12.
Summary of Geosupport support of Unit processing
As of this writing, Unit Processing is supported by:
Mainframe Batch and CICS
.net and Java classes
Mainframe GBAT Batch (Functions 1A and 1B)
Mainframe GOAT CICS (Functions 1A and 1B)
Desktop Edition GBAT (Functions 1A and 1B)!
As of this writing, Unit fields are not processed by:
Mainframe GBAT Batch (Functions 1 and 1E)
Desktop Edition GBAT (Functions 1 and 1E)
Desktop Edition GOAT