Skip to main content
Importing custom maps allows you to bring your organization’s geospatial data into Forerunner and display it as interactive map layers. Once imported, your custom data appears alongside properties, flood zones, and other layers, providing comprehensive geographic context for your workflows.
Custom map imports are performed by your Customer Success Manager. This guide helps you understand the import process, prepare your data, and work with your CSM to get your maps into Forerunner.

​
What you can import

Forerunner supports importing a wide variety of geospatial data as custom map layers. Each imported dataset becomes a map layer that you can toggle on and off in the layers panel.

​
Example map layers

CategoryExamples
Infrastructure systemsWater, sewer, stormwater networks, and utility assets
Planning and zoningLand use designations, zoning districts, development areas
Environmental featuresWetlands, conservation areas, watersheds, habitat zones
Community boundariesNeighborhoods, service districts, municipal boundaries
Critical facilitiesEmergency shelters, fire stations, police stations, schools
Historical dataPrevious flood events, damage assessments, historical boundaries
Custom datasetsAny location-based data relevant to your organization’s work

​
Common use cases

Import pipes, inlets, outfalls, and treatment facilities as interactive layers. Configure custom fields for asset IDs, install dates, and maintenance status. Use the map to plan inspections, track maintenance, and visualize system connectivity.
Import neighborhood boundaries, voting districts, or service areas as visual layers. Use colors to distinguish different areas and enable legends to help users identify districts. Reference these boundaries when analyzing property distributions or planning outreach.
Import wetlands, conservation areas, or sensitive habitats as semi-transparent polygons. Use these layers to identify properties near environmental features for permitting review or impact assessment.
Import previous flood extent polygons from past storms or events. Color-code by event severity or date. Compare historical flood areas with current FIRM data to understand risk evolution and support mitigation planning.
Import locations of shelters, emergency facilities, schools, and medical centers as point features with custom icons. Make this layer available offline for emergency response teams using the mobile app.

​
How to import map data

Custom map imports are completed through your Customer Success Manager, who will guide you through the entire process—from preparing your data to configuring how your layers appear and function in Forerunner.

​
How the import process works

The import process typically follows these steps:
  1. Initial consultation - Discuss your data requirements, use cases, and goals with your CSM
  2. Data preparation - Prepare your geospatial data (your CSM can help with format requirements and best practices)
  3. Submit your data and requirements - Provide your data file along with details about how you want the layer configured
  4. CSM reviews and validates - Your CSM verifies the data for completeness and format compliance
  5. Import and processing - The system creates map tilesets and populates the database with your features (typically takes minutes to hours depending on dataset size)
  6. Configuration - Your CSM configures styling, visibility, legends, and other layer options
  7. Layer deployment - The layer becomes available in your layers panel for your team to use
Your CSM will notify you when the import is complete and the layer is ready to use.
Import timing varies based on the size and complexity of your dataset. Small datasets (hundreds of features) typically process within minutes, while large datasets (tens of thousands of features) may take several hours.

​
Information to provide your CSM

When requesting a map import, share these details with your Customer Success Manager: Map name - What you want to call this layer in the layers panel (e.g., “Stormwater Infrastructure”, “Zoning Districts”) Description - What the layer represents and how it will be used Data file - Your geospatial data (GeoJSON preferred, but your CSM can work with other formats) Layer type - Should this be a visual-only layer or interactive with detail panels? (Learn more about layer types) Visibility preferences - Should this layer be:
  • Visible by default when users open the map?
  • Hidden from public/guest users?
  • Available for offline use in the mobile app?
Styling preferences - Beyond the colors in your data:
  • Should features have labels displayed on the map?
  • Should there be a legend showing what colors represent?
  • Are there specific icons you want for point features?
  • What line width and style for linear features?
Custom fields - Do features need additional data fields? Your CSM can configure custom fields for rich data storage (e.g., asset IDs, install dates, condition ratings, ownership information) Update schedule - If your data changes regularly, discuss an update schedule with your CSM

​
Import format requirements

Forerunner imports geospatial data in GeoJSON format, a widely-used standard for geographic data that most GIS software can export.
Don’t have your data in the right format? Our team can work with you to properly format and import your data. Contact your Customer Success Manager to discuss your specific data format and requirements.

​
Required GeoJSON structure

Your GeoJSON file must include these properties for each feature: source_id (string, required) - A unique identifier for each feature within your dataset. This should be stable and unique across all features in the map. label (string, required) - The display name for each feature. This appears when users click on the feature or view it in lists and panels. fill (string, optional) - The fill color for the feature as a hex code (e.g., “#FF0000” for red). If not provided, a default color will be assigned. fill-opacity (number, optional) - The transparency of the feature from 0 (fully transparent) to 1 (fully opaque). Defaults to 0.8 if not specified.

​
Supported geometry types

GeoJSON features can use any of these geometry types:
  • Point - Single location (e.g., fire hydrant, facility)
  • LineString - Connected line segments (e.g., pipe, road)
  • Polygon - Closed shape (e.g., boundary, zone, parcel)
  • MultiPoint - Multiple disconnected points
  • MultiLineString - Multiple disconnected lines
  • MultiPolygon - Multiple disconnected polygons

​
Example GeoJSON structure

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Polygon",
        "coordinates": [[
          [-80.1234, 26.5678],
          [-80.1235, 26.5679],
          [-80.1236, 26.5677],
          [-80.1234, 26.5678]
        ]]
      },
      "properties": {
        "source_id": "neighborhood-001",
        "label": "Downtown Neighborhood",
        "fill": "#3388FF",
        "fill-opacity": 0.6
      }
    },
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [-80.1235, 26.5680]
      },
      "properties": {
        "source_id": "facility-042",
        "label": "Community Center",
        "fill": "#FF6B35",
        "fill-opacity": 1.0
      }
    }
  ]
}

