APPENDIX 3: DATA ITEM DICTIONARY

This Data Item Dictionary is an alphabetical list of the data items for which there are fields in the Geosupport API work areas, together with descriptive information. In general, data items are listed in this appendix under the names used in the work area layouts in Appendix 2 (MSW) and Appendix 13 (COW). However, if an item is associated with multiple work area fields having varying field names, and is identical in format and range of values in all those fields, the item is documented in a generically-named entry, and there is also a separate entry for each of those fields consisting only of a reference to the generic entry. For example, there is a generic entry for CENSUS TRACT containing full descriptive information, and there are also entries for 2000 CENSUS TRACT, LEFT 2000 CENSUS TRACT, RIGHT 2000 CENSUS TRACT, 2010 CENSUS TRACT etc., containing only a reference to the entry for CENSUS TRACT.

Each entry consists of an appropriate combination of the following elements:

  • Name of Data Item. This might be identical to the name of a specific work area field or it might be a generic name for a data item that is represented by multiple work area fields.

  • Field Names. A list of the field names associated with a generic entry.

  • Function(s). A list of the Geosupport functions that utilize this data item as either an input or an output item in either WA1 or WA2. If the data item is in the added portion of WA2 that is passed when the function is called with the long WA2 option, this is so stated. Similarly, if the data is passed when the function is called with an Extended or Auxiliary or other option, it is so stated. In the list of functions, an asterisk in the second position of a function code is a ‘wild card’ signifying all functions having the indicated value in the first position, as follows:

1 * = 1, 1A, 1B, 1E, 1N; also 1Extended, 1A Extended, 1E Extended

2 * = 2, 2W

3 * = 3, 3C, 3S, 3 & 3C with Auxiliary Segments, 3 & 3C Extended (with or without Auxiliary Segments)

B * = BB, BF, BL, BN

D * = D, DG, DN

  • Work Area Format: A list of the work area format(s) that apply to this entry, namely, MSW (Mainframe-Specific Work Area) and/or COW (Character-Only Work Area).

  • Length and Format. The length of this data item in bytes, and a description of its format, including whether it is numeric, alphabetic or alphanumeric (these terms are defined below); whether it contains any special editing characters; and for numeric items, the justification and the fill character. The following terms and abbreviations are used:

RJ = Right-Justified
LJ = Left-Justified
ZF = Zero-Filled
BF = Blank-Filled

Numeric: Contains only the digits 0 through 9, and possibly blanks serving as fill characters only.
Alphabetic: Contains letters of the alphabet only. LJBF unless otherwise stated.
Alphanumeric: Can contain any allowable characters, including special characters such as hyphens. LJBF unless otherwise stated.

  • Description. A brief narrative description of the data item. The description may include citations to sections of the UPG where the data item is principally discussed. Data items that are self‑explanatory have no description and/or citations.

  • Valid Values and Code Meanings. The values or ranges of values valid for this data item and, if the item consists of codes, the meaning of each code value.

Numeric

1A/BL VERSION FLAG - See FUNCTION 1A/BL VERSION FLAG.
1990 CENSUS TRACT - See CENSUS TRACT.
2000 CENSUS BLOCK - See CENSUS BLOCK.
2000 CENSUS BLOCK SUFFIX - See CENSUS BLOCK SUFFIX.
2000 CENSUS TRACT - See CENSUS TRACT.
2010 CENSUS BLOCK - See CENSUS BLOCK.
2010 CENSUS BLOCK SUFFIX - See CENSUS BLOCK SUFFIX.
2010 CENSUS TRACT - See CENSUS TRACT.

A

ALLEY/CROSS STREETS FLAG (ALX)
Functions: 1, 1E
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: Indicates if the segment has been split by alleys, or if the cross streets named in the segment have been copied from a previous or subsequent segment because the segment itself has no cross streets.
Code Value Meaning
‘A’ Split by Alley(s)
‘X’ Cross Streets Modified
Blank Neither Split by Alleys or Cross Streets Modified
ALTERNATE LOW AND HIGH HOUSE NUMBERS
Functions: 3C
Work Area Format: MSW and COW
Length and Format: See HOUSE NUMBER
Description: These two fields are non-blank only if this blockface has addresses of both parities (the parity of a number is its attribute of being odd or even). Such a blockface is said to have ‘continuous parity’. If the blockface has continuous parity, the Continuous Parity Indicator is non-blank, the Low and High House Number fields contain the address range for one parity, and the Alternate Low and High House Number fields contain the address range for the other parity. (Which parity is in which set of house number fields is unpredictable.)
ALTERNATIVE BOROUGH FLAG
Functions: 1, 1A, 1B, 1E, 2, 3, 3C, 3S (COW only), BL, BN
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: This flag indicates either that the input address is in Marble Hill or Rikers Island and the alternative (rather than the legal) borough was specified (see Chapter V.7), or that the input address is on Ruby Street in Brooklyn but it was specified using the alternative (Queens) street name 75 Street (see Chapter V.8).
This field was also known as the Marble Hill / Rikers Island Flag.
Code Value Meaning
‘C’ Ruby Street address specified using 75 Street
‘M’ Marble Hill address with Bronx specified
‘R’ Rikers Island address with Queens specified

ALX FLAG - See ALLEY/CROSS STREETS FLAG

ANNOTATION POINT - No longer used by Geosupport. See SPATIAL COORDINATES OF THE TAX LOT CENTROID

ASSEMBLY DISTRICT
Field Names: LEFT ASSEMBLY DISTRICT
RIGHT ASSEMBLY DISTRICT
Functions: 1E, 2 (COW only), 3 (COW only), 3C (COW only)
Work Area Format: MSW and COW
Length and Format: 2 bytes. RJZF
Description: A district of the lower house of the New York State legislature. Consists of an aggregation of Election Districts
ATOMIC POLYGON - Previously known as DYNAMIC BLOCK
Functions: 1, 1B, 1E, 3(MSW: Long WA2), 3(COW), 3C
Work Area Format: MSW and COW
Length and Format: 3 bytes RJZF
Description: An atomic polygon is an un-subdivided polygon . Atomic polygons are created based on the New York City CSCL (Citywide Street Centerline) database. Atomic polygons are numbered uniquely within census tract.

ATTRIBUTE BYTE - See STREET ATTRIBUTE INDICATOR

AUXILIARY SEGMENT SWITCH (auxseg or segaux)
Functions: 3, 3C, 3 & 3C Extended
Work Area Format: COW
Length and Format: 1 byte character.
Description: When this flag is set to ‘Y’, the list of all the Segment IDs that comprise the segment will be added to the end of Work Area 2 for Functions 3 or 3C.
Code Value Meaning
‘N’ or Blank One Segment ID is returned in Work Area 2.
‘Y’ A list of all the segment IDs is added to the end of Word Area 2 for Function 3 or 3C.

B

B7SC OF “TRUE” STREET (a.k.a. B7SC OF “UNDERLYING” STREET)
Functions: 1and 1E (MSW: Long WA2 only); 1, 1B and 1E (COW)
Work Area Format: MSW and COW
Length and Format: 8 bytes (B7SC)
Description: This item typically applies to Addressable Place Names, Non-addressable Place Names and Vanity Addresses. It item contains the B7SC of the street segment upon which the address specified is actually located. This is the street segment that is identified by the field SEGMENT-ID and by the fields FACE CODE and SEQUENCE NUMBER. In most cases, the B5SC portion of this item is identical to the B5SC specified in the key. However, the two B5SCs differ when the SPECIAL ADDRESS GENERATED RECORD FLAG is either ‘B’, ‘N’, ‘P’, or ‘V’.
BBL
Functions: 1A, BL, BN, AP
Work Area Format: MSW and COW
Length and Format: 10 bytes in standard version, Numeric. (Note: the legacy version of Functions 1A and BL is no longer supported.)
Standard:
Field Length Position Comments
Borough 1 1-1
Tax Block 5 2-6 RJZF
Tax Lot 4 7-10 RJZF
Description: The first 6 bytes of the standard BBL consists of the 1-byte borough code followed by the 5-byte tax block field, which contains the tax block value right-justified and zero-filled. The last 4 bytes of the standard BBL is the standard tax lot field, which contains the tax lot value right-justified and zero-filled. See Chapter VI.8. The BBL (‘borough-block-and-lot’) identifies a parcel of real property in New York City, called a tax lot. The BBL is composed of the concatenation of the Borough Code, Tax Block and Tax Lot. If the property is a condominium (indicated by the Condominium Flag), the WA2 BBL field contains the billing BBL of the condominium (see Chapter VI.4).

BID - See BUSINESS IMPROVEMENT DISTRICT

BIKE LANE BIKE LANE is being replaced by BIKE LANE 2. See also BIKE LANE 2
Functions: 1 Extended, 1B, 1E Extended, 3 Extended, 3C Extended
Work Area Format: COW
Length and Format: 1 byte
Notice: As of Release 16D, Bike Lane has 11 codes, instead of 7. A new two-byte field, BIKE LANE 2, is being introduced. The original one-byte Bike Lane field still exists to give users a chance to update their applications. In the one-byte Bike Lane field, the value ‘A’ will appear when the new code is ‘10’, and the value ‘B’ will appear when the new code is ‘11’. We recommend that users update their applications to refer to the new Bike Lane-2 since the one-byte Bike Lane field will be deleted in a later release.
Description: Defines which street segments are part of the bicycle network as defined by the Department of Transportation.
Code Value Meaning
1 Class I: Separated Greenway
2 Class II: Striped Bike Lane
3 Class III: Signed Bicycle Route
4 Links: Connecting Segments
5 Class I, II: Combination of Class I and II
6 Class II, III: Combination of Class II and III
7 Stairs: Step streets, bridge stairs, etc.
8 Class I, III Combination of Class I and III
9 Class II, I Combination of Class II and I
A Class III, I Combination of Class III and I
B Class III, II Combination of Class III and II
BIKE LANE 2
Functions: 1 Extended, 1B, 1E Extended, 3 Extended, 3C Extended
Work Area Format: COW
Length and Format: 2 bytes, RJBF
Description: Defines which street segments are part of the bicycle network as defined by the Department of Transportation.
Note: As of Geosupport Version 16.4, Bike Lane 2 is being introduced to replace Bike Lane
The following table contains the values that can appear in the Bike Lane 2 field
Code Value Meaning Description
1 Class I: Separated Greenway
2 Class II: Striped Bike Lane
3 Class III: Signed Bicycle Route
4 Links: Connecting Segments
5 Class I, II: Combination of Class I and II
6 Class II, III: Combination of Class II and III
7 Stairs: Step streets, bridge stairs, etc.
8 Class I, III Combination of Class I and III
9 Class II, I Combination of Class II and I
10 Class III, I Combination of Class III and I
11 Class III, II Combination of Class III and II
BIKE TRAFFIC DIRECTION
Functions: 1 Extended, 1B, 1E Extended, 3 Extended, 3C Extended
Work Area Format: COW
Length and Format: 2 bytes, RJBF
Description: Defines the traffic direction of the bike lanes on a segment.
The following table contains the values that can appear in the Bike Lane 2 field
Code Value Meaning Description
Blank No bike lane No bike lane exists at this segment
FT FROM node to TO node Bike traffic flows with the segment’s logical direction, i.e. from the FROM node to the TO node.
TF TO node to FROM node Bike traffic flows against the segment’s logical direction, i.e. from the TO node to the FROM node.
TW Two-Way Bikes travel in both directions

BIN - See BUILDING IDENTIFICATION NUMBER

BLOCKFACE ID
Field Names: LEFT BLOCKFACE ID
RIGHT BLOCKFACE ID
Functions: 1 Extended, 1B, 1E Extended, 3 Extended, 3C Extended
Work Area Format: COW
Length and Format: 10 bytes. RJZF
Description: Left Blockface ID is a ten digit number identifying the block face on the left hand side of a segment. Correspondingly, Right Blockface ID identifies the block face on the right hand side of a segment. Block Face is defined as one continuous side of a physical block that is intersected on that side by two other physical through streets. Blockface IDs were established by DoITT’s consultants working on the planimetric feature classes for NYC and are not maintained by the Department of City Planning.
BOARD OF ELECTIONS PREFERRED LGC
Functions: 1E
Work Area Format: MSW and COW
Length and Format: 2 bytes. RJZF
Description: This item is the LGC (the sixth and seventh digits of the 10-digit street code) that corresponds to the NYC Board of Elections’ preferred street name for a given location.
BOROUGH CODE
Functions: All functions
Work Area Format: MSW and COW
Length and Format: 1 byte. Numeric.
Description:
Code Value Meaning
1 Manhattan
2 Bronx
3 Brooklyn
4 Queens
5 Staten Island

BOROUGH/BLOCK/LOT - See BBL

BOROUGH/TAX BLOCK/TAX LOT - See BBL

