alert - warning

This page has not been translated into Español. Visit the Español page for resources in that language.

OpenFEMA Dataset: NFIP Community Layer No Overlaps Split - v1

Versión: 1
Last Data Refresh: 02-12-2024
Entity Name NfipCommunityLayerNoOverlapsSplit
API Endpoint https://www.fema.gov/api/open/v1/NfipCommunityLayerNoOverlapsSplit
Update Frequency R/P1Y
Program URL https://www.fema.gov/flood-insurance
Categoría National Flood Insurance Program
Palabras clave nfip community

Descripción

This dataset is flattened and multicounty communities are split by county lines. "Flattened" means that there are no overlaps; larger shapes like counties are "punched out" or "clipped" where smaller communities are contained within them. This allows for choropleth shading and other mapping techniques such as calculating unincorporated county land area. Multicounty cities like Houston are split by county lines, allowing easier county summarization and alignment with certain NFIP statistics. This layer is derived from Census, State of Maine, and National Flood Hazard Layer political boundaries.

The Community Layer datasets contain geospatial community boundaries associated with Census and NFIP data. The dataset does not contain personal identifiable information (PII). The Community Layer can be used to tie Community ID numbers (CID) to jurisdiction, tribal, and special land use area boundaries.

A geodatabase (GDB) link is Included in the Full Data section below. The compressed file contains a collection of files that can store, query, and manage both spatial and nonspatial data using software that can read such a file. It contains all of the community layers, not just the layer for which this dataset page describes.

Citation: FEMA's citation requirements for datasets (API usage or file downloads) can be found on the OpenFEMA Terms and Conditions page, Citing Data section: https://www.fema.gov/about/openfema/terms-conditions.

For answers to Frequently Asked Questions (FAQs) about the OpenFEMA program, API, and publicly available datasets, please visit: https://www.fema.gov/about/openfema/faq.

If you have media inquiries about this dataset, please email the FEMA News Desk at FEMA-News-Desk@fema.dhs.gov or call (202) 646-3272. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.

Full Data

Formato Dirección Record Count Approximate File Size
csv Link to csv 37920 large (500MB - 10GB)
json Link to json 37920 large (500MB - 10GB)
jsona Link to jsona 37920 large (500MB - 10GB)
gdb Link to gdb 37920 medium (50MB - 500MB)

Data Fields

Nombre Título Tipo Descripción Is Searchable
id Record Identifier
integer
Unique ID assigned to the record yes
communityIdNumber Community ID (CID)
text
A unique identifier given to all communities in the National Flood Insurance Program (NFIP). It assists in quickly identifying specific communities and associated flood risk information when using FEMA's management systems. yes
stateCode FIPS State Code
text
FIPS two-digit numeric code used to identify the United States, the District of Columbia, US territories, outlying areas of the US and freely associated states yes
countyCode FIPS County Code
text
FIPS three-digit numeric code used to identify counties and county equivalents in the United States, the District of Columbia, US territories, outlying areas of the US and freely associated states. Please note that Indian Reservations are not counties and thus will not have a FIPS county code. yes
censusGeoid Census Geoid
text
Numeric code that uniquely identify all administrative/legal and statistical geographic areas for which the Census Bureau tabulates data. yes
county County
text
The name of a U.S. county, parish, borough, independent city or other political subdivision of a U.S. state or territory yes
communityName Community Name
text
Name of the NFIP community, generally, representing the lowest level of government with land use authority. Not every city or town is recognized as its own community with the NFIP. Each state or territory determines land use authority granted to counties/parishes/boroughs, towns/cities, tribal area, etc. within their own jurisdiction yes
communityNameShort Community Name Short
text
Name stripped of suffix yes
censusYear Census Year
smallint
The Census Year associated with the data. yes
censusPopulationEntire Census Population Entire
integer
Census Population derived from blocks: Entire Community yes
censusHousingUnitsEntire Census Housing Units Entire
integer
Census Housing Units derived from blocks: Entire Community yes
landAreaEntire Land Area Entire
float
Land area of an entire community in square kilometers. yes
censusPopulationPunched Census Population Punched
integer
Census Population derived from blocks: Remainder after flattening yes
censusHousingUnitsPunched Census Housing Units Punched
integer
Census Housing Units derived from blocks: Remainder after flattening yes
landArea2D Land Area 2D
float
Area of community after flattening in square kilometers. yes
cisType CIS Type
text
CIS Government Unit (Derived from CIS Name) yes
cisSource CIS Source
text
Source of CIS data; typically PIVOT yes
geometrySource Geometry Source
text
Source of geometry yes
alternateGeoid Alternate Geoid
text
Alternate non-census identifier, such as Maine GIS code yes
alternateName Alternate Name
text
Alternate non-census name yes
alternateLongName Alternate Long Name
text
Alternate Long Name yes
layerCreationNotes Layer Creation Notes
text
Assumptions or tidbits of note in the creation of the layer yes
censusClassCodes Census Class Codes
text
Census Class codes: https://www.census.gov/library/reference/code-lists/class-codes.html yes
censusFunctionalStatusCodes Census Functional Status Codes
text
Census Functional status codes: https://www.census.gov/library/reference/code-lists/functional-status-codes.html yes
layerTypeCode Layer Type Code
text
Includes the following types: Tribe, County, Consolidated City, Statistical Area, SLUA, Place (multi-county), Maine Town/Township, County Subdivision, Place yes

See Also

Access the metadata API calls for additional information: