You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-manager-for-agri/how-to-ingest-and-egress-farm operations data.md
+12-11Lines changed: 12 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,8 +24,9 @@ Create a farm-operations job with an ID of your choice. Users are expected to us
24
24
25
25
API documentation:[FarmOperations_CreateDataIngestionJob](/rest/api/data-manager-for-agri/dataplane-version2023-07-01-preview/farm-operations/create-data-ingestion-job)
26
26
27
-
[!NOTE]
28
-
`shapeType` and `shapeResolution` are provider specific attributes. If they aren't applicable to your provider, set the value to "none"
27
+
> [!NOTE]
28
+
>`shapeType` and `shapeResolution` are provider specific attributes. If they aren't applicable to your provider, set the value to "none"
29
+
>
29
30
30
31
Based on the startYear & operations list provided, ADMA fetches the operations data from the start year to the current date. Along with specific data (geometry), FieldView also gives us the DAT file for the activity performed on your farm/field or boundary. The DAT file contains a boundary for which the activity is performed.
31
32
@@ -55,25 +56,25 @@ Step 1: Get geometry for each operation
55
56
To continue geo spatial analysis, you can fetch the list of farm operations data associated to the `partyId` and then get geometry data for a specific operation ID (ex: `plantingId`).
You can also use the ID like `plantingId` to fetch the above data in the same API. if you remove the Id, you're able to see any other data that intersects with the same geometry across party. So it shows data for the same boundary across different parties.
0 commit comments