External GIS Integration enables Borealis Map to connect to external GIS services and spatial data files, allowing users to display external GIS layers alongside Borealis data. This provides a unified view of spatial and operational information within a single map interface.
📌 Note: External GIS sources are currently read-only. Data can be viewed in Borealis but cannot be edited. Editing capabilities are planned for a future release.
Key Benefits
- Unified Map View: Display external GIS data alongside Borealis records, such as projects, land parcels, stakeholders, commitments, and cases, in a single map.
- Reduced Data Duplication: Connect directly to external GIS services and files instead of importing and maintaining duplicate data.
- Flexible Spatial Data Support: Add spatial data from a variety of sources, including ArcGIS Feature Services, WFS services, Shapefiles, and KML/KMZ files.
- Faster Decision-Making: Access up-to-date spatial context directly in Borealis without relying on separate GIS tools or data exports.
- Consistent Access Across Borealis: Use external GIS layers across maps, map selection tools, analytics widgets, and record-level map views.
Supported Sources, Formats and Geometry Types
-
Online Services:
- ArcGIS Feature Services (REST): GIS layers published through the ArcGIS REST API.
- OGC WFS (Web Feature Service): An open standard for accessing geographic features and their attributes over the web.
- ReportAll USA: A parcel data service that provides nationwide U.S. parcel coverage.
-
File Uploads:
- ESRI Shapefiles (.shp, uploaded as .zip): A widely used vector data format developed by ESRI for storing geographic features and their attributes.
- KML/KMZ Files: Formats used to store and display geographic data. KMZ is a compressed version of KML that can include related resources in a single file.
- Geometry Types: Point, Line and Polygon.
Authentication Methods
| Online service | Supported authentication | Credentials required |
| ArcGIS Feature Service |
None Token / API Key API Header OAuth 2.0 Client Credentials |
None Static Token Header Key Name, Token Value Token Endpoint URL, Client ID, Client Secret, optional Scope |
| ReportAll USA | Path-Embedded Client ID | Client ID / Token |
| OGC WFS |
None Token / API Key API Header |
None Static Token Header Key Name, Token Value |
📌 Note: Authentication requirements depend on the external GIS service. Public services may not require authentication, while secured services may require an ArcGIS token or custom API header credentials.