BROWSE FLAG
Functions: 1, 1A, 1B, 1E, 1N, 2, 3, 3C, BB, BF
Work Area Format: COW
Length and Format: 1 byte. Alphabetic
Description:
Code Value Meaning
Blank All streets or normalized input street
P Primary streets
F Principal streets
R Preferred street Only Functions 1, 1A, 1B. 1E, 2, 3, and 3C. (Not 1N, BB, BF)
See Chapter III.7 for use of Browse Flag with Functions BB and BF.
See Chapter III.8 for use of Browse Flag with Functions 1, 1A, 1B, 1E, 1N, 2, 3, 3C.
BUILDING IDENTIFICATION NUMBER (BIN)
Functions: 1A, BL, BN, 1B (COW only) and AP (COW only)
Work Area Format: MSW and COW
Length and Format: 7 bytes. Numeric
Description: Building Identification Number. A permanent BIN is a seven-digit numerical identifier unique to each building in the City of New York. The first digit is the Borough Code. There are also two types of temporary BINs; those maintained by the Dept. of Buildings (DOB) and those maintained by the Dept. of City Planning (DCP). The temporary BINs assigned by DOB contain the number ‘8’ as the second digit, and the temporary BINs assigned by DCP contain a ‘9’ in the same position. DCP is currently in the process of phasing out all of its temporary BINs.
BUSINESS IMPROVEMENT DISTRICT (BID)
Functions: 1A, 1B, BL, BN
Work Area Format: MSW and COW
Length and Format: 6 bytes, B5SC
Description: The Business Improvement District (BID) field (which was requested by the Fire Department) consists of a borough and five-digit street code (B5SC). Function D may be used to obtain the 32-byte name of the BID. The ‘Street Attribute Indicator’ is set to ‘C’ for BIDs. An example of a Business Improvement District is ‘5 AVE BID’ Note that a BID may not be used as input to Function 1, 1A, 1B, 1E, 2*, and 3*.

CD - See COMMUNITY DISTRICT or COMMUNITY DEVELOPMENT…

CD ELIGIBILITY FLAG - See INTERIM ASSISTANCE ELIGIBILITY INDICATOR

C

CENSUS BLOCK
Field Names:
2000 CENSUS BLOCK,
LEFT 2000 CENSUS BLOCK,
RIGHT 2000 CENSUS BLOCK,
2010 CENSUS BLOCK
LEFT 2010 CENSUS BLOCK,
RIGHT 2010 CENSUS BLOCK
Functions: 1 & 1E (MSW: for 2010 - Regular WA2, for 2000 - Long WA2 Only;), 1 & 1E(COW). 2, 3 (MSW: Long WA2 Only), 3(COW), 3C
Work Area Format: MSW and COW
Length and Format: 4 bytes, numeric
Description: When appended by the CENSUS BLOCK SUFFIX, this area is the smallest geographic area defined by the U.S. Census Bureau for tabulating the census. Generally (but not always) corresponds to a physical city block. Each census block is numbered uniquely within its census tract.
CENSUS BLOCK SUFFIX
Field Names:
2000 CENSUS BLOCK SUFFIX,
LEFT 2000 CENSUS BLOCK SUFFIX,
RIGHT 2000 CENSUS BLOCK SUFFIX,
2010 CENSUS BLOCK SUFFIX,
LEFT 2010 CENSUS BLOCK SUFFIX,
RIGHT 2010 CENSUS BLOCK SUFFIX,
Functions: 1&1E (MSW: for 2010 - Regular WA2, for 2000 - Long WA2 Only;), 1, 1B &1E(COW) 2, 3 (MSW: Long WA2 Only), 3(COW), 3C
Work Area Format: MSW and COW
Length and Format: 1 byte.
Description: This suffix is defined by the U.S. Census Bureau. At the government’s discretion, this field may, or may not, contain data.
CENSUS TRACT
Field Names:
1990 CENSUS TRACT,
LEFT 1990 CENSUS TRACT,
RIGHT 1990 CENSUS TRACT,
2000 CENSUS TRACT,
LEFT 2000 CENSUS TRACT,
RIGHT 2000 CENSUS TRACT
2010 CENSUS TRACT,
LEFT 2010 CENSUS TRACT,
RIGHT 2010 CENSUS TRACT
Functions: 1, 1E, 1B, 2, 3 (MSW: 2010 - Regular WA2; 2000 - Long WA2 Only), 3(COW), 3C
Work Area Format: MSW and COW
Length and Format: 6 bytes, consisting of numeric 4-digit root followed by numeric 2-digit suffix. The root subfield is RJBF and the suffix subfield is RJZF if any. If the tract number contains no suffix, then the suffix subfield is blank.
Description: Geographic area defined by the U.S. Census Bureau for the various decennial censuses. Census tracts for a particular census year are numbered uniquely within borough.
CITY COUNCIL DISTRICT
Functions: 1B (COW), 1E, 2(COW only)
Work Area Format: MSW and COW
Length and Format: 2 bytes.
Description: A district represented by a member of the New York City Council. Consists of an aggregation of Election Districts. There are currently 51 City Council Districts.
CIVIL COURT DISTRICT
Functions: 1E, 1B (COW), 2(COW only)
Work Area Format: MSW and COW
Length and Format: 2 bytes.
Description: A district from which a Civil Court judge is elected. Consists of an aggregation of Election Districts.
COINCIDENT SEGMENT COUNT
Functions: 1, 1E, 3, 3C
Work Area Format: MSW and COW
Length and Format: 1 byte, numeric
Description: The Coincident Segment Count indicates the situation where one road is above another road. Most streets, such as Broadway in Manhattan have a value of ‘1’ in the Coincident Segment Count. However, there are a few streets where the Coincident Segment Count is greater than one. An example of this is Third Avenue and the Gowanus Expressway in Brooklyn. The Gowanus Expressway is above Third Avenue from about 18th Street until 63rd Street. For these segments, the Coincident Segment Count is ‘2’.

COMMUNITY DEVELOPMENT BLOCK GRANT (CDBG) - See INTERIM ASSISTANCE ELIGIBILITY INDICATOR

COMMUNITY DEVELOPMENT ELIGIBILITY FLAG - See INTERIM ASSISTANCE ELIGIBILITY INDICATOR

COMMUNITY DISTRICT (CD)
Functions: 1, 1E, 2, 3, 3C, 1B (COW)
Work Area Format: MSW and COW
Length and Format: 3 bytes. Numeric. The first byte is the Community District Borough Code, and the second and third bytes are the Community District Number, RJZF.
Description: There are 59 community districts in the City of New York, as well as 12 Joint Interest Areas (JIAs). The JIAs are major parks and airports that are not contained within any CD. Examples are Central Park, Van Cortlandt Park, LaGuardia and JFK Airports. The JIAs are the numerically highest items in each borough.
Code Value Meaning
101-112 Manhattan except Marble Hill
164 Central Park
201-212 Bronxexcept Rikers Island (Note: the Marble Hill section of Manhattan is in Bronx CDs 7 and 8)
226 Van Cortlandt Park
227 Bronx Park
228 Pelham Bay Park
301-318 Brooklyn
355 Prospect Park
356 Brooklyn Gateway National Recreational Area
401-414 Queens (Note: the Rikers Island section of the Bronx is in Queens CD 1)
480 LaGuardia Airport
481 Flushing Meadows - Corona Park
482 Forest Park
483 JFK International Airport
484 Queens Gateway National Recreational Area
501-503 Staten Island
595 Staten Island Gateway National Recreational Area

COMMUNITY DISTRICT ELIGIBILITY FLAG - See INTERIM ASSISTANCE ELIGIBILITY INDICATOR

COMMUNITY SCHOOL DISTRICT – see SCHOOL DISTRICT

COMPACT FLAG - See STREET NAME NORMALIZATION FORMAT FLAG

COMPASS DIRECTION
Functions: 2, 3C, 3S
Work Area Format: MSW and COW
Length and Format: 1 byte.
Description: In the case of Function 2, the compass direction identifies, for a pair of input streets that intersect at two distinct locations, which of those two intersections is to be processed. (See Chapter VII.2) In the case of Function 3C, the compass direction identifies which side of the street is to be processed. (See Section VII.5) In the case of Function 3S, if the ‘on’ street intersects the first cross street at two distinct locations, the compass direction identifies which of those two intersections is to be processed. (See Chapter VII.6)
COMPASS DIRECTION FOR INTERSECTION KEY
Functions: 2
Work Area Format: MSW and COW
Length and Format: 1 byte.
Description: If the first two entries in the LIST OF INTERSECTING STREETS are an instance of the two-node case (i.e., they intersect twice), this field contains a compass direction value identifying the intersection in terms of those two streets. If the two streets are not an instance of the two-node case, this field is blank. If both a ‘longitudinal’ compass direction (‘N’ or ‘S’) and a ‘latitudinal’ compass direction (‘E’ or ‘W ’) are valid for this intersection, the longitudinal compass direction value appears in this field.
COMPASS DIRECTION FOR 2nd INTERSECTION
Functions: 3S
Work Area Format: MSW and COW
Length and Format: 1 byte.
Description: If the ‘on’ street intersects the second cross street at two distinct locations, this compass direction identifies which of those two intersections is to be processed. (See Chapter VII.6)
CONDOMINIUM FLAG
Functions: 1A, BL, BN, 1B (COW), AP
Work Area Format: MSW and COW
Length and Format: 1 byte.
Description:
Code Value Meaning
‘C’ Property is a condominium
Blank Property is not a condo.
CONDOMINIUM IDENTIFICATION NUMBER
Functions: 1A, BL, BN, 1B (COW), AP
Work Area Format: MSW and COW
Length and Format: 4 bytes
Description: An identification number assigned by the Department of Finance to each condominium in the city. This field is blank for non-condominiums.
CONGRESSIONAL DISTRICT
Functions: 1E, 1B (COW), 2 (COW only)
Work Area Format: MSW and COW
Length and Format: 2 bytes.
Description: A district of the U.S. House of Representatives. Consists of an aggregation of Election Districts.
CONTINUOUS PARITY INDICATOR
Functions: 1, 1E, 3, 3C, 1B (COW)
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: An ‘address range’ is a sequence of house numbers along an ‘on’ street between (and including) a Low House Number and a High House Number. Every address range has one of three possible parities: odd, even or continuous. An address range of odd parity consists of all odd house numbers along the ‘on’ street between the Low and High House Numbers. An even-parity range consists of all even house numbers between the Low and High House Numbers. A continuous-parity range consists of all house numbers (both even and odd) between the Low and High House Numbers. Most New York City blockfaces contain an address range that is either of even or odd parity. However, some blockfaces have a continuous-parity address range, usually where the opposite side of the street is non-addressable because it is a park, a body of water, etc. Some examples of the continuous parity case in Manhattan are Central Park West (the east side of the street runs along Central Park and is non-addressable, while the west side has both odd and even addresses); Riverside Drive; and the portion of Fifth Avenue that runs alongside Central Park.

If a New York City blockface has a continuous parity address range, Geosupport represents this range as two separate ranges, an odd-parity range and an even-parity range. The practical effect of this depends on the Geosupport function. For Functions 1 and 1E, if an input address lies on a continuous-parity blockface, only the range (i.e., the Low and High House Numbers) whose parity is the same as that of the input address is returned in WA2. For Function 3, if an input street segment contains a continuous parity address range, both the odd and the even ranges are returned, in the WA2 fields called Left Low House Number and Left High House Number for the range of one parity, and in the fields Right Low and High House Numbers for the range of the other parity; note that in this case, in reality both the odd and the even ranges are on the same side of the street, even though they are returned in fields called ‘left’ and ‘right’. For Function 3C, if an input blockface is on a street segment containing a continuous parity address range (regardless of whether the input blockface is on the addressable or the non-addressable side of the segment), both the odd and the even ranges are returned, in the WA2 fields called Low House Number and High House Number for the range of one parity, and in the fields Alternate Low House Number and Alternate High House Number for the range of the other parity.

The field Continuous Parity Indicator indicates, for Functions 1, 1E, 3 and 3C, whether the street segment containing or corresponding to the user input is of the continuous parity type, and if so, which side of the segment is addressable.
Code Value Meaning
Blank The street segment does not have a continuous parity address range
‘L’ or ‘R’ The street segment has continuous parity. In this case, the Continuous Parity Indicator indicates which side of the street segment, the left or the right, is addressable. (Left and right are specified with respect to the direction of increasing addresses along the segment)
COOPERATIVE IDENTIFICATION NUMBER
Functions: 1A, BL, BN, 1B (COW)
Work Area Format: MSW and COW
Length and Format: 4 bytes.
Description: This is an identification number assigned by the Department of Finance to each cooperative in the city. This field is blank for non-coops.
CORNER CODE
Functions: 1A, BL, BN, 1B (COW)
Work Area Format: MSW and COW
Length and Format: 2 bytes
Description:
Code Value Meaning
‘SE’,’SW’,’NE’,’NW’ Tax lot occupies the indicated corner of the physical block
‘CR’ Tax lot occupies more than one corner
Blank Tax lot occupies no corners
COUNTY BOUNDARY INDICATOR
Functions: 3, 3C
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: This field is non-blank when the street segment lies along a borough boundary. The value of this field indicates which side of the segment is out of borough.
Code Value Meaning
‘L’ Left side of segment is out of borough
‘R’ Right side of segment is out of borough
Blank Neither side is out of borough
CROSS STREET NAMES FLAG (a.k.a. EXPANDED FORMAT FLAG)
Functions: 1, 1E, 2, 3, 3C, 1B (COW)
Work Area Format: MSW and COW
Length and Format: 1 byte character.
Description: When this flag is set to ‘E’, the LIST OF STREET NAMES is used to return street names corresponding to the street codes in the LIST OF CROSS STREETS (Functions 1, 1B, 1E, 3 and 3C) or in the LIST OF INTERSECTING STREETS (Function 2). See LIST OF STREET NAMES for related details.

