<?xml version="1.0" encoding="UTF-8"?>
<metadata>
	<idinfo>
		<citation>
			<citeinfo Sync="TRUE">
				<origin>TechniGraphics, Inc.</origin>
				<pubdate>20100219</pubdate>
				<title>State and Local Public Health Departments</title>
				<edition Sync="TRUE">2010 Q1</edition>
				<geoform Sync="TRUE">vector digital data</geoform>
				<onlink Sync="TRUE"></onlink></citeinfo>
		</citation>
		<descript Sync="TRUE">
			<abstract>
State and Local Public Health Departments

Governmental public health departments are responsible for creating and maintaining conditions that keep people healthy. A local health department may be locally governed, part of a region or district, be an office or an administrative unit of the state health department, or a hybrid of these. Furthermore, each community has a unique "public health system" comprising individuals and public and private entities that are engaged in activities that affect the public's health.

(Excerpted from the Operational Definition of a functional local health department, National Association of County and City Health Officials, November 2005)

Please reference http://www.naccho.org/topics/infrastructure/accreditation/upload/OperationalDefinitionBrochure-2.pdf for more information.

Facilities involved in direct patient care are intended to be excluded from this dataset; however, some of the entities represented in this dataset serve as both administrative and clinical locations. 

This dataset only includes the headquarters of Public Health Departments, not their satellite offices.

Some health departments encompass multiple counties; therefore, not every county will be represented by an individual record. Also, some areas will appear to have over representation depending on the structure of the health departments in that particular region.

Visiting nurses are represented in this dataset if they are contracted through the local government to fulfill the duties and responsibilities of the local health organization.

Effort was made by TechniGraphics to verify whether or not each health department tracks statistics on communicable diseases. 

Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries.

"#" and "*" characters were automatically removed from standard fields populated by TechniGraphics. Double spaces were replaced by single spaces in these same fields.

Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results.

All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. 

The currentness of this dataset is indicated by the [CONTDATE] field. Based on this field, the oldest record dates from 11/30/2009 and the newest record dates from 12/28/2009
</abstract>
			<purpose>
Homeland Security                

Use Cases: Use cases describe how the data may be used and help to define and clarify requirements.

1. A resource for preparing, mitigating, responding to and recovering from an emergency.  

2. A resource for outside responders to locate and aid in catastrophe response or disaster. 

3. A resource for situational awareness planning and response for Federal Government events.
</purpose>
		</descript>
		<timeperd>
			<timeinfo Sync="TRUE">
				<rngdates Sync="TRUE">
					<begdate Sync="TRUE">20091130</begdate>
					<enddate Sync="TRUE">20091228</enddate>
				</rngdates>
			</timeinfo>
			<current Sync="TRUE">ground condition</current>
		</timeperd>
		<status>
			<progress Sync="TRUE">Complete</progress>
			<update Sync="TRUE">Unknown</update>
		</status>
		<spdom Sync="TRUE">
			<bounding Sync="TRUE">
				<westbc Sync="TRUE">-124.418849</westbc>
				<eastbc Sync="TRUE">-116.970044</eastbc>
				<northbc Sync="TRUE">46.187865</northbc>
				<southbc Sync="TRUE">42.190262</southbc>
			</bounding>
		</spdom>
		<keywords Sync="TRUE">
			<theme>
				<themekt Sync="TRUE">LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/</themekt>
				<themekey>Public health administration.</themekey>
				<themekey>County health services</themekey>
				<themekey>Community health services--Administration.</themekey>
			</theme>
			<theme>
				<themekt>ISO 19115 Topic Category</themekt>
				<themekey>structure</themekey>
				<themekey>health</themekey>
			</theme>
			<place>
				<placekt>LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/</placekt>
				<placekey Sync="TRUE">Oregon</placekey>
			</place>
		</keywords>
		<accconst>None</accconst>
		<useconst>None</useconst>
		<ptcontac>
			<cntinfo>
				<cntperp>
					<cntper>Mike Thompson</cntper>
					<cntorg>TechniGraphics, Inc.</cntorg>
				</cntperp>
				<cntpos>Director of Research and Development</cntpos>
				<cntaddr>
					<addrtype Sync="TRUE">Mailing and Physical Address</addrtype>
					<address>3351 Eastbrook Drive</address>
					<city>Fort Collins</city>
					<state>CO</state>
					<postal Sync="TRUE">80525</postal>
					<country Sync="TRUE">USA</country>
				</cntaddr>
				<cntvoice>970-224-4996</cntvoice>
				<cntfax>970-224-3001</cntfax>
				<cntemail>mike.thompson@tgstech.com</cntemail>
				<hours Sync="TRUE">Monday - Friday 0800 - 1700 MST</hours>
			</cntinfo>
		</ptcontac>
		<secinfo Sync="TRUE">
			<secsys Sync="TRUE">DOD</secsys>
			<secclass>Unclassified</secclass>
			<sechandl>Unclassified</sechandl>
		</secinfo>
		<native Sync="TRUE">
