0Clients
0Feeds
0Critical issues
0Warnings
0Queue backlog
0Dead-letter messages
0Feeds off
0Renewals due
Operations Alerts
Feed Health
| Health | Feed | Client | Intake | Receiving | ArcGIS Writes | Last Success | Issue |
|---|
Recent Errors
| Time | Feed | Status | Message |
|---|
1Client
Create the client first if it is not listed.
Creating a new feed.
2What are you integrating?
This chooses a starting parser. You can still map fields from the real payload.
3Source intake
This controls the receiving side of the feed, separate from ArcGIS output.
Used only when MAPSS fetches the data.
POST/webhook sourceAfter saving, the app shows the URL and one-time feed API key. Give those to the device platform or manufacturer so they can POST JSON to MAPSS.
Use $.items, $.data.records, or $ when the response is already one record or an array.
Optional field saved after each poll.
Optional query parameter populated with the previous checkpoint.
Fetches the provider API once and puts the first returned record into Sample source payload.
4Destination
Leave blank while only cataloguing or testing the feed.
ArcGIS field used for updates.
JSON path used to find the matching value.
Use $.payload.longitude, $.payload.gps.lon, or a fixed value for static sensors.
Use $.payload.latitude, $.payload.gps.lat, or a fixed value for static sensors.
Lines are created from the nearest valid earlier point to the current point. If a late point arrives between two existing points, the old bridged segment can be replaced by two corrected segments.
Default is off so new feeds cannot write to ArcGIS by accident.
5Sample and field mapping
Paste an example message from the manufacturer, device platform, or webhook test.
Left side is the ArcGIS field. Right side is a JSON path such as $.device.canonical_id, $.metrics.battery, or $.payload.anyRawField.
Flexible by designThe feed type only chooses the parser. Each destination layer keeps its own mapping, geometry paths, match field, write mode, and credential.
| ArcGIS field | Source JSON path or value | New field? | Type | Alias |
|---|
6Enrichments, device details, and geofencing
Optional bounds catch wrong hemispheres or impossible project-area jumps before lines are drawn.
Device DetailsUse an existing ArcGIS table/layer, or create one in Layer Mapper. Incoming records can copy selected details such as friendly_name, species, sex, deployment_date, collar model, project, and notes.
Loads fields from the ArcGIS table and tests the sample payload device ID against it.
Copied geofence attributes appear under $.geofence.fields and as $.metrics.geofence_fieldName for easy ArcGIS mapping.
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 | Status |
|---|
Credential
Use this for ArcGIS, provider API keys, and other feed credentials.
Saved Credentials
| Name | Description | Last Changed |
|---|
Existing Feature Layer
Create Feature Layer
Use fields from checked mapping rows, or edit this list before creating the layer.
Create Device Details Table
The standard template already includes device_id, friendly_name, species, sex, deployment_date, device_type, make_model, and notes.
Test Payload
MAPSS Staff User
Staff
| Username | Name | Role | Status |
|---|