ANSI INCITS31-2009 Information technology - Codes for the Identification of Counties and Equivalent Areas of the United States Puerto Rico and the Insular Areas《信息技术.美国 波多黎各地区以及海岛地.pdf

1、American National StandardDeveloped byfor Information Technology Codes for the Identification ofCounties and Equivalent Areas of theUnited States, Puerto Rico, andthe Insular AreasINCITS 31-2009INCITS 31-2009Copyright American National Standards Institute Provided by IHS under license with ANSI Not

2、for ResaleNo reproduction or networking permitted without license from IHS-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-INCITS 31-2009Revision ofINCITS 31-1988(R2007)Amer

3、ican National Standardfor Information Technology Codes for the Identification ofCounties and Equivalent Areas of theUnited States, Puerto Rico, andthe Insular AreasSecretariatInformation Technology Industry CouncilApproved August 31, 2009 American National Standards Institute, Inc.Copyright American

4、 National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval of an American National Standard requires review by ANSI that therequirements for due process, consensus, and other criteria for approval

5、havebeen met by the standards developer.Consensus is established when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected interests. Substantial agreement means much more thana simple majority, but not necessarily unanimit

6、y. Consensus requires that allviews and objections be considered, and that a concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary; theirexistence does not in any respect preclude anyone, whether he has approvedthe standards or not, from manu

7、facturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give an interpretation of any American NationalStandard. Moreover, no person shall have the ri

8、ght or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or sponsor whose name appears on the titlepage of this standard.CAUTION NOTICE: This American Nation

9、al Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Standards mayreceive current information on all standards by calling

10、 or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2009 by Information Technology Industry Council (ITI)All rights reserved.No part of this publication may be reproduce

11、d in anyform, in an electronic retrieval system or otherwise,without prior written permission of ITI, 1101 K Street NW, Suite 610, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers of this standard have requested that holders of patents that may berequired for the

12、implementation of the standard disclose such patents to the publisher. However,neither the developers nor the publisher have undertaken a patent search in order to identifywhich, if any, patents may apply to this standard. As of the date of publication of this standardand following calls for the ide

13、ntification of patents that may be required for the implementation ofthe standard, no such claims have been made. No further patent search is conducted by the de-veloper or publisher in respect to any standard it processes. No representation is made or impliedthat licenses are not required to avoid

14、infringement in the use of this standard.Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-iContentsPageForeword ii1 Scope and Purpose 12 Definitions and Coverage . 13 Normative R

15、eference 14 Assignment of Identifying Data Codes . 25 Duties of the Maintenance Agency. 36 Designation of Maintenance Agency 3AnnexesA Class Codes . 4B Bibliography 5Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking pe

16、rmitted without license from IHS-,-,-iiForeword (This foreword is not part of American National Standard INCITS 31-2009.)This document establishes the designation of data codes for counties and countyequivalents.This standard contains two annexes. Annex A is normative and is considered part ofthis s

17、tandard. Annex B is informative and is not considered part of this standard.This standard supersedes the following:ANSI INCITS 31-1988 (R2007), Amended by ANSI INCITS 31-1988 (R2002), Code-start - Structure for the Identification of the Counties and County Equivalents of theUnited States and Its Out

