File Format

The file should resemble the newline-delimited GeoJSON (geojsonl) format which is a text-based format based on JSON for representing geographical data. The file is made up of lines, with each line containing a single feature and is a valid JSON object. Each line can be read and processed independently, without having to parse the entire file.

This integration supports the following geometrical types: Point, Line, and Polygon. Below is an example of how a single line for a feature should be structured:

{"geometry":{"type":"<Point | LineString | Polygon>","coordinates":[]},"properties":{"GLOBALID":""},"assetClass":"","action":""}

For example: {"geometry":{"type":"Point","coordinates":[-87.624632,42.694634]},"properties": {"GLOBALID":"{02BF666D-0F66-4FC9-A56B-378E87C37D23}"},"assetClass":"Dummy","action":"W1IS"}

Key	Type	Description
geometry	JSON Object	GeoJSON geometry object of type Point, LineString or Polygon. This is optional.
type	String	Case-sensitive string: "Point" / "LineString" / "Polygon"
Coordinates	Array	This is an array of positions where a position is an array of numbers which are longitude and latitude, or X and Y, precisely in that order and using decimal numbers. One position in the case of a Point geometry type. (For example: [-87.624632,42.694634]) An array of positions in the case of a LineString geometry type. (For example: [[-87.963549,41.626542],[-86.699112,42.778569],[-88.392632,41.318056]]) An array of Linear Ring in the case of a Polygon geometry type. A linear ring is a closed LineString with four or more positions. The first and last positions are equivalent, and they MUST contain identical values; their representation should also be identical. (For example: [[[-88.921225,42.614085],[-88.911225,42.614085],[-88.911225,42.624085],[-88.921225,42.624085],[-88.921225,42.614085]]])
properties	JSON Object	List of fields and values to be used to map against asset and location BO elements in respective GIS to WAM Sync Mapping Extendable Lookup. Only the properties identified in the lookup are considered for sync. GLOBALID is a required key in this object.
GLOBALID	String	Mapped against gisId value in the sync request. This is considered as unique identifier.
assetClass	String	Mapped against the GIS Asset Class element in GIS to WAM Sync Mapping Extendable Lookup to identify which mapping to use to create sync request for the respective feature.
action	String	To identify if the operation is add/update/delete. Valid values are W1IS/W1UP for insert or update, W1DL for delete. For either W1IS or W1UP, if the GLOBALID is found in WAM then the respective Asset and Asset Location will be updated. If the GLOBALID is not found, then a new Asset and Asset Location will be created. In case of W1DL, only GLOBALID key is needed, using which the respective asset will be identified and retired. Any other properties will not be processed.

Note:

For abandoning an asset, the action should be W1UP. The process looks for a designated “abandonment” GIS field and a corresponding “abandonment” value on the GIS feature to mark the feature as abandoned. The “abandonment” GIS field and value combination are configured on the Esri WAM Integration master configuration record.

• Any other keys apart from the ones mentioned above will be ignored.
• Every line in the file should be a valid JSON without any empty lines in the file.