abel/FarmMapsApiClient_KB34_MAST
1
0
Fork 0
forked from FarmMaps/FarmMapsApiClient
Code Issues Pull Requests Packages Projects Releases Wiki Activity
fb92fa0d1c
FarmMapsApiClient_KB34_MAST/FarmmapsKPI/KPIInput.json

891 lines
41 KiB
JSON
Raw Normal View History

blah test
2023-03-22 13:48:13 +00:00
[
{
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
"useExistingCropfieldWithChildren": false,
"deleteNewlyCreatedAfterCalc": true,
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
"fieldName": "test_Potato_ZeroFertilizer_Consumption_Sand",
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
//Note when you run the FarmmapsKPI project, somewhere to your C:\git\FarmMapsApiClient_KB34_MAST\FarmmapsKPI\bin\Debug\netcoreapp3.1\ directory, files named like this are written:
//'Settings_aardappelveld_test_Potato_ZeroFertilizer.json', where 'aardappelveld_test_Potato_ZeroFertilizer.json' is your fieldName (see below)
//1 useExistingCropfieldWithChildren = false -> create new
//2 useExistingCropfieldWithChildren = true && CropfieldItemCode = "" or absent -> read fieldName (see below) -> read all codes from settings json file
//3 useExistingCropfieldWithChildren = true && CropfieldItemCode like "deb48a74c5b54299bb852f17288010e9" in KPIinput -> if you have in your account already an existing cropfield then use that
"CropfieldItemCode": "", // could contain for example this: "abae97f89f3c4ac08953b1b8bea9f076" if this is an exisiting CropfieldItemCode in your account.
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//And then if useExistingCropfieldWithChildren = true, this would be used.
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
"dataCropfield": {
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//"area": 4.22, //Leave empty, KPI app will calculate it from geometry
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
"final": true, //always true
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
"soilCode": "1", //From codelist CL405. Can be no longer be omitted
"soilName": "Sand",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"cropTypeCode": "1010101", //From codelist CL263
"cropTypeName": "Potato", //From codelist CL263
Added KPI G1 ammonia emissions (only on test servers) - Ammonia emissions from fertilizers not yet fully functional
2024-07-04 11:35:33 +00:00
"productionPurposeCode": "003", //From codelist CL251. For testing, see case with consumption & starch potato
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"productionPurposeName": "consumption" //From codelist CL251
},
"CropRecordingItemCode": "", // could contain for example this: "314aa1b6480b493ba28a5f55039a01d4" if this is the CropRecordingItemCode of the provided CropfieldItemCode. And then if useExistingCropfieldWithChildren = true, this would be used
"OperationItemCodes": [], // could contain for example this: ["4d1a6f28ea3f414180663baa4b08c60f"] or ["4d1a6f28ea3f414180663baa4b08c60f","21e08386f0454ad79acfebf78649d59b"] if these are the operations of the provided CropRecordingItemCode. And then if useExistingCropfieldWithChildren = true, these would be used
"dataOperations": [], //leaving the operations empty means no fertilizer is applied
"CropfieldCharacteristicItemCode": "",
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
"DataCropfieldCharacteristics": [
{
//PO20231029: not different yields from different parts of fields?
"code": "860619", //From codelist CL265. 860619 refers to cropyield in ton/ha
"label": "cropyield",
"value": "48.01"
}
],
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//"DownloadFolder": "Downloads", //"C:\\hugoschrererdir\\kpidir\\", // "Downloads", -> if you just put "Downloads" the program will download to somewhere in ..\FarmMapsApiClient_KB34_MAST\FarmmapsKPI\bin\Debug\netcoreapp3.1\Downloads\
"CropYear": 2022,
//geometryJson = polygon of location of the cropfield, coordinates in LON,LAT (LON: decimal degrees East, LAT: decimal degrees North)
"geometryJson": {
"type": "Polygon",
"coordinates": [
[
[
5.5945257993548765,
52.57080744107003
],
[
5.598645994070678,
52.571540800206236
],
[
5.599381743127071,
52.57012773140724
],
[
5.595408698222548,
52.56968054825188
],
[
5.5945257993548765,
52.57080744107003
]
]
]
}
},
{
"useExistingCropfieldWithChildren": false,
"deleteNewlyCreatedAfterCalc": true,
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
"fieldName": "test_Potato_ZeroFertilizer_Consumption_Clay",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//Note when you run the FarmmapsKPI project, somewhere to your C:\git\FarmMapsApiClient_KB34_MAST\FarmmapsKPI\bin\Debug\netcoreapp3.1\ directory, files named like this are written:
//'Settings_aardappelveld_test_Potato_ZeroFertilizer.json', where 'aardappelveld_test_Potato_ZeroFertilizer.json' is your fieldName (see below)
//1 useExistingCropfieldWithChildren = false -> create new
//2 useExistingCropfieldWithChildren = true && CropfieldItemCode = "" or absent -> read fieldName (see below) -> read all codes from settings json file
//3 useExistingCropfieldWithChildren = true && CropfieldItemCode like "deb48a74c5b54299bb852f17288010e9" in KPIinput -> if you have in your account already an existing cropfield then use that
"CropfieldItemCode": "", // could contain for example this: "abae97f89f3c4ac08953b1b8bea9f076" if this is an exisiting CropfieldItemCode in your account.
//And then if useExistingCropfieldWithChildren = true, this would be used.
"dataCropfield": {
//"area": 4.22, //Leave empty, KPI app will calculate it from geometry
"final": true, //always true
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
"soilCode": "7", //From codelist CL405. Can no longer be omitted
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"soilName": "Clay", //From codelist CL405
"cropTypeCode": "1010101", //From codelist CL263
"cropTypeName": "Potato", //From codelist CL263
Added KPI G1 ammonia emissions (only on test servers) - Ammonia emissions from fertilizers not yet fully functional
2024-07-04 11:35:33 +00:00
"productionPurposeCode": "003", //From codelist CL251. For testing, see case with consumption & starch potato
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"productionPurposeName": "consumption" //From codelist CL251
},
"CropRecordingItemCode": "", // could contain for example this: "314aa1b6480b493ba28a5f55039a01d4" if this is the CropRecordingItemCode of the provided CropfieldItemCode. And then if useExistingCropfieldWithChildren = true, this would be used
"OperationItemCodes": [], // could contain for example this: ["4d1a6f28ea3f414180663baa4b08c60f"] or ["4d1a6f28ea3f414180663baa4b08c60f","21e08386f0454ad79acfebf78649d59b"] if these are the operations of the provided CropRecordingItemCode. And then if useExistingCropfieldWithChildren = true, these would be used
"dataOperations": [], //leaving the operations empty means no fertilizer is applied
"CropfieldCharacteristicItemCode": "",
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
"DataCropfieldCharacteristics": [
{
//PO20231029: not different yields from different parts of fields?
"code": "860619", //From codelist CL265. 860619 refers to cropyield in ton/ha
"label": "cropyield",
"value": "48.01"
}
],
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//"DownloadFolder": "Downloads", //"C:\\hugoschrererdir\\kpidir\\", // "Downloads", -> if you just put "Downloads" the program will download to somewhere in ..\FarmMapsApiClient_KB34_MAST\FarmmapsKPI\bin\Debug\netcoreapp3.1\Downloads\
"CropYear": 2022,
//geometryJson = polygon of location of the cropfield, coordinates in LON,LAT (LON: decimal degrees East, LAT: decimal degrees North)
"geometryJson": {
"type": "Polygon",
"coordinates": [
[
[
5.5945257993548765,
52.57080744107003
],
[
5.598645994070678,
52.571540800206236
],
[
5.599381743127071,
52.57012773140724
],
[
5.595408698222548,
52.56968054825188
],
[
5.5945257993548765,
52.57080744107003
]
]
]
}
},
{
"useExistingCropfieldWithChildren": false,
"deleteNewlyCreatedAfterCalc": true,
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
"fieldName": "test_Potato_ZeroFertilizer_Starch_Sand",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//Note when you run the FarmmapsKPI project, somewhere to your C:\git\FarmMapsApiClient_KB34_MAST\FarmmapsKPI\bin\Debug\netcoreapp3.1\ directory, files named like this are written:
//'Settings_aardappelveld_test_Potato_ZeroFertilizer.json', where 'aardappelveld_test_Potato_ZeroFertilizer.json' is your fieldName (see below)
//1 useExistingCropfieldWithChildren = false -> create new
//2 useExistingCropfieldWithChildren = true && CropfieldItemCode = "" or absent -> read fieldName (see below) -> read all codes from settings json file
//3 useExistingCropfieldWithChildren = true && CropfieldItemCode like "deb48a74c5b54299bb852f17288010e9" in KPIinput -> if you have in your account already an existing cropfield then use that
"CropfieldItemCode": "", // could contain for example this: "abae97f89f3c4ac08953b1b8bea9f076" if this is an exisiting CropfieldItemCode in your account.
//And then if useExistingCropfieldWithChildren = true, this would be used.
"dataCropfield": {
//"area": 4.22, //Leave empty, KPI app will calculate it from geometry
"final": true, //always true
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
"soilCode": "1", //From codelist CL405. Can be no longer be omitted
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"soilName": "Sand",
"cropTypeCode": "1010101", //From codelist CL263
"cropTypeName": "Potato", //From codelist CL263
Added KPI G1 ammonia emissions (only on test servers) - Ammonia emissions from fertilizers not yet fully functional
2024-07-04 11:35:33 +00:00
"productionPurposeCode": "002", //From codelist CL251. For testing, see case with consumption & starch potato
write A1 yield & strawYield to output update definitions update TODO.txt
2024-03-11 13:35:03 +00:00
"productionPurposeName": "starch" //From codelist CL251
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
},
"CropRecordingItemCode": "", // could contain for example this: "314aa1b6480b493ba28a5f55039a01d4" if this is the CropRecordingItemCode of the provided CropfieldItemCode. And then if useExistingCropfieldWithChildren = true, this would be used
"OperationItemCodes": [], // could contain for example this: ["4d1a6f28ea3f414180663baa4b08c60f"] or ["4d1a6f28ea3f414180663baa4b08c60f","21e08386f0454ad79acfebf78649d59b"] if these are the operations of the provided CropRecordingItemCode. And then if useExistingCropfieldWithChildren = true, these would be used
"dataOperations": [], //leaving the operations empty means no fertilizer is applied
"CropfieldCharacteristicItemCode": "",
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
"DataCropfieldCharacteristics": [
{
//PO20231029: not different yields from different parts of fields?
"code": "860619", //From codelist CL265. 860619 refers to cropyield in ton/ha
"label": "cropyield",
"value": "48.01"
}
],
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
//"DownloadFolder": "Downloads", //"C:\\hugoschrererdir\\kpidir\\", // "Downloads", -> if you just put "Downloads" the program will download to somewhere in ..\FarmMapsApiClient_KB34_MAST\FarmmapsKPI\bin\Debug\netcoreapp3.1\Downloads\
"CropYear": 2022,
//geometryJson = polygon of location of the cropfield, coordinates in LON,LAT (LON: decimal degrees East, LAT: decimal degrees North)
"geometryJson": {
"type": "Polygon",
"coordinates": [
[
[
5.5945257993548765,
52.57080744107003
],
[
5.598645994070678,
52.571540800206236
],
[
5.599381743127071,
52.57012773140724
],
[
5.595408698222548,
52.56968054825188
],
[
5.5945257993548765,
52.57080744107003
]
]
]
}
},
{
"useExistingCropfieldWithChildren": false,
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"deleteNewlyCreatedAfterCalc": true,
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
"fieldName": "aardappelveld_test_Potato_cattlemanure144kgnha_plusUrea92kgNha",
in KPIApplication possible to (1) add an operation, e.g. applying fertilizer and (2) add a cropfield characteristic containing cropyield.
2023-10-04 15:21:05 +00:00
"CropfieldItemCode": "",
"dataCropfield": {
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//"area": 4.22, //Leave empty, KPI app will calculate it from geometry
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
"final": true, //always true
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
"soilCode": "5", //From codelist CL405. Can be no longer be omitted
"soilName": "Loam", //From codelist CL405.
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"cropTypeCode": "1010101", //From codelist CL263
"cropTypeName": "Potato", //From codelist CL263
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
//"rootDepthMax": 45, //not needed for KPI calculation, but shown here to know this is a possible property
//"emergenceDate": "2022-05-16T00:00:00", //not needed for KPI calculation, but shown here to know this is a possible property
Added KPI G1 ammonia emissions (only on test servers) - Ammonia emissions from fertilizers not yet fully functional
2024-07-04 11:35:33 +00:00
"productionPurposeCode": "003", //From codelist CL251. Can be omitted if unknown
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"productionPurposeName": "consumption" //From codelist CL251. Can be omitted if unknown
de niet verplichte inputs verwijderd van de input file. Wel wordt er dus de input file gebruikt die in de C:\Users\hoeve065\Documents\hoofdmap_werk\project_KB34MAST nutrienten DB\API04.03\FarmMapsApiClient_KB34_MAST\FarmmapsKPI\bin\Debug\netcoreapp3.1\KPIInput.json staat, en niet bij het KPI programma.
2023-05-02 08:55:24 +00:00
},
in KPIApplication possible to (1) add an operation, e.g. applying fertilizer and (2) add a cropfield characteristic containing cropyield.
2023-10-04 15:21:05 +00:00
"CropRecordingItemCode": "",
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
"OperationItemCodes": [],
"dataOperations": [
{
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//"area": "0.08", //if leave empty then write code to fill in value from geometry (operation applied to whole field). Fill in different value if operation applied to part of the field (e.g. in case of variable rate application, VRA)
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
"contractor": false,
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"designator": "Kunstmest strooien", //refers to codelist CL127 with operation methods
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
"from": "2022-05-23T11:34:00",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"method": "70400", //refers to codelist CL127 with operation methods
"n": "92", //refers to codelist CL022 with fertilizer types & npk contents
"name": "Kunstmest strooien", //refers to codelist CL127 with operation methods
"product": "7360", //refers to codelist CL022 with fertilizer types
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
//"type": "MAN", //indicates wether the fertilization is anorganic (MAN) or organic (MOR)
don't write duplicate KPIOutput items to output csv
2023-10-16 11:55:12 +00:00
"quantity": "200",
Included relevant codelist for dataOperations operationCode and status.
2024-04-11 09:31:56 +00:00
//"status": "3", // refers to codelist CL256. where 3 stand for completed. The status does not matter and is not used in the KPI calculations
"operationCode": "7", // refers to codelist CL018 consisting of main catergorie of operations. Code 7 stands for fertilization
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
"to": "2022-05-23T12:34:00",
"unit": "kg/ha",
"unitCode": "KGMHAR"
},
{
"k": "201.6",
"n": "144",
"p": "60.8",
"to": "2022-04-19T09:19:00",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//"area": "0.08", //if leave empty then write code to fill in value from geometry (operation applied to whole field). Fill in different value if operation applied to part of the field (e.g. in case of variable rate application, VRA)
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
"from": "2022-04-19T08:19:00",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"name": "Injecteren", //refers to codelist CL127 with operation methods
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
"unit": "kg/ha",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"method": "70700", //refers to codelist CL127 with operation methods
Included relevant codelist for dataOperations operationCode and status.
2024-04-11 09:31:56 +00:00
//"status": "3", // refers to codelist CL256. where 3 stand for completed. The status does not matter and is not used in the KPI calculations
"operationCode": "7", // refers to codelist CL018 consisting of main catergorie of operations. Code 7 stands for fertilization
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"product": "2329", //refers to codelist CL022 with fertilizer types
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
//"type": "MAN",//indicates wether the fertilization is anorganic (MAN) or organic (MOR)
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
"quantity": "32000",
"unitCode": "KGMHAR",
"contractor": false,
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"designator": "Injecteren"
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
}
],
in KPIApplication possible to (1) add an operation, e.g. applying fertilizer and (2) add a cropfield characteristic containing cropyield.
2023-10-04 15:21:05 +00:00
"CropfieldCharacteristicItemCode": "",
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
"DataCropfieldCharacteristics": [
{
"code": "860619", //From codelist CL265. 860619 refers to cropyield in ton/ha
"label": "cropyield",
"value": "48.01"
}
],
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
//"DownloadFolder": "Downloads", //"C:\\hugoschrererdir\\kpidir\\", // "Downloads", -> if you just put "Downloads" the program will download to somewhere in ..\FarmMapsApiClient_WURtest\FarmmapsDataDownload\bin\Debug\netcoreapp3.1\Downloads\
in KPIApplication possible to (1) add an operation, e.g. applying fertilizer and (2) add a cropfield characteristic containing cropyield.
2023-10-04 15:21:05 +00:00
"CropYear": 2022,
blah test
2023-03-22 13:48:13 +00:00
"geometryJson": {
"type": "Polygon",
"coordinates": [
[
de niet verplichte inputs verwijderd van de input file. Wel wordt er dus de input file gebruikt die in de C:\Users\hoeve065\Documents\hoofdmap_werk\project_KB34MAST nutrienten DB\API04.03\FarmMapsApiClient_KB34_MAST\FarmmapsKPI\bin\Debug\netcoreapp3.1\KPIInput.json staat, en niet bij het KPI programma.
2023-05-02 08:55:24 +00:00
[
5.5945257993548765,
52.57080744107003
],
[
5.598645994070678,
52.571540800206236
],
[
5.599381743127071,
52.57012773140724
],
[
5.595408698222548,
52.56968054825188
],
[
5.5945257993548765,
52.57080744107003
]
blah test
2023-03-22 13:48:13 +00:00
]
]
farmmapsKPI receives minimum necessary input and writes relevant KPI output
2023-10-13 14:37:50 +00:00
}
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
},
{
"useExistingCropfieldWithChildren": false,
"deleteNewlyCreatedAfterCalc": true,
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
"fieldName": "aardappelveld_test_Potato_Urea92kgNha",
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"CropfieldItemCode": "",
"dataCropfield": {
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//"area": 4.22, //Leave empty, KPI app will calculate it from geometry
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"final": true, //always true
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
"soilCode": "5", //From codelist CL405. Can be no longer be omitted
"soilName": "Loam", //From codelist CL405.
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"cropTypeCode": "1010101", //From codelist CL263
"cropTypeName": "Potato", //From codelist CL263
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
//"rootDepthMax": 45, //not needed for KPI calculation, but shown here to know this is a possible property
//"emergenceDate": "2022-05-16T00:00:00", //not needed for KPI calculation, but shown here to know this is a possible property
Added KPI G1 ammonia emissions (only on test servers) - Ammonia emissions from fertilizers not yet fully functional
2024-07-04 11:35:33 +00:00
"productionPurposeCode": "003", //From codelist CL251. Can be omitted if unknown
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"productionPurposeName": "consumption" //From codelist CL251. Can be omitted if unknown
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
},
"CropRecordingItemCode": "",
"OperationItemCodes": [],
"dataOperations": [
{
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//"area": "0.08", //if leave empty then write code to fill in value from geometry (operation applied to whole field). Fill in different value if operation applied to part of the field (e.g. in case of variable rate application, VRA)
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"contractor": false,
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"designator": "Kunstmest strooien", //refers to codelist CL127 with operation methods
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"from": "2022-05-23T11:34:00",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"method": "70400", //refers to codelist CL127 with operation methods
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"n": "92",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"name": "Kunstmest strooien", //refers to codelist CL127 with operation methods
"product": "7360", //refers to codelist CL022 with fertilizer types
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"quantity": "200",
Included relevant codelist for dataOperations operationCode and status.
2024-04-11 09:31:56 +00:00
//"status": "3", // refers to codelist CL256. where 3 stand for completed. The status does not matter and is not used in the KPI calculations
"operationCode": "7", // refers to codelist CL018 consisting of main catergorie of operations. Code 7 stands for fertilization
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"to": "2022-05-23T12:34:00",
"unit": "kg/ha",
"unitCode": "KGMHAR"
}
],
"CropfieldCharacteristicItemCode": "",
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
"DataCropfieldCharacteristics": [
{
"code": "860619", //From codelist CL265. 860619 refers to cropyield in ton/ha
"label": "cropyield",
"value": "48.01"
}
],
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
//"DownloadFolder": "Downloads", //"C:\\hugoschrererdir\\kpidir\\", // "Downloads", -> if you just put "Downloads" the program will download to somewhere in ..\FarmMapsApiClient_WURtest\FarmmapsDataDownload\bin\Debug\netcoreapp3.1\Downloads\
"CropYear": 2022,
"geometryJson": {
"type": "Polygon",
"coordinates": [
[
[
5.5945257993548765,
52.57080744107003
],
[
5.598645994070678,
52.571540800206236
],
[
5.599381743127071,
52.57012773140724
],
[
5.595408698222548,
52.56968054825188
],
[
5.5945257993548765,
52.57080744107003
]
]
]
}
},
{
"useExistingCropfieldWithChildren": false,
"deleteNewlyCreatedAfterCalc": true,
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
"fieldName": "aardappelveld_test_Potato_Urea92kgNha_ZuidLimburg",
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"CropfieldItemCode": "",
"dataCropfield": {
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//"area": 4.22, //Leave empty, KPI app will calculate it from geometry
"final": true, //always true
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
"soilCode": "5", //From codelist CL405. Can be no longer be omitted
"soilName": "Loam", //From codelist CL405.
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"cropTypeCode": "1010101", //From codelist CL263
"cropTypeName": "Potato", //From codelist CL263
//"rootDepthMax": 45, //not needed for KPI calculation, but shown here to know this is a possible property
//"emergenceDate": "2022-05-16T00:00:00", //not needed for KPI calculation, but shown here to know this is a possible property
Added KPI G1 ammonia emissions (only on test servers) - Ammonia emissions from fertilizers not yet fully functional
2024-07-04 11:35:33 +00:00
"productionPurposeCode": "003", //From codelist CL251. Can be omitted if unknown
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"productionPurposeName": "consumption" //From codelist CL251. Can be omitted if unknown
},
"CropRecordingItemCode": "",
"OperationItemCodes": [],
"dataOperations": [
{
//"area": "0.08", //if leave empty then write code to fill in value from geometry (operation applied to whole field). Fill in different value if operation applied to part of the field (e.g. in case of variable rate application, VRA)
"contractor": false,
"designator": "Kunstmest strooien", //refers to codelist CL127 with operation methods
"from": "2022-05-23T11:34:00",
"method": "70400", //refers to codelist CL127 with operation methods
"n": "92",
"name": "Kunstmest strooien", //refers to codelist CL127 with operation methods
Included relevant codelist for dataOperations operationCode and status.
2024-04-11 09:31:56 +00:00
//"status": "3", // refers to codelist CL256. where 3 stand for completed. The status does not matter and is not used in the KPI calculations
"operationCode": "7", // refers to codelist CL018 consisting of main catergorie of operations. Code 7 stands for fertilization
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"product": "7360", //refers to codelist CL022 with fertilizer types
"quantity": "200",
"to": "2022-05-23T12:34:00",
"unit": "kg/ha",
"unitCode": "KGMHAR"
}
],
"CropfieldCharacteristicItemCode": "",
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
"DataCropfieldCharacteristics": [
{
"code": "860619", //From codelist CL265. 860619 refers to cropyield in ton/ha
"label": "cropyield",
"value": "48.01"
}
],
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//"DownloadFolder": "Downloads", //"C:\\hugoschrererdir\\kpidir\\", // "Downloads", -> if you just put "Downloads" the program will download to somewhere in ..\FarmMapsApiClient_WURtest\FarmmapsDataDownload\bin\Debug\netcoreapp3.1\Downloads\
"CropYear": 2022,
"geometryJson": {
"type": "Polygon",
"coordinates": [
[
[
5.900,
50.800
],
[
5.901,
50.800
],
[
5.901,
50.801
],
[
5.900,
50.801
],
[
5.900,
50.800
]
]
]
}
},
{
"useExistingCropfieldWithChildren": false,
"deleteNewlyCreatedAfterCalc": true,
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
"fieldName": "caseQuoteNnotProvidedInDataOperations",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"CropfieldItemCode": "",
"dataCropfield": {
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
"soilCode": "1", //From codelist CL405. Can be no longer be omitted
"soilName": "Sand",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//"area": 4.22, //Leave empty, KPI app will calculate it from geometry
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"final": true, //always true
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"cropTypeCode": "1010101", //From codelist CL263
"cropTypeName": "Potato", //From codelist CL263
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
//"rootDepthMax": 45, //not needed for KPI calculation, but shown here to know this is a possible property
//"emergenceDate": "2022-05-16T00:00:00", //not needed for KPI calculation, but shown here to know this is a possible property
Added KPI G1 ammonia emissions (only on test servers) - Ammonia emissions from fertilizers not yet fully functional
2024-07-04 11:35:33 +00:00
"productionPurposeCode": "003", //From codelist CL251. Can be omitted if unknown
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"productionPurposeName": "consumption" //From codelist CL251. Can be omitted if unknown
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
},
"CropRecordingItemCode": "",
"OperationItemCodes": [],
"dataOperations": [
{
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//"area": "0.08", //if leave empty then write code to fill in value from geometry (operation applied to whole field). Fill in different value if operation applied to part of the field (e.g. in case of variable rate application, VRA)
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"contractor": false,
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"designator": "Kunstmest strooien", //refers to codelist CL127 with operation methods
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"from": "2022-05-23T11:34:00",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"method": "70400", //refers to codelist CL127 with operation methods
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
//"n": "92",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"name": "Kunstmest strooien", //refers to codelist CL127 with operation methods
Included relevant codelist for dataOperations operationCode and status.
2024-04-11 09:31:56 +00:00
//"status": "3", // refers to codelist CL256. where 3 stand for completed. The status does not matter and is not used in the KPI calculations
"operationCode": "7", // refers to codelist CL018 consisting of main catergorie of operations. Code 7 stands for fertilization
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"product": "7360", //refers to codelist CL022 with fertilizer types
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"quantity": "200",
"to": "2022-05-23T12:34:00",
"unit": "kg/ha",
"unitCode": "KGMHAR"
}
],
"CropfieldCharacteristicItemCode": "",
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
"DataCropfieldCharacteristics": [
{
"code": "860619", //From codelist CL265. 860619 refers to cropyield in ton/ha
"label": "cropyield",
"value": "48.01"
}
],
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
//"DownloadFolder": "Downloads", //"C:\\hugoschrererdir\\kpidir\\", // "Downloads", -> if you just put "Downloads" the program will download to somewhere in ..\FarmMapsApiClient_WURtest\FarmmapsDataDownload\bin\Debug\netcoreapp3.1\Downloads\
"CropYear": 2022,
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"geometryJson": {
"type": "Polygon",
"coordinates": [
[
[
5.5945257993548765,
52.57080744107003
],
[
5.598645994070678,
52.571540800206236
],
[
5.599381743127071,
52.57012773140724
],
[
5.595408698222548,
52.56968054825188
],
[
5.5945257993548765,
52.57080744107003
]
]
]
}
},
{
"useExistingCropfieldWithChildren": false,
"deleteNewlyCreatedAfterCalc": true,
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
"fieldName": "examplePesticide_11767N",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"CropfieldItemCode": "", // could contain for example this: "abae97f89f3c4ac08953b1b8bea9f076" if this is an exisiting CropfieldItemCode in your account.
"dataCropfield": {
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
"soilCode": "1", //From codelist CL405. Can be no longer be omitted
"soilName": "Sand",
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"final": true, //always true
"cropTypeCode": "1010101", //From codelist CL263
"cropTypeName": "Potato", //From codelist CL263
Added KPI G1 ammonia emissions (only on test servers) - Ammonia emissions from fertilizers not yet fully functional
2024-07-04 11:35:33 +00:00
"productionPurposeCode": "003", //From codelist CL251. Can be omitted if unknown
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"productionPurposeName": "consumption" //From codelist CL251. Can be omitted if unknown
},
"CropRecordingItemCode": "", // could contain for example this: "314aa1b6480b493ba28a5f55039a01d4" if this is the CropRecordingItemCode of the provided CropfieldItemCode. And then if useExistingCropfieldWithChildren = true, this would be used
"OperationItemCodes": [], // could contain for example this: ["4d1a6f28ea3f414180663baa4b08c60f"] or ["4d1a6f28ea3f414180663baa4b08c60f","21e08386f0454ad79acfebf78649d59b"] if these are the operations of the provided CropRecordingItemCode. And then if useExistingCropfieldWithChildren = true, these would be used
"dataOperations": [
{
"to": "2022-07-13T17:27:00",
"from": "2022-07-13T16:27:00",
"name": "Volveld spuiten (3/3)", //refers to codelist CL127 with operation methods
"method": "80200", //refers to codelist CL127 with operation methods
Included relevant codelist for dataOperations operationCode and status.
2024-04-11 09:31:56 +00:00
//"status": "3", // refers to codelist CL256. where 3 stand for completed. The status does not matter and is not used in the KPI calculations
"operationCode": "8", // refers to codelist CL018 consisting of main catergorie of operations. Code 8 stands for crop protection
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
"products": [
{
"product": "11767 N", //CTBG code, lookup via CTBG API. Important: with space N",
"quantity": "1.25",
"unitCode": "LTRHAR"
//"designator": "Amistar"
}
]
}
],
"CropfieldCharacteristicItemCode": "",
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
"DataCropfieldCharacteristics": [
{
"code": "860619",
"label": "cropyield",
"value": "48.01"
}
],
More testing & demo's in KPIInput.json: * pesticide * effect of soiltype: yes, different target & threshold for nitrogen (OK) * effect of productionpurpose: none? * effect of location: different nitrogen balance due to different atmospheric deposition (OK) And update TODO.txt
2023-11-01 12:05:49 +00:00
//"DownloadFolder": "Downloads", //"C:\\hugoschrererdir\\kpidir\\", // "Downloads", -> if you just put "Downloads" the program will download to somewhere in ..\FarmMapsApiClient_KB34_MAST\FarmmapsKPI\bin\Debug\netcoreapp3.1\Downloads\
"CropYear": 2022,
//geometryJson = polygon of location of the cropfield, coordinates in LON,LAT (LON: decimal degrees East, LAT: decimal degrees North)
also write totalNapplied to csv file with KPI outputs per cropfield
2023-10-16 13:34:07 +00:00
"geometryJson": {
"type": "Polygon",
"coordinates": [
[
[
5.5945257993548765,
52.57080744107003
],
[
5.598645994070678,
52.571540800206236
],
[
5.599381743127071,
52.57012773140724
],
[
5.595408698222548,
52.56968054825188
],
[
5.5945257993548765,
52.57080744107003
]
]
]
}
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
},
{
"useExistingCropfieldWithChildren": false,
"deleteNewlyCreatedAfterCalc": true,
"fieldName": "doperwt_heleJaar",
"CropfieldItemCode": "",
"dataCropfield": {
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
"soilCode": "1", //From codelist CL405. Can be no longer be omitted
"soilName": "Sand",
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
"final": true, //always true
"cropTypeCode": "1030101", //From codelist CL263
"cropTypeName": "Garden pea" //From codelist CL263
},
"CropRecordingItemCode": "",
"OperationItemCodes": [],
"dataOperations": [],
"CropfieldCharacteristicItemCode": "",
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
"DataCropfieldCharacteristics": [
{
"code": "860619", //From codelist CL265. 860619 refers to cropyield in ton/ha
"label": "cropyield",
"value": "9.58" //CBS: https://www.cbs.nl/nl-nl/cijfers/detail/37738, 2022: 40.4 Mkg / 4216 ha = 40400 / 4216
}
],
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
//"DownloadFolder": "Downloads", //"C:\\hugoschrererdir\\kpidir\\", // "Downloads", -> if you just put "Downloads" the program will download to somewhere in ..\FarmMapsApiClient_WURtest\FarmmapsDataDownload\bin\Debug\netcoreapp3.1\Downloads\
"CropYear": 2022,
//"StartDate": "2022-04-15", //PO20231108: StartDate & EndDate important for legumes, where Nitrogen fixation depends on number of days from start to end. More days = more N fixation
//"EndDate": "2022-07-30", // if StartDate & EndDate left empty then whole year from cropYear
"geometryJson": {
"type": "Polygon",
"coordinates": [
[
[
5.5945257993548765,
52.57080744107003
],
[
5.598645994070678,
52.571540800206236
],
[
5.599381743127071,
52.57012773140724
],
[
5.595408698222548,
52.56968054825188
],
[
5.5945257993548765,
52.57080744107003
]
]
]
}
},
{
"useExistingCropfieldWithChildren": false,
"deleteNewlyCreatedAfterCalc": true,
"fieldName": "doperwt_groeiperiode",
"CropfieldItemCode": "",
"dataCropfield": {
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
"soilCode": "1", //From codelist CL405. Can be no longer be omitted
"soilName": "Sand",
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
"final": true, //always true
"cropTypeCode": "1030101", //From codelist CL263
"cropTypeName": "Garden pea" //From codelist CL263
},
"CropRecordingItemCode": "",
"OperationItemCodes": [],
"dataOperations": [],
"CropfieldCharacteristicItemCode": "",
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
"DataCropfieldCharacteristics": [
{
"code": "860619", //From codelist CL265. 860619 refers to cropyield in ton/ha
"label": "cropyield",
"value": "9.58" //CBS: https://www.cbs.nl/nl-nl/cijfers/detail/37738, 2022: 40.4 Mkg / 4216 ha = 40400 / 4216
}
],
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
//"DownloadFolder": "Downloads", //"C:\\hugoschrererdir\\kpidir\\", // "Downloads", -> if you just put "Downloads" the program will download to somewhere in ..\FarmMapsApiClient_WURtest\FarmmapsDataDownload\bin\Debug\netcoreapp3.1\Downloads\
"CropYear": 2022,
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
"StartDate": "2022-04-15", //PO20231108: StartDate & EndDate important for legumes, where Nitrogen fixation depends on number of days from start to end. More days = more N fixation
"EndDate": "2022-07-30", // if StartDate & EndDate left empty then whole year from cropYear
"geometryJson": {
"type": "Polygon",
"coordinates": [
[
[
5.5945257993548765,
52.57080744107003
],
[
5.598645994070678,
52.571540800206236
],
[
5.599381743127071,
52.57012773140724
],
[
5.595408698222548,
52.56968054825188
],
[
5.5945257993548765,
52.57080744107003
]
]
]
}
},
{
"useExistingCropfieldWithChildren": false,
"deleteNewlyCreatedAfterCalc": true,
"fieldName": "test_WinterWheat_DefaultStrawRemainsInField",
//Note when you run the FarmmapsKPI project, somewhere to your C:\git\FarmMapsApiClient_KB34_MAST\FarmmapsKPI\bin\Debug\netcoreapp3.1\ directory, files named like this are written:
//'Settings_aardappelveld_test_Potato_ZeroFertilizer.json', where 'aardappelveld_test_Potato_ZeroFertilizer.json' is your fieldName (see below)
//1 useExistingCropfieldWithChildren = false -> create new
//2 useExistingCropfieldWithChildren = true && CropfieldItemCode = "" or absent -> read fieldName (see below) -> read all codes from settings json file
//3 useExistingCropfieldWithChildren = true && CropfieldItemCode like "deb48a74c5b54299bb852f17288010e9" in KPIinput -> if you have in your account already an existing cropfield then use that
"CropfieldItemCode": "", // could contain for example this: "abae97f89f3c4ac08953b1b8bea9f076" if this is an exisiting CropfieldItemCode in your account.
//And then if useExistingCropfieldWithChildren = true, this would be used.
"dataCropfield": {
//"area": 4.22, //Leave empty, KPI app will calculate it from geometry
"final": true, //always true
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
"soilCode": "1", //From codelist CL405. Can be no longer be omitted
"soilName": "Sand",
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
"cropTypeCode": "1020101", //From codelist CL263
"cropTypeName": "Winter wheat" //From codelist CL263
},
"CropRecordingItemCode": "", // could contain for example this: "314aa1b6480b493ba28a5f55039a01d4" if this is the CropRecordingItemCode of the provided CropfieldItemCode. And then if useExistingCropfieldWithChildren = true, this would be used
"OperationItemCodes": [], // could contain for example this: ["4d1a6f28ea3f414180663baa4b08c60f"] or ["4d1a6f28ea3f414180663baa4b08c60f","21e08386f0454ad79acfebf78649d59b"] if these are the operations of the provided CropRecordingItemCode. And then if useExistingCropfieldWithChildren = true, these would be used
"dataOperations": [], //leaving the operations empty means no fertilizer is applied
"CropfieldCharacteristicItemCode": "",
"DataCropfieldCharacteristics": [
{
//PO20231029: not different yields from different parts of fields?
"code": "860619", //From codelist CL265. 860619 refers to cropyield in ton/ha
"label": "cropyield",
"value": "10.0"
}
],
//"DownloadFolder": "Downloads", //"C:\\hugoschrererdir\\kpidir\\", // "Downloads", -> if you just put "Downloads" the program will download to somewhere in ..\FarmMapsApiClient_KB34_MAST\FarmmapsKPI\bin\Debug\netcoreapp3.1\Downloads\
"CropYear": 2022,
//geometryJson = polygon of location of the cropfield, coordinates in LON,LAT (LON: decimal degrees East, LAT: decimal degrees North)
"geometryJson": {
"type": "Polygon",
"coordinates": [
[
[
5.5945257993548765,
52.57080744107003
],
[
5.598645994070678,
52.571540800206236
],
[
5.599381743127071,
52.57012773140724
],
[
5.595408698222548,
52.56968054825188
],
[
5.5945257993548765,
52.57080744107003
]
]
]
}
},
{
"useExistingCropfieldWithChildren": false,
"deleteNewlyCreatedAfterCalc": true,
"fieldName": "test_WinterWheat_StrawRemovedFromField",
//Note when you run the FarmmapsKPI project, somewhere to your C:\git\FarmMapsApiClient_KB34_MAST\FarmmapsKPI\bin\Debug\netcoreapp3.1\ directory, files named like this are written:
//'Settings_aardappelveld_test_Potato_ZeroFertilizer.json', where 'aardappelveld_test_Potato_ZeroFertilizer.json' is your fieldName (see below)
//1 useExistingCropfieldWithChildren = false -> create new
//2 useExistingCropfieldWithChildren = true && CropfieldItemCode = "" or absent -> read fieldName (see below) -> read all codes from settings json file
//3 useExistingCropfieldWithChildren = true && CropfieldItemCode like "deb48a74c5b54299bb852f17288010e9" in KPIinput -> if you have in your account already an existing cropfield then use that
"CropfieldItemCode": "", // could contain for example this: "abae97f89f3c4ac08953b1b8bea9f076" if this is an exisiting CropfieldItemCode in your account.
//And then if useExistingCropfieldWithChildren = true, this would be used.
"dataCropfield": {
//"area": 4.22, //Leave empty, KPI app will calculate it from geometry
"final": true, //always true
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
"soilCode": "1", //From codelist CL405. Can be no longer be omitted
"soilName": "Sand",
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
"cropTypeCode": "1020101", //From codelist CL263
"cropTypeName": "Winter wheat" //From codelist CL263
},
"CropRecordingItemCode": "", // could contain for example this: "314aa1b6480b493ba28a5f55039a01d4" if this is the CropRecordingItemCode of the provided CropfieldItemCode. And then if useExistingCropfieldWithChildren = true, this would be used
"OperationItemCodes": [], // could contain for example this: ["4d1a6f28ea3f414180663baa4b08c60f"] or ["4d1a6f28ea3f414180663baa4b08c60f","21e08386f0454ad79acfebf78649d59b"] if these are the operations of the provided CropRecordingItemCode. And then if useExistingCropfieldWithChildren = true, these would be used
"dataOperations": [], //leaving the operations empty means no fertilizer is applied
"CropfieldCharacteristicItemCode": "",
"DataCropfieldCharacteristics": [
{
//PO20231029: not different yields from different parts of fields?
"code": "860619", //From codelist CL265. 860619 refers to cropyield in ton/ha
"label": "cropyield",
"value": "10.0"
},
{
"code": "fm009", //TODO: which codelist?
"label": "strawyield",
added example with greenmanure
2024-05-02 13:57:32 +00:00
"value": "6.8"
DataCropfieldCharacteristics as an array containing cropyield and possibly strawyield. If no strawyield is filled in then straw remains in field.
2024-02-27 14:44:07 +00:00
}
],
"CropYear": 2022,
//geometryJson = polygon of location of the cropfield, coordinates in LON,LAT (LON: decimal degrees East, LAT: decimal degrees North)
two example inputs for testing garden pea (doperwt) for whole year of part of growing period
2023-11-08 12:51:30 +00:00
"geometryJson": {
"type": "Polygon",
"coordinates": [
[
[
5.5945257993548765,
52.57080744107003
],
[
5.598645994070678,
52.571540800206236
],
[
5.599381743127071,
52.57012773140724
],
[
5.595408698222548,
52.56968054825188
],
[
5.5945257993548765,
52.57080744107003
]
]
]
}
added example with greenmanure
2024-05-02 13:57:32 +00:00
},
{
"useExistingCropfieldWithChildren": false,
"deleteNewlyCreatedAfterCalc": true,
"fieldName": "test_WinterWheat_greenmanure",
//Note when you run the FarmmapsKPI project, somewhere to your C:\git\FarmMapsApiClient_KB34_MAST\FarmmapsKPI\bin\Debug\netcoreapp3.1\ directory, files named like this are written:
//'Settings_aardappelveld_test_Potato_ZeroFertilizer.json', where 'aardappelveld_test_Potato_ZeroFertilizer.json' is your fieldName (see below)
//1 useExistingCropfieldWithChildren = false -> create new
//2 useExistingCropfieldWithChildren = true && CropfieldItemCode = "" or absent -> read fieldName (see below) -> read all codes from settings json file
//3 useExistingCropfieldWithChildren = true && CropfieldItemCode like "deb48a74c5b54299bb852f17288010e9" in KPIinput -> if you have in your account already an existing cropfield then use that
"CropfieldItemCode": "", // could contain for example this: "abae97f89f3c4ac08953b1b8bea9f076" if this is an exisiting CropfieldItemCode in your account.
//And then if useExistingCropfieldWithChildren = true, this would be used.
"dataCropfield": {
//"area": 4.22, //Leave empty, KPI app will calculate it from geometry
"final": true, //always true
KPI ammonia emissions is now fully functional (including in the example input file)
2024-08-26 08:35:58 +00:00
"soilCode": "1", //From codelist CL405. Can be no longer be omitted
"soilName": "Sand",
added example with greenmanure
2024-05-02 13:57:32 +00:00
"cropTypeCode": "1020101", //From codelist CL263
"cropTypeName": "Winter wheat" //From codelist CL263
},
"CropRecordingItemCode": "", // could contain for example this: "314aa1b6480b493ba28a5f55039a01d4" if this is the CropRecordingItemCode of the provided CropfieldItemCode. And then if useExistingCropfieldWithChildren = true, this would be used
"OperationItemCodes": [], // could contain for example this: ["4d1a6f28ea3f414180663baa4b08c60f"] or ["4d1a6f28ea3f414180663baa4b08c60f","21e08386f0454ad79acfebf78649d59b"] if these are the operations of the provided CropRecordingItemCode. And then if useExistingCropfieldWithChildren = true, these would be used
"dataOperations": [],
"CropfieldCharacteristicItemCode": "",
"DataCropfieldCharacteristics": [
{
"code": "860619", //From codelist CL265. 860619 refers to cropyield in ton/ha
"label": "cropyield",
"value": "10"
},
{
"code": "501505", //From codelist CL265. 501505 refers to green manure after main crop.
"label": "cropgreenmanureaftercultivation",
changed explanation of optional inputs for green manure.
2024-06-05 12:06:13 +00:00
"value": "1040102", // Code is from CL263. You can put any CL263 crop here. However, the KPI app only works with a limited selection of greenmanure crops, see CL104 for the names.
//"cropHeight": 100, //optional input. Height of greemmanure in cm.
//"plantingDate": "2022-08-01T12:34:00" // optional input. Plantingsdate of greenmanure. required layout "2022-07-23T12:34:00".
added example with greenmanure
2024-05-02 13:57:32 +00:00
}
],
"CropYear": 2022,
"geometryJson": {
"type": "Polygon",
"coordinates": [
[
[
5.5945257993548765,
52.57080744107003
],
[
5.598645994070678,
52.571540800206236
],
[
5.599381743127071,
52.57012773140724
],
[
5.595408698222548,
52.56968054825188
],
[
5.5945257993548765,
52.57080744107003
]
]
]
}
blah test
2023-03-22 13:48:13 +00:00
}
]
Reference in New Issue Copy Permalink