1. (a) The following standards apply to the collection and maintenance of the centerline attributes that are intended for incorporation into the ACF program.
2. (b) Minimum standards for ACF attributes. Table 1

   Field Name	Length	Type	Alpha Case	Description
   PL_ADD_F		Longinteger		Primary Left From Address number
   PL_ADD_T		Longinteger		Primary Left To Address number
   PR_ADD_F		Long integer		Primary Right From Address number
   PR_ADD_T		Longinteger		Primary Right To Address number
   PRE_DIR	2	Text	Upper	Primary Directional Prefix
   PRE_TYPE	4	Text	Proper	Primary Prefix Street Type
   PSTR_NAM	72	Text	Proper	Primary Street Name
   PSTR_TYPE	4	Text	Proper	Primary Suffix Street Type
   PSUF_DIR	2	Text	Upper	Primary Directional Suffix
   PSTR_FULNAM	255	Text	Proper	Stores the complete primary street name
   CITY_L	30	Text	Proper	Stores the USPS preferred last line city name
   CITY_R	30	Text	Proper	Stores the USPS preferred last line city name
   COMM_L	30	Text	Proper	Stores the e9-1-1jurisdictional community
   COMM_R	30	Text	Proper	Stores the e9-1-1jurisdictional community
   CN_R_FIPS	3	Text		County FIPS code Right
   CN_L_FIPS	3	Text		County FIPS code Left
   STATE_L	2	Text	Upper	State Left
   STATE_R	2	Text	Upper	State Right
   ZIP5_L	5	Text		Zip Code Left
   ZIP5_R	5	Text		Zip Code Left Right
   UNIQUE_ID		Longinteger		Unique Identifier
   META _ID	20	Text		Metadata Identifier
   ALTERNATE 1
   A1_LFADD		Longinteger		Alternative 1 Left From Address number
   A1_LTADD		Longinteger		Alternative 1 Left To Address number
   A1_RFADD		Longinteger		Alternative 1 Right From Address number
   A1_RTADD		Longinteger		Alternative 1 Right To Address number
   A1_PRTYP	4	Text	Proper	Alternative 1 Street PrefixType
   A1_STR	72	Text	Proper	Alternative 1 Street Name
   A1_DRPR	2	Text	Upper	Alternative 1 Directional Prefix
   A1_STYP	4	Text	Proper	Alternative 1 Street Type
   A1_DRSF	2	Text	Upper	Alternative 1 Directional Suffix
   A1_FULNAM	255	Text	Proper	Alternative 1 complete streetname
   ALTERNATE 2
   A2_LFADD		Longinteger		Alternative 2 Left From Address number
   A2_LTADD		Longinteger		Alternative 2 Left To Address number
   A2_RFADD		Longinteger		Alternative 2 Right From Address number
   A2_RTADD		Longinteger		Alternative 2 Right To Address number
   A2_PRTYP	4	Text	Proper	Alternative 2 Street PrefixType
   A2_STR	72	Text	Proper	Alternative 2 Street Name
   A2_DRPR	2	Text	Upper	Alternative 2 Directional Prefix
   A2_STYP	4	Text	Proper	Alternative 2 Street Type
   A2_DRSF	2	Text	Upper	Alternative 2 Directional Suffix
   A2_FULNAM	255	Text	Proper	Alternative 2 complete streetname
   ALTERNATE 3
   A3_LFADD		Longinteger		Alternative 3 Left From Address number
   A3_LTADD		Longinteger		Alternative 3 Left ToAddress number
   A3_RFADD		Longinteger		Alternative 3 Right From Address number
   A3_RTADD		Longinteger		Alternative 3 Right To Address number
   A3_PRTYP	4	Text	Proper	Alternative 3 Street PrefixType
   A3_STR	72	Text	Proper	Alternative 3 Street Name
   A3_DRPR	2	Text	Upper	Alternative 3 Directional Prefix
   A3_STYP	4	Text	Proper	Alternative 3 Street Type
   A3_DRSF	2	Text	Upper	Alternative 3 Directional Suffix
   A3_FULNAM	255	Text	Proper	Alternative 2 complete streetname
   RD_CLASS1	25	Text	Upper	The entity by or through which a road is maintained. Acceptable values are “federal”, “state”, “county”, “municipal”, “private”,“levee road”, or “public”.
   RD_DESIGN2	25	Text	Upper	Design characteristic of the road. Acceptable values are “dual carriageway”, “single carriageway”, “traffic circle”, “connector segment”, “grade- separated ramp”, “at- grade ramp”, “frontage road”, or “highwayfacility”
   RD_SURFTYP3	25	Text	Upper	Road surface type.Recommended values are ‘paved’ or ‘unpaved’.
   LOG_DIRECT4	25	Text	Upper	Indication of whether travel on a dual carriageway road is in the log or antilog direction. Acceptable values are “log” or “antilog”.
   AH_Dist	2	Text		The number of the Department District in which the road is contained (1 – 10).
   AH_County	25	Text		The Department assigned number of the county in which the road is contained (1 – 75).
   AH_Route	100	Text		The assigned official route number or name based on Department Road Inventory and official local road names.
   AH_Section	3	Text		Department assigned section number of each highway and local road.
   AH_BLM	6	Number		Department calculated begin log mile of each highway and local road segment.
   AH_ELM	6	Number		Department calculated end log mile of each highway and local road segment.
   AH_Length	6	Number		Department calculated length of each highway and local road segment.
   AH_Seg_Num	5	Number		Calculated segment number based on road direction.
   AH_Rev_ACF	Yes/No	Text	Proper	States if the road direction in the delivered file from AGISO was reversed to match the Department log direction (Yes or No).
   AH_ID	150	Text		Concatenated county x route x section x log_direct x segment number. Unique ID required by FHWA
   AH_RoadID	150	Text		Concatenated county x route x section x log_direct for Dynamic Segmentation.
   AH_Signed	10	Text	Proper	Manner in which each road is signed for quick retrieval.Interstate = Interstate HighwaysUS = U.S. Highways State = State Highways Local = All other localroadways

   1federal = maintained by specific federal agencies, e.g. U.S. Forest Service, U.S. Fish and Wildlife Service, U.S. Army Corps of Engineers, National Park Service, etc. State = interstate highways, US highways, state highways, and any other road maintained by a state government entity county = road officially accepted into a county road system and maintained as such by a county road department municipal = road maintained by an incorporated municipality private = any road or driveway not maintained by a public entity levee road = road constructed atop a regulated levee under the jurisdiction of a local levee district public = roads receiving some amount of county maintenance for public use, but not accepted as an official county road 2Each RD_DESIGN value is defined in 15 CAR § 280-105, Definitions. 3A county may choose to maintain surface type attributes more detailed than “paved” or “unpaved”. However, the RD_SURFTYP field will at a minimum carry the “paved” or “unpaved” attribute to meet the all public roads linear referencing system requirement. 4log = log direction, i.e. in the direction of increasing log mile values antilog = antilog direction, i.e. in the direction of decreasing log mile values *Note: The line in this instance is a linear geospatial theme that represents a centerline. Address ranges are typically established for individual centerline segments so address matching may be performed. Whenever practical, street names and address ranges shall conform to the actual situs addresses assigned.
