Zip Data Maps

[Bran Bast]

TheSecretary of State serves as a repository for certain public data related to elections. Much of that data is available through the links below. To check on the availability and cost of getting other data, see the Data Practices Requests page.

The National Flood Hazard Layer (NFHL) is a geospatial database that contains current effective flood hazard data. FEMA provides the flood hazard data to support the National Flood Insurance Program. You can use the information to better understand your level of flood risk and type of flooding. The NFHL can also be used in place of the FIRM for NFIP purposes with appropriate care.

The NFHL is made from effective flood maps and Letters of Map Change (LOMC) delivered to communities. NFHL digital data covers over 90% of the U.S. population. New and revised data is being added continuously. If you need information for areas not covered by the NFHL data, there may be other FEMA products which provide coverage for those areas.

In the NFHL Viewer, you can use the address search or map navigation to locate an area of interest and the NFHL Print Tool to download and print a full Flood Insurance Rate Map (FIRM) or FIRMette (a smaller, printable version of a FIRM) where NFHL data exists. Technical GIS users can also utilize a series of dedicated GIS web services that allow the NFHL database to be incorporated into websites and GIS applications. For more information on available services, go to the NFHL GIS Services User Guide.

Pending Flood Insurance Rate Map (FIRM) Databases are scheduled to be adopted by the local government and become effective within six months. This is the final step in the process before new flood hazard data becomes effective. Pending FIRM Databases have been designated final by the Letter of Final Determination issued to community officials. However, they do not officially define the minimum requirements for National Flood Insurance Program (NFIP) purposes until they become effective at the end of the six-month adoption and compliance period.

They are published in the Pending NFHL as soon as possible to give community officials, lenders, and the public time to prepare for new official data. Pending data may include new or revised Flood Insurance Rate Maps (FIRM), Flood Insurance Study (FIS) Reports and FIRM Databases. If pending data is available for your community, you can view it and compare it with existing data on the Flood Map Changes Viewer.

The Flood Hazard and Risk Data Viewer shares a variety of flood hazard and risk data from FEMA. This viewer provides a single location to view a large inventory of data that represents both current and future flood conditions to help users understand their flood hazard and other risk-related information. Some flood hazard and flood risk data produced by FEMA define minimum requirements for the National Flood Insurance Program (NFIP). This viewer includes these required NFIP data and includes other data showing current and potential future flood hazard and risk. This provides users access to more complete flood hazard data. FEMA also uses this viewer to provide communities an opportunity to comment on early drafts of flood hazard data.

The MSC or NFHL Viewer is the best place to start to understand the official NFIP flood hazard determinations for your area of interest. Where an effective flood map exists and provides data, that data must be used to establish the minimum NFIP requirements.

If effective data is not available in your community, or you are interested in more information about flood risk in your area, the Flood Hazard and Risk Data Viewer may have information beyond information in the sources above that focus on the regulatory NFIP requirements. This includes information about sea level rise in coastal areas and base level engineering products from FEMA. The BLE data may progress and eventually be included in the Effective NFHL, or they may not. See Base Level Engineering Resources for more information.

.CSV (Comma Separated Value): Submit data separated by commas, with each column surrounded by quotes. Header row and spatial attributes (latitude and longitude coordinates) are required.

.KML/.KMZ (Keyhole Markup Language): Represent the data as SchemaData and SimpleFields (preferred) or ExtendedData. KML/KMZ files can be created with Google Earth and must have address fields. See the Google Earth YouTube Channel for more information.

The following fields are listed as either Required, Preferred, or Optional for address points (geocode) datasets. Failure to include the required information could result in processing delays or rejection.

The following fields are listed as either Required, Preferred, or Optional for road, trail, and pedestrian path datasets. Failure to include the required information could result in processing delays or rejection.

The following fields are listed as either Required, Preferred, or Optional for building footprints, property boundaries, and parcels datasets. Failure to include the required information could result in processing delays or rejection.

The data you submit must be viewable in Google Earth Pro. Submitting your data files as per the above Data Requirements should be sufficient, but we encourage you to verify before submitting your data. For more information on Google Earth Pro, see General Help Page , Installation of Google Earth Pro Help Page.

An electric vehicle charging station (also known as EVSE - Electric Vehicle Supply Equipment) is a publicly-accessible physical kiosk, pole, pillar or outlet that supplies electric energy to recharge batteries in plug-in electric and hybrid vehicles. An EV Charging Station is typically located on streets, retail shopping centers, restaurants or parking places.

The Open Charge Point Interface (OCPI) enables a scalable, automated EV roaming setup between Charge Point Operators and eMobility Service Providers. It supports authorization, charge point information exchange, charge detail record exchange, remote charge point commands and the exchange of smart-charging related information between parties. If your data is in OCPI format (even if you are not a part of OCPI) we can onboard your data.

The Google EV Location Feed Specification (GELFS) defines a common format for electric vehicle (EV) charging locations and associated information. GELFS enables EV charging networks to publish this data to be consumed by a variety of applications including Google Maps.

A Location object denotes a physical location such as a physical address at a specific location for a single network provider. The Location object is synonymous with a POI; for example, if there are 20 charging stations within a parking lot, this is represented via a single Location object.

As such, authentication describes how the user asserts that they have an identity, which in turn can be used by the network to determine appropriate access to the resource. For example, a physical membership card, an app or a credit card. Each authentication method is specified as a separate object, and these objects are referred to by their IDs inside the Port objects.

The following table provides a definition, the feature structure, and a link to the capturing rules for each of the required (16) files. Failure to include the required information could result in processing delays or rejection.

An Anchor represents the curated Point used as the preferred display location of a specific Address OR non-addressable device, service, equipment or physical environment. In both cases, the record serves as the anchoring point from which another feature (i.e. Occupant) can derive, reference or inherit the Anchor's attribution.

A Kiosk models the extent of the physical object, only. It is not used to describe the business or service that is operating out of the Kiosk. An Occupant (via Anchor) or Amenity would model the operation.

Note 1: The modeling of multiple integrated buildings, with both integrated and non-integrated floor arrangements is a non-trivial undertaking. IMDF does NOT offer definitive guidance that is capable of responding to all architectural scenarios. IMDF, instead, offers guidance that is generally applicable.

Note 2: The objective of IMDF is to provide guidance with respect to the modeling of ground truth conditions. A Level is NOT expected to possess a form that makes it immediately amenable for rendering in a map application. Additionally, IMDF is not expressly concerned with cartographic requirements or aesthetic rules, though rules do, to the extent possible, take these needs into consideration.

With few exceptions, an Opening models the presence, location and physical extent (width) of an entrance. An entrance may be a physical presence such as a door that swings, slides or rotates, a gate/turnstile, or threshold.

A Relationship models the physical or conceptual association between two map elements as an edge, with the optional inclusion of an intermediary element that plays a contributing contextual role in the relationship. The semantic intent of a Relationship is determined by the nature of the referenced elements and their respective roles in the map itself.

A Venue models the presence, location and approximate extent of a place. A Venue is an abstract modeling concept whose only tangible elements are the associated descriptive properties, and the other feature types that lay within it which model physical items such as buildings, floors and rooms. Ideally, the polygonal geometry of a Venue feature represents a formal property boundary associated with the Venue.

The following fields are listed as either Required, Preferred, or Optional for trucking restriction datasets. Failure to include the required information could result in processing delays or rejection.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

3a8082e126