Integration
Hub

Staff login

Staff access for feed management, ArcGIS outputs, and platform operations.

Password login is enabled for emergency recovery. Prefer Cognito MFA sign-in in production. See docs/operations/cognito-only-cutover-2026-08-23.md.

Enter the 6-digit code from your authenticator app.

Scan with your authenticator app

Add to 1Password / authenticator

Prefer a password manager? Use the button above — it opens a standard otpauth link so 1Password can save the one-time password.

At least 12 characters with upper, lower, number, and symbol.

At least 12 characters with upper, lower, number, and symbol.

Integration Hub

Dashboard

Health, traffic, and platform summary

Waiting for first refresh.

Integration health Loading…

Active/inactive feeds with auth failures, capture-first, and poll vs push intake.
Feed Status Intake Health Last auth failure

Error feed rollup

Recent monitor activity

Time Feed Level Message

Enrichment

Platform traffic & latency

Drag to zoom · scroll to zoom · double-click to reset
Loading traffic…

Feeds

Operational feed list with health, lifecycle, and diagnostics. Use to create or edit a stream, or to start from a provider template.

Archive / restore Archive stops intake. Filter Archived only, then Restore to Paused before resuming.
Select feeds for bulk actions
Use Edit or the row ⋯ menu for Export, Clone, Pause, and Archive. Secondary intake and diagnostics details expand under each feed name.
Feed Client Status Activity Actions

Connector Library

Choose a provider, understand what MAPSS has validated, and start a guided feed setup.

0Available
0Native
0Guided
0Needs adapter
ProviderImplementationCertificationIntakeValidationOwnershipFeedsActions

Provider support varies by validation level. "Contract tested" and higher states indicate production readiness. Live testing is required before enabling ArcGIS writes for new clients. Legacy connectors are available for reference and migration planning only.

Connector Studio

Edit immutable connector revisions with validation, four-eyes approval, and explicit feed migration.

Select a connector to open Studio.

Connector

Overview

Intake

Packet

Sample event data derived from the test sample. Read-only — edit the source executable code. 

No sample data available.

Fields

ArcGIS field contract inferred from normalizing the sample through the connector. Draft revisions can edit declarative field rows (structured JSON only).

No field projection yet.

Outputs

Default History, Latest, Summary, and Lines recipes. Draft revisions can toggle enabled state and geometry type per output (structured JSON only).

Mappings

Default source→ArcGIS mappings inferred from the field projection. Draft revisions can edit mapping rows here; feed-level overrides remain in Feed Setup.

No mapping projection yet.

Guide

Projected setup hints from the connector definition (read-only). Edit intake and documentation fields on their tabs; this panel never accepts executable code.

Validation

Publish blockers

Mapping live gate

Metadata live gate

Tests

Harness evidence

Connector readiness gate

Certification checklist: docs/operations/connector-certification-checklist-template.md

Test run ledger

Compatibility

Affected feeds

Feed Setup

Choose the closest template, test each stage, and keep ArcGIS writes off until the preview looks right. Register or create destination layers under so the same layer can later be enriched.
Next step: choose the client and feed name.
Unsaved draft changes
Step 1 of 6 Complete the client and feed identity first.
1Who Is This Feed For?
Start with the client and a feed name your team will immediately recognize. The integration ID is the stable system name used for API identification.
Create the client first if it is not listed.
Suggested from the client and connector until you type a custom name.
Updates automatically until you type a custom system ID.
Creating a new feed.Saves client and feed identity without later-step checks.
2Choose A Starter Template
Search by manufacturer, platform, or use case. MAPSS will show whether the connector is ready, guided, or still needs a provider adapter.
The list filters as you type.
Choose the closest match for the manufacturer or platform.
Connector statusChoose a template to see what is ready and what must still be tested.
Saves the connector choice and provider name.
3How Does Data Reach MAPSS?
This step is only about the source side. ArcGIS output is configured in the next step.
Use POST when the provider can push data to us. Use Poll when MAPSS must fetch from the provider API.
Turn this off to keep monitoring the feed without sending incident emails.
Separate multiple addresses with commas. Leave blank to use the MAPSS operations address.
Confirms when an emailed incident has cleared.
Use the expected reporting interval plus a reasonable delay before intervention is required.
Health email not tested
Send a test after choosing recipients to confirm the delivery route before enabling the feed.
Provider POST setup
The live key is hidden unless you set a replacement here or it has already been saved in this browser. Provider keys up to 64 characters are supported.
Copy this key now. MAPSS cannot show it again after you leave this screen.
Radio network identifier that becomes the last segment of the Hub intake URL.
When a new source/device ID arrives, MAPSS creates a minimal unassigned registry row. It never guesses species, sex, or subject identity.
Save the feed first if you want MAPSS to auto-generate the feed key.
Binary webhook decoding
Choose an existing credential or click New to create one.
Use $.items, $.data.records, or $ when the response is already one record or an array.
How often MAPSS should fetch the provider API.
Fetch the provider API once and place the first returned record into the sample payload below.
OAuth token exchangeMAPSS requests a short-lived token before fetching.
Signed requestThe signing key stays in the selected credential.
Login before fetching
Pagination
Per-device detail fetch
API protocolREST is the normal default.
Request details and expert settings
Optional field saved after each poll.
Optional query parameter populated with the last saved position.
Expert workflow JSON
MAPSS keeps provider-specific options here. Guided controls above are merged into this configuration when saving.
No source test yet
Use Test Source Fetch for fetched feeds, or save the feed and give the POST details to the provider for webhook feeds.
Saves intake settings and the feed API key without ArcGIS output checks.
4Choose The ArcGIS Outputs
Which outputs should this feed maintain? Select one or more. History (or Latest) is enough for most feeds. Only tick Summary or Lines when you need those derived layers — Save only requires a layer for the outputs you enable.
4.1 HistoryAdd every accepted point as a new feature.
Fields not checked
No History create yet
Configure the History layer to see results here.
Saves the complete feed, including every selected output.
4.2 LatestUpdate one current point for each device.
Fields not checked
No Latest create yet
Configure the Latest layer to see results here.
Saves the complete feed, including every selected output.
4.3 SummaryMaintain record count, active duration, latest movement, geofence, and selected device details per device.
Automatic summary fieldsSummary creates operational fields automatically. Device-detail columns are included only when you enable Device Details and select those fields.
Fields not checked
No Summary create yet
Configure the Summary layer to see results here.
Saves the complete feed, including every selected output.
4.4 LinesCreate valid movement segments in device-time order.
Line validation uses the feed's single Max realistic speed value in Optional Enrichments And Rules.
Automatic line fieldsLines use MAPSS-generated segment, start/end, distance, duration, speed, and direction fields rather than the packet mapping below.
No Lines create yet
Configure the Lines layer to see results.
Saves the complete feed, including every selected output.
Shared Point SettingsUsed by History, Latest, and Summary.
Latest and summary matching
Validation checks each selected output before publishing is enabled.Saves intake toggles and ArcGIS choices. ArcGIS outputs are required only when writes are enabled.
No shared ArcGIS check yet
Load History fields or Validate All Outputs here. Create and select results stay on each output.
5Map History And Latest Fields
Applies to History and Latest. Both point outputs use this packet-to-ArcGIS mapping. Summary and Lines use their automatic fields described in sections 4.3 and 4.4. Paste one real example payload, read the source fields, load the ArcGIS fields, then drag source fields onto ArcGIS fields.
Paste JSON to validate inlinePaste an example message from the provider, or use Test Source Fetch above to load one automatically.
Fastest way to map1. Read Source Fields. 2. Load ArcGIS Fields. 3. Apply Top Matches. 4. Drag and drop to address any remaining requirements.
Wrong ArcGIS field type?ArcGIS cannot change a field's type after creation. Give the mapping a new field name, tick New field, choose the correct type, create the checked field, and save the feed.
Raw field mapping JSON (advanced)
Left side is the ArcGIS field. Right side is a JSON path such as $.device.canonical_id, $.metrics.battery, or $.payload.anyRawField.
ArcGIS field Source JSON path or value New field? Type Alias
No mapping preview yet
Read the source fields, load the ArcGIS fields, and preview the outgoing feature before you save.
Saves mapping progress without requiring every later step. >Save the feed once the source test and ArcGIS preview look right. Archive stops intake; use Restore on archived feeds before resuming. Administrators can permanently delete archived feeds.
Feed not saved yet
Saving stores the intake settings, mappings, quality rules, enrichments, and ArcGIS destinations.
6Feed processing & metrics
Per-event processing during ingest: movement & metrics, device join, geofence, and quality. Not layer enrichment jobs — use Enrichment jobs / Enrichment Setup for solar/lunar backfill on registered layers.
Legacy feed enrichment (deprecated) Solar and moon context on the ingest pipeline is deprecated. Create a layer enrichment job under instead.
Copies solar/lunar settings into a draft layer job. Preview and enable there, then remove these legacy checkboxes.
Makes every selected output match its connector, output type, mapping, and enabled enrichments.
API base URL
These rules are saved with this feed.
Feed-specific qualityUse a higher speed cap for vehicle feeds such as Mozetech, and tighter rules for collars or static assets.
Older points can still be kept for lines and history unless you explicitly block them.
Optional bounds catch wrong hemispheres or impossible project-area jumps before lines are drawn.
Device, asset & deployment registryChoose a category profile (animal, person, vehicle, or asset) and select which fields to sync to live feeds. Use an existing table or create one with the matching schema.
Selected fields are stored on the feed and copied from the registry table into live enrichment and mapping.
Select a profile to preview synced layer fields.
Geofences apply to every selected outputThe match result and selected boundary fields are added to History, Latest, Summary, and Lines. Existing destination layers can be updated below; new layers include these fields automatically.
No enrichment test yet
Turn on device details or geofence checks only when you want to test or use them for this feed.
Saves the complete feed, including outputs, mappings, quality rules, and enrichments.

