Service Package

Basemap and Data Provisioning for Disconnected Environments

Every map needs a basemap, and nearly every basemap assumes you're connected to the internet. Deployed and disconnected users aren't.

So teams build offline packages themselves, from whatever sources they can find, one time. Then the data goes stale, because there's no repeatable way to refresh it.

What goes in a package

OpenStreetMap as vector tiles, refreshed on a schedule you set

Imagery basemaps, open source (Landsat at about 30m globally) or commercial, tiled for performance

Elevation data for terrain analysis and 3D views, from SRTM at 90m globally up to higher resolution where you have it

MGRS and UTM grid overlays and military symbology layers

Reference layers like HIFLD infrastructure data for U.S. missions

An automated update pipeline, so the next refresh isn't a whole new project

Sized to where you're going

The first question is always how much data fits where you're going. A global package at open-source resolution is one conversation. Sub-meter imagery over an area of operations is a different one. We size the package to your hardware and your bandwidth, not the other way around.

Where we've done this

We ran enterprise basemaps for USSOCOM's AIDE program for more than ten years, serving raster and vector tiles to SOF users across multiple classified domains, with hub-and-spoke replication and bandwidth controls for constrained enclaves.

CoreSpatial Basemaps by NGS is the productized version of that work, with OpenStreetMap updated quarterly.

Duration and procurement

Duration: 1 to 3 weeks.

  • Fixed scope and fixed price, agreed before work starts.
  • Available through GSA MAS (47QTCA26D002H) and Tradewinds.

Talk to an engineer about your environment.

Discuss a Requirement