When possible, the BBL and BIN are returned in the output area of Work Area 1 for Functions 1, 1A, 1B, and 1E.

The cross street names feature incurs processing overhead, and should only be used when necessary. Note that Function 1B returns the principal street codes and street names of the cross streets in the Blockface portion of Work Area 2. Therefore it is typically not necessary to set the Cross Street Names flag with Function 1B.
Code Value Meaning
Blank The names of cross or intersecting streets are not returned in the LIST OF STREET NAMES. The BBL an BIN are not returned in the output area of Work Area 1.
‘E’ The names of cross or intersecting streets are returned in the LIST OF STREET NAMES The BIN and BBL of the input address are returned in the output area of Work Area 1.
CROSS STREET REVERSAL FLAG
Functions: 3, 3C
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: This flag indicates the relationship between the order in which the user specified the input cross streets and the direction of increasing addresses along the ‘on’ street.
Code Value Meaning
Blank The direction from Street Name 2 to Street Name 3 (the two input cross street fields) conforms to the direction of increasing addresses
‘R’ The direction from Street Name 2 to Street Name 3 is opposite to the direction of increasing addresses

CROSS SREETS
See LIST OF CROSS STREETS (Functions 1, 1E, 3, 3C, 1B)
See LIST OF INTERSECTING STREET (Function 2)
See LIST OF CROSS STREET CODES (Function 3S)

CURVE FLAG
Functions: 1, 1E, 3, 3C, 1B (COW)
Work Area Format: MSW and COW
Length and Format: 1 byte character
Description: This flag indicates whether the given geographic feature segment is in reality curved. If so, the curve may be an arc of a circle or an irregular curve. When the segment specified by the input data is an arc of a circle, Functions 1 and 1E return Spatial Coordinates that are positioned relative to this arc rather than to the segment’s chord (the imaginary straight line joining the curved feature’s endpoints). When the segment specified by the input data is an irregular curve, Functions 1 and 1E return blanks in the Spatial Coordinate fields (q.v.), and issue a warning with Reason Code value ‘P’. In the case of Functions 3 and 3C, if the input data define a street stretch encompassing more than one segment (because of a T-intersection or bend), the Curve Flag is set ‘on’ (non-blank) if at least one of the constituent segments of the stretch is curved. See also discussion of Segment Length.
Code Value Meaning
Blank Segment is not curved
‘I’ Segment is an irregular curve, i.e., it is curved but it is not an arc of a circle
‘L’ Segment is an arc of a circle on the left side of the line joining the segment’s FROM and TO nodes
‘R’ Segment is an arc of a circle on the right side of the line joining the segment’s FROM and TO nodes

D

DCP PREFERRED LGC
Functions: 1, 1A and BL (regular WA2 only), 2, 3, 3C, BN
Work Area Format: MSW and COW
Length and Format: 2 bytes RJZF
Description: Identifies the local group of street names designated by the Department of City Planning as ‘preferred’ for display purposes for a specific location on a street.
DCP ZONING MAP
Functions: 1A/BL/BN, 1A/BL/BN Extended, 1A/BL Long WA2, 1A/BL TPAD Long WA2, 1B
Work Area Format: COW
Length and Format: 3 bytes
Description: The DCP Zoning Map field contains the DCP Zoning Map number.

DEPARTMENT OF SANITATION SNOW PRIORITY CODE - See DSNY SNOW PRIORITY CODE

DISTANCE BETWEEN DUPLICATE INTERSECTIONS
Functions: 2
Work Area Format: MSW and COW
Length and Format: 5 bytes numeric
Description: When the two input streets intersect exactly twice, this field contains the distance, in feet, between those two intersections.
DOGLEG FLAG
Functions: 3
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: A dogleg is a street configuration in which a street has a displacement or offset as it crosses another street. A non-blank value in the Dogleg Flag indicates that at least one of the cross streets forms a dogleg as it crosses the ‘on’ street, in such a way that at least one side of the ‘on’ street has a blockface encompassing more than one segment.
When Function 3 returns a non-blank value in this flag, the work area represents the ‘innermost’ segment of the dogleg configuration.
The Dogleg Flag value indicates which side or sides of the street has (or have) the long blockface(s).
Code Meaning
Blank Not a dogleg
‘B’ Both sides of the ‘on’ street have long blockfaces formed by doglegs. This can only occur if both cross streets form doglegs as they cross the ‘on’ street.
‘L’ The left side of the street has a long blockface formed by a dogleg
‘R’ The right side of the street has a long blockface formed by a dogleg
A Function 3C call will return information on the long blockface when the user input data specifies a side of a street where there is a long blockface formed by a dogleg or doglegs. The Dogleg Flag will not be set in response to a function 3C call.
DOT STREET LIGHT CONTRACTOR AREA
Functions: 1, 1E, 2, 3, 3C, 1B (COW)
Work Area Format: MSW and COW
Length and Format: 1 byte
Description:
Code Meaning
‘1' Street lights serviced by Manhattan contractors
‘2' Street lights serviced by Bronx contractors
‘3' Street lights serviced by Brooklyn contractors
‘4' Street lights serviced by Queens contractors
‘5' Street lights serviced by Staten Island contractors
‘X' Street light is located on the Brooklyn, Queens boundary
‘N’ Street light is located in one borough, but serviced by a different borough

DSNY ... - See also SANITATION ...

DSNY SNOW PRIORITY CODE
Functions: 1/1E, 1/1E Extended, 1B, 3, 3 Extended, 3C, 3C Extended
Work Area Format: COW
Length and Format: 1 byte character
Description: DSNY (Department of Sanitation) Snow Priority code is used during snow emergencies. It helps DSNY to determine the snow removal schedule, routes and resources needed.
The DSNY (Department of Sanitation) Snow Priority indicates the priority of the street with respect to snow removal. New snow priority codes were assigned with Version 16.4 The snow priority codes are as follows:
Code Value Meaning
C Critical
S Critical
S Sector
H Haulster
V Non-DSNY Street (unchanged)
The DSNY definition of the new codes is as follows:
C - Critical Routes: These routes are comprised of highways (main beds, entrances, exits interchanges), arterial roadways, main travel thoroughfares (single lane and multi-lane), bus routes, that contain emergency services & first responder facilities (Hospitals, EMS, FDNY, NYPD) and schools.
C - Critical Routes: These routes are comprised of highways (main beds, entrances, exits interchanges), arterial roadways, main travel thoroughfares (single lane and multi-lane), bus routes, that contain emergency services & first responder facilities (Hospitals, EMS, FDNY, NYPD) and schools.
S - Sector Routes: Designed to encompass all streets that are not classified as Critical Streets and are wide enough to accommodate a full size DSNY collection truck with a plow attached.
H - Haulster Routes: Designed to service dead ends and streets that cannot be serviced with a collection truck or salt spreader with a plow attached due to narrow street width or tight turning radius (either entering or exiting the street).
Important Note: The old code values (i.e. prior to Version 16.4) are no longer in use. They were P (Primary), S (Secondary) and T (Tertiary)If a user application checks for specific Snow Priority Values, the application will need to be updated
It is also important to note that the new Snow Priority values provided to DCP were for roadbed geography only. Snow Priority values will not be returned for generic geography, unless requested for a future release by DSNY.

DYNAMIC BOCK - See ATOMIC POLYGON

E

s
ELECTION DISTRICT (ED)
Field Names: LEFT ELECTION DISTRICT
RIGHT ELECTION DISTRICT
Function: 1E, 3 (COW only), 3C (COW only), 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 3 bytes
Description: A set of districts defined by the NYC Board of Elections to conduct elections. There are approximately 6,000 Election Districts (EDs) in NYC. Each ED is numbered uniquely within its Assembly District. All of NYC’s higher-level political districts, namely Assembly Districts, City Council Districts, Municipal Court Districts, Congressional Districts and State Senatorial Districts, are defined as aggregates of Eds.

EXPANDED FORMAT FLAG - See CROSS STREET NAMES FLAG EXTENDED MODE SWITCH - See MODE SWTICH

F

FACE CODE
Functions: 1, 1E, 3, 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 4 bytes. Numeric
Description: A Face Code is assigned to each linear geographic feature represented in the LION file. These consist of streets and certain non-street features, such as census boundaries, shorelines and railroad tracks. Face Codes serve as part of LION keys, which identify a unique LION record. Face Code values are assigned uniquely within borough.
FEATURE TYPE CODE
Functions: 1, 1E, 3, 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: Identifies the type of geographic feature represented by the work area
Code Meaning
blank Public street that exists physically, other than a type ‘W’ feature (see below)
‘1' Railroad
‘2' Shoreline
‘3' Census block boundary without physical existence
‘4' Other non-street feature
‘5' ‘Paper street’, i.e., a public street that is legally ‘mapped’ but does not exist physically
‘6' ‘Private street that exists physically
‘7' Physically nonexistent district boundary, other than a type ‘3’ feature (see above)
‘8' Physical Boundary such as a cemetery wall
‘9' Paper street’ that coincides with a non-physical boundary such as a Census block
‘C' CCO (Corporation Council Opinion). Street dedicated for public use (See Glossary)
‘W' Path, non-vehicular, addressable
Note: As of Release 16D, Physical Boundaries, such as cemetery walls, will no longer appear as cross streets in Functions 1/1E, 1B, 2, 3 and 3C
FIRE BATTALION
Functions: 1, 1E, 2, 3 (MSW: Long WA2), 3 (COW), 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 2 bytes
Description: An administrative fire district composed of Fire Companies/
FIRE COMPANY NUMBER
Functions: 1, 1E, 2, 3 (MSW: Long WA2), 3 (COW), 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 3 bytes. Numeric RJZF
Description: The smallest kind of administrative fire district defined by the NYC Fire Department. There are three types, indicated by the Fire Company Type: engine companies, Squad and ladder companies.
FIRE COMPANY NUMBER
Functions: 1, 1E, 2, 3 (MSW: Long WA2), 3 (COW), 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: Fire companies are characterized by the type of apparatus they use to fight fires.
Code Meaning
‘E’ Engine Company
‘L’ Ladder Company
‘Q’ Fire Squad
Note: ‘Q’ may appear as ‘SQ’ on GOAT screens
FIRE DIVISION
Functions: 1, 1E, 2, 3 (MSW: Long WA2), 3 (COW), 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 2 bytes
Description: An administrative fire district composed of Fire Battalions.

FROM NODE - See NODE NUMBER

FROM NODE ID - See NODE NUMBER

FUNCTION 1A/BL VERSION FLAG
Functions: 1A, BL
Work Area Format: MSW and COW
Work Area Format: MSW and COW
Length and Format: 1 byte
Length and Format: Code Meaning
Description:
Code Meaning
‘S’ Standard version - Required for MSW
‘L’ Invalid - No Longer Supported
Blank COW: Standard version
MSW: Invalid

G

GAP FLAG
Functions: 3S
Work Area Format: MSW and COW
Length and Format: 1 byte
Description:
Code Value Meaning
‘E’ Engine Company
‘L’ Ladder Company
‘Q’ Fire Squad
Note: ‘Q’ may appear as ‘SQ’ on GOAT screens
1, 1E, 2, 3 (MSW: Long WA2), 3 (COW), 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 2 bytes
Description: An administrative fire district composed of Fire Battalions.

FROM NODE - See NODE NUMBER

FROM NODE ID - See NODE NUMBER