Browse declarative layer enrichment types (solar/lunar, Sentinel-2 EVI, weather, and planned catalogue entries). No executable expressions. Create jobs under against layers registered in .

Catalogue

Declarative library only — definitions ship as versioned JSON in the repository.

Type Category Status Version Provider

Selectable types

Saved layer enrichment jobs and run history. Jobs target — the same layers feeds publish to. This is separate from feed processing & metrics in step 6 (movement, geofence, device join).

Saved jobs

Job IDClientLayerStatusScope

Runs

RunJobPhaseStartedFinishedModeDiscoveredOKFailedProgressErrorsms

Usage this period

-Processing units
-Sentinel requests
-Weather API calls
-MAPSS estimate
Staff guide: Layer enrichment jobs update registered ArcGIS features in place. Feed processing stays on Feed Setup step 6. Use preview before enable. Configure schedule and populate scope in Enrichment Setup. Sentinel imagery requires ; detailed billing remains under Clients & access → Billing.

Create or edit a layer enrichment job against a (register existing under ArcGIS Layers, or create/connect during ). Jobs start as draft; preview before enabling.

Job wizard

Uses OpenWeather timemachine at feature location. Configure credentials under Enrichment providers.
Planned enrichment — raster zonal statistics are wired for preview and runner tests only. Jobs cannot be enabled until the catalogue entry is published.
Planned enrichment — feature spatial join is wired for preview and runner tests only. Jobs cannot be enabled until the catalogue entry is published.
UseFieldAliasTypeLayerTarget
Run preview to validate geometry, timestamp, and field mappings.

Enrichment providers

OAuth and API-key credentials for external enrichment APIs (Sentinel Hub, OpenWeather). Layer job definitions and runs are under Enrichment jobs and Enrichment Setup.


                

                
OpenWeather

                
                
                
                

                
                
                
                

                

                  
                  
                

                

              

              

                
Provider health

                
ProviderDeploymentStatusLast authLast error

                
Enrichment catalogue availability

                
EntryProviderStatusDescription

              

            

          

          

            

              
Client

              

                

                  

                    Short lowercase name used for grouping feeds.
                  

                  

                    
                  

                  

                    
                  

                

                

                  

                    
                  

                  

                    
                  

                  

                    
                  

                

                

                  

                    
                  

                  

                    
                  

                

                

                  

                    
                  

                  

                    
                  

                

                

                  

                    
                  

                  

                    
                  

                  

                    
                  

                

                

                  
                

                

                  
                

              

            

            

              
Clients

              

                

                  
                

                

                  

                    
                      

                        ID
                        Name
                        Status
                        Billing Email
                        ArcGIS Defaults
                        Platform Fee
                        
                      

                    
                    
                  

                

              

            

          

          

            

              
Billable Feed

              

                

                  

                    
                  

                  

                    
                  

                  

                    
                  

                

                

                  

                  

                    
                  

                  

                

                

                  

                    
                  

                  

                    
                  

                  

                    
                  

                

                

                  

                    
                  

                  

                    
                  

                  

                    
                  

                

                

                  

                    
                  

                  

                    
                  

                  

                    
                  

                

                

                  
                

                

                  
                

              

            

            

              
Upcoming Renewals

              

                

                  
                

                

                  

                    
                      

                        Client
                        Feed
                        Renewal
                        Days
                        Annual Fee
                        Billing Contact
                      

                    
                    
                  

                

              

            

            

              
