SINAG AgriSense, Crop Trend Analysis, and Climate historical analytics run on Google Earth Engine (GEE). Each SINAG account must link its own service-account JSON key. Until that is done, those tools stay locked.
You need a JSON key from Google Cloud first. If you do not have one yet, follow Configure Google Earth Engine API and service key, then come back here to upload it.
What this unlocks
- SINAG AgriSense (draw or upload a field, vegetation indices, image analysis)
- Crop Trend Analysis (NDVI time series)
- Climate Info historical ERA5 analytics
Upload the key in SINAG
-
Open Account Management
Sign in, then go to Account Management.
-
Open GEE Setup
In the left menu, choose GEE Setup. You should see Google Earth Engine (GEE) Configuration and an upload box marked required for AgriSense.
-
Select the JSON file
Click the dashed upload area and choose the service-account
.jsonfile you downloaded from Google Cloud (JSON only, max 500 KB). The file name appears when the selection is valid. -
Submit Key
Click Submit Key. SINAG stores the key, the service-account email, and the Google Cloud project ID on your user profile.
-
Confirm it is linked
After a successful save you should see Active Service Account (masked email) and Active Project ID with a Linked badge. Refresh Platform tools. AgriSense and Crop Trend Analysis should no longer show the lock / GEE Key Missing dialog.
Treat the JSON file like a password. Do not email it, commit it to git, or paste it into chat. Anyone with the file can use your Earth Engine quota.
Replace a key later
If Google Cloud rotated the key, or you received a new JSON from your office, upload the new file in the same GEE Setup panel. SINAG overwrites the stored credentials.
If tools stay locked
- Confirm GEE Setup shows Linked, then hard-refresh the tools menu.
- The file must be a Google service-account JSON (it includes
type,project_id,private_key, andclient_email). - If analysis still errors, the Cloud project may be missing the Earth Engine API, the service-account role, or GEE registration — see the API and service-key guide.