FUNCTION 1A/BL VERSION FLAG
Function: 1A, BL
Work Area Format: MSW and COW
Length and Format: 1 byte
Description:
Code Meaning
‘S’ Standard version - Required for MSW
‘L’ Invalid - No Longer Supported
Blank COW: Standard version
MSW: Invalid
GAP FLAG
Functions: 3S
Work Area Format: MSW and COW
Length and Format: 1 byte
Description:
Code Value Meaning
Blank No gap, i.e., the ‘on’ street connects this intersection with its predecessor in list. The gap flag in the 1st entry in the list is always blank.
‘G’ A gap exists along the ‘on’ street between this intersection and its predecessor
‘C’ Real Streets Only have been requested, resulting in segment lengths being ‘Combined’ and one or more nodes being omitted between this intersection and its predecessor in the list (COW Only).
‘D’ A dog-leg type gap exists along the ‘on’ street between this intersection and its predecessor
‘N’ A new stretch exists.
For more information on the types of ‘gaps’ that can be returned by Function 3S, see Chapter VII.6
GENERATED RECORD FLAG
Functions: 3, 3C
Work Area Format: MSW and COW
Length and Format: 1 byte/td>
Description: This flag indicates that the geography defined by the input ‘on’ street and two cross streets is not a conventional street segment.  There are several cases: a segment one of whose cross-features is a pseudo-street name (codes C, D); a street stretch formed by consolidating more than one consecutive LION segment (codes B, L, M, R, S and T); or a segment that is part of such a street stretch (types F, G). If the input data simultaneously satisfy the criteria for a Generated Record Flag value of C or D and for some other value, the flag contains the value other than C or D.
‘B’ Record has been generated by consolidating several LION segments to represent a stretch of a street where there is a node that is not at an intersection, such as a bending point (or a consecutive sequence of such nodes).
‘C’ Record generated because one or both nodes of segment lie on the City Limit (Bronx-Westchester or Queens-Nassau border), but segment itself lies entirely within the City. The cross street list for a node on the City Limit contains the special street code assigned to the pseudo-street name CITY LIMIT in the Bronx or Queens, as appropriate.
‘D’ Record has been generated for a dead end segment, i.e. a segment at least one of whose nodes either has no other segments incident at it, or has segments of non-street features only. The cross street list at such a node contains only the special street code assigned to the pseudo-street name DEAD END in the given borough.
‘F’ Record represents a segment that is part of a street stretch that either contains a bending point at which there are no cross streets, or the left side of which is the long blockface of a T-intersection or a consecutive sequence of T-intersections.
‘G’ Record represents a segment that is part of a street stretch, that either contains a bending point at which there are no cross streets, or the right side of which is the long blockface of a T-intersection or a consecutive sequence of T-intersections.
‘L’ Record has been generated to represent the long blockface on the left side of a T-intersection.
‘M’ Record has been generated by consolidating two or more LION segments to represent a stretch of a street containing a node or a consecutive sequence of nodes at which the ‘on’ feature intersects with no streets but intersects with more than one type of non-street feature.
‘R’ Record has been generated to represent the long blockface on the right side of a T-intersection.
‘S’ Record has been generated by consolidating two or more LION segments to represent a stretch of a street containing a node or a consecutive sequence of nodes at which the ‘on’ feature intersects with no streets but intersects with one or more shorelines.
‘T’ Record has been generated by consolidating two or more LION segments to represent a stretch of a street containing a node or a consecutive sequence of nodes at which the ‘on’ feature intersects with no streets but intersects with one or more train tracks.

H

HEALTH AREA
Functions: 1, 1E, 2, 3, 3C, 1B
Work Area Format: MSW and COW
Length and Format: 4 bytes
Description: Districts defined by the NYC Department of Health and used to report statistics on births, deaths, communicable diseases etc. Health Areas are aggregates of Census Tracts.
HEALTH CENTER DISTRICT
Functions: 1, 1E, 2 (COW only), 3 Extended, 3C Extended
Work Area Format: MSW and COW
Work Area Format: 2 bytes
Description: Districts defined by the NYC Department of Health for administrative purposes. Health Center Districts are aggregates of Health Areas.

HEZ - See HURRICANE EVACUATION ZONE

HIGH HOUSE NUMBER - See HOUSE NUMBER

HOUSE NUMBER a.k.a. ADDRESS NUMBER
Field Names: HOUSE NUMBER (WA1 input field, Functions 1, 1A, 1B, 1E,AP);
NORMALIZED HOUSE NUMBER (WA1 output field, Functions 1, 1A, 1B, 1E, AP);
LOW HOUSE NUMBER
HIGH HOUSE NUMBER (WA2 output fields, Functions 1, 1A, 1B, 1E, 3C,AP);
LEFT LOW HOUSE NUMBER,
LEFT HIGH HOUSE NUMBER,
RIGHT LOW HOUSE NUMBER,
RIGHT HIGH HOUSE NUMBER (WA2 output fields, Function 3)
ALTERNATE LOW HOUSE NUMBER,
ALTERNATE HIGH HOUSE NUMBER (WA2 output fields, Function 3C)
UNDERLYING HOUSE NUMBER FOR VANITY ADDRESSES (WA2, 1 and 1E-MSW: Long WA2, 1, 1B, and 1EE-COW, AP? )
Functions: 1, 1A, 1E, 3, 3C, 1B COW only)
Work Area Format: MSW and COW
Length and Format: See Chapter V.2.
Description: If the field name indicates the house number is normalized, for MSW it is in HNI format, and for COW it is in HNS format; otherwise, it is in HND format (see Chapter V.2).
HOUSE NUMBER JUSTIFICATION FLAG
Functions: 1, 1E, 1A, D, DG, DN, 1B?
Work Area Format: COW
Length and Format 1 byte
Description: Indicates whether the HOUSE NUMBERS IN DISPLAY format (HNDs) in the output area should be left-justified or right-justified.
Code Value Meaning
‘L’ or Blank Left-justify Normalized House Numbers (default)
‘R’ Right-justify Normalized House Numbers
HOUSE NUMBER NORMALIZATION LENGTH
Functions: 1, 1E, 1A, 1B, D, DG, DN
Work Area Format: COW
Length and Format: 2 bytes, numeric
Description: Indicates the length requested for the HOUSE NUMBERS IN DISPLAY format (HNDs) in the output area. Valid values are between 12 and 16. If the field is left blank, the default is 12. For more information, see Chapter V.2.
HURRICANE EVACUATION ZONE (HEZ)
Function: 1/1E, 1/1E Extended, 1B
Work Area Format: COW
Length and Format: 2 bytes, alphanumeric, RJBF
Description: Information used by Emergency Management (previously known as Office of Emergency Management (OEM)) in emergency situations.
New York City’s hurricane contingency plans are based on six evacuation zones: 1, 2, 3, 4, 5, 6.  The value of 0 represents water polygons and the value of X indicates land that is not part of an evacuation zone.
Value Description
0 Coastal Water polygon
1-6 Hurricane Evacuation Zone designation
X Land not part of an evacuation zone
Additional information may be found at http://www1.nyc.gov/site/em/ready/hurricane-evacuation.page

I

INSTRUCTIONAL DIVISION - See INSTRUCTIONAL REGION

INTERIM ASSISTANCE ELIGIBILITY INDICATOR (IAEI) - a.k.a. CD Eligibility Flag

INTERIM ASSISTANCE ELIGIBILITY INDICATOR (IAEI) - a.k.a. CD Eligibility Flag
Functions: 1, 1E, 2 (COW only), 3, 3C, 1B
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: Indicates whether the input location is in a census tract that meets the U.S. Department of Housing and Urban Development (HUD) criteria to be eligible for Community Development Block Grant (CDBG) funding. A census tract is eligible for CDBG funding if at least 51.00% of the residents are low- and moderate-income persons (less than 80% of the Median Family Income) and 50% of its total floor area must be comprised of residential usage. All other census tracts are ineligible.
In Release 19B, the ‘CD Eligibility’ values were updated to reflect more current data. Updated income data was provided by HUD and residential usage was calculated by the Department of City Planning (DCP) using PLUTO data (18v2.1).
Code Value Meaning
‘E’ Input location is in a CD-eligible census tract
‘I’ Location is not in a CD-eligible census tract
Blank Location is in a census tract, the CD-eligibility status of which is unknown to the Geosupport System.(Note: This is an error condition and should be reported).

INTERSECTING STREETS - See LIST OF INTERSECTING STREETS

INTERSECTION REPLICATION COUNTER
Functions: 2
Work Area Format: MSW and COW
Length and Format: 1 byte, numeric
Description: The Intersection Replication Counter is non-blank only if the two streets intersect more than once, in which case this field contains the number of such intersections.
INTERIOR LOT FLAG
Functions: 1A, BL, BN
Work Area Format: MSW and COW
Length and Format: 1 byte
Description:
Code Value Meaning
‘I’ Tax lot is interior to physical block, i.e., it has no street frontages.
Blank Tax lot has at least one street frontage

INTERNAL LABEL POINT - See SPATIAL COORDINATES OF THE TAX LOT CENTROID

IRREGULARLY-SHAPED LOT FLAG
Functions: 1A, BL, BN
Work Area Format: MSW and COW
Length and Format: 1 byte
Description:
Code Value Meaning
‘I’ Tax lot is irregularly-shaped, i.e., non-rectangular
Blank Tax lot is rectangular

JOINT INTEREST AREA (JIA) - See COMMUNITY DISTRICT

L

LATITUDE, LONGITUDE
Functions: 1/1E Extended, all variations of 1A/BL/BN (viz. Regular, Long and Extended), 1B, 2W, 3 Extended, 3C Extended
Work Area Format: COW
Length and Format: Latitude: 9 bytes
Longitude: 11 bytes
Description: Spatial coordinates based on the lines of latitude and longitude.  Lines of latitude measure the north-south position between the poles with the equator defined as 0 degrees. Lines of longitude (or meridians) measure the east-west position, with the prime meridian running through Greenwich, England.  For NYC, Latitude is always positive and Longitude is always negative. 
The latitude and longitude of a location are calculated based on the spatial coordinates (x,y) returned for that location. As a result, the latitude and longitude returned by the Address Processing functions (e.g. 1/1E Extended) will be somewhat different from the values returned by Tax Lot and Building processing functions (e.g. 1A/BL/BN). See also SPATIAL COORDINATES and SPATIAL COORDINATES OF THE TAX LOT CENTROID.

LEFT 1990 CENSUS TRACT - See CENSUS TRACT.
LEFT 2000 CENSUS BLOCK - See CENSUS BLOCK.
LEFT 2000 CENSUS BLOCK SUFFIX - See CENSUS BLOCK SUFFIX.
LEFT 2000 CENSUS TRACT - See CENSUS TRACT.
LEFT 2010 CENSUS BLOCK - See CENSUS BLOCK.
LEFT 2010 CENSUS BLOCK SUFFIX - See CENSUS BLOCK SUFFIX.
LEFT 2010 CENSUS TRACT - See CENSUS TRACT.
LEFT ASSEMBLY DISTRICT - See ASSEMBLY DISTRICT.
LEFT BLOCKFACE ID - See BLOCKFACE ID.
LEFT ELECTION DISTRICT - See ELECTION DISTRICT.

LENGTH IN FEET FROM PREVIOUS NODE
Functions: 3S
Work Area Format: MSW and COW
Length and Format: MSW: 3 bytes packed; COW: 5 bytes numeric RJZF
Description: The length between two nodes.

LGI - See LIST OF GEOGRAPHIC IDENTIFIERS

LION KEY
Functions: 1, 1E, 3, 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 10 bytes. Numeric
Description: The LION Key identifies a record in the CSCL file and relates to predecessor file known as LION. It consists of:
BOROUGH CODE ( 1 byte)
FACE CODE (4 bytes)
SEQUENCE NUMBER (5 bytes)

LION NODE - See NODE NUMBER LION NODE ID - See NODE NUMBER LION NODE NUMBER - See NODE NUMBER LION SEGMENT ID See SEGMENT ID LION SEQUENCE NUMBER - See SEQUENCE NUMBER LIST OF ADDRESS RANGES - See LIST OF GEOGRAPHIC IDENTIFIERS