Subscriptions

              

                

                  
                  
                  
                

                

                  

                    
                      

                        ID
                        Client
                        Feed
                        Provider
                        Renewal
                        Annual Fee
                        Feed Status
                        Billing Status
                        Lifecycle Date
                        
                      

                    
                    
                  

                

              

            

            

              
Enrichment Usage Billing
-Processing units
-Sentinel requests
-Weather API calls
-Allowance remaining
-MAPSS estimate
Platform Costs & Usage Allocation

              

                

                  

                    
                    
                  

                  
                  
                

                

                  
-AWS platform MTD

                  
-Shared platform cost

                  
-Usage-driven cost

                  
-Cost data refreshed

                

                

                

                  Actual total, estimated allocationThe platform total comes from AWS Cost Explorer. Client and feed amounts are management estimates that divide shared cost equally and usage-driven cost by measured workload.
                

                
AWS services

                

                  

                    
ServiceTypeMonth-to-date

                    
                  

                

                
Client estimates

                

                  

                    
ClientFeedsAllocation unitsShareEstimated cost

                    
                  

                

                
Feed estimates

                

                  

                    
                      

                        Client
                        Feed
                        Normalized
                        Published
                        Quality blocks
                        Failed
                        Allocation units
                        Share
                        Estimated cost
                      

                    
                    
                  

                

              

            

          

          

            

              
Credential

              

                
                

                  

                    Staff see the short name (client/purpose). The platform
                      prefix is added when saving. Renaming
                      updates linked feeds and clients.
                  

                  

                    
                  

                

                

                  Use this for ArcGIS, provider API keys, and other feed
                    credentials.
                

                

                  
                

                

              

            

            

              
Saved Credentials

              

                

                  
                

                

                

                  

                    
                      

                        Credential
                        Linked to
                        Last Changed
                        
                      

                    
                    
                  

                

              

            

          

          

            

              
Registered Layers

              

                

                  Layers registered here are shared by
                  Connectors (feed destinations) and
                  Enrichments (layer jobs). Search by title, URL, client, feed, or credential.
                

                

                  
                  

                    
                    
                    
                  

                

                

                  Load clients to see registered layers.
                

                

              

            

            

              
Layer tasks

              

                

                  Register an existing service layer, connect by URL, create a hosted layer, or create a device details table.
                

                

                  
                  
                  
                  
                

              

            

            
            
            

              
Register Existing Layer

              

                

                  Search for and register a layer so feeds and enrichment jobs can select it from a shortlist.
                  Layers created or connected during Feed Setup can also be registered here for reuse.
                

                

                  

                    
                  

                  

                    
                    

                      
                    

                  

                  

                    
                    

                      
                    

                  

                

                

                  

                    
                  

                  

                    
                  

                

                

                  
                  

                    

                      
                        

                          Title
                          Credential
                          Feeds
                          
                        

                      
                      
                    

                  

                

                

                  
                  
                  
                

                

                  
Ready

                  

                    Choose a client and credential, then search ArcGIS.
                  

                

              

            

            
            
            

              
Connect to Existing Layer

              

                

                  Load schema and fields from an existing feature layer by URL.
                

                

                  

                    
                  

                  

                    
                  

                

                

                  
                  
                

                

              

            

            
            
            

              
Create New Feature Layer

              

                

                  Create a new hosted feature layer or table with custom fields.
                

                

                  

                    
                  

                  

                    
                  

                  

                    
                  

                  

                    
                  

                  

                    
                  

                

                

                  Define layer schema or use a template.
                

                

                  
                  
                

                

              

            

            
            

              
Create Device Details Table

              

                

                  Create a non-spatial table for device metadata and enrichment fields.
                

                

                  

                    
                    
                  

                  

                    
                  

                  

                    
                  

                

                

                  

                    
                  

                  

                    
                    
                  

                

                

                  Profile fields are created from the selected category.
                    Add optional extra columns here.
                

                

                  
                  
                

                

              

            

          

          

            

              
Operations
Service Status
Current feed disruptions and recent recoveries recorded by MAPSS health monitoring.

              
            

            
Loading statusChecking current feed incidents.

            

            

              
Current Disruptions
Issues that require intervention or are still being monitored.

              
StartedClientFeedSeverityIssueUpdated

            

            

              
Recent History
Resolved incidents are retained for one year.

              

              
ResolvedClientFeedIssueDuration

            

          


          

            

              

                Operations
                
