<?xml version="1.0" encoding="UTF-8"?><metadata>
<idinfo>
<citation>
<citeinfo>
<origin>TechniGraphics, Inc.</origin>
<pubdate>20080919</pubdate>
<edition>4th Quarter 2008</edition>
<geoform>vector digital data</geoform>
<ftname>ems</ftname>
<onlink>withheld</onlink>
<title>Emergency Medical Services</title>
</citeinfo>
</citation>
<descript>
<abstract>
EMS Locations in North Carolina
The EMS stations dataset consists of any location where emergency medical services (EMS) personnel are stationed or based out of, or where equipment that such personnel use in carrying out their jobs is stored for ready use. Ambulance services are included even if they only provide transportation services, but not if they are located at, and operated by, a hospital. If an independent ambulance service or EMS provider happens to be collocated with a hospital, it will be included in this dataset. The dataset includes both private and governmental entities.
This dataset is comprised completely of license free data.
The Fire Station dataset and the EMS dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes.
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.
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 upon this field, the oldest record dates from 01/05/2005 and the newest record dates from 08/15/2008
</abstract>
<purpose>
Homeland Security
Use Cases: Use cases describe how the data may be used and help to define and clarify requirements.
1. An assessment of whether or not the total emergency medical services capability in a given area is adequate.
2. A list of resources to draw upon by surrounding areas when local resources have temporarily been overwhelmed by a disaster - route analysis can determine those entities that are able to respond the quickest.
3. A resource for Emergency Management planning purposes.
4. A resource for catastrophe response to aid in the retrieval of equipment by outside responders in order to deal with the disaster.
5. A resource for situational awareness planning and response for Federal Government events.
</purpose>
<langdata>en</langdata>
</descript>
<timeperd>
<timeinfo>
<rngdates>
<begdate>20050105</begdate>
<enddate>20080815</enddate>
</rngdates>
<sngdate>
<caldate>The year (and optionally month, or month and day) for which the data set corresponds to the ground.</caldate>
</sngdate>
</timeinfo>
<current>ground condition</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>Unknown</update>
</status>
<spdom>
<bounding>
<westbc>-84.312103</westbc>
<eastbc>-75.424460</eastbc>
<northbc>36.579997</northbc>
<southbc>33.751698</southbc>
</bounding>
<lboundng>
<leftbc>133652.358088</leftbc>
<rightbc>929791.715621</rightbc>
<bottombc>12508.484142</bottombc>
<topbc>313962.330662</topbc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekt>LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/</themekt>
<themekey>Airplane ambulances</themekey>
<themekey>Ambulances</themekey>
<themekey>Ambulance service.</themekey>
<themekey>Emergency medical services.</themekey>
<themekey>Emergency medical personnel.</themekey>
<themekey>Fire departments.</themekey>
<themekey>Fire stations.</themekey>
<themekey>Helicopter ambulances</themekey>
<themekey>Search and rescue operations.</themekey>
</theme>
<theme>
<themekt>ISO 19115 Topic Category</themekt>
<themekey>structure</themekey>
</theme>
<place>
<placekt>LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/</placekt>
<placekey>North Carolina</placekey>
</place>
</keywords>
<accconst>None</accconst>
<useconst>None</useconst>
<ptcontac>
<cntinfo>
<cntperp>
<cntper>Mike Thompson</cntper>
<cntorg>TechniGraphics, Inc.</cntorg>
</cntperp>
<cntpos>Director of Geospatial Datasets</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>mthompson@tgstech.com</cntemail>
<hours>Monday - Friday, 0800 - 1700 MST</hours>
</cntinfo>
</ptcontac>
<secinfo>
<secsys>DOD</secsys>
<secclass>Unclassified</secclass>
<sechandl>Unclassified</sechandl>
</secinfo>
<native>ESRI ArcCatalog 9.3.1.1850</native>
<natvform>Feature Class</natvform>
</idinfo>
<dataqual>
<attracc>
<attraccr>
For entities that were contacted, 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 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 FIPS to State Compare Check: The county represented by the tabular FIPS Code is actually in the state specified in the [STATE] field.
County Name to State Compare Check: The county represented by the tabular county name is actually in the state specified in the [STATE] 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 TGS 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 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.
</attraccr>
</attracc>
<logic>See "Attribute_Accuracy_Report". Many of the checks described in that section check for both attribute accuracy and logical consistency.</logic>
<complete>
The EMS dataset only includes entities that provide transportation and does not include fixed location clinics or hospitals, as these are included in other datasets.
Administrative Locations: Locations that serve only an administrative function (e.g., a business office) are intended to be excluded from this dataset. Locations that serve both an administrative function as well as an operational function are included in the dataset.
</complete>
<posacc>
<horizpa>
<horizpar>
The geographic location of entities was verified to be correct relative to the street data and version indicated by the [ST_VENDOR] and [ST_VERSION] fields. The horizontal accuracy is indicated by the [GEOPREC] field. A value of "BLOCKFACE" indicates the entity was geocoded on the correct street segment (block) and correct side of the street. A value of "ONENTITY" indicates that the location is on the entity's facility, as determined by USGS DOQQ imagery, and that it is on the correct street segment (block) and correct side of the street. Entities that are part of a larger institution (e.g., University Campus or Military Base) with "BLOCKFACE" precision may be located at the main entrance to the larger institution.
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.
Emergency Medical Services not having a permanent location are depicted at the city/town hall or at the center of the town or service area if a city/town hall does not exist.
</horizpar>
</horizpa>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>TechniGraphics, Inc.</origin>
<pubdate>20080513</pubdate>
<title>Emergency Medical Services 2008 Q2</title>
<edition>2nd Quarter 2008</edition>
<geoform>vector digital data</geoform>
</citeinfo>
</srccite>
<typesrc>Digital Database File</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>20041229</begdate>
<enddate>20080501</enddate>
</rngdates>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>EMS_2008_Q2</srccitea>
<srccontr>The basic attribution (name, address, city, state, zip code, and telephone number) came from this dataset, unless the entity was updated by TGS during Q408 processing.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>North Carolina State Center for Health Statistics (NCSCHS)</origin>
<pubdate>20040301</pubdate>
<title>NCEMS</title>
<edition>Unspecified</edition>
<geoform>vector digital data</geoform>
</citeinfo>
</srccite>
<typesrc>Electronic Mail System</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>20040301</caldate>
</sngdate>
</timeinfo>
<srccurr>publication date</srccurr>
</srctime>
<srccitea>NC_EMS_1</srccitea>
<srccontr>This was used as a source for emergency medical services in North Carolina.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>North Carolina Office of State Fire Marshal (NCOSFM)</origin>
<pubdate>20080305</pubdate>
<title>Directory of Fire Departments and Rescue Squads</title>
<edition>Unspecified</edition>
<geoform>vector digital data</geoform>
<onlink>withheld</onlink>
</citeinfo>
</srccite>
<typesrc>Online</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>20080305</caldate>
</sngdate>
</timeinfo>
<srccurr>publication date</srccurr>
</srctime>
<srccitea>NC_EMS_2</srccitea>
<srccontr>This was used as a source for emergency medical services in North Carolina.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>United States Fire Administration (USFA)</origin>
<pubdate>20061201</pubdate>
<title>USFA National Fire Department Census Database</title>
<edition>Unspecified</edition>
<geoform>vector digital data</geoform>
</citeinfo>
</srccite>
<typesrc>CD-ROM</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>20061201</caldate>
</sngdate>
</timeinfo>
<srccurr>publication date</srccurr>
</srctime>
<srccitea>NFDC_1</srccitea>
<srccontr>This was used as a source for emergency medical services in the United States.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>United States Fire Administration (USFA)</origin>
<pubdate>20071128</pubdate>
<title>USFA National Fire Department Census Database</title>
<edition>Unspecified</edition>
<geoform>vector digital data</geoform>
</citeinfo>
</srccite>
<typesrc>CD-ROM</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>20071128</caldate>
</sngdate>
</timeinfo>
<srccurr>publication date</srccurr>
</srctime>
<srccitea>NFDC_2</srccitea>
<srccontr>This was used as a source for emergency medical services in the United States.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>NAVTEQ</origin>
<pubdate>2007</pubdate>
<title>NAVSTREETS</title>
<edition>2007.2</edition>
<geoform>vector digital data</geoform>
</citeinfo>
</srccite>
<typesrc>CD-ROM</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>2007</caldate>
</sngdate>
</timeinfo>
<srccurr>publication date</srccurr>
</srctime>
<srccitea>NAVTEQ_Streets_2007_Q2</srccitea>
<srccontr>This version of NAVTEQ streets was used as a reference for automatic shifting of entities that were previously manually geocoded and for the automatic geocoding and manual geolocating of entities.</srccontr>
</srcinfo>
<procstep>
<procdesc>
1) The Fire Station dataset and the EMS dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes.
&gt;
&gt;
2) Entities were processed to determine or verify their name, physical address, city, state, five (5) digit zip code, phone number, and geospatial location. Entities that were contacted were also asked if they provided fire protection services, EMS services, or both. Entities not located on military bases were contacted and asked to describe their location relative to landmarks in reference data (mainly streets) and features visible in ortho imagery. A phone number was not available for some entities, so their information was verified using other verbal contacts made through a telephone call.
&gt;
&gt;
3) Due to a request made by the Department of Defense, TGS made every effort to not contact military bases starting 03/27/2007 and ending 05/28/2008. During this time, entities located on military bases were verified through alternate resources, such as maps and ortho imagery. These records have not been contacted by TGS, and therefore, do not have directions.
&gt;
&gt;
4) All text fields were set to all upper case.
&gt;
&gt;
5) Leading and trailing spaces were trimmed from all text fields.
&gt;
&gt;
6) Non printable and diacritic characters were removed from all text fields.
&gt;
&gt;
</procdesc>
<srcused>withheld</srcused>
<srcused>withheld</srcused>
<srcused>withheld</srcused>
<srcused>withheld</srcused>
<srcused>withheld</srcused>
<srcused>withheld</srcused>
<procdate>20080919</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntperp>
<cntper>Nicole Hackworth</cntper>
<cntorg>TechniGraphics, Inc.</cntorg>
</cntperp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>Mailing and Physical Address</addrtype>
<address>2000 Noble Drive</address>
<city>Wooster</city>
<state>Ohio</state>
<postal>44691</postal>
<country>USA</country>
</cntaddr>
<cntvoice>330-263-6222</cntvoice>
<cntemail>nhackworth@tgstech.com</cntemail>
<hours>Monday - Friday, 0730 - 1630 EST</hours>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>Metadata imported.</procdesc>
<srcused>withheld</srcused>
<procdate>20090330</procdate>
<proctime>11203400</proctime>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct>Vector</direct>
<ptvctinf>
<esriterm Name="ems">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="1"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">1767</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<planar>
<planci>
<plance>coordinate pair</plance>
<coordrep>
<absres>0.000433</absres>
<ordres>0.000433</ordres>
</coordrep>
<plandu>meters</plandu>
</planci>
</planar>
<geodetic>
<horizdn>North American Datum of 1983</horizdn>
<ellips>Geodetic Reference System 80</ellips>
<semiaxis>6378137.000000</semiaxis>
<denflat>298.257222</denflat>
</geodetic>
<cordsysn>
<geogcsn>GCS_North_American_1983</geogcsn>
<projcsn>NAD_1983_StatePlane_North_Carolina_FIPS_3200</projcsn>
</cordsysn>
</horizsys>
<vertdef>
<altsys>
<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
<altres>1.000000</altres>
</altsys>
</vertdef>
</spref>
<eainfo>
<detailed Name="ems">
<enttyp>
<enttypl Sync="FALSE">ems</enttypl>
<enttypd>The EMS stations dataset consists of any location where emergency medical services (EMS) personnel are stationed or based out of, or where equipment that such personnel use in carrying out their jobs is stored for ready use. Ambulance services are included even if they only provide transportation services, but not if they are located at, and operated by, a hospital. If an independent ambulance service or EMS provider happens to be collocated with a hospital, it will be included in this dataset. The dataset includes both private and governmental entities.</enttypd>
<enttypds>TGS</enttypds>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">1767</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
<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>SHAPE</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
<attalias Sync="TRUE">SHAPE</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ID</attrlabl>
<attrdef>Unique identifier for feature.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">ID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>SECCLASS</attrlabl>
<attrdef>Security classification of feature.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<edom>
<edomv>UNCLASSIFIED</edomv>
<edomvd>Entity is unclassified.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">SECCLASS</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>NAME</attrlabl>
<attrdef>Name of entity.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">NAME</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>TELEPHONE</attrlabl>
<attrdef>Ten (10) digit telephone number for entity formatted as nnn-nnn-nnnn.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<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>
<attalias Sync="TRUE">TELEPHONE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">12</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ADDRESS</attrlabl>
<attrdef>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>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">ADDRESS</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">80</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ADDRESS2</attrlabl>
<attrdef>Location within physical address, e.g., floor, suite, building.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">ADDRESS2</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">80</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>CITY</attrlabl>
<attrdef>
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 TGS has tried to replace those cities with an acceptable alternative, some of them may remain in this dataset.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">CITY</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">120</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>STATE</attrlabl>
<attrdef>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>TGS</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>
<attalias Sync="TRUE">STATE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ZIP</attrlabl>
<attrdef>Five (5) digit USPS zip code for entity's physical location.</attrdef>
<attrdefs>TGS</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>
<attalias Sync="TRUE">ZIP</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ZIPP4</attrlabl>
<attrdef>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>TGS</attrdefs>
<attrdomv>
<codesetd>
<codesetn>USPS Address Information System (AIS) - ZIP9</codesetn>
<codesets>United States Postal Service</codesets>
</codesetd>
</attrdomv>
<attalias Sync="TRUE">ZIPP4</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>COUNTY</attrlabl>
<attrdef>County name where entity is located.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<codesetd>
<codesetn>Geographic Names Information System (GNIS)</codesetn>
<codesets>US Department of the Interior - US Geologic Survey</codesets>
</codesetd>
</attrdomv>
<attalias Sync="TRUE">COUNTY</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>FIPS</attrlabl>
<attrdef>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>TGS</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) http://www.itl.nist.gov/fipspubs/co-codes/states.txt</codesets>
</codesetd>
</attrdomv>
<attalias Sync="TRUE">FIPS</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>DIRECTIONS</attrlabl>
<attrdef>Directions to entity location, or description of the entity's location.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">DIRECTIONS</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>EMERGTITLE</attrlabl>
<attrdef>Title of person or name of office for emergency point of contact.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">EMERGTITLE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>EMERGTEL</attrlabl>
<attrdef>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>TGS</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>
<attalias Sync="TRUE">EMERGTEL</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>EMERGEXT</attrlabl>
<attrdef>Telephone extension for emergency point of contact.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">EMERGEXT</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>CONTDATE</attrlabl>
<attrdef>Date entity was contacted by TGS.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Date</udom>
</attrdomv>
<attalias Sync="TRUE">CONTDATE</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>CONTHOW</attrlabl>
<attrdef>Method by which entity was contacted.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<edom>
<edomv>PHONE</edomv>
<edomvd>Entity was contacted by phone.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>FAX</edomv>
<edomvd>Entity was contacted by fax.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>MAIL</edomv>
<edomvd>Entity was contacted by mail.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>EMAIL</edomv>
<edomvd>Entity was contacted by email.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>WEB</edomv>
<edomvd>Entity information was gathered and/or verified by official entity website as a last resort.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<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>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>&lt;BLANK&gt;</edomv>
<edomvd>Entity has not been contacted by TGS.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">CONTHOW</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>GEODATE</attrlabl>
<attrdef>Date entity was geocoded by TGS.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Date</udom>
</attrdomv>
<attalias Sync="TRUE">GEODATE</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>GEOHOW</attrlabl>
<attrdef>Method by which entity was geocoded.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<edom>
<edomv>AUTO</edomv>
<edomvd>Entity was automatically geocoded.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>MANUAL</edomv>
<edomvd>Entity was manually geocoded.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>ADJUSTED</edomv>
<edomvd>Entity was shifted by TGS to an updated set of NAVTEQ streets. This only applies if the entity was manually geocoded by TGS to a previous version of NAVTEQ streets.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>PROVIDED</edomv>
<edomvd>Entity was geocoded using coordinates provided by the original source.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">GEOHOW</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>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>TGS</attrdefs>
<attrdomv>
<codesetd>
<codesetn>North American Industry Classification System (NAICS 2007)</codesetn>
<codesets>US Census Bureau - http://www.census.gov/epcd/www/naics.html</codesets>
</codesetd>
</attrdomv>
<attalias Sync="TRUE">NAICSCODE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">6</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>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 field, 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 if that is the function that qualified it to be included in this dataset.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<edom>
<edomv>AIR AMBULANCE SERVICES</edomv>
<edomvd>AIR AMBULANCE SERVICES - [NAICS Code 621910]: Entities that are primarily engaged in providing transportation of patients by air that have medical care capabilities are classified under this description.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>AMBULANCE AND FIRE SERVICE COMBINED</edomv>
<edomvd>AMBULANCE AND FIRE SERVICE COMBINED - [NAICS Code 922160]: Entities providing ambulance services with fire protection service are classified under this description.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>AMBULANCE SERVICES, AIR OR GROUND</edomv>
<edomvd>AMBULANCE SERVICES, AIR OR GROUND - [NAICS Code 621910]: Entities that are primarily engaged in providing transportation of patients by ground or air that have medical care capabilities are classified under this description.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>FIRE AND RESCUE SERVICE</edomv>
<edomvd>FIRE AND RESCUE SERVICE - [NAICS Code 922160]: Entities that are involved in fire fighting and rescue service are classified under this description, unless they are privately owned or primarily involved in forest fire fighting.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>FIREFIGHTING, FOREST</edomv>
<edomvd>FIREFIGHTING, FOREST - [NAICS Code 115310]: Entities that are primarily involved in forest fire fighting are classified under this description.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>FIRE FIGHTER TRAINING SCHOOLS</edomv>
<edomvd>FIRE FIGHTER TRAINING SCHOOLS - [NAICS Code 611519]: Entities that are primarily involved in training fire fighters are classified under this description.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>FIRE FIGHTING SERVICES AS A COMMERCIAL ACTIVITY</edomv>
<edomvd>FIRE FIGHTING SERVICES AS A COMMERCIAL ACTIVITY - [NAICS Code 561990]: Entities providing fire protection for a commercial facility are classified under this description.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>POLICE AND FIRE DEPARTMENTS, COMBINED</edomv>
<edomvd>POLICE AND FIRE DEPARTMENTS, COMBINED - [NAICS Code 922120]: Entities providing combined police and fire protection service are classified under this description.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>RESCUE SERVICES, AIR</edomv>
<edomvd>RESCUE SERVICES, AIR - [NAICS Code 621910]: Entities that have medical care capabilities and are primarily engaged in the rescue of patients by air are classified under this description.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>RESCUE SERVICES, MEDICAL</edomv>
<edomvd>RESCUE SERVICES, MEDICAL - [NAICS Code 621910]: Entities that have medical care capabilities and are primarily engaged in the rescue of patients by ground are classified under this description.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">NAICSDESCR</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">120</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>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>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">GEOLINKID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>X</attrlabl>
<attrdef>Longitude in WGS 84 Decimal Degrees.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<rdom>
<rdommin>-180</rdommin>
<rdommax>180</rdommax>
<attrunit>WGS 84 Decimal Degrees</attrunit>
</rdom>
</attrdomv>
<attalias Sync="TRUE">X</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl>Y</attrlabl>
<attrdef>Latitude in WGS 84 Decimal Degrees.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<rdom>
<rdommin>-90</rdommin>
<rdommax>90</rdommax>
<attrunit>WGS 84 Decimal Degrees</attrunit>
</rdom>
</attrdomv>
<attalias Sync="TRUE">Y</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl>ST_VENDOR</attrlabl>
<attrdef>Indicates name of vendor providing original street data used for geocoding.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<edom>
<edomv>NAVTEQ</edomv>
<edomvd>NAVTEQ streets were used for geocoding.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>TGS</edomv>
<edomvd>TGS drew in a new street segment that does not exist in the file supplied by NAVTEQ.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>TIGER</edomv>
<edomvd>TIGER/Line streets were used for geocoding.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">ST_VENDOR</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ST_VERSION</attrlabl>
<attrdef>Indicates the year and quarter of streets used for geocoding.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<edom>
<edomv>2007Q2</edomv>
<edomvd>2nd Quarter 2007 NAVTEQ street data was used for geocoding.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>2006FE</edomv>
<edomvd>2006fe version of TIGER/Line streets were used for geocoding in areas where NAVTEQ does not have coverage.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">ST_VERSION</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>GEOPREC</attrlabl>
<attrdef>Geocoding precision.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<edom>
<edomv>BLOCKFACE</edomv>
<edomvd>Entity is geocoded to correct block and correct side of street per street data indicated by [ST_VENDOR] and [ST_VERSION].</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>ONENTITY</edomv>
<edomvd>Entity is geocoded on entity rooftop per aerial imagery (in most cases USGS DOQQs).</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">GEOPREC</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">32</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>PHONELOC</attrlabl>
<attrdef>Indicates whether the phone number in the [TELEPHONE] field rings to the actual location of the entity.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<edom>
<edomv>YES</edomv>
<edomvd>Phone number rings to the actual entity location.</edomvd>
<edomvds>TGS</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>TGS</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>TGS</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">PHONELOC</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">3</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>QC_QA</attrlabl>
<attrdef>Organization that performed Quality Control/Quality Assurance on the record.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<edom>
<edomv>TGS</edomv>
<edomvd>TGS has performed Quality Control/Quality Assurance on all TGS added records and all records contacted since 01/01/2005.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>&lt;BLANK&gt;</edomv>
<edomvd>The record is not TGS added or has not had Quality Control/Quality Assurance performed by TGS, or Quality Control/Quality Assurance was performed prior to 01/01/2005.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">QC_QA</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">3</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>STATE_ID</attrlabl>
<attrdef>State Emergency Medical Services Data ID. For states that contributed data, this field is populated with the unique ID used by the state to track EMS locations.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">STATE_ID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>FDID</attrlabl>
<attrdef>A unique five-character identifier assigned by the state to identify a particular fire department within the state. The first two characters designate the county and the last three designate the department within the county. This identifier is only unique within each state, not nationwide.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">FDID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">32</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>FRST_MBRS</attrlabl>
<attrdef>
Total number of fire fighter members associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Number</udom>
</attrdomv>
<attalias Sync="TRUE">FRST_MBRS</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl>EMS_MBRS</attrlabl>
<attrdef>
Total number of EMS members associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Number</udom>
</attrdomv>
<attalias Sync="TRUE">EMS_MBRS</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl>TOTALPERS</attrlabl>
<attrdef>
Total number of members associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Number</udom>
</attrdomv>
<attalias Sync="TRUE">TOTALPERS</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl>NUMTRKS</attrlabl>
<attrdef>
Total number of fire trucks associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Number</udom>
</attrdomv>
<attalias Sync="TRUE">NUMTRKS</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl>NUMABUL</attrlabl>
<attrdef>
Total number of ambulances associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Number</udom>
</attrdomv>
<attalias Sync="TRUE">NUMABUL</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl>TOTAL_VEHI</attrlabl>
<attrdef>
Total number of vehicles associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Number</udom>
</attrdomv>
<attalias Sync="TRUE">TOTAL_VEHI</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl>NBR_STA</attrlabl>
<attrdef>
The total number of stations associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Number</udom>
</attrdomv>
<attalias Sync="TRUE">NBR_STA</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">LEVEL_</attrlabl>
<attalias Sync="TRUE">LEVEL_</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>OWNER</attrlabl>
<attrdef>
The type of ownership for the entity.
The values that this field is populated with came from individual states and have not been validated or checked by TGS.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">OWNER</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>TYPE</attrlabl>
<attrdef>
Type of employees.
The values that this field is populated with came from individual states and have not been validated or checked by TGS.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">TYPE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>SPECIALTY</attrlabl>
<attrdef>
Indicates any type of specialty unit available at the facility.
The values that this field is populated with came from individual states and have not been validated or checked by TGS.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">SPECIALTY</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>EMSLICENSE</attrlabl>
<attrdef>
License number for EMS agency provided by the state.
The values that this field is populated with came from individual states and have not been validated or checked by TGS.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">EMSLICENSE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">32</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>EMERPHONE</attrlabl>
<attrdef>
Emergency Contact Number as provided by individual states. Some values also include telephone extensions and/or alternate telephone numbers. All alphabetic characters have been translated to the corresponding numeric digit.
The values in this field have not been verified by TGS.
</attrdef>
<attrdefs>TGS</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 &lt;http://www.nanpa.com&gt;</udom>
</attrdomv>
<attalias Sync="TRUE">EMERPHONE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>FRST</attrlabl>
<attrdef>Indicates if the entity also has fire fighting capabilities.</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<edom>
<edomv>Y</edomv>
<edomvd>Indicates the entity has fire fighting capabilities.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>N</edomv>
<edomvd>Indicates the entity does not have fire fighting capabilities.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>&lt;BLANK&gt;</edomv>
<edomvd>Unable to determine if entity has fire fighting capabilities.</edomvd>
<edomvds>TGS</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">FRST</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">3</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>PERM_ID</attrlabl>
<attrdef>
The unique permanent identifier of The National Structures Dataset.
The values in this field have not been verified by TGS.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">PERM_ID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">40</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>GNIS_ID</attrlabl>
<attrdef>
The unique permanent identifier of the Geographic Names Information System that is up to eight (8) digits in length and unique within the nation.
The values in this field have not been verified by TGS.
</attrdef>
<attrdefs>TGS</attrdefs>
<attrdomv>
<udom>Text</udom>
</attrdomv>
<attalias Sync="TRUE">GNIS_ID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">32</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
</eainfo>
<metainfo>
<metd>20090330</metd>
<metc>
<cntinfo>
<cntperp>
<cntper>Mike Thompson</cntper>
<cntorg>TechniGraphics, Inc.</cntorg>
</cntperp>
<cntpos>Director of Geospatial Datasets</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>mthompson@tgstech.com</cntemail>
<hours>Monday - Friday, 0800 - 1700 MST</hours>
<cntorgp>
<cntper>The person responsible for the metadata information.</cntper>
<cntorg>The organization responsible for the metadata information.</cntorg>
</cntorgp>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<langmeta>en</langmeta>
<mettc>local time</mettc>
</metainfo>
<Esri>
<CreaDate>20090330</CreaDate>
<CreaTime>11203400</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20220523</SyncDate>
<SyncTime>13454900</SyncTime>
<ModDate>20220523</ModDate>
<ModTime>14402300</ModTime>
<DataProperties>
<itemProps>
<itemName>ems</itemName>
<imsContentType>002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">133652.358088</westBL>
<eastBL Sync="TRUE">929791.715621</eastBL>
<southBL Sync="TRUE">12508.484142</southBL>
<northBL Sync="TRUE">313962.330662</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</itemProps>
<coordRef>
<type>Projected</type>
<geogcsn>GCS_North_American_1983</geogcsn>
<csUnits>Linear Unit: Meter (1.000000)</csUnits>
<projcsn>NAD_1983_StatePlane_North_Carolina_FIPS_3200</projcsn>
<peXml>&lt;ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/2.8.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_North_Carolina_FIPS_3200&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Lambert_Conformal_Conic&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,609601.22],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-79.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,34.33333333333334],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,36.16666666666666],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,33.75],UNIT[&amp;quot;Meter&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,32119]]&lt;/WKT&gt;&lt;XOrigin&gt;-37137499.999920025&lt;/XOrigin&gt;&lt;YOrigin&gt;-28547399.99993277&lt;/YOrigin&gt;&lt;XYScale&gt;9235.9851305225584&lt;/XYScale&gt;&lt;ZOrigin&gt;0&lt;/ZOrigin&gt;&lt;ZScale&gt;1&lt;/ZScale&gt;&lt;MOrigin&gt;0&lt;/MOrigin&gt;&lt;MScale&gt;1&lt;/MScale&gt;&lt;XYTolerance&gt;0.0008661772281943215&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.002&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.002&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;32119&lt;/WKID&gt;&lt;LatestWKID&gt;32119&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<ArcGISFormat>1.0</ArcGISFormat>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<ArcGISProfile>FGDC</ArcGISProfile>
</Esri>
<distinfo>
<resdesc>Downloadable Data</resdesc>
</distinfo>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdContact>
<rpIndName>Mike Thompson</rpIndName>
<rpIndName>The person responsible for the metadata information.</rpIndName>
<rpOrgName>TechniGraphics, Inc.</rpOrgName>
<rpOrgName>The organization responsible for the metadata information.</rpOrgName>
<rpPosName>Director of Geospatial Datasets</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>970-224-4996</voiceNum>
<faxNum>970-224-3001</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>3351 Eastbrook Drive</delPoint>
<city>Fort Collins</city>
<adminArea>CO</adminArea>
<postCode>80525</postCode>
<country>US</country>
<eMailAdd>mthompson@tgstech.com</eMailAdd>
</cntAddress>
<cntHours>Monday - Friday, 0800 - 1700 MST</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt Sync="TRUE">20220523</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distTranOps>
<onLineSrc>
<linkage>withheld</linkage>
</onLineSrc>
</distTranOps>
<distFormat>
<formatName Sync="TRUE">Enterprise Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle>Emergency Medical Services</resTitle>
<date>
<pubDate>2008-09-19</pubDate>
</date>
<resEd>4th Quarter 2008</resEd>
<citRespParty>
<rpOrgName>TechniGraphics, Inc.</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;EMS Locations in North Carolina The EMS stations dataset consists of any location where emergency medical services (EMS) personnel are stationed or based out of, or where equipment that such personnel use in carrying out their jobs is stored for ready use. Ambulance services are included even if they only provide transportation services, but not if they are located at, and operated by, a hospital. If an independent ambulance service or EMS provider happens to be collocated with a hospital, it will be included in this dataset. The dataset includes both private and governmental entities. This dataset is comprised completely of license free data. The Fire Station dataset and the EMS dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. 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. 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 upon this field, the oldest record dates from 01/05/2005 and the newest record dates from 08/15/2008&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>
Homeland Security
Use Cases: Use cases describe how the data may be used and help to define and clarify requirements.
1. An assessment of whether or not the total emergency medical services capability in a given area is adequate.
2. A list of resources to draw upon by surrounding areas when local resources have temporarily been overwhelmed by a disaster - route analysis can determine those entities that are able to respond the quickest.
3. A resource for Emergency Management planning purposes.
4. A resource for catastrophe response to aid in the retrieval of equipment by outside responders in order to deal with the disaster.
5. A resource for situational awareness planning and response for Federal Government events.
</idPurp>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<idPoC>
<rpIndName>Mike Thompson</rpIndName>
<rpOrgName>TechniGraphics, Inc.</rpOrgName>
<rpPosName>Director of Geospatial Datasets</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>970-224-4996</voiceNum>
<faxNum>970-224-3001</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>3351 Eastbrook Drive</delPoint>
<city>Fort Collins</city>
<adminArea>CO</adminArea>
<postCode>80525</postCode>
<country>US</country>
<eMailAdd>mthompson@tgstech.com</eMailAdd>
</cntAddress>
<cntHours>Monday - Friday, 0800 - 1700 MST</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="012"/>
</maintFreq>
</resMaint>
<placeKeys>
<thesaName>
<resTitle>LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/</resTitle>
</thesaName>
<keyword>North Carolina</keyword>
</placeKeys>
<themeKeys>
<thesaName>
<resTitle>LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/</resTitle>
</thesaName>
<keyword>Airplane ambulances</keyword>
<keyword>Ambulances</keyword>
<keyword>Ambulance service.</keyword>
<keyword>Emergency medical services.</keyword>
<keyword>Emergency medical personnel.</keyword>
<keyword>Fire departments.</keyword>
<keyword>Fire stations.</keyword>
<keyword>Helicopter ambulances</keyword>
<keyword>Search and rescue operations.</keyword>
</themeKeys>
<themeKeys>
<thesaName>
<resTitle>ISO 19115 Topic Category</resTitle>
</thesaName>
<keyword>structure</keyword>
</themeKeys>
<searchKeys>
<keyword>Airplane ambulances</keyword>
<keyword>Ambulances</keyword>
<keyword>Ambulance service.</keyword>
<keyword>Emergency medical services.</keyword>
<keyword>Emergency medical personnel.</keyword>
<keyword>Fire departments.</keyword>
<keyword>Fire stations.</keyword>
<keyword>Helicopter ambulances</keyword>
<keyword>Search and rescue operations.</keyword>
<keyword>structure</keyword>
<keyword>NC</keyword>
<keyword>North Carolina</keyword>
<keyword>Department of Information Technology</keyword>
<keyword>DIT</keyword>
<keyword>Center for Geographic Information and Analysis</keyword>
<keyword>CGIA</keyword>
<keyword>NC OneMap</keyword>
</searchKeys>
<resConst>
<SecConsts>
<class>
<ClasscationCd value="001"/>
</class>
<classSys>DOD</classSys>
<handDesc>Unclassified</handDesc>
</SecConsts>
</resConst>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<envirDesc>ESRI ArcCatalog 9.3.1.1850</envirDesc>
<dataExt>
<geoEle>
<GeoBndBox>
<exTypeCode>true</exTypeCode>
<westBL>-84.312103</westBL>
<eastBL>-75.424460</eastBL>
<northBL>36.579997</northBL>
<southBL>33.751698</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2005-01-05</tmBegin>
<tmEnd>2008-08-15</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-84.312103</westBL>
<eastBL Sync="TRUE">-75.424460</eastBL>
<northBL Sync="TRUE">36.579997</northBL>
<southBL Sync="TRUE">33.751698</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;https://www.nconemap.gov/pages/terms&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<tpCat>
<TopicCatCd value="017"/>
</tpCat>
</dataIdInfo>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report type="DQConcConsis">
<measDesc>See "Attribute_Accuracy_Report". Many of the checks described in that section check for both attribute accuracy and logical consistency.</measDesc>
</report>
<report type="DQCompOm">
<measDesc>
The EMS dataset only includes entities that provide transportation and does not include fixed location clinics or hospitals, as these are included in other datasets.
Administrative Locations: Locations that serve only an administrative function (e.g., a business office) are intended to be excluded from this dataset. Locations that serve both an administrative function as well as an operational function are included in the dataset.
</measDesc>
</report>
<dataLineage>
<dataSource>
<srcDesc>The basic attribution (name, address, city, state, zip code, and telephone number) came from this dataset, unless the entity was updated by TGS during Q408 processing.</srcDesc>
<srcMedName>
<MedNameCd value="digital database file"/>
</srcMedName>
<srcCitatn>
<resTitle>Emergency Medical Services 2008 Q2</resTitle>
<resAltTitle>EMS_2008_Q2</resAltTitle>
<date>
<pubDate>2008-05-13</pubDate>
</date>
<resEd>2nd Quarter 2008</resEd>
<citRespParty>
<rpOrgName>TechniGraphics, Inc.</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2004-12-29</tmBegin>
<tmEnd>2008-05-01</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>This was used as a source for emergency medical services in North Carolina.</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
<srcCitatn>
<resTitle>NCEMS</resTitle>
<resAltTitle>NC_EMS_1</resAltTitle>
<date>
<pubDate>2004-03-01</pubDate>
</date>
<resEd>Unspecified</resEd>
<citRespParty>
<rpOrgName>North Carolina State Center for Health Statistics (NCSCHS)</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2004-03-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>This was used as a source for emergency medical services in North Carolina.</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
<srcCitatn>
<resTitle>Directory of Fire Departments and Rescue Squads</resTitle>
<resAltTitle>NC_EMS_2</resAltTitle>
<date>
<pubDate>2008-03-05</pubDate>
</date>
<resEd>Unspecified</resEd>
<citRespParty>
<rpOrgName>North Carolina Office of State Fire Marshal (NCOSFM)</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
<citOnlineRes>
<linkage>withheld</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2008-03-05</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>This was used as a source for emergency medical services in the United States.</srcDesc>
<srcMedName>
<MedNameCd value="001"/>
</srcMedName>
<srcCitatn>
<resTitle>USFA National Fire Department Census Database</resTitle>
<resAltTitle>NFDC_1</resAltTitle>
<date>
<pubDate>2006-12-01</pubDate>
</date>
<resEd>Unspecified</resEd>
<citRespParty>
<rpOrgName>United States Fire Administration (USFA)</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2006-12-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>This was used as a source for emergency medical services in the United States.</srcDesc>
<srcMedName>
<MedNameCd value="001"/>
</srcMedName>
<srcCitatn>
<resTitle>USFA National Fire Department Census Database</resTitle>
<resAltTitle>NFDC_2</resAltTitle>
<date>
<pubDate>2007-11-28</pubDate>
</date>
<resEd>Unspecified</resEd>
<citRespParty>
<rpOrgName>United States Fire Administration (USFA)</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2007-11-28</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>This version of NAVTEQ streets was used as a reference for automatic shifting of entities that were previously manually geocoded and for the automatic geocoding and manual geolocating of entities.</srcDesc>
<srcMedName>
<MedNameCd value="001"/>
</srcMedName>
<srcCitatn>
<resTitle>NAVSTREETS</resTitle>
<resAltTitle>NAVTEQ_Streets_2007_Q2</resAltTitle>
<date>
<pubDate>2007</pubDate>
</date>
<resEd>2007.2</resEd>
<citRespParty>
<rpOrgName>NAVTEQ</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2007</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<prcStep>
<stepDesc>
1) The Fire Station dataset and the EMS dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes.
&gt;
&gt;
2) Entities were processed to determine or verify their name, physical address, city, state, five (5) digit zip code, phone number, and geospatial location. Entities that were contacted were also asked if they provided fire protection services, EMS services, or both. Entities not located on military bases were contacted and asked to describe their location relative to landmarks in reference data (mainly streets) and features visible in ortho imagery. A phone number was not available for some entities, so their information was verified using other verbal contacts made through a telephone call.
&gt;
&gt;
3) Due to a request made by the Department of Defense, TGS made every effort to not contact military bases starting 03/27/2007 and ending 05/28/2008. During this time, entities located on military bases were verified through alternate resources, such as maps and ortho imagery. These records have not been contacted by TGS, and therefore, do not have directions.
&gt;
&gt;
4) All text fields were set to all upper case.
&gt;
&gt;
5) Leading and trailing spaces were trimmed from all text fields.
&gt;
&gt;
6) Non printable and diacritic characters were removed from all text fields.
&gt;
&gt;
</stepDesc>
<stepDateTm>2008-09-19</stepDateTm>
<stepProc>
<rpIndName>Nicole Hackworth</rpIndName>
<rpOrgName>TechniGraphics, Inc.</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>330-263-6222</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>2000 Noble Drive</delPoint>
<city>Wooster</city>
<adminArea>Ohio</adminArea>
<postCode>44691</postCode>
<country>US</country>
<eMailAdd>nhackworth@tgstech.com</eMailAdd>
</cntAddress>
<cntHours>Monday - Friday, 0730 - 1630 EST</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>EMS_2008_Q2</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>NC_EMS_1</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>NC_EMS_2</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>NFDC_1</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>NFDC_2</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>NAVTEQ_Streets_2007_Q2</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="produced">
<srcCitatn>
<resAltTitle>NC_EMS_2008_Q4</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>Metadata imported.</stepDesc>
<stepDateTm>2009-03-30T11:20:34</stepDateTm>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>withheld</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
</dataLineage>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="ems">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="004"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">1767</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="32119"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">4.2(3.0.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
</metadata>