3. (c) Typographic conventions. The “#” symbol, hyphens, or other punctuations shall not be used in any part of centerline attribute files created with the intent to be incorporated into the ACF program.

4. (d) Directional prefixes and suffixes.

   1. (1)

      1. (A) Centerline files intended for incorporation into the ACF program shall use directional prefixes and suffixes established by the United States Postal Service.
      2. (B) Refer to Appendix A.
   2. (2) The directional prefixes and suffixes shall be uppercase.

5. (e) Metadata identifier.

   1. (1) Centerline files intended for incorporation into the ACF program shall have a metadata identifier that associates (links) the contributed file to its proper metadata.
   2. (2) Each segment shall have a metadata code assigned at the state level.

6. (f) Street name.

   1. (1) When primary street names are numbers, the numeral shall be used rather than the actual spelling.
   2. (2) For example, “1” would be used rather than “First”.

   3. (3)

      1. (A) Names that are made up of numbers shall also include additional characters such as “th”, “rd”, “st”, or “nd”, e.g., “1st”, “2nd”, “3rd”, etc.
      2. (B) These characters shall be included in the primary street name field.
   4. (4) Street names shall utilize capital and lowercase letters.

   5. (5)

      1. (A) Common abbreviations are acceptable in the street name.
      2. (B) These might include, but are not limited to Dr (Doctor) or Jr (Junior).
      3. (C) This will ensure the name fits the field length requirements.

   6. (6)

      1. (A) In addition to the rules described above, naming conventions for the primary street names in the ACF should in all cases correspond to the actual situs addresses assigned by the local addressing authority.
      2. (B) These should also be consistent with the naming conventions used in the situs address point data maintained by the local jurisdiction and with the local Master Street Address Guide (MSAG), if applicable.

7. (g) Street type.

   1. (1) Centerline files created with the intent to be incorporated into the ACF program shall use street abbreviations established by the United States Postal Service.
   2. (2) The street type shall be composed of upper and lowercase characters.

8. (h) Unique identifier.

   1. (1) Each line segment within the Arkansas Centerline File Program shall have a unique identifier.
   2. (2) The unique identifier shall be assigned at the state level.

Codification Notes: "ACF" means Arkansas Centerline File.