LIST OF BUILDINGS ON TAX LOT
Functions: 1A and BL - Long WA2 only
Work Area Format: MSW and COW
Length and Format: 17,500 bytes, consisting of 2,500 slots for 7-byte BINs
Description: List of the BUILDING IDENTIFICATION NUMBER (BIN) of each building on the tax lot. See Chapter VI.6.
LIST OF BUILDINGS ON TAX LOT
Functions: 1A and BL - Long WA2 only
Work Area Format: MSW and COW
Length and Format: 17,500 bytes, consisting of 2,500 slots for 7-byte BINs
Description: List of the BUILDING IDENTIFICATION NUMBER (BIN) of each building on the tax lot. See Chapter VI.6.
LIST OF CROSS STREET CODES
Functions: 3S
Work Area Format: MSW and COW
Length and Format: MSW: 8 bytes, packed decimal, consisting of 2 slots for intersecting PB5SCs. COW: 40 bytes, numeric, consisting of 5 slots for intersecting B7SCs.
Description: MSW: For each intersecting street, in general, this is the lowest and second lowest PB5SCs for the cross streets, as described below in COW. COW: For each intersecting street, this is a list of up to five B7SCs, starting, in general (see Note below), with the lowest B7SC, followed by the next lowest, followed by the remaining B7SCs in ascending order.
The purpose of the ordering of the first two street codes is to facilitate the ability of users to form consistent keys for geographic retrieval of application data.
Note 1: In order to provide the user with the most meaningful information, ‘normal’ streets will be listed first, followed by ‘special’ streets, such as Ramps and Exits. Railroads, Shorelines and Borough Boundaries will appear next, followed by Named Intersections, CITY LIMITs, DEAD ENDs and BENDs. This will occur even if the ‘special’ streets have lower street codes than the ‘normal’.
Note 2: To avoid unnecessary listing of BENDs, Function 3S lists a BEND only if the angle of the bend is 60 degrees or more. (Prior to Release 16D, a bend was listed if the angle was 20 degrees or more.) Also, a bend is not included in the list of cross streets when another real street intersects there as well.
Note 3: Since Function 3S returns B7SCs, it is now possible for two streets to have the same B5SCs and different B7SCs, e.g. in Brooklyn, at the intersection of Clinton Street with Livingston Street and Aitken Place, Livingston Street and Aitken Place have the same B5SC (3-56530) but different B7SCs (3-56530-01 and 3-56530-02 respectively).
LIST OF CROSS STREETS
Field Names: LIST OF CROSS STREETS AT LOW ADDRESS END
LIST OF CROSS STREETS AT HIGH ADDRESS END
Functions: 1/1E Regular, 1/1E Extended (COW), 3, 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: - MSW: 20 bytes, consisting of slots for up to five 4-byte PB5SCs. ‘Empty’ slots contain packed zeros.
• COW (Regular): 30 bytes, consisting of slots for up to five 6-byte B5SCs. ‘Empty’ slots contain either numeric zeros or blanks.
• COW (1/1E Extended): 40 bytes, consisting of slots for up to five 8-byte B7SCs. ‘Empty’ slots contain either numeric zeros or blanks. This list is in addition to the B5SC (30 bytes) list.
Description: A list of PB5SCs for MSW and B5SCs (and B7SCs) for COW (and COW 1/1E Extended), for up to five streets incident upon a delimiting node (endpoint) of a blockface or street segment. The number of non-empty list entries is returned in the corresponding WA2 field NUMBER OF CROSS STREETS AT (LOW or HIGH) ADDRESS END. It is possible for the list to be entirely empty. If the node lies on a borough boundary, the list may contain streets from both boroughs. Subject to the space limitation, the list may include the pseudo-streets ‘City Limit’, ‘Dead End’ and ‘Bend’. The inclusion of ‘Bend’ in the list indicates that the node is a bending point of the ‘on’ street, not that it is a bending point of a cross street (although that may also be true). The purpose of the ordering of the first two street codes is to facilitate the ability of users to form consistent keys for geographic retrieval of application data.
Special handling has been given to Railroads, Shorelines, Coincident Streets and streets where two street names having different B5SCs are both valid (a.k.a. Special Address ‘Type B’ situation)
Note: As a result of this special handling, the first one or two street codes in the lists of intersecting streets may not always be the lowest two street codes. For example a railroad or shoreline would now be put last in the list, even if they have lower street codes than the other intersecting streets.
Some examples follow:
- Consider the situation of coincident street features, e.g. 3rd Avenue and Gowanus Expressway in Brooklyn. The Gowanus Expressway is above 3rd Avenue between approximately 18th Street and 65th Street.
  • If a user issues a Function 3 call requesting information about the segment of 3rd Avenue between 19th and 20th Streets, Geosupport will recognize that 3rd Avenue and the Gowanus Expressway are coincident streets and will not return Gowanus Expressway as an intersecting street. Please note that Geosupport will also accept as input Gowanus Expressway between 19th and 20th Streets. With this input, 3rd Avenue will not be listed as a cross street at either end.
  • If a user issues a Function 3S call, requesting the stretch on 3rd Avenue between 40th Street and 50th Street, Geosupport will recognize that 3rd Avenue and Gowanus Expressway are coincident streets and will not list them as intersecting.
- Consider the situation where a railroad is determined to be one of the cross streets. An example exists in Queens at Kneeland Street between Queens Boulevard and Dead End.
  • A Function 3 call will return QUEENS BOULEVARD and LONG ISLAND RAILROAD as cross streets at the low end. Even though the Long Island Railroad has a numerically smaller street code than Queens Boulevard, it is listed after Queens Boulevard.
- Consider the situation where two street names, with different street codes, are valid for the same blockface. An example exists in Queens where 207th Street and Clearview Expressway are both valid between 39th Avenue and Boyce Avenue.
  • o A Function 3 call will be accepted with either street name (viz. 207th Street or Clearview Expressway) as the on-street.

LIST OF CROSS STREETS AT HIGH ADDRESS END - See LIST OF CROSS STREETS

LIST OF CROSS STREETS AT LOW ADDRESS END - See LIST OF CROSS STREETS

LIST OF GEOGRAPHIC IDENTIFIERS (LGI)
Functions: 1A and BL - regular WA2, BN
Work Area Format: MSW and COW
Length and Format: 756 bytes total, consisting of space for 21 36-byte entries, each entry having fields for the following data items:/td>
Low House Number of Address Range
High House Number of Address Range
B5SC
DCP-Preferred LGC
BIN
Entry Type Code
Side of Street Indicator.
Description: The List of Geographic Identifiers (LGI) is intended to provide a comprehensive geographic profile of a tax lot by listing, so far as the information is known and space allows, all of the lot’s buildings; all of the street addresses and non-addressable street frontages of each building; all of the lot’s ‘vacant frontages’ (i.e., street frontages of the lot not associated with buildings); and any NAPs associated with the lot. The LGI contains space for up to 21 entries. The number of non-empty entries is indicated in the WA2 field NUMBER OF GEOGRAPHIC IDENTIFIERS. The types of entries that the LGI can contain are as follows:
List of Geographic Identifiers - Possible Entry Types
Entry Type Code Represents Description
Blank Address range A real address range of a building on a given tax lot. There are values in the Low House Number, High House Number, B5SC, DCP-Preferred LGC, Side of Street Indicator and BIN fields. A single address is represented as an address range in which the low and high house numbers are identical.
B NAUB A Non-Addressable Un-named Building (NAUB) (see Chapter VI.3). The Low and High House Number and Side of Street Indicator fields are blank. The B5SC and DCP-Preferred LGC fields usually contain the street code and LGC, correspondingly, of the street nearest to or most accessible to the NAUB, but they may be blank. The BIN field contains a meaningful value. Note: If the NAUB has frontages on more than one street, there are multiple type B entries to represent all of the NAUB’s street frontages.
F Vacant Street
Frontage
A street frontage of the tax lot at which there are no buildings (including NAUBs) and to which no pseudo-addresses have been assigned. The Low and High House Number, BIN and Side of Street Indicator fields are empty. There are values in the B5SC and DCP-Preferred LGC fields.
G NAP of a
Complex
A Non-Addressable Place name (NAP) of a complex of buildings and/or other geographic features, usually on a large site or superblock (see Chapter III.6). The house number and BIN fields are empty. The B5SC, DCP-Preferred LGC, and Side of Street Indicator fields contain the values of these items assigned to the NAP.
N NAP of a A NAP of a building or other geographic feature that is not part of Simplex a complex (see Chapter III.6). The house number fields are empty. The B5SC, DCP-Preferred LGC, and Side of Street Indicator fields contain the values of these items assigned to the given NAP. The BIN field is non-empty only if the NAP represents a building.
Q Pseudo-Address Range A pseudo-address range assigned to a vacant street frontage of the tax lot. There are values in the Low House Number, High House Number, B5SC, DCP-Preferred LGC and Side of Street Indicator fields. A single address is represented as an address range in which the low and high house numbers are identical. The BIN field is empty
R Real Street of a
Vanity Address
Entry indicates the street and the side of that street on which the building entrance having a vanity address is really located and for which no other address for that building exists. For a discussion of vanity addresses, see Chapter V.9. In a type R entry, the Low and High House Number fields are empty, and there are non-empty values in the B5SC, DCP-Preferred LGC, Side of Street Indicator and BIN fields. Whenever the LGI contains a type R entry, it also contains a type V entry for the associated vanity address
V Vanity Address A vanity address or address range. For a detailed discussion of vanity addresses, see Chapter V.9. There are non-empty values in the Low House Number, High House Number, B5SC, DCP-Preferred LGC, Side of Street Indicator and BIN fields. A single address is represented as an address range in which the low and high house numbers are identical. Whenever the LGI contains a type V entry, it also contains an either an address range entry or a type R entry that indicates the street on which the associated building entrance is really located.
W Blank-Wall Bldg Frontage A building frontage along a street that is not associated with any addresses, such as some building facades with no entrances. The Low and High House Number and Side of Street Indicator fields are blank. There are values in the B5SC and DCP-Preferred LGC fields. The BIN field contains a meaningful value. Note: Type W entries exist only for buildings that also have at least one real address range entry. If a building has no real address ranges, the building is a NAUB, and its street frontages, if any, are represented by type B entries rather than type W entries.
X NAP of a Constituent Entity of a Complex A NAP of a constituent entity of a complex. (The NAP of the entire complex is represented by a separate entry of type G.) The house number fields are empty. The B5SC, DCP-Preferred LGC and Side of Street Indicator fields contain the values of these items assigned to the NAP. The BIN field is non-empty only if the NAP represents a building.

The combination of fields in an LGI entry that contain information depends on the entry type, as indicated in the following table:

List of Geographic Identifiers - Which Fields Contain Values By Entry Type

Entry Type Code Entry Type Low & High House Numbers B5SC LGC Side of Street Indicator BIN
blank Real Address Range
B NAUB (*) (*)
F Vacant Street Frontage
G NAP of a complex
N NAP of a complex (\**)
Q Pseudo-Address Range
R Real Street of Vanity Address
V Vanity Address
W Blank-Wall Building Façade
X NAP of a constituent entity of a complex (\**)

(*) NAUB entries may or may not contain B5SC and LGC values. An entry for a NAUB contains a B5SC value and an LGC value only if the GSS staff has determined that the NAUB fronts on, is adjacent to or is principally accessible from a particular street.

(**) The BIN field is non-empty only if the NAP represents a building.

The LGI’s entries are ordered so that entries with non-empty BINs are listed first, grouped by BIN. Except for a special case (alternative borough for Marble Hill and Rikers Island - see Chapter V.7), if the input address is a real address, the first group of entries in the LGI are those for the BIN corresponding to the input address, and (except for alternative street records for Ruby Street - see Chapter V.8) the address range encompassing the input address is the very first entry in the LGI. After all the entries with non-empty BINs are listed, any entries with empty BINs, such as entries for pseudo-address ranges, are listed in no particular order as space allows. If the input address is a pseudo-address range, it may or may not appear in the LGI, depending on space and on the order in which the non-BIN entries happen to be listed.

LIST OF GEOGRAPHIC IDENTIFIERS OVERFLOW FLAG - See LGI OVERFLOW FLAG

LIST OF INTERSECTING STREETS – See also LIST OF CROSS STREETS
Function: 2
Work Area Format: MSW and COW
Length and Format: MSW: 20 bytes, consisting of slots for up to five 4-byte PB5SCs. ‘Empty’ slots contain packed zeros. COW: 30 bytes, consisting of slots for up to five 6-byte B5SCs. ‘Empty’ slots contain numeric zeros or blanks.
Description: A list of PB5SCS for MSWs and B5SCs for COWs for up to five streets incident upon the intersection. The field NUMBER OF INTERSECTING STREETS contains the number of non-empty entries in the list. If the intersection lies on a borough boundary, the list may contain streets from both boroughs. Subject to the space limitation, the list may include the two input streets, and may include the pseudo-streets ‘City Limit’ and ‘Dead End’. The list never includes the pseudo-street ‘Bend’. The list always contains at least one entry (it contains precisely one entry in the case of a bending point of a street at which there are no other streets). The street codes of the input streets may, or may not, be included in the list (depending upon their numerical value.) Note, special handling has been given to Railroads, Coincident Street Features, etc. As a result of this special handling, the first one or two street codes in the list of intersecting streets may not always be the lowest two street codes. See LIST OF CROSS STREETS for further description and examples of the special handling.
LIST OF SEGMENT IDS
Functions: 3 and 3C
Work Area Format: COW
Length and Format: 500 bytes, consisting of a count of segment ids and 70 slots for 7-byte Segment IDs
Description: This list is generated only if Auxiliary Segment Switch is set to ‘Y’. See Chapter VII.4 and Appendix13.
LIST OF STREET CODES
Functions: 1*, 2, 3*, BB, BF
Work Area Format: COW
Length and Format: 80 bytes, consisting of 10 fields for B7SCs
Description: List of borough and 7-byte street codes, corresponding to the LIST OF STREET NAMES. The number of street codes in the list is returned in the WA1 output field NUMBER OF STREET CODES AND STREET NAMES IN LIST.
LIST OF STREET NAMES (WA1 output field)
Functions: 1*, 2, 3*, BB, BF
Work Area Format: MSW and COW
Length and Format: 320 bytes, consisting of 10 fields for street names, each 32 bytes.
Description: This field is used by several Geosupport features (see below) to return a list of street names. The number of street names in the list is returned in the WA1 output field NUMBER OF STREET NAMES IN LIST for MSWs, and in the WA1 output field NUMBER OF STREET CODES AND STREET NAMES IN LIST for COWs.
The similar names feature uses the List of Street Names to return up to ten street names deemed ‘similar’ to a rejected input street name (see Chapter III.5).
The browse functions, Functions BB and BF, use the List of Street Names to return up to ten normalized street names in alphabetical order as part of a street name browse (see Chapter III.7).
The local street name validation feature uses the List of Street Names to return up to four locally valid alias street names corresponding to a street name rejected as locally invalid (see Chapter IV.5).
The cross street names feature (see CROSS STREET NAMES FLAG) uses the List of Street Names to return street names corresponding to the street codes in the LIST OF CROSS STREETS (Functions 1, 1E, 3 and 3C) or the LIST OF INTERSECTING STREETS (Function 2).
In the case of Functions 1, 1E, 3 and 3C, the first five 32-byte street name fields in the List of Street Names are used for the street names corresponding to the street codes in the LIST OF CROSS STREETS AT LOW ADDRESS END; the second five 32-byte street name fields in the List of Street Names are used for the street names corresponding to the street codes in the LIST OF CROSS STREETS AT HIGH ADDRESS END. The actual number of street names is found in Work Area 2 in the fields which provide the number of cross streets at each end of the street segment.
In the case of Function 2, the first five 32-byte street name fields in the List of Street Names are used for the street names corresponding to the street codes in the LIST OF INTERSECTING STREETS. The actual number of street names is found in Work Area 2 in the field which provides the number of intersecting streets at the specified intersection.
LOCATIONAL STATUS OF SEGMENT
Functions: 3, 3C
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: Indicates locational status of segment per codes below.
Code Meaning
‘H’ Segment internal to a block, but not a Dead End (A Land Hook)
‘I’ Dead End Segment
‘X’ Tract Boundary Segment (other than borough boundary)
‘1' Segment bordering Manhattan
‘2' Segment bordering Bronx
‘3' Segment bordering Brooklyn
‘4' Segment bordering Queens
‘5' Segment bordering Staten Island
‘9' Segment bordering City Limits

