Altitude information guide
An altitude display or setting is not an operating entitlement. A responsible plan starts with the exact aircraft, the intended location, the task, people and site constraints, then checks the applicable local requirements for that setting.
Treat altitude information as one part of a site plan
An aircraft setting, a manufacturer display, GEO location guidance, property access, and local operating requirements address different questions. Keeping those questions separate gives a team a more credible way to decide whether an aerial perspective is appropriate.
| Information layer | What to understand | Responsible next step |
|---|---|---|
| Exact aircraft and controller | The system being considered for a planned assignment. | Record the actual kit before relying on general model information. |
| Operating location | Terrain, structures, people, access, and the proposed route or area. | Make the site context explicit before any flight decision. |
| Applicable requirements | The current rules and permissions relevant to the planned location and task. | Use the appropriate authority information for the specific plan. |
| Grounded alternative | A camera, pole, manual inspection, or another method that can deliver the task. | Keep an alternative available when the aerial role is not suitable. |
Market version is not GEO
GEO is location-based guidance. It is separate from a product's market-version context, and neither replaces the requirements that apply to an intended operating area.
Use a clear stop point
Stop the planning process when the site, task, people, access, operating requirements, or fallback cannot be described clearly. A model name or a controller setting should not pressure a team into a task that is better completed from the ground or after more site preparation.
Consumer and enterprise context
Consumer systems
For Mini, Air, and Mavic systems, use the normal aircraft, controller, condition, and location record. A consumer system does not need an invented enterprise project review.
Commercial / enterprise
For enterprise systems, include the complete aircraft, controller, payload where relevant, and project-management context in the site decision.
Related Reboot Hub paths
Separate market-version evidence from location guidance.China DJI trust hub
Understand the evidence categories.Drone Wiki
Research the model family.Model comparison
Compare drone roles and families.
FAQ
Does an altitude display decide what is permitted at a location?
No. A display is only one part of the equipment context. The location, task, people, property access, and applicable operating requirements must be considered separately.
What should be recorded before an altitude-sensitive assignment?
Record the exact aircraft and controller, the planned location and task, site constraints, the applicable authority information, and a grounded alternative.
Is DJI GEO the same as local operating requirements?
No. GEO is location-based guidance. Applicable operating requirements are separate and should be checked for the intended task and location.
Do standard consumer systems require enterprise configuration review?
No. Consumer systems use the normal equipment and site record. Enterprise systems can need a broader project-configuration record.
Why keep a grounded alternative in the plan?
It prevents an aerial method from becoming the only answer when the site, task, or operating context is not suitable.
Keep exploring
Further reading
From The Reboot Hub Chronicle
From Drone Guides
