Information Resources and Technology Management


You are invited to read the definitions of terms used in this data standard.

Geographic Area Name
Official names used to identify geographic areas created by the Service to support and implement the Ecosystem Approach to Fish and Wildlife Conservation.
Character Field
Geographic area name, up to a maximum of  100 characters, including the letters A-Z, the numbers 1-9, Roman numerals, punctuation marks, and the forward slash (/) character. 
Recommended Field Name GEONAME
The official values to be used for this data element are provided in the Source section. 
An electronic copy of the official values to be used for this data element is available here. An electronic copy of the file is also available here in MS Word format. These values are current as of January 24, 2005. The source files include Region numbers to identify the geographic areas associated with each Region.   
Historical Data For information on past versions of this standard, contact the Chief Data Officer

Part 052, FW 1, Ecosystem Approach to Fish and Wildlife Conservation.

Part 270, FW 6, Data Management and Standards, has been superceded by Part 274, FW 2, Establishing Service Data Standards.

Ecosystem Approach to Fish and Wildlife Conservation: An Assessment by Ohio State University - an evaluation of the above document and results.

Use Instructions
As of the approval date, this data element will be used in any new automated system, data set, database, or information application, including new Geographic Information System (GIS) data and applications. This data element will also be used in any major modifications to existing systems or versions of these data-related items that use the official names of the geographic areas managed by the Service. The "Not Applicable" designation should be assigned to Service organizations that do not have a geographic area association, such as the Regional Directorate and Regional administration offices. Further guidance on using the "Not Applicable" designation will be provided in the future.

Service staff are strongly encouraged to utilize this data element in existing systems, data sets, databases, and information applications. Where existing systems and data-related items are not in compliance, they should be modified to achieve compatibility and implement this data standard.

Approval Date
March 21, 2000
Validation Date
November 29, 2013
Data Steward Chief Data Officer


Last updated: May 9, 2019