Raptor Maps' Field Glossary

action

The action object contains information about the suggested action for a given anomaly. The primary field is the "action" field which contains a string value with the name of the suggested action. Possible values are CLAIM, NO_ACTION, REPAIR, REPLACE, TRACK, UNSPECIFIED.

"action": {
        "action": <string>, -- enumerated value from list above
        "action_source": "system_specified",
        "created_tsecs": <integer>,
        "creator_id": <integer>,
        "defect_id": <integer>,
        "id": <integer>,
        "inspection_id": <integer>,
        "status": 1,
        "updated_tsecs": <integer>,
        "updator_id": <integer>
    },

anomaly_life_cycle

The anomaly life cycle object consists of two values, an ID and a status. The ID is a numerical representation of the status. The status is a string description of the anomaly status.

object_notation_json

Raptor Maps' new standard for object locator text. Each notation object contains a row name, string name, module name. These refer to the physical equipment on the farm and a full explanation can be found in our knowledge hub. For the API response. Each notation element contains an x and a y component, the default goes west to east, and north to south respectively.

If an object's location is 2,29,6,1,4,2 we can break that into three pairs.
2, 29 means the second row in the x direction, 29th row in the y direction
6, 1 means the 6th string horizontally into the row, and the 1st string vertically
4,2 gives us the location of the module, 4th in the string, in the 2nd segment of the string

In our API response that will look like this:

"object_notation_json": {
            "row": {
                "object_name": "2,29",
                "prefix": "",
                "rule_index": 0
            },
            "string": {
                "object_name": "6,1",
                "prefix": "",
                "rule_index": 1
            },
            "module": {
                "object_name": "4,2",
                "prefix": "",
                "rule_index": 2
            }
        },

object_type

This field describes the equipment level at which the anomaly was found. Values are module, row, or string. For instance, cracking would be a module level anomaly; tracker mounts would be a row level; and wiring might affect an entire string.

priority

This field describes the priority level assigned to a particular anomaly. The first level of priority is determined automatically by Raptor Maps based on the anomaly type but can be changed.

tag

The tag object contains information about the anomaly type. The tag field is the primary field in the object and is the identifier for the anomaly. The tag_display_text is a string description corresponding to the tag id.

The structure of the tag object is this:

"tag": {
                "color": <string>,
                "id": <integer>,
                "org_power_factor": <float>,
                "power_factor": <float>,
                "tag": <string>,
                "tag_display_text": <string>
            },