Microsoft Windows XP Professional Version 2002 Service Pack 2

TGS PinPoint® v.1.11

Metadata written using TKME by Peter N. Schweitzer (U.S. Geological Survey, Reston, VA 22092) version 2.9.17 &lt;http://geology.usgs.gov/tools/metadata/&gt;

Metadata tested for compliance to FGDC-STD-001-1998 and converted to HTML using MP version 2.8.25 by Peter N. Schweitzer (U.S. Geological Survey) &lt;http://geology.usgs.gov/tools/metadata/&gt;
</native>
	</idinfo>
	<dataqual Sync="TRUE">
		<attracc Sync="TRUE">
			<attraccr>
For entities that were verified through alternate resources, the name, address, city, state, and five (5) digit zip codes were verified to be correct as of the date indicated by the [CONTDATE] field. The existence of the entity was also verified, as well as whether or not it met the criteria for inclusion in this dataset. Four (4) digit zip code extensions were derived from USPS (United States Postal Service) data and were not verified.

ID Check: The [ID] field is not blank and each of its values is unique.

Coordinate Check: Coordinates are not null or zero and the [X] and [Y] fields match the shape.

Basic Address Check: Physical addresses were verified to be non blank and to not be a "PO Box", "General Delivery", "Highway Contract", or "Rural Route" address.

Highway Address without Type Check: Physical addresses containing the word "Highway" or "Route" were verified to also contain a type designator such as "State", "US", or "County", if one actually exists for the highway or route. These type designators are often missing from addresses, leading to confusion if more than one "Highway" of the given number exists in an area.

Basic Name Check: Entity name is not blank, is not the same as entity city, and has a minimum of two (2) characters. Name does not contain punctuation characters that can interfere with database operations, such as " (quote) and * (asterisk).

City Check: Entity's [CITY] field is not blank, and entity is located within 25 miles of its tabular city as found in the NAVTEQ Named Places reference file.

State Check: The entity is located within its tabular state.

County Check: The entity is located within its tabular county.

FIPS Check: The tabular FIPS Code matches the entity's tabular county and tabular state.

County in Name vs. Geographic Location Check: If an entity's [NAME] field contains the word "county" or "co", the same county value should also be in the entity's [COUNTY] field.

Basic Phone Check: All phone numbers (including the area code) are ten (10) numeric digits. Alphabetic characters have been converted to the corresponding numeric digit.

NPA_NXX Check: Area codes (sometimes called "Number Planning Areas", or NPA's) and central office codes (sometimes known as exchanges, or NXX's) were validated against data from the North American Number Planning Administration (NANPA). In some cases, NPA-NXX combinations did not show up in the NANPA data but were verified to work.

Area Code Distance Check: The entity's area code (NPA) is valid, and the entity is not more than 25 miles from its area code boundary, as defined by data from the North American Number Planning Administration (NANPA), unless TechniGraphics has previously verified that the phone number rings to a headquarters location or otherwise does not ring to the entity's location.

Zip Code Check: The entity's zip code is five (5) or nine (9) numeric digits, is listed in the postal database, is in the same state as indicated by the entity's [STATE] value, and is not a PO Box only zip code.

Zip City Check: The entity's zip code and its city were verified to match according to the USPS Address Information System (AIS).

Zip Code Distance Check: The entity is located within 25 miles of its zip code boundary, as defined by the U.S. Census Bureau's 1999 Zip Code file.

NAICS Code Check: The NAICS field is not blank, the NAICS Code is one of the accepted codes for this layer, the NAICS Description is an acceptable Index Entry for the NAICS Code, and certain key words in the entity name do not conflict with the NAICS Code.

Collocation Check: Entities with different addresses must not share the exact same geospatial location.

Geographic Spell Check: Words that appear in the entity name were checked against a standard English word list (and Spanish word list for entities in Puerto Rico). Words not appearing in these standard word lists were then checked against names appearing in the Geographic Names Information System (GNIS) of geographic features that are located within 25 miles of the entity. Proper names were manually reviewed for correct spelling.

Supplied Coordinates Distance Check: Entity is located within 3 miles of coordinates supplied by the original source.
</attraccr>
		</attracc>
		<logic Sync="TRUE">See "Attribute_Accuracy_Report". Many of the checks described in that section check for both attribute accuracy and logical consistency.</logic>
		<complete Sync="TRUE">
