This is taking longer than expected.

Try againBrowse the library
AI Blocks

All AI specialists

Hire an AI drone mapping specialist

Describe the site, the products you need and the accuracy you must reach. You get a capture and processing plan for drone photogrammetry.

What you give

  • The site: area size, terrain and any boundary file
  • The products you need, such as an orthomosaic, height model, point cloud or 3D mesh, and what each is for
  • Ground control points you already have, and how they are measured (optional)

What you get

  • A flight plan with height, overlap, speed and camera settings
  • A ground control and checkpoint plan
  • Go and no-go checks for weather and light
  • A processing order with the quality check after each stage

An example

You are planning a first drone mapping flight over a site and want a settings plan.

You ask: “Describe the site, the products you need and the accuracy you must reach. Use the material I attach and ask for anything essential that is missing.”

You get back:

  • Brief and assumptions. The site, products, accuracy and equipment as understood, with assumptions and MISSING items.
  • Flight plan. Height, pixel size, overlap, speed, camera settings and light notes.
  • Ground control. How many control points and checkpoints, where they go and how to measure them.

An example, not your task.

Hire this specialist

It is free and needs no account. Download the pack, give it to your AI and tell it the job. Your AI asks for anything it is missing, then does the work and checks it.

Download the specialist

Related specialists

Skills and workflows for this job: Research a topic properly

Details

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

  • A flight plan with height, overlap, speed and camera settings
  • A ground control and checkpoint plan
  • Go and no-go checks for weather and light
  • A processing order with the quality check after each stage
  • A product table with pixel size and file format for each product
  • An accuracy report plan and open questions

How it does the job well

  • Never give an expected accuracy as a fact. You cannot see the site, the photos or the results.
  • Software menus, settings and versions change. Mark specific settings "check your software's help".
  • Do not confirm that a flight is legal. Airspace and permits are the user's check.
  • Give drafts and proposals. Get the user's go-ahead before anything that sends, publishes, spends money or changes a live system.
  • Agree the question and the decision it supports before analysing.
  • Check the data first: date range, grain, missing values, duplicates and definitions.
  • Compare like with like: same period length, definitions and segments.

Mistakes it avoids

  • Reporting a change without checking whether tracking or definitions changed.
  • Treating correlation as cause.
  • Averages that hide important segments or outliers.

What a good result looks like

An example, not your task: You are planning a first drone mapping flight over a site and want a settings plan.

  • Brief and assumptions. The site, products, accuracy and equipment as understood, with assumptions and MISSING items.
  • Flight plan. Height, pixel size, overlap, speed, camera settings and light notes.
  • Ground control. How many control points and checkpoints, where they go and how to measure them.
  • On-site checks. Weather and image checks, each with a go or no-go rule.
  • Processing steps. Numbered stages from image culling to height model, with a quality check after each.
  • Products. Each product with pixel size, file format and use.

How the work is checked

  • Numbers reconcile to the source totals, and the reconciliation is shown.
  • Every chart and number states its source, period and definition.
  • Limits and next checks are listed.
  • States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

  • Collect the brief. It confirms the site, products, accuracy, drone and software. It asks once for anything missing, then marks it MISSING.
  • Plan the flight. It sets height, overlap, speed, camera settings and the best light, and adjusts for hills.
  • Plan ground control. It plans where to place control points and checkpoints, and when RTK or PPK is enough.
  • Plan the checks on the day. It lists weather limits and image checks that tell you to re-fly before leaving site.
  • Plan the processing. It orders image culling, alignment, dense cloud, mesh, orthomosaic, height model and ground control.
  • Plan accuracy and handoff. It plans the error report, visual checks and how to load products into your GIS tool.

How the role works

  1. Checks your task, context and available tools.
  2. Picks the methods needed and prepares a work plan.
  3. Carries out supported tasks, with each method's limits and review gates.
  4. Checks the real deliverables and corrects supported faults.
  5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id gis-drone-reality-mapping only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/gis-drone-reality-mapping/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

  • The site: area size, terrain and any boundary file
  • The products you need, such as an orthomosaic, height model, point cloud or 3D mesh, and what each is for
  • The accuracy you must reach, in centimeters, and whether it is survey grade
  • Your drone and camera or sensor, such as RGB, multispectral, thermal or LiDAR, and whether it has RTK or PPK
  • The processing software you have, such as Pix4D, Agisoft Metashape or WebODM (optional)
  • Ground control points you already have, and how they are measured (optional)

Helpful context (optional)

  • The quality report from your processing software.
  • A map of the site boundary and where control points can go.

Tools and access

  • Claude, ChatGPT or Gemini: The plan works from a pasted profile and your brief.
  • Claude Code: It can read your project folder and quality reports, so fixes fit your real results.

Functions and deliverables

  • Drone mapping specialist: Plan a drone mapping job: flight settings, ground control points, processing steps and accuracy checks for orthomosaics, terrain models and 3D meshes.
    • A flight plan with height, overlap, speed and camera settings
    • A ground control and checkpoint plan
    • Go and no-go checks for weather and light
    • A processing order with the quality check after each stage
    • A product table with pixel size and file format for each product
    • An accuracy report plan and open questions
    Source: Michael Sitarzewski and Agency Agents contributors.
  • Metric definition writer: Share a metric, calculation and business use. Get a YAML definition, validation results and questions for the data owner.
    • A filled metric, dimension or entity YAML
    • A validation report
    • dbt-ready field names
    • Notes on edge cases
    Source: Nimrod Fisher.

Tasks you can use it for

  • You are planning a first drone mapping flight over a site and want a settings plan.
  • You need an orthomosaic or height model for construction progress, a mine, a farm or a flood study.
  • Your last map had holes, blur or position errors, and you need to find out why.
  • You must choose between GCPs and RTK, or between Pix4D, Metashape and WebODM.

Limits to check before starting

  • You need a legal boundary or certified survey: hire a licensed surveyor.
  • You need to analyze satellite images: use the Geospatial machine learning planner.
  • You only need an aerial photo placed on a map: use the GIS analyst.
  • You already have LiDAR and need a 3D scene: use the 3D map scene developer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

  • Add the pack to your AI as a skill. Or open a new chat and paste SKILL.md, then references/source-agent.md.
  • Write your brief. Give the site size, the products and the accuracy you need, and your drone and camera. Add your software if you have it.
  • Say 'Plan this mapping job. Do not guess my accuracy target.' Your AI asks once for what is missing.
  • Read the ground control plan first. Change it if you cannot place points at the spread it asks for.
  • Check the airspace rules and any permit for your site yourself. The AI cannot confirm them.
  • After the flight, send back image problems or error figures from your software, and ask what to change.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/gis-drone-reality-mapping for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.