A software name, coordinate example or equipment recommendation does not prove that a particular archaeology project can create a usable GIS record. Start with the research question, site custodian, exact kit, capture method, coordinate record, data boundary and current project route.
What should an archaeology team establish before creating a drone-to-GIS record in Italy?
Decision layer
Evidence to retain
What it can establish
What it cannot establish
Research and site question
Specific archaeology question, site custodian, area, required output, people and ground method
What the project needs to learn
That a software name guarantees a useful result
Exact system
Aircraft, camera or payload, controller, batteries, accessories, version, serial and condition record
What equipment is proposed
A universal accuracy or output claim
Capture method
Documented coverage approach, reference or coordinate record, exclusions and review owner
What is intended to be collected
That a tutorial selects the correct method for every site
Data boundary
Access, storage, metadata, review, publication and handover expectations
Who handles project material
That a research project has no data or permission boundary
Current project route
Current custodian and responsible-route response for actual site, people and activity
What needs confirmation
That an older GIS process grants site access
Why should the archaeology question come before the software choice?
A GIS handover is only as useful as the question, method and record behind it. Documenting the actual site, system, capture boundary and data plan lets a team evaluate tools honestly without inventing an accuracy result or assuming a generic tutorial authorises site work.
How should a team turn the review into an action plan?
Action
What to retain
1. Define the archaeology question
Record site custodian, area, required output, people and ground method.
2. Document the exact kit
Keep aircraft, camera or payload, controller, batteries, accessories, version, serial and condition evidence.
3. Write the capture record
Describe intended coverage, reference or coordinate record, exclusions and review owner.
4. Set data boundaries
Keep access, storage, metadata, publication and handover expectations visible.
5. Use the current project route
Confirm the actual site, people and activity before capture.