Facilities involved in direct patient care are intended to be excluded from this dataset; however, some of the entities represented in this dataset serve as both administrative and clinical locations. 

This dataset only includes the headquarters of Public Health Departments, not their satellite offices.

Some health departments encompass multiple counties; therefore, not every county will be represented by an individual record. Also, some areas will appear to have over representation depending on the structure of the health departments in that particular region.

Visiting nurses are represented in this dataset if they are contracted through the local government to fulfill the duties and responsibilities of the local health organization.

TechniGraphics was not tasked with ensuring the completeness of this layer.
</complete>
		<posacc Sync="TRUE">
			<horizpa Sync="TRUE">
				<horizpar Sync="TRUE">
The horizontal accuracy is indicated by the [GEOPREC] field. Values are either "APPROXIMATE" or "ONENTITY". Based on the accuracy of the ortho imagery available to TechniGraphics, points are placed "ONENTITY" at the center of the main building. If the main building is not readily identifiable, points are placed "APPROXIMATE" at the center of the core building complex within the overall facility. If no specific core building complex is readily identifiable due to the size of the facility area or there being multiple building clusters, the point is placed "APPROXIMATE" in the center of the overall facility area. If the center of the overall facility area is unable to be determined, the point is placed "APPROXIMATE" along the correct street segment (block) on the correct side of the street.

Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries.
</horizpar>
			</horizpa>
		</posacc>
		<lineage>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>TechniGraphics, Inc.</origin>
						<pubdate>2009</pubdate>
						<title>TechniGraphics Research</title>
						<edition>Unspecified</edition>
						<geoform>tabular digital data</geoform>
					</citeinfo>
				</srccite>
				<typesrc>Digital Database File</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2009</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>TGS_Research</srccitea>
				<srccontr>This was used as a source for Public Health Departments in the United States.</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>NAVTEQ</origin>
						<pubdate>2009</pubdate>
						<title>NAVSTREETS</title>
						<edition>2009.2</edition>
						<geoform>vector digital data</geoform>
					</citeinfo>
				</srccite>
				<typesrc>CD-ROM</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2009</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>NAVTEQ_Streets_2009_Q2</srccitea>
				<srccontr>This version of NAVTEQ streets was used as a reference in the automatic geocoding and manual geolocating of entities during processing.</srccontr>
			</srcinfo>
			<procstep>
				<procdesc>
1) TechniGraphics attempted to contact alternate resources to determine or verify the entity's name, physical address, city, state, five (5) digit zip code, ten (10) digit phone number, and geospatial location. Contacts were asked to describe the entity's location relative to landmarks in reference data (mainly streets) and features visible in ortho imagery.

2) If TechniGraphics was unable to make contact with authoritative sources, verification was made through alternate references.

3) All text fields were set to all upper case.

4) Leading and trailing spaces were trimmed from all text fields.

5) Non printable and diacritic characters were removed from all text fields.
</procdesc>
				<srcused>TGS_Research</srcused>
				<srcused>NAVTEQ_Streets_2009_Q2</srcused>
				<procdate>20100219</procdate>
				<srcprod>Public_Health_Depts</srcprod>
				<proccont>
					<cntinfo>
						<cntperp>
							<cntper>Nicole Hackworth</cntper>
							<cntorg>TechniGraphics, Inc.</cntorg>
						</cntperp>
						<cntpos>Production Manager</cntpos>
						<cntaddr>
							<addrtype>Mailing and Physical Address</addrtype>
							<address>2000 Noble Drive</address>
							<city>Wooster</city>
							<state>OH</state>
							<postal>44691</postal>
							<country>USA</country>
						</cntaddr>
						<cntvoice>330-263-6222</cntvoice>
						<cntemail>nicole.hackworth@tgstech.com</cntemail>
						<hours>Monday - Friday 0800 - 1700 EST</hours>
					</cntinfo>
				</proccont>
			</procstep>
			<procstep><procdesc Sync="TRUE">Dataset copied.</procdesc><srcused Sync="TRUE"></srcused><procdate Sync="TRUE">20100624</procdate><proctime Sync="TRUE">18194600</proctime></procstep></lineage>
	</dataqual>
	<spdoinfo Sync="TRUE">
		<direct Sync="TRUE">Vector</direct>
		<ptvctinf Sync="TRUE">
			<sdtsterm Name="">
				<sdtstype Sync="TRUE">Entity point</sdtstype>
				<ptvctcnt Sync="TRUE">35</ptvctcnt>
			</sdtsterm>
		</ptvctinf>
	</spdoinfo>
	<spref Sync="TRUE">
		<horizsys Sync="TRUE">
			<geograph>
				<latres Sync="TRUE">0.000001</latres>
				<longres Sync="TRUE">0.000001</longres>
				<geogunit Sync="TRUE">Decimal degrees</geogunit>
			</geograph>
			<geodetic>
				<horizdn Sync="TRUE">D_WGS_1984</horizdn>
				<ellips Sync="TRUE">WGS_1984</ellips>
				<semiaxis Sync="TRUE">6378137.000000</semiaxis>
				<denflat Sync="TRUE">298.257224</denflat>
			</geodetic>
		</horizsys>
	</spref>
	<eainfo Sync="TRUE">
		<detailed Sync="TRUE" Name="">
			<enttyp Sync="TRUE">
				<enttypl>State and Local Public Health Departments</enttypl>
				<enttypd Sync="TRUE">
