TechniGraphics, Inc.
20080919
New Hampshire Fire Stations
4th Quarter 2008
vector digital data
\\guero\jj\d-links\contact\dataarchive\CSD\firestations\firestations.shpfirestations
Fire Stations in New Hampshire
Any location where fire fighters are stationed or based out of, or where equipment that such personnel use in carrying out their jobs is stored for ready use. Fire Departments not having a permanent location are included, in which case their location has been depicted at the city/town hall or at the center of their service area if a city/town hall does not exist. This dataset includes those locations primarily engaged in forest or grasslands fire fighting, including fire lookout towers if the towers are in current use for fire protection purposes. This dataset includes both private and governmental entities. Fire fighting training academies are also included.
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/07/2005 and the newest record dates from 07/14/2008.
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 fire fighting 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.
en
20050107
20080714
REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.
ground condition
Unknown
-72.549611
-70.683747
45.051581
42.704730
756046.1362611238296.94865076032.987223930087.586664
LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/
Airplane ambulances
Ambulances
Ambulance service.
Emergency medical services.
Emergency medical personnel.
Fire departments.
Fire stations.
Helicopter ambulances
Search and rescue operations.
ISO 19115 Topic Category
structure
LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/
New Hampshire
None
None
Mike Thompson
TechniGraphics, Inc.
Director of Geospatial Datasets
Mailing and Physical Address
3351 Eastbrook Drive
Fort Collins
CO
80525
USA
970-224-4996
970-224-3001
mthompson@tgstech.com
Monday - Friday, 0800 - 1700 MST
DOD
Unclassified
Unclassified
Microsoft Windows Vista Version 6.0 (Build 6001) Service Pack 1; ESRI ArcCatalog 9.3.0.1770
Shapefile
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.
See "Attribute_Accuracy_Report". Many of the checks described in that section check for both attribute accuracy and logical consistency.
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.
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.
Fire Departments 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.
TechniGraphics, Inc.
20080513
Fire Stations 2008 Q2
2nd Quarter 2008
vector digital data
Digital Database File
20050103
20080501
ground condition
FireStations_2008_Q2
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.
New Hampshire Fire Academy (NHFA)
Unknown
New Hampshire Licensed Emergency Medical Services
Unspecified
Publication date is unknown - received on 20080507
Electronic Mail System
20080507
publication date
NH_FireStations_1
This was used as a source for fire stations in New Hampshire.
New Hampshire Department of Safety, Division of Fire Safety, Office of the State Fire Marshal (NHDOSFM)
Unknown
Fire Chiefs
Unspecified
Publication date is unknown - received on 20080506
Electronic Mail System
20080506
publication date
NH_FireStations_2
This was used as a source for fire stations in New Hampshire.
United States Fire Administration (USFA)
20061201
USFA National Fire Department Census Database
Unspecified
vector digital data
CD-ROM
20061201
publication date
NFDC_1
This was used as a source for fire stations in the United States.
United States Fire Administration (USFA)
20071128
USFA National Fire Department Census Database
Unspecified
vector digital data
CD-ROM
20071128
publication date
NFDC_2
This was used as a source for fire stations in the United States.
NAVTEQ
2007
NAVSTREETS
2007.2
vector digital data
CD-ROM
2007
publication date
NAVTEQ_Streets_2007_Q2
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.
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.
>
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.
>
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.
>
4) All text fields were set to all upper case.
>
5) Leading and trailing spaces were trimmed from all text fields.
>
6) Non printable and diacritic characters were removed from all text fields.
>
FireStations_2008_Q2
NFDC_1
NFDC_2
NH_FireStations_1
NH_FireStations_2
NAVTEQ_Streets_2007_Q2
20080919
NH_FireStations_2008_Q4
Nicole Hackworth
TechniGraphics, Inc.
Project Manager
Mailing and Physical Address
2000 Noble Drive
Wooster
Ohio
44691
USA
330-263-6222
nhackworth@tgstech.com
Monday - Friday, 0730 - 1630 EST
Dataset copied.2009010813001100
Vector
Entity point
326
SimplePointFALSE326TRUEFALSE
North American Datum of 1983
Geodetic Reference System 80
6378137.000000
298.257222
GCS_North_American_1983NAD_1983_StatePlane_New_Hampshire_FIPS_2800_Feetcoordinate pairsurvey feet0.0000000.000000Transverse Mercator0.999967-71.66666742.500000984250.0000000.000000
Fire Stations in New Hampshire
Any location where fire fighters are stationed or based out of, or where equipment that such personnel use in carrying out their jobs is stored for ready use. Fire Departments not having a permanent location are included, in which case their location has been depicted at the city/town hall or at the center of their service area if a city/town hall does not exist. This dataset includes those locations primarily engaged in forest or grasslands fire fighting, including fire lookout towers if the towers are in current use for fire protection purposes. This dataset includes both private and governmental entities. Fire fighting training academies are also included.
TGS
Feature Class326
FID
Internal feature number.
ESRI
Sequential unique whole numbers that are automatically generated.
FIDOID400
SHAPE
Feature geometry.
ESRI
Coordinates defining the features.
ShapeGeometry000
ID
Unique identifier for feature.
TGS
Text
IDString50
SECCLASS
Security classification of feature.
TGS
UNCLASSIFIED
Entity is unclassified.
TGS
SECCLASSString30
NAME
Name of entity.
TGS
Text
NAMEString254
TELEPHONE
Ten (10) digit telephone number for entity formatted as nnn-nnn-nnnn.
TGS
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 <http://www.nanpa.com>.
TELEPHONEString12
ADDRESS
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.
TGS
Text
ADDRESSString80
ADDRESS2
Location within physical address, e.g., floor, suite, building.
TGS
Text
ADDRESS2String80
CITY
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.
TGS
Text
CITYString120
STATE
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.
TGS
Official USPS Abbreviations - State Abbreviations
United States Postal Service http://www.usps.com/ncsc/lookups/usps_abbreviations.html
STATEString2
ZIP
Five (5) digit USPS zip code for entity's physical location.
TGS
USPS Address Information System - Domain is further restricted by only allowing physical (non PO Box) zip codes.
United States Postal Service
ZIPString5
ZIPP4
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.
TGS
USPS Address Information System (AIS) - ZIP9
United States Postal Service
ZIPP4String4
COUNTY
County name where entity is located.
TGS
Geographic Names Information System (GNIS)
US Department of the Interior - US Geologic Survey
COUNTYString50
FIPS
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.
TGS
Federal Information Processing Standards Publications - Counties and Equivalent Entities of the U.S., Its Possessions, and Associated Areas
National Institute of Standards and Technology (NIST) http://www.itl.nist.gov/fipspubs/co-codes/states.txt
FIPSString5
DIRECTIONS
Directions to entity location, or description of the entity's location.
TGS
Text
DIRECTIONSString254
EMERGTITLE
Title of person or name of office for emergency point of contact.
TGS
Text
EMERGTITLEString50
EMERGTEL
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.
TGS
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
EMERGTELString15
EMERGEXT
Telephone extension for emergency point of contact.
TGS
Text
EMERGEXTString10
CONTDATE
Date entity was contacted by TGS.
TGS
Date
CONTDATEDate8
CONTHOW
Method by which entity was contacted.
TGS
PHONE
Entity was contacted by phone.
TGS
FAX
Entity was contacted by fax.
TGS
MAIL
Entity was contacted by mail.
TGS
EMAIL
Entity was contacted by email.
TGS
WEB
Entity information was gathered and/or verified by official entity website as a last resort.
TGS
ALT REF
Geospatial reference information obtained from local authorities, e.g., downloadable parcel maps, 911 streets, and shape files.
TGS
<BLANK>
Entity has not been contacted by TGS.
TGS
CONTHOWString10
GEODATE
Date entity was geocoded by TGS.
TGS
Date
GEODATEDate8
GEOHOW
Method by which entity was geocoded.
TGS
AUTO
Entity was automatically geocoded.
TGS
MANUAL
Entity was manually geocoded.
TGS
ADJUSTED
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.
TGS
PROVIDED
Entity was geocoded using coordinates provided by the original source.
TGS
GEOHOWString10
NAICSCODE
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.
TGS
North American Industry Classification System (NAICS 2007)
US Census Bureau - http://www.census.gov/epcd/www/naics.html
NAICSCODEString6
NAICSDESCR
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.
TGS
AIR AMBULANCE SERVICES
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.
TGS
AMBULANCE AND FIRE SERVICE COMBINED
AMBULANCE AND FIRE SERVICE COMBINED - [NAICS Code 922160]: Entities providing ambulance services with fire protection service are classified under this description.
TGS
AMBULANCE SERVICES, AIR OR GROUND
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.
TGS
FIRE AND RESCUE SERVICE
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.
TGS
FIRE DEPARTMENTS (E.G., GOVERNMENT, VOLUNTEER (EXCEPT PRIVATE))
FIRE DEPARTMENTS (E.G., GOVERNMENT, VOLUNTEER (EXCEPT PRIVATE)) - [NAICS Code 922160]: Entities that are involved in fire fighting are classified under this description, unless they are privately owned, are primarily involved in forest fire fighting, or also operate a rescue service.
TGS
FIREFIGHTING, FOREST
FIREFIGHTING, FOREST - [NAICS Code 115310]: Entities that are primarily involved in forest fire fighting are classified under this description.
TGS
FIRE FIGHTER TRAINING SCHOOLS
FIRE FIGHTER TRAINING SCHOOLS - [NAICS Code 611519]: Entities that are primarily involved in training fire fighters are classified under this description.
TGS
FIRE FIGHTING SERVICES AS A COMMERCIAL ACTIVITY
FIRE FIGHTING SERVICES AS A COMMERCIAL ACTIVITY - [NAICS Code 561990]: Entities providing fire protection for a commercial facility are classified under this description.
TGS
FIRE MARSHALS' OFFICES
FIRE MARSHALS' OFFICES - [NAICS Code 922160]: Entities that are fire marshals' offices are classified under this description.