LONGITUDE - See LATITUDE

LOW HOUSE NUMBER - See HOUSE NUMBER

MARBLE HILL/RIKERS ISLAND FLAG - See ALTERNATIVE BOROUGH FLAG

M

MODE SWITCH
Functions: 1, 1E, 1A, 3, 3C, BL, BN
Work Area Format: COW Only
Length and Format: 1 byte
Description: Indicates request for Extended Work Area 2 for the supported functions. These extended work areas contain street names in addition to Street Codes. Users no longer have to make separate D, DG, or DN calls to get the street names. In addition, CSCL data is returned in the extended Work Area 2. See [Appendix 13](/appendices/appendix13/) for the Work Area layouts. Also, see Chapter II.7.
Code Meaning
‘X’ Extended information in Extended WA2 requested
Blank Extended information not requested (default)

N

NEIGHBORHOOD TABULATION AREA (NTA) CODE
Field Names: NTA or NTA CODE
Functions: 1, 1 Extended, 1E, 1E Extended, 1B, 3, 3 Extended, 3C, 3C Extended
Work Area Format: COW
Length and Format: 4 bytes alphanumeric
Description: The Neighborhood Tabulation Areas (NTAs) are aggregations of census tracts that reflect the 2010 Census. The NTAs are assigned a 4-byte code and a 75-byte name. They are used by the Population Division of the Department of City Planning. See [Appendix 16](/appendices/appendix16/) for a description of the NTA’s history and significance.
The first two bytes of the NTA code are an alphabetic borough code as follows:
Code Borough
MN Manhattan
BX Bronx
BK Brooklyn
QN Queens
SI Staten Island
The remaining two bytes are numeric and uniquely define the NTA.

NODE ID - See NODE NUMBER

NODE NUMBER (a.k.a. NODE ID)
Field Names: FROM NODE
FROM NODE ID
TO NODE
TO NODE ID
Functions: 2, 3 (COW only), 3C (COW Only), 3S (COW Only), 1B (COW Only)
Work Area Format: MSW and COW
Length and Format: 7 bytes. Numeric
Description: A node is an endpoint of a geographic feature segment represented in CSCL/LION. Most nodes are points where a feature bends or terminates or where two features intersect in CSCL/LION. Each node has a node ID assigned to it, which is unique in the entire city. Node ID assignments are permanent; if a node is deleted from CSCL, its node ID is retired and is never reassigned to a different node.
A Node ID may be used to identify an intersection or the end points of a segment. An end point node is often referred to as a From Node or a To Node.

NORMALIZED HOUSE NUMBER - See HOUSE NUMBER

NTA - See NEIGHBORHOOD TABULATION AREA (NTA) CODE

NTA CODE - See NEIGHBORHOOD TABULATION AREA (NTA) CODE

NTA NAME - See also NEIGHBORHOOD TABULATION AREA (NTA) CODE
Field Names: NTA NAME
Functions: 1 Extended, 1E Extended, 1B, 3 Extended, 3C Extended
Work Area Format: COW
Length and Format: 75 bytes alphanumeric
Description: See NEIGHBORHOOD TABULATION AREA (NTA) CODE
NUMBER OF BUILDINGS ON TAX LOT
Functions: 1A, BL - long WA2 only
Work Area Format: MSW and COW
Length and Format: 4 bytes numeric.
Description: Indicates the number of entries in the LIST OF BUILDINGS. Maximum value is 2,500
NUMBER OF CROSS STREETS
Field Names: NUMBER OF CROSS STREETS AT LOW ADDRESS END,
NUMBER OF CROSS STREETS AT HIGH ADDRESS END
Functions: 1, 1E, 3, 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: One byte, containing a numeric digit from 0 to 5.
Description: Indicates the number of non-empty entries in the corresponding LIST OF CROSS STREETS.

NUMBER OF CROSS STREETS AT HIGH ADDRESS END - See NUMBER OF CROSS STREETS

NUMBER OF CROSS STREETS AT LOW ADDRESS END - See NUMBER OF CROSS STREETS

NUMBER OF GEOGRAPHIC IDENTIFIERS
Functions: 1A and BL - regular WA2 only, BN, AP
Work Area Format: MSW and COW
Length and Format: 2 bytes for MSW; 4 bytes for COW
Description: Indicates the number of entries in the LIST OF GEOGRAPHIC IDENTIFIERS. For Function AP, the number is always ‘0001’
NUMBER OF INTERSECTING STREETS
Functions: 2
Work Area Format: MSW and COW
Length and Format: One byte, containing a numeric digit from 1 to 5.
Description: Indicates the number of non-empty entries in the LIST OF INTERSECTING STREETS.
NUMBER OF PARKING LANES
Functions: 1/1E Extended, 1B, 3 Extended, 3C Extended
Work Area Format: COW
Length and Format: 2 bytes, RJBF.
Description: The number of lanes in a carriageway (roadway) that are reserved for parking of vehicles. The number of parking lanes were determined by DoITT’s consultants working on the planimetric feature classes for NYC.
NUMBER OF STREET CODES AND STREET NAMES IN LIST
Functions: 1*, 2, 3*, BB, BF
Work Area Format: COW
Length and Format: 2 bytes, Numeric
Description: Indicates the number of street names returned in the LIST OF STREET NAMES, corresponding to the number of street codes returned in the LIST OF STREET CODES..
NUMBER OF STREET FRONTAGES OF LOT
Functions: 1A, BL, BN
Work Area Format: MSW and COW
Length and Format: 2 bytes, RJZF.
Description: Indicates the number of streets on which the given lot has at least one frontage.
NUMBER OF STREET NAMES IN LIST (WA1 output item)
Functions: 1*, 2, 3*, BB, BF
Work Area Format: MSW
Length and Format: 2 bytes, packed decimal
Description: Indicates the number of street names returned in the LIST OF STREET NAMES.
NUMBER OF TOTAL LANES
Functions: 1/1E Extended, 1B, 3 Extended, 3C Extended
Work Area Format: COW
Length and Format: 2 bytes, RJBF.
Description: The total number of lanes in a carriageway (roadway) including travel lanes and parking lanes. The total number of lanes were determined by DoITT’s consultants working on the planimetric feature classes for NYC.
NUMBER OF TRAVEL LANES
Functions: 1/1E Extended, 1B, 3 Extended, 3C Extended
Work Area Format: COW
Length and Format: 2 bytes, RJBF
Description: The number of lanes in a carriageway (roadway) that are designated for the movement of vehicles traveling from one destination to another. The number of travel lanes were determined by DoITT’s consultants working on the planimetric feature classes for NYC.

P

PARKING LANES - See NUMBER OF PARKING LANES

PLATFORM INDICATOR - See WORK AREA FORMAT INDICATOR

POLICE PATROL BOROUGH
Functions: 1, 1X, 1E, 1EX, 2, 2W, 3, 3X, 3C, 3CX, 1B
Work Area Format: COW Only
Length and Format: 2 bytes
Description: Police Patrol Boroughs are sub-borough geographic areas defined by the Police Department. They are composed of Police Precincts. Since the Police Department is supporting the Police Patrol Borough field, it is recommended that it be used.. Geosupport still returns the 1-byte POLICE PATROL BOROUGH COMMAND field to support those existing applications that access it.
Code Meaning
MS Manhattan South
MN Manhattan North
BX Bronx
BS Brooklyn South
BN Brooklyn North
QN Queens North
SI Staten Island
QS Queens South
POLICE PATROL BOROUGH COMMAND (See also POLICE PATROL BOROUGH)
Functions: 1, 1E, 2, 3, 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: These are sub-borough geographic areas defined by the Police Department. They are composed of Police Precincts.
Code Meaning
1 Manhattan South
2 Manhattan North
3 Bronx
4 Brooklyn South
5 Brooklyn North
6 Queens North
7 Staten Island
8 Queens South

Note: It is recommended that you use the POLICE PATROL BOROUGH field (not the POLICE PATROL BOROUGH COMMAND field) since the Police Department is supporting the POLICE PATROL BOROUGH field.

POLICE PRECINCT
Functions: 1, 1E, 2, 3, 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 3 bytes. RJZF.
Description: Police Patrol Borough Commands are sub-divided into Police Precincts which are defined by the Police Department
POLICE SECTOR
Functions: 1/1E Extended, 1B, 2, 2W, 3 Extended, 3C Extended
Work Area Format: COW
Length and Format: 4 bytes. RJBF.
Description: In order to support Neighborhood Policing, the NYC Police Department has divided each precinct into four or five fully-staffed Police Sectors. The Police Sectors correspond, as much as possible, to the boundaries of actual established neighborhoods.
The Police Sector field consists of the Precinct Number followed by a letter, e.g. 114A.
POLICE SERVICE AREA
Functions: 1/1E Extended, 1B
Work Area Format: COW
Length and Format: 1 byte
Description: The NYC Police Department Housing Bureau is responsible for the safety of residents, employees, and visitors in New York City Housing Authority developments. The Housing Bureau Police are stationed in Police Service Areas (PSAs), each of which provides services to a set of housing developments. Note that not all housing developments are assigned to a PSA.
The Police Service Area field consists of one byte that designates a PSA, e.g. PSA 3 patrols housing developments in several precincts in Brooklyn North. When an address is not part of a housing development, the field is blank.

PUBLIC USE MICRODATA AREA (PUMA) CODE - See PUMA CODE

PUMA CODE
Field Names: PUMA CODE
Functions: 1 Extended, 1E Extended, 1B, 3 Extended, 3C Extended
Work Area Format: COW
Length and Format: 5 bytes, RJZF
Description: PUMAs (Public Use Microdata Areas) are approximations of New York City's Community Districts which were developed for use with the Census Bureau's Public Use Microdata Samples (PUMS). In order to make the boundaries consistent with PUMAs, NTAs were created using whole census tracts, from the 2010 census, within PUMAs. For more information on the history and significance of NTAs and PUMAs, see Appendix 16. See also NEIGHBORHOOD TABULATION AREA (NTA) CODE

R