Governmental public health departments are responsible for creating and maintaining conditions that keep people healthy. A local health department may be locally governed, part of a region or district, be an office or an administrative unit of the state health department, or a hybrid of these. Furthermore, each community has a unique "public health system" comprising individuals and public and private entities that are engaged in activities that affect the public's health.

Please reference http://www.naccho.org/topics/infrastructure/accreditation/upload/OperationalDefinitionBrochure-2.pdf for more information.
</enttypd>
				<enttypds Sync="TRUE">Operational Definition of a functional local health department, National Association of County and City Health Officials, November 2005</enttypds>
			</enttyp>
			<attr>
				<attrlabl Sync="TRUE">FID</attrlabl>
				<attrdef Sync="TRUE">Internal feature number.</attrdef>
				<attrdefs Sync="TRUE">ESRI</attrdefs>
				<attrdomv>
					<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl Sync="TRUE">SHAPE</attrlabl>
				<attrdef Sync="TRUE">Feature geometry.</attrdef>
				<attrdefs Sync="TRUE">ESRI</attrdefs>
				<attrdomv>
					<udom Sync="TRUE">Coordinates defining the features.</udom>
				</attrdomv>
			</attr>
			<attr Sync="TRUE">
				<attrlabl Sync="TRUE">ID</attrlabl>
				<attrdef Sync="TRUE">Unique identifier for feature assigned by TechniGraphics. These identifiers are intended to be unique across all layers on which TechniGraphics has worked.</attrdef>
				<attrdefs Sync="TRUE">TechniGraphics</attrdefs>
				<attrdomv Sync="TRUE">
					<udom>Text</udom>
				</attrdomv>
			</attr>
			<attr Sync="TRUE">
				<attrlabl>SECCLASS</attrlabl>
				<attrdef Sync="TRUE">Security classification of feature.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv Sync="TRUE">
					<edom Sync="TRUE">
						<edomv Sync="TRUE">UNCLASSIFIED</edomv>
						<edomvd Sync="TRUE">Entity is unclassified.</edomvd>
						<edomvds Sync="TRUE">TechniGraphics</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr Sync="TRUE">
				<attrlabl Sync="TRUE">NAME</attrlabl>
				<attrdef Sync="TRUE">Name of entity.</attrdef>
				<attrdefs Sync="TRUE">TechniGraphics</attrdefs>
				<attrdomv>
					<udom Sync="TRUE">Text</udom>
				</attrdomv>
			</attr>
			<attr Sync="TRUE">
				<attrlabl>TELEPHONE</attrlabl>
				<attrdef Sync="TRUE">Ten (10) digit telephone number for entity formatted as nnn-nnn-nnnn.</attrdef>
				<attrdefs Sync="TRUE">TechniGraphics</attrdefs>
				<attrdomv Sync="TRUE">
					<udom>Phone numbers formatted as nnn-nnn-nnnn. Only numeric digits are used. The area code and exchange must form a valid combination. A list of valid area code and exchange combinations can be obtained from &lt;http://www.nanpa.com&gt;.</udom>
				</attrdomv>
			</attr>
			<attr Sync="TRUE">
				<attrlabl>ADDRESS</attrlabl>
				<attrdef Sync="TRUE">Physical street address for entity. "PO Box", "General Delivery", "Rural Route", and "Highway Contract" addresses are not considered physical addresses and should not appear in this field. Some areas do not have regular city style addressing, so entities in those areas may not have a street number. In such cases, the name of the road on which they are located is listed in this field. Some rural areas may not have named roads. In these rare cases, this field will be blank.</attrdef>
				<attrdefs Sync="TRUE">TechniGraphics</attrdefs>
				<attrdomv>
					<udom Sync="TRUE">Text</udom>
				</attrdomv>
			</attr>
			<attr Sync="TRUE">
				<attrlabl>ADDRESS2</attrlabl>
				<attrdef Sync="TRUE">Location within physical address, e.g., floor, suite, building.</attrdef>
				<attrdefs Sync="TRUE">TechniGraphics</attrdefs>
				<attrdomv>
					<udom Sync="TRUE">Text</udom>
				</attrdomv>
			</attr>
			<attr Sync="TRUE">
				<attrlabl Sync="TRUE">CITY</attrlabl>
				<attrdef Sync="TRUE">
