Grok is not your GIS. It is a briefing partner for what you already collected. If you ask it to “analyze this site” and accept the numbers, you will brief a superintendent with fiction.
Why this matters
A thumbnail of an orthomosaic looks like enough. The model will give you 14.2 acres, a flow direction, a stand count, and a vegetation clearance. It may even sound like last year’s lab. None of those quantities live in a screenshot unless you already measured them and typed them in.
This lesson is how you talk to Grok about imagery and GIS the way a careful shop talks: what the picture is, when it was flown or captured, what it is for, what you already know, and what you will measure in the software — not in the chat.
Russell Tech work lives in that interval: rover to map, flight to mosaic, mosaic to a decision. The model can help you ask better questions. It cannot certify a drainage plan, a spray buffer, or a conductor clearance.
Teach
You cannot drop the archive. A 4 GB GeoTIFF, an image service, a file geodatabase — those stay in the GIS. What you bring to grok.com is a briefing set:
- A PNG or JPEG export (overview plus one inset if needed).
- A screenshot with the scale bar, north arrow, and legend visible. If the export has no scale bar, say so.
- A tiny table: what you already measured (with units and the tool).
- The question the map must help answer.
Tell Grok what it is looking at. Models guess. Guessing a crop, a CRS, or a county is how you get a mixed-up entity.
This is [ortho / DEM hillshade / rover points / NAIP / phone photo / scanned plat].
Captured: [date or "unknown"]
GSD or scale: [if known, else "unknown"]
CRS / stored as: [if known, else "unknown — do not assume"]
Purpose of this map: [the decision]
Already measured (only these numbers exist):
- ...
Do not invent acres, lengths, elevations, coordinates, counts, or clearances.
Ask for the right class of output
- Hypotheses a crew could test.
- A checklist of what to measure next in QGIS, ArcGIS, or the collector.
- Questions the image cannot answer (night drainage, a tree height from a single nadir still, a legal boundary from a pretty fence).
- A critique of your read.
Do not ask for “the acreage,” “the NDVI,” “how many plants,” or “is this safe to spray.” NDVI is a calculation on bands you did not attach. A stand count from a thumbnail is entertainment. A spray decision is a label plus a licensed applicator, not a chat.
HOLD / WRONG / UNVERIFIED still apply, now to spatial claims.
- HOLD. You measured it, or it is printed on the export (a labeled 400 ft grid you can see).
- WRONG. You checked. The slough is on the south line, not the north. The “pivot” is a center-pivot neighbor, not your field.
- UNVERIFIED. Any number Grok typed that you did not measure. Treat as unused.
A fourth miss shows up in this work: false precision. “14.22 acres.” “127 stems per acre.” “18.5 ft clearance.” The decimal is a costume. Strike it.
Search, carefully. Live web is useful for finding the NRCS Web Soil Survey page, a FEMA service, an FAA chart tool, a county GIS, a product manual. Then you open that page. Grok quoting a 2019 blog about a buffer is not the label. Do not let Search “confirm” an acreage. Search cannot see your mosaic.
Ag, vegetation, development — same rails
- After a storm: ask what drainage questions the wet soil pattern suggests. Measure flow path in the GIS.
- Pivot vs corner: ask what to flag for a field visit. Do not accept a crop ID from true color alone if you did not scout.
- Utility corridor: from a photo, you may list what a patrol should look at. You may not issue a clearance.
- New subdivision at a prairie edge: access, lot orientation, the slough, the county road. No invented lot count if the lots are not labeled.
Phone photo as a field note. The Grok app can look at a structure, a washout, a canopy edge. Same rule: describe what you want named, forbid measurements it cannot make, and write UNVERIFIED on anything you did not pace off or shoot with the instrument. A pretty identification of “maybe leafy spurge” is a scout lead, not a management decision.
Imagine is for a simple diagram after the facts exist: a labeled pad sketch, a crew position, a north-up lot layout from numbers you typed. It is not a substitute for the ortho.
Worked example
A superintendent wants a Monday read on a new rural development. The GIS lead exports a north-up PNG of the Thursday ortho: prairie west, slough on the south line, county road east, gravel spur, no lots staked in the imagery. Scale bar is in the export. No area has been calculated.
Bad prompt: “Analyze this drone map and give me acres and drainage.”
Useful prompt (Think, file attached):
Intent: A 12-line analysis brief I can say out loud. Hypotheses and next measurements only.
Context: Thursday ortho, rural development, Hughes-area prairie edge (do not invent the PLSS). PNG attached. Scale bar visible. We have not calculated area. We have not run a DEM product yet. Purpose: Monday call with the superintendent about drainage and access, not a grading plan.
Constraints:
- Do not invent acres, lot counts, elevations, coordinates, or a flood zone.
- Every claim gets HOLD / UNVERIFIED / NEED-TO-MEASURE.
- If you cannot see it on the PNG, write NOT IN IMAGE.
- End with three measurements I should do in the GIS before the call.
- Session-quality: quote what you think you see (slough, road, pad) in plain language I can refute.
Grok called the slough a “detention pond,” invented 14.2 acres, and said the site was “outside the floodplain.” The lead marked pond as UNVERIFIED (it is a slough; hydrology unknown), 14.2 as WRONG (not measured), floodplain as WRONG (not in image; would be a FEMA/county check). The three GIS next steps were usable: digitize the wet signature and the road edge, extract a rough flow path once the DEM exists, and do not report area until the AOI is agreed.
The lead kept the questions, threw out the numbers, and did not forward the first draft.
Your turn
Open grok.com. New thread named imagery brief — [site]. Attach an export, a screenshot, or a phone photo you have the right to use. If you cannot attach, describe the image in 8–10 honest lines and say NO FILE. Do not use a random internet pretty picture as if it were your job.
Exercise d-geo-l02-e1
| Field | Value |
|---|
| whereToDo | grok.com |
| time | 24 min |
Copy-ready prompts
Message 1 — attach the file first if you have it:
I am in Grok Mastery (Russell Tech), Pathway D, Geospatial, lesson 2 — imagery and GIS analysis prompts.
Mode: Think if you can.
This is [type].
Captured: [date or unknown]
GSD or scale: [or unknown]
CRS: [or unknown — do not assume]
Purpose: [the decision]
Already measured (only these numbers exist):
- [or "none"]
I have attached: [file / NO FILE + 8–10 line description]
Write an Analysis Brief:
- What you think you see (plain language, no quantities)
- Three hypotheses a crew could test
- Three things this image cannot answer
- Next measurements in a GIS or on the ground (tool + what to record)
- Claim table: every quantity or official status you are tempted to state, labeled HOLD / WRONG / UNVERIFIED / NOT IN IMAGE
- Session stamp: today's date and "Analysis brief written by Grok in this thread."
Do not invent acres, lengths, elevations, coordinates, stand counts, NDVI, flood zones, or clearances.
If I gave no number, you have no number.
Message 2 — after you read the brief:
I am marking your claim table. [List any line that is WRONG or that you treated as HOLD without a measurement.]
Reprint only the claim table with my marks, then a 4-line "What I must measure before I brief anyone."
Do not defend a number I did not give.
Artifact to paste
- The Analysis Brief (including the claim table and stamp).
- The reprinted claim table with your marks.
- One sentence from you: the single number or status you almost forwarded, and why you will not.
Rubric
- Pass: Brief is Grok-authored and stamped. No unmarked invented quantity. Claim table exists. You marked at least one UNVERIFIED or you honestly had a HOLD you measured. Image is yours to use. Next measurements name a tool.
- Fail: “Looks like 20 acres.” No file and no description. A flood-zone or clearance verdict. You wrote the brief without Grok. NDVI from a JPEG. A random stock aerial.
Common failure
The common failure is asking the model to be the instrument. Area, count, height, NDVI, a legal line. You skipped the GIS because the sentence was ready. The sentence is the cheapest part of the job.
The twin failure is mystery screenshots. No date, no scale, no purpose, cropped legend. Grok will still talk. You will not know what year the water was high.
What’s next
You can brief an image without shipping fiction. Next: ops documentation — the packet that makes Monday’s map trustworthy: who, when, CRS, raw vs product, and what the map does not answer.