Dead-letter Recovery

                
Investigate messages that exhausted automatic retries without mixing them into a selected feed's live monitor.

              

              
            

            

              Controlled recoveryInspect and select specific messages before clearing them. Replay sends one message back to its paired processing queue and removes it from the dead-letter queue only after that send succeeds. Purging is reserved for a whole named stage when every message there is known to be disposable. Payload metadata is redacted before display.
            

            

              
              
              
              
              
              
            

            

              Open this page to load currently visible dead-letter messages.
              

                
                
                
                
                
              

            

            

            

            

              

                
QueuedStageClientFeedEventReceivesErrorInspectActions

                
No messages loaded.

              

            

          


          

            

              
Feed Monitor

              

                

                  Read-only live operations viewUse this page to inspect
                  intake history, publishing behaviour, and exactly why some
                  accepted records did not write to ArcGIS. Active testing lives
                  on its own page so staff can troubleshoot without feeling like
                  they are touching the live stream.
                

                

                
                

                  

                    
                  

                  

                    
                  

                  

                    
                  

                

                

                  Open API & Webhook Docs
                  

                    Waiting for first refresh.
                  

                

                

                

                

                

                  `Normalized only` means MAPSS accepted the event, normalized
                  it, and then deliberately did not produce an ArcGIS write. The
                  exact reason is shown in the rows below.
                

                

                

                

            

              
Recent Intake Summary

              

              

            

            

              

                
Authentication failures

                
Ingest API key rejections and provider poll credential failures.

                Rejected API keys and disabled-feed attempts (redacted; no secrets stored).
              

              

            

            

              

                
Provider Fetch

                Redacted capability diagnostics from the latest poll.
              

              

            

            

              

                
ArcGIS Layer Schema

                Detect missing fields, type changes, and admin edits that can break publishing.
              

              

                
              

              

                Select a feed and run a schema check to compare expected fields against the live ArcGIS layer.
              

            

            

                    

                      
Intake Trend

                      Load a feed to see recent intake frequency and
                        results.
                    

                    

                      

                        
                          

                            Bucket
                            In
                            Published
                            Blocked
                            Failed
                            Queued
                            Result mix
                          

                        
                        
                      

                    

                  

                  

                    

                      
Why Records Did Not Publish

                      Click a reason to filter the recent intake list
                        below.
                    

                    

                    

                      

                        
                          

                            Reason
                            Category
                            Count
                            Latest
                          

                        
                        
                      

                    

                  

                  

                    

                      
Recent Intakes

                      Load a feed to see recent accepted records and
                        outcomes.
                    

                    

                      

                      
                      
                      
                      
                      
                      
                      
                      

                      
                      Filters run on the server before paging.
                      

                        
                      

                    

                    

                      

                        
                          

                            Received
                            Device
                            Observed
                            Result
                            Why
                            Data
                          

                        
                        
                      

                    

                  

                

              

            

          

          

            

              
Feed Testing

              

                

                  Step-by-step troubleshootingUse the dry-run buttons to
                  validate fetch, normalization, enrichments, and ArcGIS feature
                  output. Only Send Through Intake hits the live
                  receiver.
                

                
                

                  

                    
                  

                  

                    
                  

                  

                    
                  

                

                

                  

                    
                    

                      

                        
                        
                      

                      Needed only when sending a live intake test.
                    

                  

                  

                    
                  

                

                

                  Open API & Webhook Docs
                

                

              

            

            

              
Test Each Step

              

                
                

                  
                

                

              

            

          

          

            

              
MAPSS Staff User

              

                

                  Login uses email. Staff sign in with their MAPSS email
                  and password. Username is for platform record-keeping
                  key and can be left blank when creating a user.
                

                

                  

                    
                  

                  

                  

                    
                  

                  

                    
                  

                  

                    
                    Optional. Leave blank to derive from the email local-part
                      (login still uses email).
                  

                

                

              

            

            

              
Role definitions

              

                

              

            

            

              
Operator maintenance

              

                

                  Dry-run maintenance wrappers. Apply requires Administrator and confirm=true.
                

                

                  
                  
                

                

                

                  Staging trials: WorkerProvisionedConcurrency=1 when queue/publish wait is high;
                  ARCGIS_METADATA_ON_PUBLISH=true on one pinned feed (worker env).
                

              

            

            

              
Recent security audit

              

                

                  In-process ring buffer of recent staff security audit events (login,
                  credential, and destructive actions). CloudWatch Logs retain the
                  authoritative trail.
                

                

                  
                  
                  
                

                

              

            

            

              
Staff

              

                

                  
                    

                      Email / username
                      Name
                      Role
                      Status
                      Actions