The name of the city associated with the entity's physical address. For physical addresses that the U.S. Postal Service (USPS) delivers to, this should be a "city" acceptable to the USPS as defined in their Address Information System (AIS). Sometimes the USPS does not deliver mail to a physical address but recognizes the location (i.e., they list the location as "undeliverable"). The cities associated with these locations are acceptable. In some cases, the USPS does not recognize individual physical addresses in a city; rather, they list the city as having "General Delivery". In these cases, the city and associated zip code are acceptable (the entity's [ADDRESS] field will contain a street address, not "general delivery"). The entity may not actually be located within the city limits of the "city" specified in its [CITY] field. Instead, it may actually be located within the city limits of another city. In some cases, the "city" that appears in this field may not even be a city in an administrative sense, but it is still an acceptable "city" to the USPS. An example of this is "Notre Dame, IN". There is no city in Indiana called "Notre Dame", but this is considered an acceptable city by the USPS for any delivery going to the University of Notre Dame which is actually located in the city of South Bend. "Notre Dame", like most USPS cities, is an easily recognized place, and it gives the user of the data a good general idea of where the entity is located (if the entity is located in a small municipality, the USPS "city" may be more recognizable than the name of the municipality), and it would be part of the address one would use to send a shipment to the entity's location. Using the USPS acceptable "city" also allows someone to do a logical consistency check between the zip code and the city by using the USPS AIS.

Sometimes an entity may report a city that is not accepted by the USPS, and although TechniGraphics has tried to replace those cities with an acceptable alternative, some of them may remain in this dataset.
</attrdef>
				<attrdefs Sync="TRUE">TechniGraphics</attrdefs>
				<attrdomv>
					<udom>Text</udom>
				</attrdomv>
			</attr>
			<attr Sync="TRUE">
				<attrlabl Sync="TRUE">STATE</attrlabl>
				<attrdef Sync="TRUE">Two (2) character abbreviation for state associated with the entity's physical address. In almost all cases, this is the same as the state where the entity has been depicted geospatially. However, there are cases, particularly where an entity is part of a larger facility that cuts across state lines, where the entity's location may be depicted in a state other than the one indicated in this field. Also, the state in which an entity appears to be located may change depending on the scale of the state boundary theme being used.</attrdef>
				<attrdefs Sync="TRUE">TechniGraphics</attrdefs>
				<attrdomv>
					<codesetd>
						<codesetn>Official USPS Abbreviations - State Abbreviations</codesetn>
						<codesets>United States Postal Service http://www.usps.com/ncsc/lookups/usps_abbreviations.html</codesets>
					</codesetd>
				</attrdomv>
			</attr>
			<attr Sync="TRUE">
				<attrlabl>ZIP</attrlabl>
				<attrdef Sync="TRUE">Five (5) digit USPS zip code for entity's physical location.</attrdef>
				<attrdefs Sync="TRUE">TechniGraphics</attrdefs>
				<attrdomv>
					<codesetd>
						<codesetn>USPS Address Information System - Domain is further restricted by only allowing physical (non PO Box) zip codes.</codesetn>
						<codesets>United States Postal Service</codesets>
					</codesetd>
				</attrdomv>
			</attr>
			<attr Sync="TRUE">
				<attrlabl>ZIPP4</attrlabl>
				<attrdef Sync="TRUE">Four (4) digit USPS zip code extension.  These values are automatically assigned using the entity's physical address and USPS address information system (AIS) data.</attrdef>
				<attrdefs Sync="TRUE">TechniGraphics</attrdefs>
				<attrdomv>
					<codesetd>
						<codesetn>USPS Address Information System (AIS) - ZIP9</codesetn>
						<codesets>United States Postal Service</codesets>
					</codesetd>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl Sync="TRUE">COUNTY</attrlabl>
				<attrdef Sync="TRUE">County name where entity is located.</attrdef>
				<attrdefs Sync="TRUE">TechniGraphics</attrdefs>
				<attrdomv>
					<codesetd>
						<codesetn>Geographic Names Information System (GNIS)</codesetn>
						<codesets>US Department of the Interior - US Geologic Survey</codesets>
					</codesetd>
				</attrdomv>
			</attr>
			<attr Sync="TRUE">
				<attrlabl>FIPS</attrlabl>
				<attrdef Sync="TRUE">Five (5) digit FIPS (Federal Information Processing Standards) Code for the County where entity is located. The first two (2) digits represent the state and the last three (3) digits identify the county within the state.</attrdef>
				<attrdefs Sync="TRUE">TechniGraphics</attrdefs>
				<attrdomv>
					<codesetd>
						<codesetn>
