C# client using FarmMaps API to connect to a database for crop nutrient parameters
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Abel Hoeven, van 641e09f833 Merge branch 'master' of https://git.akkerweb.nl/abel/FarmMapsApiClient_KB34_MAST 1 month ago
FarmMapsBlight Updated receiving of root items 1 year ago
FarmmapsApi KPI items ophalen voor een cropfield werkt nu. wel dus een bestaand cropfield ingeven bij de settings in de BIN. Alle KPIs worden opgehaald na een minuut wachten. 2 months ago
FarmmapsBulkSatDownload Updated receiving of root items 1 year ago
FarmmapsCleanUp new project FarmmapsCleanUp to clean up cropfielditems and satellitetaskcodes used only once 2 years ago
FarmmapsDataDownload test 2 months ago
FarmmapsHaulmkilling Updated receiving of root items 1 year ago
FarmmapsHerbicide Updated receiving of root items 1 year ago
FarmmapsKPI Merge branch 'master' of https://git.akkerweb.nl/abel/FarmMapsApiClient_KB34_MAST 1 month ago
FarmmapsNbs Updated receiving of root items 1 year ago
FarmmapsPoten Updated receiving of root items 1 year ago
FarmmapsZonering Updated receiving of root items 1 year ago
Secrets added download of all crop recordings of 1 field - using a manual croprecording itemcode 1 year ago
.gitignore Projects FarmmapsBulkSatDownload and FarmmapsDataDownload fully updated and tested 2 years ago
FarmmapsApiSamples.sln blah test 2 months ago
README.MD Update 'README.MD' 1 year ago

README.MD

NOT PRODUCTION READY CODE, JUST AN EXAMPLE

Put your clientId and clientSecret or your Farmmaps-account data (username and password) in a newly created appsettings.secrets.json file inside the root of the Secrets project.

appsettings.secrets.json

{
  //API credential sign-in
  "ClientId": "<clientId>",
  "ClientSecret": "<clientSecret>"
}

Or when using a Farmmaps account to sing-in

appsettings.secrets.json

{
 //Sign-in using farmmaps account
 "Username": "",
 "Password": ""
}
  • Isn't 100% complete.
  • Needs proper testing of all public api methods.
  • Needs documentation of all public api methods.