​
Coordinate reference system

All GeoJSON data must use the WGS84 coordinate reference system (EPSG:4326), which is the standard for GeoJSON. Coordinates should be in longitude, latitude order. If your source data uses a different coordinate system, you’ll need to reproject it to WGS84 before creating your GeoJSON file.
Most modern GIS software (QGIS, ArcGIS, etc.) can export to GeoJSON in WGS84 automatically. Look for “Export to GeoJSON” or “Save as GeoJSON” options in your GIS tool.

​
Preparing your data for import

Before working with your Customer Success Manager to import your map, follow these steps to prepare your data:

​
Clean and validate your data

  1. Remove unnecessary fields - Keep only the properties you need: source_id, label, fill, fill-opacity, and any custom attributes you want to store
  2. Ensure unique source_ids - Each feature must have a unique source_id within your dataset
  3. Validate geometry - Use GIS software to check for invalid geometries, self-intersections, or topology errors
  4. Check coordinate system - Verify your data is in WGS84 (EPSG:4326)
  5. Test your GeoJSON - Use online validators like geojson.io to verify your file is properly formatted

​
Optimize for performance

Simplify complex geometries - Features with thousands of vertices can slow down map rendering. Use your GIS software’s simplification tools to reduce complexity while maintaining visual accuracy. Split large datasets - If you have thousands of features, consider splitting them into logical groups (by category, region, or type) and importing as separate layers. Remove overlapping features - When possible, merge or remove redundant overlapping features to improve visual clarity and performance.

​
Choose colors thoughtfully

Use distinct colors - If importing multiple layers, choose colors that are visually distinct from each other and from default Forerunner layers. Consider accessibility - Choose colors that work for colorblind users and have sufficient contrast against your typical basemap. Use opacity strategically - Semi-transparent fills (0.5-0.8 opacity) work well for polygons, allowing underlying basemap details to show through. Coordinate with your team - Discuss color choices with your Customer Success Manager to ensure consistency with your organization’s existing layers.

​
Types of custom map layers

Your CSM can configure imported maps as different layer types depending on your needs—such as visual-only layers for reference information, interactive layers for assets you want to track and manage, or data-enabled layers that enrich property information through spatial queries. Learn more about the different layer types and their capabilities in the Map Layers documentation.
If your organization needs to use non-FEMA flood maps for regulatory purposes, Forerunner can import custom flood maps that function as effective or preliminary FIRMs. This is a separate capability from custom map layers. See Flood layers for details.

​
Exporting data from common GIS tools

​
QGIS

  1. Open your layer in QGIS
  2. Right-click the layer and select Export > Save Features As
  3. Set format to GeoJSON
  4. Set CRS to EPSG:4326 - WGS84
  5. Configure field mapping to include source_id, label, fill, fill-opacity
  6. Save the file

​
ArcGIS Pro

  1. Use the Features to JSON geoprocessing tool
  2. Set input features and output location
  3. Set Format GeoJSON option to GEOJSON
  4. Ensure the output coordinate system is GCS WGS 1984
  5. Use field calculator to create required fields if needed
  6. Run the tool

​
Online tools

If you don’t have GIS software, several online tools can help:
  • geojson.io - Draw features manually or import shapefiles and export as GeoJSON
  • mapshaper.org - Convert shapefiles, simplify geometries, and export to GeoJSON
  • QGIS Cloud - Web-based GIS for basic editing and export
If you’re new to GIS or need help preparing your data, your Customer Success Manager can provide guidance or recommend resources to help you get started.

​
Best practices

Take time to properly prepare and validate your GeoJSON before requesting import. This prevents issues during import and ensures your layer looks professional when deployed.
Feature labels appear throughout the interface—in detail panels, search results, and lists. Use clear, descriptive labels that help users identify features quickly.
Keep notes about where your data came from, when it was created, and what it represents. Share this with your CSM so they can add appropriate metadata and documentation.
If your data will need regular updates, establish a process with your CSM early. Decide on update frequency and how you’ll provide refreshed GeoJSON files.
For very large datasets, consider importing a small sample first to verify styling, field configuration, and performance before importing the full dataset.
If your team uses the mobile app, discuss which layers should be available offline. Large raster layers may not be suitable for offline use due to storage constraints.

​
Troubleshooting

Solution: Use online tools like geojson.io or geojsonlint.com to identify formatting errors. Common issues include:
  • Missing required properties (source_id or label)
  • Invalid coordinate arrays
  • Unclosed polygons
  • Incorrect nesting of GeoJSON structure
Most GIS software exports valid GeoJSON automatically, so format errors often indicate manual edits or export configuration issues.
Solution: This usually indicates a coordinate reference system issue. Verify your data is in WGS84 (EPSG:4326) and coordinates are in longitude, latitude order. Some systems use latitude, longitude order which will place features incorrectly.
Solution: Simplify your geometries using GIS tools before export, or split your dataset into multiple layers by category or region. You can also adjust opacity and styling through your CSM to reduce visual weight.
Solution: Contact your CSM with an updated GeoJSON file. They can refresh the layer while preserving your configuration. For interactive layers with user-created records or files attached, discuss the update process carefully to avoid data loss.
Solution: Ensure users refresh their browser to load the new layer. The layer may also be configured to only show at certain zoom levels—have users try zooming in or out. Verify the layer isn’t hidden from their user role or marked as hidden from public if they’re guest users.