On April 24, the National Geospatial-Intelligence Agency posted a request for information in connection with the Homeland Infrastructure Foundation-Level Data Transportation Contract. Responses are due by 5:00 p.m. Eastern on May 9.

The National Geospatial-Intelligence Agency (NGA) Homeland Security Infrastructure Program (HSIP) Branch is seeking and requesting information on how an interested contractor could provide a commercial national Transportation, Public Venues, Hydrography, and Boundaries geospatial database (geospatial vector data layers) in direct support of the Nation’s Homeland Security, Homeland Defense, and Emergency Response and Recovery missions to protect the nation’s infrastructure.

The purpose of this Request for Information (RFI) is to gain information on current Industry offerings and capabilities that would meet NGA’s mission requirements.


NGA has a mission-critical need for:

A Consolidated, Spatially Enabled, ESRI File Based Geodatabase – This spatially-enabled geodatabase shall be delivered as an application ready product that is compatible with ArcGIS desktop (10.x) and ArcGIS Pro without additional evaluation or transformation of content. This desktop geodatabase will have de-normalized any related tables or products, translated any coded domain values to textual attribution/description, and deliver consolidated feature classes (see below bullets) along with their associated attribution and metadata.

  • Points of Interest (POI) – These point feature types will clearly represent all core and premium feature types that are commercially available and verified through a proven validation process. A few examples of these feature types may include, but are not limited to, gas stations, hotels, hospitals and truck stops. This data shall be easily accessible and identifiable within a GIS desktop environment. All coded domains that represent feature types or feature classes shall be translated into full textual descriptions and grouped into common feature datasets. Every POI shall identify the correct feature type, business name, spatial location, full address (street number, street name, city, state, zip code), and preferred contact information as attribution.

  • Map Features – The data must be capable of displaying base map features in a clear and concise manner. These feature types will include, but will not be limited to, administrative areas, park and campus areas, hydrological features, building footprints. All coded domains that represent feature types shall be translated into full textual descriptions and grouped into common feature datasets. Every Map Feature shall correctly identify the feature type, name, and spatial location.

  • Road networks – The data must be capable of capturing turn by turn road networks that are traveled by regular automotive traffic. Networks will expose any road restrictions and render automotive and enhanced truck routing. This network will be application ready by immediately plugging directly into and interfacing with the ArcGIS Network Analyst extension.

  • Stand Alone Address Locators – Data will contain a complete composite of address locators that are built on parcel, address, block, city, and zip level information.

  • Historic Traffic Patterns – Data will expose collected traffic patterns and render them within the GIS desktop environment as a feature class.

  • Off-road networks – The data must be capable of capturing off-road networks that can be traveled via foot traffic or other non-automotive traffic.

  • Coverage Areas – United States and Territories, Canada, Mexico and hurricane prone islands and countries.

  • Metadata – All feature level metadata will be in Federal Geographic Data Committee (FGDC) format and directly attached to every feature class within the enterprise geodatabase. This data will fully describe the feature classes, all attribution, publication information, all access and use constrains. The format of the data is described at the following FGDC Metadata standards website: (

  • Compatible with existing NGA visualization capabilities – The data must be provided in a standard data format or a format that is Open Geospatial Consortium (OGC) compliant and compatible with existing NGA visualization capabilities (such as Map of the World). NGA requires this to maximize the integration with existing visualization capabilities to facilitate the discovery through web map services.

  • Data Dictionary—A full description of the consolidated geodatabase that clearly links the overview of content, a full listing of all feature types, tables, and all associated attribution.

Full information is available here.

Source: FedBizOpps