Federal Information Processing Standards Publications - Counties and Equivalent Entities of the U.S., Its Possessions,
and Associated Areas.
</codesetn>
						<codesets>National Institute of Standards and Technology (NIST) &lt;http://www.itl.nist.gov/fipspubs/co-codes/states.txt&gt;</codesets>
					</codesetd>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl Sync="TRUE">DIRECTIONS</attrlabl>
				<attrdef Sync="TRUE">A description of the entity's location or status.</attrdef>
				<attrdefs Sync="TRUE">TechniGraphics</attrdefs>
				<attrdomv>
					<udom>Text</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>EMERGTITLE</attrlabl>
				<attrdef Sync="TRUE">Title of person or name of office for emergency point of contact.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<udom>Text</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>EMERGTEL</attrlabl>
				<attrdef Sync="TRUE">Ten (10) digit telephone number of emergency point of contact formatted as nnn-nnn-nnnn. All alphabetic characters have been translated to the corresponding numeric digit.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<udom>Phone numbers, including area code, formatted as nnn-nnn-nnnn. A list of valid area code and exchange combinations can be found at http://www.nanpa.com</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>EMERGEXT</attrlabl>
				<attrdef Sync="TRUE">Telephone extension for emergency point of contact.</attrdef>
				<attrdefs Sync="TRUE">TechniGraphics</attrdefs>
				<attrdomv>
					<udom>Text</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>CONTDATE</attrlabl>
				<attrdef Sync="TRUE">Date entity was contacted by TechniGraphics.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<udom>Date</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>CONTHOW</attrlabl>
				<attrdef Sync="TRUE">Method by which entity was contacted.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<edom>
						<edomv>ALT REF</edomv>
						<edomvd>Geospatial reference information obtained from local authorities, e.g., downloadable parcel maps, 911 streets, and shape files.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>PHONE</edomv>
						<edomvd>Entity was contacted by phone.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>&lt;BLANK&gt;</edomv>
						<edomvd>Entity has not been contacted by TechniGraphics.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>GEODATE</attrlabl>
				<attrdef>Date entity was geocoded by TechniGraphics.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<udom>Date</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl Sync="TRUE">GEOHOW</attrlabl>
				<attrdef>Method by which entity was geocoded.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<edom>
						<edomv>MANUAL</edomv>
						<edomvd>Entity was manually geocoded.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl Sync="TRUE">NAICSCODE</attrlabl>
				<attrdef>NAICS (North American Industry Classification System) Code for entity. NAICS Codes (and NAICS Descriptions) have been assigned based upon the entity's primary function, regardless of if that is the function that qualified it to be included in this dataset.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<codesetd>
						<codesetn>North American Industry Classification System (NAICS 2007)</codesetn>
						<codesets>US Census Bureau - &lt;http://www.census.gov/epcd/www/naics.html&gt;</codesets>
					</codesetd>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl Sync="TRUE">NAICSDESCR</attrlabl>
				<attrdef>NAICS (North American Industry Classification System) Description for entity. The "Index Entries" that appear on the NAICS webpage (http://www.census.gov/epcd/www/naics.html) are being used to populate this attribute as opposed to the "NAICS Title". While there is a one to one correspondence between NAICS Codes and "NAICS Titles", there is a one to many relationship between NAICS Codes and the "Index Entries". By using the "Index Entries", we have placed the entities that make up this layer into more specific categories; however, the user of this data should be aware that this was not the intended purpose of these "Index Entries". The "Index Entries" were intended as a way to search the NAICS database and as a way of enumerating ways in which establishments falling under the given NAICS Code may be named. Thus, there are often two or more "Index Entries" that are synonyms, for example: "Prisons" and "Penitentiaries". In cases like this, we have standardized on one "Index Entry".  NAICS Descriptions (and NAICS Codes) have been assigned based upon the entity's primary function, regardless of the function that qualified it to be included in this dataset.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<edom>
						<edomv>COMMUNITY HEALTH PROGRAMS ADMINISTRATION</edomv>
						<edomvd>
[NAICS Code: 923120]: This industry comprises government establishments primarily engaged in the planning, administration, and coordination of public health programs and services, including environmental health activities, mental health, categorical health programs, health statistics, and immunization services. Government establishments primarily engaged in conducting public health-related inspections are included in this industry.

Entities that operate at the local or tribal level of government are classified under this description.
</edomvd>
						<edomvds>U.S. Census Bureau</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>HEALTH PROGRAM ADMINISTRATION</edomv>
						<edomvd>
[NAICS Code: 923120]: This industry comprises government establishments primarily engaged in the planning, administration, and coordination of public health programs and services, including environmental health activities, mental health, categorical health programs, health statistics, and immunization services. Government establishments primarily engaged in conducting public health-related inspections are included in this industry.

Entities that operate at the state or other level of government are classified under this description.
</edomvd>
						<edomvds>U.S. Census Bureau</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl Sync="TRUE">GEOLINKID</attrlabl>
				<attrdef>Link ID for the street segment to which the entity was geocoded. Refer to the [ST_VENDOR] and [ST_VERSION] fields for the street vendor and version that was used to geocode the entity.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<udom>Text</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl Sync="TRUE">X</attrlabl>
				<attrdef>Longitude in WGS 84 Decimal Degrees.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>-180</rdommin>
						<rdommax>180</rdommax>
						<attrunit>WGS 84 Decimal Degrees</attrunit>
					</rdom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl Sync="TRUE">Y</attrlabl>
				<attrdef>Latitude in WGS 84 Decimal Degrees.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>-90</rdommin>
						<rdommax>90</rdommax>
						<attrunit>WGS 84 Decimal Degrees</attrunit>
					</rdom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>ST_VENDOR</attrlabl>
				<attrdef>Indicates name of vendor providing original street data used for geocoding.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<edom>
						<edomv>NAVTEQ</edomv>
						<edomvd>NAVTEQ streets were used for geocoding.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>TGS</edomv>
						<edomvd>TechniGraphics drew in a new street segment that does not exist in the file supplied by NAVTEQ.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>&lt;BLANK&gt;</edomv>
						<edomvd>Entity was geocoded using coordinates provided by the original source; therefore, the street vendor is unknown.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr Sync="TRUE">
				<attrlabl>ST_VERSION</attrlabl>
				<attrdef>Indicates the year and quarter of streets used for geocoding.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<edom>
						<edomv>2009Q2</edomv>
						<edomvd>2nd Quarter 2009 NAVTEQ street data was used for geocoding.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>&lt;BLANK&gt;</edomv>
						<edomvd>Entity was geocoded using coordinates provided by the original source; therefore, the street version is unknown.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl Sync="TRUE">GEOPREC</attrlabl>
				<attrdef>Geocoding precision.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<edom>
						<edomv>APPROXIMATE</edomv>
						<edomvd>Entity is geocoded either to the center of the core building cluster, to the center of the facility area per aerial imagery (in most cases USGS DOQQs), or to the correct block and correct side of street per street data indicated by [ST_VENDOR] and [ST_VERSION].</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>ONENTITY</edomv>
						<edomvd>Entity is geocoded on entity rooftop per aerial imagery (in most cases USGS DOQQs). If entity is not plotted on rooftop, it will be denoted in the [DIRECTIONS] field.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl Sync="TRUE">PHONELOC</attrlabl>
				<attrdef>Indicates whether the phone number in the [TELEPHONE] field rings to the actual location of the entity.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<edom>
						<edomv>YES</edomv>
						<edomvd>Phone number rings to the actual entity location.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>NO</edomv>
						<edomvd>Phone number does not ring to the actual entity location. It may ring to an administrative office or central location.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>&lt;BLANK&gt;</edomv>
						<edomvd>Unknown - It is not known if the entity's phone number rings to the entity's location.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>QC_QA</attrlabl>
				<attrdef>Organization that performed Quality Control/Quality Assurance on the record.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<edom>
						<edomv>TECHNIGRAPHICS</edomv>
						<edomvd>TechniGraphics has performed Quality Control/Quality Assurance on the entity record.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>&lt;BLANK&gt;</edomv>
						<edomvd>The record was not added by TechniGraphics or has not had Quality Control/Quality Assurance performed by TechniGraphics.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>WEBSITE</attrlabl>
				<attrdef>Uniform Resource Locator (URL) for website associated with facility.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<udom>Text</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>GNIS_ID</attrlabl>
				<attrdef>
Geographic Names Information System ID

A permanent, unique number assigned to a geographic feature for the sole purpose of uniquely identifying that feature as a record in any information system database, dataset, file, or document and for distinguishing it from all other feature records so identified. The number is assigned sequentially (highest existing number plus one) to new records as they are created in the Geographic Names Information System. The number, by design, carries no information or association to the content of the feature record and therefore is not subject to change as attribute values change. Once assigned to a feature, the number is never changed or withdrawn, and never reassigned. The Feature ID can be applied in conjunction with system-unique record identifiers in any database or system, thus providing a national standard common reference identifier across multiple datasets. The Feature ID is stored in the GNIS database as an integer with a maximum of ten digits.
</attrdef>
				<attrdefs>(http://geonames.usgs.gov/domestic/metadata.htm) - U.S. Geological Survey, 19810501, U.S. Geographic Names Information System (GNIS)</attrdefs>
				<attrdomv>
					<udom>Text</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>SOURCE</attrlabl>
				<attrdef>Original source of entity record.</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<edom>
						<edomv>TECHNIGRAPHICS</edomv>
						<edomvd>Entity information was provided by TechniGraphics.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>GOVT_LEVEL</attrlabl>
				<attrdef>
Government Level

The level of government at which the entity operates.
</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<edom>
						<edomv>LOCAL</edomv>
						<edomvd>Entity operates at the local level of government.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>OTHER</edomv>
						<edomvd>Entity is not government-run but is contracted by state, local, or tribal government to serve in a health department capacity.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>STATE</edomv>
						<edomvd>Entity operates at the state level of government</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>TRIBAL</edomv>
						<edomvd>Entity operates at the tribal level of government.</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>TOT_STAFF</attrlabl>
				<attrdef>
Total Staff

Total number of staff at the health department.
</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<udom>Number</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>SPEC_EQUIP</attrlabl>
				<attrdef>
Specialized Equipment

Indicates whether or not the entity has specialized equipment.
</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<edom>
						<edomv>YES</edomv>
						<edomvd>Entity does have specialized equipment</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>NO</edomv>
						<edomvd>Entity does not have specialized equipment</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>&lt;BLANK&gt;</edomv>
						<edomvd>It is unknown whether or not the health department has specialized equipment</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>SDR</attrlabl>
				<attrdef>
Surveillance Data Repository

Indicates whether or not the entity tracks statistics on communicable diseases.
</attrdef>
				<attrdefs>TechniGraphics</attrdefs>
				<attrdomv>
					<edom>
						<edomv>YES</edomv>
						<edomvd>Entity does track communicable diseases</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>NO</edomv>
						<edomvd>Entity does not track communicable diseases</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>&lt;BLANK&gt;</edomv>
						<edomvd>It is unknown whether or not the entity tracks communicable diseases</edomvd>
						<edomvds>TechniGraphics</edomvds>
					</edom>
				</attrdomv>
			</attr>
		</detailed>
	</eainfo>
	<metainfo>
		<metd>20100219</metd>
		<metc>
			<cntinfo>
				<cntperp>
					<cntper>Mike Thompson</cntper>
					<cntorg>TechniGraphics, Inc.</cntorg>
				</cntperp>
				<cntpos>Director of Research and Development</cntpos>
				<cntaddr>
					<addrtype>Mailing and Physical Address</addrtype>
					<address>3351 Eastbrook Drive</address>
					<city>Fort Collins</city>
					<state>CO</state>
					<postal>80525</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>970-224-4996</cntvoice>
				<cntfax>970-224-3001</cntfax>
				<cntemail>mike.thompson@tgstech.com</cntemail>
				<hours>Monday - Friday 0800 - 1700 MST</hours>
			</cntinfo>
		</metc>
		<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
		<metstdv>FGDC-STD-001-1998</metstdv>
	</metainfo>
	<Esri><MetaID>{F789152E-3D81-43F1-8430-1D20B6F164F4}</MetaID><CreaDate>20100624</CreaDate><CreaTime>18194600</CreaTime><SyncOnce>TRUE</SyncOnce><DataProperties><lineage><Process ToolSource="C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\Project" Date="20100624" Time="181946">Project F:\geo_gis\HSIP\TGS_WGS84\2010_02_19_OR_Public_Health_Departments\2010_02_19_OR_Public_Health_Departments.shp F:\geo_gis\HSIP\TGS_WGS84\ORLAM\2010_02_19_OR_Public_Health.shp PROJCS['NAD_1983_Oregon_Statewide_Lambert_Feet_Intl',GEOGCS['GCS_North_American_1983',DATUM['D_North_American_1983',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Lambert_Conformal_Conic'],PARAMETER['False_Easting',1312335.958005249],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-120.5],PARAMETER['Standard_Parallel_1',43.0],PARAMETER['Standard_Parallel_2',45.5],PARAMETER['Latitude_Of_Origin',41.75],UNIT['Foot',0.3048]] NAD_1983_To_WGS_1984_1 GEOGCS['GCS_WGS_1984',DATUM['D_WGS_1984',SPHEROID['WGS_1984',6378137.0,298.257223563]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]]</Process></lineage></DataProperties></Esri><distInfo><distributor><distorTran><onLineSrc><linkage Sync="TRUE">file://</linkage><protocol Sync="TRUE">Local Area Network</protocol></onLineSrc></distorTran></distributor></distInfo></metadata>