REAL STREET ONLY FLAG
Functions: 3S
Work Area Format: COW
Length and Format: 1 byte. Alphabetic
Description:
Code Value Meaning
Blank All streets are returned
R Real streets only (not Bends or Non-Street Features

RIGHT 1990 CENSUS TRACT - See CENSUS TRACT.
RIGHT 2000 CENSUS BLOCK - See CENSUS BLOCK.
RIGHT 2000 CENSUS BLOCK SUFFIX - See CENSUS BLOCK SUFFIX.
RIGHT 2000 CENSUS TRACT - See CENSUS TRACT.
RIGHT 2010 CENSUS BLOCK - See CENSUS BLOCK.
RIGHT 2010 CENSUS BLOCK SUFFIX - See CENSUS BLOCK SUFFIX.
RIGHT 2010 CENSUS TRACT - See CENSUS TRACT.
RIGHT ASSEMBLY DISTRICT - See ASSEMBLY DISTRICT.
RIGHT BLOCKFACE ID - See BLOCKFACE ID.
RIGHT ELECTION DISTRICT - See ELECTION DISTRICT.

ROADBED REQUEST SWITCH
Functions: 1 1, 1E, 3S, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: Indicates request for Roadbed information for roads that are divided into two or more roadbeds. If Roadbed information is requested for a street that is not divided, Geosupport returns the generic information. For functions 1 and 1E, the Segment Type Code will indicate the type of information that is being returned. For more information on function 3S see Chapter VII.6.
Code Meaning
‘R’ Roadbed information requested
Blank Generic (non-roadbed) information requested (default)
RPAD BUILDING CLASSIFICATION CODE
Functions: 1A, BL, BN, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 2 bytes
Length and Format: 2 bytes
Description: This is a set of land use/building classification codes defined by the Real Property Assessment Division (RPAD) of the Department of Finance.  If a tax lot has more than one building or land use, RPAD assigns the building class code they deem to describe best the ‘principal’ building or the ‘predominant’ land use on the tax lot.  The values and meanings of this set of codes can be obtained from the Department of Finance.
RPAD CONDO IDENTIFICATION NUMBER
Functions: 1A, BL, BN, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 4 bytes
Description This is an identification number assigned by the Department of Finance to each condominium in the city. It identifies the condominium as a whole and not a specific condominium unit.
RPAD SELF-CHECK CODE (RPAD SCC) FOR BBL
Functions: 1A, BL, BN, 1B (COW only)
Work Area Format: MSW and COW
ANNOUNCEMENT: As of Geosupport Release 19C (on or about August 2019), the RPAD SCC fields will all contain blank values. In Release 19B the RPAD SCC for some BBLs may also be affected. See the background information below.
Background information: The “RPAD SCC” values are derived from the Department of Finance’s (DOF) RPAD file. DOF’s new version of the RPAD file, now called the Property Master file, does not contain “RPAD SCC” values since DOF has phased them out. For Release 19B, Geosupport will continue to return existing “RPAD SCC” values based on the old RPAD file; however, with Release 19C, the “RPAD SCC” fields will all contain blank values.
Description: For each BBL value, the Department of Finance has computed a Self-Check Code (SCC). This is a one-digit number computed from the BBL value using an algorithm chosen by DOF. The purpose of the SCC is to assist in validating key-entered BBLs. For more information on SCCs inquire to the information technology division of the Department of Finance.

S

-
SANBORN VOLUME AND PAGE
Functions: 1A, BL, BN, 2, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: The Volume field is 3 bytes (2-digit volume number + 1-digit character suffix). The Page field is 4 bytes (3-digit page number + 1-digit character suffix).
Description: The Sanborn Map Company maintains a 79 volume atlas of New York City geography that is widely used by New York city agencies. The atlases contain approximately 6000 maps covering all five boroughs
SANITATION BULK ITEMS PICKUP
Functions: 1/1E, 1/1E Extended, 1B
Work Area Format: COW
Length and Format: 5 bytes
Description: This field contains the schedule for the Department of Sanitation (DSNY) pilot program of scheduled Bulk Items Pickup. Release 16D includes the implementation of scheduled collection of disposed Bulk Items for specific locations across the City (previously, disposed bulk items were collected in these areas on regular refuse collection. This field indicates which days of the week the Department of Sanitation will pick up recycling at the given address. See SANITATION ORGANICS RECYCLING PICKUP for the codes.
SANITATION COLLECTION SCHEDULING SECTION AND SUBSECTION
Functions: 1, 1E, 1B (COW only), 2 (COW only??)
Work Area Format: MSW and COW
Length and Format: 2 bytes
Description: District Sections and Subsections defined by the Department of Sanitation for waste collection.
SANITATION DISTRICT
Work Area Format: MSW and COW
Length and Format: 3 bytes. Numeric. The first byte is the Borough Code, and the second and third bytes are the District Number.
Description: Districts defined by the Department of Sanitation for waste collection.
SANITATION ORGANICS RECYCLING PICKUP
Functions: 1, 1E, 1/1E Extended, 1B
Work Area Format: COW
Length and Format: 5 bytes
Description: Indicates which days of the week the Department of Sanitation (DSNY) will pick up organics (compostable waste) recycling at the given address. Organics recycling is currently only available in pilot areas. In Release 16D, the pilot program was expanded to include more ‘Large Buildings (+10 units)’ (as defined by DSNY)
Value Description
M Monday
T Tuesday
W Wednesday
TH Thursday
F Friday
S Saturday
E ‘E’ is used in combination with a day of the week (as noted above) to indicate that collection occurs ‘every’ week on that day.
Z Recycling is collected privately
SANITATION RECYCLING PICKUP
Functions: 1, 1E, 1B (COW only)??
Work Area Format: MSW and COW
Length and Format: 3 bytes
Description: Indicates which days of the week the Department of Sanitation will pick up recycling at the given address. See SANITATION ORGANICS RECYCLING PICKUP for the codes.
SANITATION REGULAR PICKUP
Functions: 1, 1E, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 5 bytes
Description: Indicates which days of the week the Department of Sanitation will pick up non-recycling waste at the given address. See SANITATION ORGANICS RECYCLING PICKUP for the codes.
SCHOOL DISTRICT (previously known as Community School District)
Functions: 1, 1E, 2, 3, 3C, 1B (COW)
Work Area Format: MSW and COW
Length and Format: 2 bytes
Description: School district code
SEGMENT AZIMUTH
Functions: 3, 3C
Work Area Format: MSW and COW
Length and Format: 3 bytes
Description: This item represents the direction in which the segment lies on the earth’s surface, expressed as an angle in degrees measured counterclockwise from due east.  The segment is considered to be pointing in the direction of increasing addresses, and the azimuth value can range from 0 to 359 degrees, inclusive. For example, a segment pointing due east has an azimuth of 0; one pointing due north has an azimuth of 90; one pointing due west has an azimuth of 180; one pointing halfway between due west and due south (i.e., pointing due southwest) has an azimuth of 225.
SEGMENT ID
Functions: 1 and 1E (MSW: Long WA2 only), 1 and 1E (COW), 3, 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 7 bytes. RJZF
Description: Identifies, uniquely within the entire city, a geographic feature segment represented in the CSCL/LION file.
SEGMENT LENGTH IN FEET
Functions: 1, 1E, 3, 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: MSW: Fns 1 and 1E - 5 bytes numeric, Fns 3 and 3C - 3 bytes packed decimal COW: Fns 1, 1E, 3, 3C - 5 bytes numeric
Description: Except for curved segments (see Curve Flag), the Segment Length is computed from the Spatial Coordinates of the segment’s endpoints, as digitized in the LION file. For curved segments, the Segment Length is computed by summing the lengths of the small straight line segments that approximate the curve in the GIS version of LION; this is a more accurate approximation to the true arc length of the curve than would be the segment’s ‘secant length’, that is, the straight line distance between the curve’s extreme endpoints. In the case of Functions 3 and 3C, if the input data define a street stretch encompassing more than one segment (because of a T-intersection or bend), the Segment Length returned is the sum of the lengths of the constituent segments of the stretch. Similarly for Functions 1 and 1E, if the input lies on a segment that is generated from multiple segments, the Segment Length returned is the sum of the lengths of the constituent segments. In all cases, the Segment Length has a very approximate level of accuracy only, and should not be used in applications requiring high precision.
SEGMENT ORIENTATION
Functions: 3, 3C
Work Area Format: MSW and COW
Length and Format: 1 byte character
Description: This item is a set of codes grouping the possible azimuth values of a segment into eight categories.  The categories are "approximately" due north, south, east and west, and the four quadrants of the rectangular coordinate system for segments that do not lie approximately due north, south, east or west.  "Approximately" as used here means "within 5 degrees".  In Manhattan, all orientation codes are defined with a 30‑degree clockwise shift (i.e., 30 is subtracted from the azimuth value) in order to conform to the conventional concept that the midtown streets and avenues lie due east‑west and due north‑south, respectively.  For example, "approximately due north" means "within 5 degrees of due north"; for the boroughs other than Manhattan, this corresponds to the range of azimuth values from 85 to 95; in Manhattan, the corresponding azimuth value range is 55 to 65. There is a ninth orientation category, with a code value of ‘U’, meaning Geosupport could not determine the segment’s orientation because of a problem with the segment’s Spatial Coordinates.  All occurrences of an orientation code of ‘U’ should be reported to Geographic Systems Section staff.
Code Value Meaning Manhattan Other Boroughs
U Orientation is undefined
E Approximately due east 325-335 0-5 and 355-359
1 First quadrant, i.e. northeasterly 336-359 6-84
and 0-54
N Approximately due north 55-65 85-95
2 Second quadrant, i.e. northwesterly 66-144 96-174
W Approximately due west 145-155 175-185
3 Third quadrant, i.e. southwesterly 156-234 186-264
S Approximately due south 235-245 265-275
4 Fourth quadrant, i.e. southeasterly 246-324 276-354
SEGMENT TYPE CODE
Functions: 1, 1E, 3, 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: Indicates type of segment
Code Value Meaning
‘U’ Undivided
‘G’ Generic
‘B’ Both Generic and Roadbed
‘R’ Roadbed
‘C’ Connector
‘E’ Exit/Entrance Ramp
‘T’ Terminator
‘F’ Faux segment (used when a street or ramp physically ends at a roadbed, but connectivity needs to be maintained with the generic segment.)
SEQUENCE NUMBER
Functions: 1, 1E, 3, 3C, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 5 bytes
Description: Identifies a CSCL/LION record uniquely within Face Code. Generally,Sequence Numbers are assigned in the geographic order in which the corresponding segments occur along the geographic feature identified by the given face code. The Borough Code, Face Code and Sequence Number concatenated form the LION key, which serves as a unique identifier for one CSCL/LION record.
SIDE OF STREET INDICATOR
Functions: 1, 1E, 1A - regular WA2, 3C
Work Area Format: MSW and COW
Length and Format: 1 byte character
Description: This field indicates on which side of the street, left or right, the blockface containing the input address lies. Left and right are defined with respect to the direction of increasing addresses along the ‘on’ street.
Code Value Meaning
L Block face is on left side of street with respect to direction of increasing address
R Generic

SNOW PRIORITY - See DSNY SNOW PRIORITY

SPATIAL COORDINATES (See also SPATIAL COORDINATES OF TAX LOT CENTROID)
Functions: 1, 1B (blockface information), 1E, 2, 3 Extended, 3C Extended, AP (For Function 1A, BL, BN, 1B (property level information) see also SPATIAL COORDINATES OF TAX LOT CENTROID)
Work Area Format: MSW and COW
Length and Format: Spatial coordinates consist of two fields, an X Coordinate and a Y Coordinate, each 7 bytes RJZF.
Description: Spatial coordinates are a pair of numbers that specify a location on the earth’s surface. Geosupport returns spatial coordinates for an input address (Functions 1, 1B (blockface information), 1E, and AP), intersection (Function 2), and nodes at the end of a blockface (Functions 3 Extended and 3C Extended). Spatial coordinates are often used in conjunction with separate computer mapping and Geographic Information System (GIS) software to generate maps and for spatial analysis, although the Geosupport System does not itself provide users with such capabilities. Note: For Functions 1, 1B (blockface information) and 1E, the spatial coordinates that Geosupport returns are imprecise approximations of real-world locations, and are not appropriate for use in applications that require a high level of spatial accuracy.
Spatial coordinates are expressed various geodetic coordinate systems, of which latitude/longitude is a well-known example. The coordinate system that Geosupport uses is known as the State Plane Coordinate (SPC) system. The SPC system is based upon the fact that, in a small enough geographic area, the earth’s surface can be assumed to be flat without introducing a significant error. In the SPC system, each state of the U.S. is subdivided into zones small enough to model as planar areas. In each SPC zone, a Cartesian coordinate system is established, with the X and Y coordinate axes oriented due east and due north, respectively, and the origin selected to be a point well to the southwest of the entire zone. (The origin is so selected to insure that the X and Y coordinates of all points within the zone are positive values.) The SPC zone that New York City is in, and which Geosupport uses, is called the New York-Long Island zone, NAD 83. In the SPC system, one unit of X or Y represents one foot of distance on the ground.  A major advantage of the SPC system over other map projection systems is the ease of calculating the distance between two points.
In the case of Functions 1, 1B (blockface information) and 1E, if the street segment on which the input address lies is a straight line segment or an arc of a circle, Geosupport computes and returns output spatial coordinates using a complex algorithm, a detailed description of which is beyond the scope of this document. If, however, the input address lies on a irregularly curved geographic feature (see Curve Flag), Functions 1, 1B (blockface information), and 1E return blanks in the spatial coordinate fields.
Functions 1, 1B (blockface information), and 1E’s spatial coordinates algorithm produces a point position based on how the input address is prorated with respect to the administrative address range allocated to the entire blockface. In addition, the computed point is positioned slightly set off from the segment, on the side of the street where the input address is located. This offset is graphically desirable and also insures that the point will fall within the interiors of the proper political and administrative district boundary polygons for the given address. The computed point is a rough approximation to the location of the input address, intended to be used only for thematic mapping and other purposes that do not require a high level of spatial accuracy.
The spatial coordinates returned by Functions 1/1E/1B (blockface information) for NAPs and Vanity Addresses (see Chapter V.9) were an estimate calculated by Geosupport. As of Version 11.2, Geosupport will use the Citywide Street Centerline file (CSCL) X-Y Coordinates. The CSCL information guarantees that the X-Y coordinates fall within the actual location of the NAP or Vanity Address.
In the case of Function 2, the spatial coordinates returned are those of the LION node that corresponds to the input street intersection. Those coordinates represent an approximate center point of the intersection.
In the case of Function 3 Extended and Function 3C Extended, the spatial coordinates returned are those of the nodes at the end of the blockface. Those coordinates represent an approximate center point of the intersection.
In the case of Function AP, the spatial coordinates returned are those of the Address Point which is within 5 feet of the entrance(s) of the building.
In the case of Functions 1A, BL, BN, 1B (property level information),the spatial coordinates returned are those of the Tax Lot Centroid. See SPATIAL COORDINATES OF THE TAX LOT CENTROID
SPATIAL COORDINATES OF THE TAX LOT CENTROID
Functions: 1A, BL, BN, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: Spatial coordinates consist of two fields, an X Coordinate and a Y Coordinate, each 7 bytes RJZF.
Description: Note: Internal Label Points and Annotation Points are no longer used They are replaced by Tax Lot Centroid.
The Tax Lot Centroid is created in ESRI’s ArcGIS software using the Department of Finance’s Digital Tax Map (DTM). The coordinates associated with the Tax Lot Centroid are guaranteed to be within the property, unlike the coordinates returned by either Function 1 or Function 1E, where the Spatial Coordinates are an approximation based in the address range of the particular street the address is on. In addition, the Function 1/1E Spatial Coordinates always fall in the street bed and not within a tax lot, and most likely will not be adjacent to the tax lot the address is in. Additionally, when using Function 1A, the same coordinates will be returned no matter which of a tax lot’s addresses is used as input. There are a few properties which do not have a Tax Lot Centroid; consequently, no coordinates will be returned for these properties.
See SPATIAL COORDINATES for a description of the coordinate system (SPC) used by Geosupport.
SPECIAL ADDRESS GENERATED RECORD FLAG (a.k.a. SAF FLAG or SPECIAL ADDRESS FLAG)
Functions: 1, 1E, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 1 byte character
Description: A non-blank value in this flag indicates one of a variety of special addressing situations.
Code Value Meaning
‘A’ The address range returned in this work area is alternative to the address range that is stored in LION for this blockface. This case arises most commonly when the input address is an old (superseded) address on a blockface on which the buildings were re-numbered at some time in the past. For such an input address, the address range returned in this work area is the old address range, whereas the current address range is stored in LION. Another situation in which this flag is ‘A’ is when the given street segment has continuous parity address ranges on both sides of the street, such as when buildings are numbered consecutively around the arc of a cul-de-sac.
‘B’ The input street name or five-digit street code is different from that stored in LION for this blockface. This case arises when two street names having different B5SCs are both valid along a street or portion of a street. These are situations in which treating the two street names as aliases would result in an address range overlap.
‘C’ The input address pertains to Ruby Street, a street along the Brooklyn-Queens border that has a unique addressing situation. See ChapterV.8.
‘D’ The input address involves a duplicate address situation. See Chapter V.6.
‘E’ The input address is in one of the neighborhoods in which the name of the neighborhood can serve as an alternative street name for the streets in that neighborhood. Two Bronx neighborhoods, Edgewater Park and Harding Park, have this characteristic.
‘G’ The input name or street code corresponds to a non-addressable place name of a complex. A complex is a geographic feature that contains constituent entities that are separately geographically identifiable. Typical examples of complexes include airports, housing projects and university and hospital campuses. See Chapter III.6.
‘N’ The input name or street code corresponds to a non-addressable place name of a ‘stand-alone’ geographic feature (a geographic feature that is neither a complex nor a constituent entity of a complex). Typical examples are individual named buildings, such as Empire State Building, Shea Stadium, Carnegie Hall. See Chapter III.6.
‘O’ The blockface contains out-of-sequence and/or opposite-parity addresses. An out-of-sequence address contains a house number that is out of sequence with those of the immediately adjacent buildings. An opposite-parity address contains a house number that is of the opposite parity to the predominant parity on the blockface. See Chapter V.10.
‘P’ The input address contains an addressable place name. Example: 2 Penn Plaza. See Chapter III.6.
‘S’ The input address contains a house number suffix and is either the first or last address on this blockface.
‘V’ The input address is a ‘vanity address’, that is, an address in which the street name refers to a different street than the one on which the referenced building entrance is actually located. See Chapter V.9.
‘X’ The input data specify a non-addressable place name of a constituent entity of a complex. Examples: AVERY FISHER HALL and NEW YORK STATE THEATER are names of constituent entities of the complex LINCOLN CENTER. See Chapter III.6
SPEED LIMIT
Function: 1/1E Extended, 1B, 3/3C Extended
Work Area Format: COW
Length and Format: 2 bytes, blank if no data.
Description: The Speed Limit field contains the speed limit, in miles per hour, of the paved area of the input location.

Speed Limit data was provided by the NYC Department of Transportation and currently does not cover the entire city. Additional data will be made available in future releases.
SPLIT ELECTION DISTRICT FLAG
Function: 1E, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 1 byte
Description:
Code Value Meaning
‘S’ Block face is split among two or more election districts
blank Block face lies entirely within an election district
STATE SENATORIAL DISTRICT
Function: 1E, 1B (COW only), 2 (COW only)
Work Area Format: MSW and COW
Length and Format: 2 bytes. Numeric.
Description: A district of the upper house of the New York State legislature. Consists of an aggregation of Election Districts/td>
STREET ATTRIBUTE INDICATOR (a.k.a. ATTRIBUTE BYTE)
Functions: WA1 output field - 1, 1A, 1B, 1E, 1N, AP, D, DG, DN
Work Area Format: MSW and COW
Length and Format: 1 byte character
Description: Indicates certain characteristics of selected streets
Code Value Meaning
‘A’ Address Place Name
‘B’ Name of bridge
‘C’ Building Improvement District (BID)
‘D’ Duplicate Address Pseudo-Street Name (DAPS)
‘E’ Input street is entirely in Edgewater Park (a Bronx neighborhood that has special addressing characteristics).
‘F’ Input street is partly in Edgewater Park and partly outside of it.
‘G’ NAP of a complex.
‘H’ All house numbers on input street are hyphenated.
‘I’ Intersection Name
‘J’ Non-physical Boundary Feature
‘M’ House numbers on input street are of mixed hyphenation, i.e., some are hyphenated and some are not.
‘N’ Input street is a Non-Addressable Place Name (NAP)
‘O’ Shore Line
‘P’ Pseudo-street name
‘R’ Rail Line
‘S’ Front-Truncated Street Name
‘T’ Tunnel
‘U’ Misc. structure
‘X’ NAP Of a Constituent Entity of a Complex
‘Z’ Exit or Entrance Rampse
Blank None of the above. In particular, all addresses on the input street are un-hyphenated
STREET NAME NORMALIZATION FORMAT FLAG
Functions: 1, 1A, 1E, 1N, 2, 3, 3C, 3S, D, DG, DN, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 1 byte.
Description: Specifies the format in which Geosupport is to return output normalized street names. The default is to return street names in the sort format.
Code Value Meaning
blank Return normalized street names in the sort format
‘C’ Return normalized street names in the compact format
‘S’ Return normalized street names in the sort format
STREET NAME NORMALIZATION LENGTH LIMIT (SNL)
Functions: WA1 input item, Functions 1, 1A, 1E, 1N, 2, 3, 3C, 3S, D, DG, DN, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 2 bytes, blank or numeric, either LJBF or RJZF.
Description: Specifies the maximum length in bytes within which Geosupport is to normalize street names. The minimum and maximum permissible SNL values are 4 and 32. The default that is in effect if the application does not specify an SNL value is 32
STREET WIDTH
STREEET WIDTH MAXIMUM
Functions: 1/1E Extended, 1B, 3 Extended, 3C Extended
Work Area Format: COW
Length and Format: Street Width: 3 bytes, RJBF
Street Width Maximum, 3 bytes, RJBF
Description: The width, in feet, of the paved area of the street. Street Width contains the width at the narrowest part of the street. Street Width Maximum contains the width at the widest part of the street. If the width is consistent along the street segment then both values are identical.

T

TAX BLOCK
Functions: 1A, BL, BN, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 5 bytes
Description: See Chapter VI.2.
TAX LOT
Function: 1A, BL, BN, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 4 bytes
Description: See Chapter VI.2.

TAX LOT CENTROID - See SPATIAL COORDINATES OF THE TAX LOT CENTROID

TAX MAP SECTION
Function: 1A, BL, BN, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 2 bytes
Description: The Department of Finance real property tax maps are organized into sections; each section is organized into volumes; and each volume consists of pages. Tax Map Section values are unique within borough
TAX MAP VOLUME
Functions: 1A, BL, BN, 1B (COW only)
Work Area Format: MSW and COW
Length and Format: 2 bytes
Description: See description at Tax Map Section. Tax Map Volume values are unique within Tax Map Section.

TO NODE - See NODE NUMBER TO NODE ID - See NODE NUMBER TOTAL LANES - See NUMBER OF TOTAL LANES

TRAFFIC DIRECTION
Functions: 1/1E Extended, 1B, 3 Extended, 3C Extended
Work Area Format: COW
Length and Format: 1 byte
Description:
blank Non-street feature (or unknown if not a non-street feature)
A One way street, traffic flows against the segment’s directionality, i.e., from the segment’s TO node to the FROM node
P Pedestrian path, non-vehicular
T Two‑way street
W One way street, traffic flows with the segment’s directionality, i.e., from the FROM node to the TO node

TRAVEL LANES - See NUMBER OF TRAVEL LANES

U

UNDERLYING B7SC OF TRUE STREET - See B7SC OF “TRUE” STREET

UNIT INFORMATION FIELDS
Field Names: UNIT INPUT
UNIT – SORT FORMAT
UNIT – TYPE
UNIT – IDENTIFIER
UNIT – DISPLAY FORMAT
Functions: 1* (COW only)
Work Area Format: COW
Length and Format: See Chapter V.15 Unit Information Feature
Description: See Chapter V.15 Unit Information Feature
USPS PREFERRED CITY NAME
Functions: 1/1E Extended, 1B
Work Area Format: COW
Length and Format: 25 bytes
Description: The USPS (United States Postal Service) Preferred City Name (e.g. Astoria, Jackson Heights) is of particular importance for Queens addresses.
For Queens, the USPS Preferred City Name is based on the ZIP code associated with the input address. Unless there is a special ZIP code, the following holds true for the other boroughs. For Manhattan, the USPS Preferred City Name is New York.  For all the other boroughs, the USPS Preferred City Name is the borough name, viz. Bronx, Brooklyn, and Staten Island.
In the rare, and unexpected, instance where there is no city name available for a Queens location, then the city name will be set to a default of QUEENS and the following warning message will be issued: GRC 01, Reason Code Y:
ZIP NOT IN CITY NAME TABLE. GENERIC CITY NAME RETURNED. NOTIFY DCP/GSS

V

VACANT LOT FLAG
Work Area Format: MSW and COW
Length and Format: 1 byte
Description:
Code Value Meaning
‘V’ Tax lot is currently vacant, i.e., it has no existing buildings
Blank Tax lot has at least one existing building

W

WORK AREA FORMAT INDICATOR
Functions: All
Work Area Format: MSW and COW
Length and Format: 1 byte
Description: This indicator specifies which work area layouts are to be used in an API call. Note: This indicator is also known as the Platform Indicator.
Code Meaning
blank The IBM mainframe specific work areas (MSWs) are used. The MSWs contain packed decimal fields. In general, these work areas are the ones described throughout this manual
‘C’ The platform-independent work areas known as the Character-Only Work Areas (COWs) are used. These contain no packed decimal fields. For information on using COWs on the mainframe and the differences from the MSWs, see [Appendix 12](/appendices/appendix12/). For the work area layouts of the COWs, see [Appendix 13](/appendices/appendix13/).

X

XY COORDINATES - see SPATIAL COORDINATES

X-Y COORDINATES - see SPATIAL COORDINATES

ZIP CODE
Functions: 1, 1A, 1E, 2, 3, 3C, 1B
Work Area Format: MSW and COW
Length and Format: 5 bytes. Numeric
Description: U.S. Postal Service’s 5-digit ZIP code
ZIP code may also be used as input with functions 1, 1A, 1B, and 1E to identify the borough or Duplicate Address Pseudo-Street name (DAPS).