18、lying and Associated Areas for Information Interchange (for-merly ANSI X3.31-1988 (R1994)andFIPS PUB 6-4, Counties and Equivalent Entities of the U.S., Its Possessions, and As-sociated Areas (Withdrawn 2008 September 02).Requests for interpretation, suggestions for improvement or addenda, or defect

19、re-ports are welcome. They should be sent to InterNational Committee for InformationTechnology Standards (INCITS), ITI, 1101 K Street NW, Suite 610, Washington, DC20005.This standard was processed and approved for submittal to ANSI by INCITS. Com-mittee approval of this standard does not necessarily

20、 imply that all committee mem-bers voted for its approval. At the time it approved this standard, INCITS had thefollowing members:Don Wright, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems, Inc. Scott FosheeSteve Zilles (Alt.)AIM Global, Inc. Dan MullenCh

21、arles Biss (Alt.)Apple Computer, Inc. Kwok LauHelene Workman (Alt.)David Singer (Alt.)Distributed Managment Task Force . Tony DiCenzoJeff Hilland (Alt.)Winston Bumpus (Alt.)Electronic Industries Alliance . Edward Mikoski, Jr.EMC Corporation Gary RobinsonFarance, Inc. Frank FaranceTimothy Schoechle (

22、Alt.)Google Zaheda BhoratRobert Tai (Alt.)GS1 US Ray DelnickiFrank Sharkey (Alt.)James Chronowski (Alt.)Mary Wilson (Alt.)Hewlett-Packard Company. Karen HigginbottomPaul Jeran (Alt.)IBM Corporation . Ronald F. SillettiRobert Weir (Alt.)IEEE . Judith GormanTerry DeCourcelle (Alt.)Bill Ash (Alt.)Jodie

23、 Haasz (Alt.)Bob Labelle (Alt.)Susan Tatiner (Alt.)Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-iiiOrganization Represented Name of RepresentativeIntel .Philip WennblomDave T

24、hewlis (Alt.)Grace Wei (Alt.)Steven Balogh (Alt.)Lexmark InternationalDon WrightDwight Lewis (Alt.)Paul Menard (Alt.)Microsoft CorporationJim HughesDave Welsh (Alt.)Mark Ryland (Alt.)National Institute of Standards parishes in Louisiana; independent cities in Maryland, Missouri, Nevada, and Virginia

25、; and municipios in Puerto Rico. The District of Columbia serves as a county equivalent for itself. In the case of aggregated insular areas (minor outlying islands) for which no county equivalents have been otherwise defined, each island and island group generally recognized as a separate territoria

26、l unit shall be treated as a county equivalent. 3. Normative Reference The following standard contains provisions which, through reference in this text, constitute provisions of this American National Standard. All standards are subject to revision, and parties to agreements based on this American N

27、ational Standard are encouraged to investigate the possibility of applying the most recent edition of the standard indicated below. INCITS 38, Information Technology Codes for the Identification of the States and Equivalent Areas within the United States, Puerto Rico, and the Insular Areas Copyright

28、 American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-INCITS 31-2009 2 4. Assignment of identifying data codes 4.1 Assignment of county codes Each county and county equivalent to be identified

29、 under this standard shall be assigned a single county code consisting of three digits. Each assigned county code shall be unique within a state or state equivalent. 4.2 Initial sequencing of names for county code assignment For each state and state equivalent, the names of the counties and county e

30、quivalents (except for independent cities) shall be arranged in alphabetical order. This sequence shall be followed by the names of the independent cities of that state or state equivalent, if any, also arranged in alphabetical order. 4.3 Initial assignment procedure For each state and state equival

31、ent, county codes shall be assigned in an ascending numerical sequence to the county and county equivalent names arranged as specified in 4.2. One and only one county code shall be assigned to each county or county equivalent. 4.4 Assignment interval and values for county codes In the initial assign

32、ment of county codes within each state, there shall be a minimum arithmetic interval of two between successive assignments. For each state except Alaska, and for the District of Columbia and Puerto Rico, the lowest numbered initial assignment shall be 001. For Alaska, the lowest numbered initial ass

33、ignment shall be 010. For independent cities of any state or state equivalent, the lowest numbered initial assignment shall be 510. 4.5 New entries Subsequent to the initial assignments, new entries shall be assigned county codes so that, to the greatest extent possible, the alphabetic order within

34、each sequence is maintained. 4.6 Unique representation To permit unique representation of each county or county equivalent among all such units identified under this standard, the three-digit county code shall be used in conjunction with a two-character representation of the state or state equivalen

35、t in which the county or county equivalent is located. The two-character representation of each state and the District of Columbia shall be specified in codes maintained at http:/www.census.gov/geo/www/ansi/ansi.html as detailed in INCITS 38. The alphabetic representations of state equivalents other

36、 than the District of Columbia shall be those for which the U.S. Post Office provides a structure 4.7 Combined representation When the county code is used together with the two-character state representation, the latter shall occur to the left (that is, in the more significant positions). No separat

37、or between the two representational types is required when data are interchanged in machine-readable form among data processing systems. However, if visual separators Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking p

38、ermitted without license from IHS-,-,-INCITS 31-2009 3 are needed to facilitate human understanding and readability, hyphens (-) or spaces may be displayed. 4.8 Class codes Associated with each County Code is a County Class Code. These codes are additional information for each county that identifies

39、 it as a county or incorporated place, or as having an obsolete name. 5. Duties of the maintenance agency 5.1 Assignment of county codes The maintenance agency shall carry out the functions related to assignment of county codes specified in 4.1 through 4.8 of this standard 5.2 Data accuracy and curr

40、ency The maintenance agency shall assure the accuracy and currency of names and county codes of the county and county equivalents. 5.3 Documentation and dissemination of data files The maintenance agency shall produce a complete file of the identified counties and county equivalents, and their assig

41、ned county codes. This file is publicly available at: http:/www.census.gov/geo/www/ansi/ansi.html. Changes shall be reported by the issuance of change notices, or by the re-issuance of the updated complete file. 5.4 Documentation and dissemination of user information The maintenance agency shall pre

42、pare information to aid users in applying the file of names and codes of states and state equivalents. The information shall include a description of the organization and characteristics of the data, including the layout of records and specification of fields. Characteristics of machine-readable med

43、ia containing the data files shall be given. This information is publicly available at: http:/www.census.gov/geo/www/ansi/ansi.html. 6. Designation of maintenance agency The functions assigned in INCITS 31 to the maintenance agency shall be administered by the U.S. Census Bureau. The class codes (An

44、nex A) are applied by the U.S. Census Bureau, Governments Division based on review of their governmental functions, organization, and fiscal responsibility. Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted w

45、ithout license from IHS-,-,-INCITS 31-2009 4 Annex A Class Codes (normative) CLASS CODES Class C: Incorporated Places Class Code Definition C7 Identifies an incorporated place that is an independent city: that is, it also serves as a county equivalent. Class H: Counties and Statistically Equivalent

46、Entities Class Code Definition H1 Identifies an active county or statistically equivalent entity that does not qualify under subclass C7 or H6. H4 Identifies a legally defined inactive or nonfunctioning county or statistically equivalent entity that does not qualify under subclass H6. H5 Identifies

47、census areas in Alaska, a statistical county equivalent entity. H6 Identifies a county or statistically equivalent entity that is areally coextensive or governmentally consolidated with an incorporated place, part of an incorporated place, or a consolidated city. Class X: Obsolete or Incorrect Names

48、 Class Code Definition X1 Identifies an incorporated place that is an independent city: that is, it also serves as a county equivalent. X2 Name of entity changed. X3 Name of entity incorrect or less preferred; entity may continue to exist, but is being dropped as not pertinent. X4 Entity absorbed by one or more surviving entities. X6 Entity abolished as no longer appropriate or pertinent. Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-INCITS 31-2009 5 Annex B