The CAGIS Electronic Address Standard was designed with the purpose of enhancing the potential for data sharing and electronic records integration among CAGIS participants. It is also a key element that will allow the many legacy record systems to be integrated with CAGIS enterprise data, opening opportunities for new applications using the powerful capabilities of GIS technology. The Electronic Address Standard is incorporated into all standard CAGIS data schemas where applicable. Electronic master indexes of street names, addressing and other relevant geocodes created for the use of CAGIS participants will employ the standard and is now being maintained in the operations workflows linked with the mandated authorities for street name and address assignments (Cincinnati Public Works and Hamilton County Regional Planning). Geocode validation software tools and GIS files that employ the standards have also been developed that should make it easier for agencies to implement the Standard. The desktop user can use the latest CAGIS GEN6 ArcView project to deploy these tools. The same tools should also help to reduce data entry error and provide one means of improving enterprise data quality. Record systems that incorporate the Standard into their data design will not only have improved opportunity for integration with CAGIS data, but will also have improved opportunity for integrating between record systems that have been designed in compliance with the standard. Compliance with a multi-participant data standard has obvious benefits such as minimizing software development costs and the potential for making data more usable for more users. For these reasons, it is recommended that the Electronic Address Standard be incorporated in all new data designs that are developed by CAGIS participants.

It is recognized that many participants may have significant capital investments in data design and software technologies that support current applications and systems. Over time, these legacy systems have resulted in multiple, nonconforming standards that cannot be easily converted without great cost. Further, while the vision of a shared standard is the preferred vision of the future, it is recognized that all agencies may not justify the conversion expense or effort with the same quickness as others. Users should note that CAGIS has the capability to translate legacy records to the new standard, however because legacy addresses are often ambiguous, perfect translations are rare. CAGIS can standardize addresses and create reports on those addresses that are not matched with records in the STRMASTR and ADDMASTR tables (comprehensive listings of valid street names and addresses). It is recommended that when legacy systems are retired for newer designs, that the Electronic Address Standard be incorporated into those designs by agencies desiring more complete records integration or that desire access to the integrated software solutions that will be available through CAGIS.

1) House and street location components (House number, street name, unit, building, etc.)

2) Place name components (City, County, State, Zip code, etc.)

3) Integration Components (Street Name ID, Address Record ID, City Permits ID, County Permits ID, Street Segment ID, ParcelId, Group Parcel ID)

The Address Standard identifies the following sub-components,

Place name components are address modifiers that distinguish between local addressing systems related to jurisdiction or mail delivery zones. Place name modifiers distinguish between local systems duplicate house number and street name systems. For the CAGIS Standard, the key place name sub-components are defined as follows,

• Unique Parcel Record ID - PARCELID
• Identifier Linking Consolidated Parcels - GRPPCLID
• Unique street name ID - STRNAMID
• Unique address record ID - ADDRECID
• Unique street segment record ID - STRSEGID
• Unique node record ID - NODEID
• Unique street intersection record ID - INTERXID
• Unique Building record ID - BLDGID
• Unique City Permit Address ID - CITYPERMID
• Unique County Permit Address ID - CNTYPERMID

The rules for creating these ID's are found in the CAGIS Geographic Integration Framework Documentation. These ID's are used for tracking maintenance, validation, rapid integration, translation, and record matching.

STRNAMID - Composed of the concatenation of the 1^st 5 characters of the street name, followed by a 2 character sequence#, followed by the street direction

ADDRECID - Composed of the concatenation of a PARCELID + a left 0 filled HOUSE NUMBER + the first character of the street name.

NODEID - Composed of the concatenation of the CAGIS facet id followed by last 4 digits of the integer rounded X State Plane coordinate id followed by last 4 digits of the integer rounded Y State Plane coordinate.

STRSEGID - Composed of the concatenation of the low X NODEID with the high X NODEID

INTERXID - Composed the same as the node id. The State Plane point is derived from the label point of the logical intersection polygon

E 8th ST vs W 8th ST, or

N Elm ST vs S Elm ST.

The City of Cincinnati and Hamilton County do not employ post directionals in their street name designations. Post directionals are generally used by city's to distinguish between streets that have the same directional employed on parallel streets in the same quadrant. When they are encountered in record systems in this community it is usually because the data gathered has is refinancing the street name that is represented on some street signage within the County that places the street direction after the name. These are not the official spellings and should be discouraged from use in electronic record systems.

In some instances directions are commonly considered among Hamilton County citizens to be part of the street name. The Electronic Standard Will always abbreviate directionals and parse them to the prefix/direction field unless the following conditions occurs.

1. A Street name could have the instance of having two directions preceding a street name component. In this instance the first directional will be abbreviated and placed into the prefix field, the second fully spelled. An example is:

W NORTH BEND RD

2. The direction is the street name. In this instance, the direction will not be abbreviated. An example is

These rules are designed to simplify decisions on parsing and abbreviating addresses for electronic file systems. CAGIS has created provisions for a special field in the STREETS database that enable instances of streets where directions are commonly considered as part of the street name (not a directional indicator) can be labeled with a special class of labels that will provide the common spellings for these streets on maps. Further, software will be provided that enables queries to use abbreviated or non-abbreviated spellings.

Required first word abbreviations (Note these are the only abbreviations allowed in the Street Name Field)

RULES FOR STREET NAMES WITH NUMBERS AS PART OF THE STREET NAME :

Some street names may have numbers as part of the street name, but are not considered what would intuitively be considered a 'Numbered Street'. In these Instances, the numbers are to be spelled out. Examples of this are,

 I-70

I-275

 No other use of special characters for new street names is allowed.

LEGAL DATA VALUES Street Name Suffix/Street Type field is for those suffixes that are appended to street names that are traditionally used for street classification or defining general street type, such as street, road, avenue, boulevard, etc. The following list defines the only allowable street name suffix/street type values. The list also defines the legal range of suffix spellings anD abbreviations.

BUILDING 1

BLDG A

LEGAL DATA VALUES: The Jurisdiction Type field contains values that designate the jurisdiction type ofthe value stored in the City/Township/ /Jurisdiction field. The value designates type as City, unincorporated areas, and Township values. Legal data values are,

 COUNTY

LEGAL DATA VALUES: Most of the addresses used by agencies in the CAGIS consortium are in Hamilton County. However, the County Field can contain any County designation.