Know what is already in the job.
Northstar AI can inspect project inventory, recent collected points, active selection, CRS/vertical-reference state, surfaces, alignments, GCPs and recent activity before it recommends or performs the next step.
In-house AeroGeo North technology · NorthStar CAD v1.8.28 for Windows & macOS · NorthStar Field for Android & iOS
One project. One agent. Field to deliverable.
NorthStar is the local-first geospatial platform We build for our geospatial, CAD and field operations. It brings together drafting, terrain analysis, editable geometry, GNSS collection and project-aware AI. The same desktop CAD experience runs on Windows and macOS; NorthStar Field carries the project into Android and iOS for collection, visualization and field decisions.

Northstar AI
Northstar AI now operates as a managed geospatial orchestration layer: it can privately plan complex work, inspect live project prerequisites, combine the relevant survey/CAD/GIS/GNSS/terrain/drainage/photogrammetry/LiDAR/QA reasoning, call deterministic Northstar actions one at a time, and verify returned evidence before it reports completion.
Northstar AI can inspect project inventory, recent collected points, active selection, CRS/vertical-reference state, surfaces, alignments, GCPs and recent activity before it recommends or performs the next step.
Suggested actions adapt to live project state so QA, terrain, stakeout, reconciliation and drafting workflows can move forward without requiring the operator to invent the exact prompt wording.
Northstar can identify missing prerequisites, inconsistencies and the next valid operation, then use deterministic tools to advance safe, reversible work.
When the anchor is unambiguous, prompts such as “create a 50 m polyline due north from the point” use survey azimuths and create persistent editable project linework. Northstar does not invent missing survey or design inputs.
For multi-step work, the server can identify intent, prerequisites, missing inputs, likely actions, risk and appropriate verification before choosing the next visible Northstar action.
Compact project workflow memory helps resolve follow-ups such as “continue”, “that one” or “use the same surface”. The live .nscad project, local project state and deterministic tools remain authoritative.
Failed actions and online-provider errors are classified so Northstar can choose a materially different safe recovery route where one exists rather than treating a single failure as the final answer.
Consequential tool results are evaluated against the operator’s goal. Northstar should inspect or otherwise verify project state when needed before saying a surface, import, export or edit is complete.
Operational model: connected AI improvements can be delivered server-side to compatible internal clients, while client-code changes are deployed through the normal desktop/mobile build process.
One Northstar workflow
The current builds preserve a deliberate field-to-office workflow without cloud project storage: export the active .nscad project, transfer it by the operator’s chosen method, and import it on the destination device.

NorthStar CAD v1.8.28 · Windows and macOS
Plan views, labelled survey points, contours, DEM/TIN rendering, 3D terrain views, project-aware AI, editable features and QGIS-oriented deliverables are presented in the same desktop workspace on Windows and macOS.

NorthStar Field · iOS and Android
Mobile collection and drafting sit beside terrain colour palettes, surface contours, configurable layer visibility, GNSS/RTK controls and reference geometry. Local project exchange keeps the desktop and mobile workflows connected.
Real application captures · October 2026
See NorthStar CAD on Windows and macOS, plus NorthStar Field on Android and iOS. These are genuine application screenshots, not interface mockups. The Alpine Massif terrain shown here is a synthetic demonstration dataset, not a surveyed site. Select a screenshot to open the original view.
One consistent workspace across both desktop platforms. Plan view, editable survey geometry, colour-coded terrain, contours, integrated project tools, and immersive 3D review.
Desktop captures reflect the shared Windows/macOS interface. Data on screen is from a synthetic 12 × 10 km Alpine Massif demonstration with a local/assumed coordinate system.
Field CAD, contour-aware collection, terrain/slope interpretation, high/low elevation analysis and project-aware AI.
Screenshots are interface demonstrations. “No Fix” indicators do not represent RTK-fixed positioning.
3D terrain, the Collector, CAD editing, selectable layers, GeoPackage/QGIS exchange controls and elevation analysis.
Public geometry is reference data, not survey control. Imported datasets and physical stakeout require appropriate verification.
Desktop interoperability
The current desktop integrations are designed to move project geometry into established production tools instead of locking it inside Northstar. Third-party applications are separately licensed.
Windows detects the installed Autodesk application and can open the Northstar project handoff. The example shows transferred contour/linework geometry in Civil 3D.
The macOS integration can launch FreeCAD and send project geometry into the CAD workspace for continued inspection and editing.
Northstar can send the active 3D project into Blender as real terrain geometry; the example shows the triangulated DTM and contour objects in the scene.
Integration scope: the Civil 3D image demonstrates project geometry handoff; it does not by itself claim creation of a native Autodesk Civil 3D TIN Surface definition. Northstar also exposes supported workflows for Agisoft Metashape Professional, WebODM Local and Litchi where installed/configured.
Current platform focus
Current desktop installations share the same CAD workflow. The mobile experiences are designed for field collection, drafting, GNSS/RTK setup, map interpretation and local project transfer. The images above show the actual user interfaces; capabilities depend on each device, project CRS and available data.
Reference-map data, synthetic demonstration terrain and approximate DEM-derived elevations are not replacements for survey-grade coordinates or professional verification.
October 2026 / Platform development
Recent NorthStar development prioritizes the daily realities of collecting data, checking geometry, moving through a project and delivering usable files. Updates described here are build-level capabilities, not independent certifications of third-party integration or flight compliance.
Point/Line modes, code-first capture, stakeout, line continuation and object review streamline collection while keeping survey context visible.
Point, line, surface and project geometry views, independent layer visibility controls, improved mobile +Z-up presentation and more responsive terrain display.
NorthStar AI 3.1 development adds context-sensitive command handling, project-state awareness, diagnostic evidence and task-completion checks. Operators still validate results.
Desktop CAD/DXF exchange, project autosave and last-project continuity, plus mission-planning export aligned to the 46-column Litchi CSV schema. Missions require preflight validation in Litchi.
Build references: Windows CAD 1.8.28 · macOS CAD 1.8.28 · Android Field (pictured current build) · iOS Field (pictured v1.8.96). Platform capabilities vary. See NorthStar CAD Interiors for our developing architectural workflow.
Integrated capabilities
Use natural language for project review, drafting, survey, terrain, drainage, QA and workflow guidance while deterministic Northstar tools perform the actual engineering operations.
Create and edit survey/CAD geometry with object snap, surface Z snap, inverse, bearing-distance, grade/slope, alignments, station/offset, profiles and sections. Convert selected or visible 3D line vertices directly into persistent, surface-ready survey points without re-observing the geometry.
Build or retrieve DEM, DTM, DSM and TIN surfaces through the current Northstar Data workflow, generate contours, inspect terrain in 3D and run drainage, low-point, watershed and crossing analysis. Address/location lookup can establish an online terrain request before any project geometry exists, and explicit width × height requests are preserved. Vertex-to-point conversion continues to preserve stored XYZ for controlled TIN creation.
Stake points, lines and alignments with target arrows, nearest-point geometry logic, chainage, signed L/R offset and vertical cut/fill guidance where a valid target elevation exists. A persistent pole/antenna-height control corrects observed Z before ground-elevation display, capture and vertical guidance.
Manage GCP/check-point data, export WebODM GCP Editor CSV and generate gcp_list.txt automatically when image observations are tagged.
Process point-cloud data into terrain surfaces and derive editable 3D linework, terrain features and candidate infrastructure geometry for operator review.
Search 11,090 horizontal/compound CRS entries and 1,107 vertical references while canonical authority identifiers are passed to the geospatial engine.
Use the Portal for sign-in, entitlement, managed Northstar AI, God's Eye and authenticated DEM/vector/data services. Project files remain local and move separately through .nscad import/export.
Plan grid missions and hand off to compatible workflows with AutoCAD/Civil 3D, FreeCAD, Blender, WebODM Local, Agisoft Metashape Professional and Litchi where separately installed/configured.
AeroGeo North maintains internal operator material alongside Windows CAD v1.8.28, macOS CAD v1.8.28, Android Field (pictured current build) and iOS Field (pictured v1.8.96). That keeps field-to-office procedures, QA checks, project transfer and connected services consistent as the tools evolve.
Local field-to-finish workflow
Set CRS/vertical reference, import source data, prepare control, design geometry, surfaces and field targets.
Export the desktop project as .nscad and import it into Northstar Field. Project transfer is local and operator-controlled; the Northstar Portal is not used for project storage or transport.
Use phone GNSS or compatible RTK/NMEA, collect coded observations and stake points, lines or alignments in the portrait Collector with side-mounted graphical guidance.
Export the updated .nscad project from Field and import it on desktop, preserving the project data without cloud project storage or sync.
Review the project with adaptive Northstar AI, use suggested actions or Reconcile / Optimize to resolve workflow gaps, then continue terrain/CAD/WebODM processing and generate the required deliverables.
Responsible AI + engineering use
Northstar AI is a planning and orchestration layer over deterministic Northstar tools. Operators remain responsible for control, CRS/vertical datum, units, design criteria, residuals, quantities and project-specific QA.
Current engineering boundary
Northstar is a CAD, survey, visualization and processing-assistance platform. It does not replace legal survey, professional engineering design, statutory approvals or project-specific standards. Automatically generated geometry and AI recommendations require review before field, design, construction or safety use.
Compact server-side workflow memory is used for conversational continuity such as the current goal and recent action outcome. It does not replace project files, Portal, field notes, control records or professional QA, and it must not be treated as authoritative geometry or survey evidence.
In-house AeroGeo North technology
Northstar CAD + Field is not sold, licensed or distributed as a standalone software product. AeroGeo North develops and uses it internally because a purpose-built workflow supports control over project data, faster field-to-office handoff, consistent terrain/geometry handling and the ability to improve the tools around real project requirements.
FAQ
No. Northstar CAD + Field is an internal AeroGeo North platform. Clients engage AeroGeo North for geospatial, survey-support, drone, mapping, terrain and related project services; the software supports how We perform that work.
Our projects often move between terrain data, CAD geometry, field observations, stakeout, 3D review and final deliverables. Keeping those stages inside a project-aware workflow reduces unnecessary conversions and lets us adapt the tools to the actual work rather than force the work around a generic application.
No. It accelerates processing, visualization, organization and checking. Control, datum, design criteria, quantities, regulated work and final project decisions remain subject to the appropriate professional and project-specific review.
Northstar's current operator workflow is provider-neutral. Northstar Data acts as the authenticated federated broker and chooses/falls back among supported online/open-data sources in the backend. Legacy provider-specific action names remain compatibility-only for older workflows; new operator actions do not require choosing or troubleshooting a specific provider. Online/open-data geometry remains reference data, not survey control.
Yes. CAD v1.8.28 supports direct Project-panel deletion for individual items and complete collections, including survey points, linework, flight datasets, GCPs, alignments, surfaces, raster layers and photogrammetry jobs. Supported deletions participate in the global Undo history.
Northstar AI may infer ordinary workflow intent, but it does not invent missing survey coordinates, elevations, design grades, CRS/datum values, stations, tolerances or other engineering inputs. When the necessary context is unambiguous, it can invoke deterministic tools to create persistent editable geometry; high-impact actions still require operator confirmation.
Northstar automatically falls back to the local project-aware Agent so the core CAD/field workflow is not dependent on cloud reasoning. Network-dependent features such as Portal, NTRIP and cloud AI still require connectivity when used.
Yes. Northstar Northstar Field can stake points, linework and alignments on the current mobile clients. Line/alignment stakeout targets the nearest position on the geometry and reports chainage and signed left/right offset. In Collector, horizontal guidance is kept to the left side and CUT/FILL/ON GRADE guidance to the right when a valid target elevation exists, leaving the centre available for project geometry.
CAD v1.8.28 and Android Field (pictured current build) explicitly show that the session has expired and that the operator must sign in again. Portal actions remain disabled until authentication succeeds, rather than leaving an apparently active but unusable login state.
Yes, when the anchor and required inputs are unambiguous. For example, with a single project point, “create a 50 m polyline due north from the point” resolves North as survey azimuth 0° and creates ordinary editable project linework. If several candidate points exist, Northstar requires a specific point or an unambiguous selected/latest reference.
No. Field uses an offline survey canvas. Imported/project geometry, selected features, stakeout, live terrain and field observations remain available without web-map tiles.
Yes. CAD v1.8.28 and the current Field clients can convert selected or visible line/polyline vertices into persistent survey points while preserving stored XYZ. Shared XY vertices are deduplicated at 0.001 m, existing surveyed elevations are protected on conflicts, and the generated points can be used immediately to build a TIN surface.
The current Field clients include a persistent POLE control. The active height is subtracted from observed GNSS antenna/device elevation before ground Z is displayed or recorded and before cut/fill or vertical stakeout guidance is calculated. A 0.000 m setting leaves the observation unchanged.
Yes. AeroGeo North maintains a current iOS Field build for internal use, including local projects, Draw, Collector, GNSS/RTK selection, stakeout and Project 3D.
No. Users remain responsible for professional judgment, control, project standards, design criteria, QA and required approvals.
Yes. CAD v1.8.28 and the current Field clients can use address/location context to establish an online terrain request even when the project has no seed point, feature or GCP. Requested terrain dimensions are preserved. Online terrain is reference data and does not become surveyed control merely because it is loaded into the project.
That is intentional in the current Field workflow. A DEM/surface is an elevation target rather than a single horizontal navigation target, so the surface stakeout HUD reports vertical CUT, FILL, ON GRADE or NO TARGET Z only. Horizontal guidance remains available for normal point, line and alignment stakeout.
Not necessarily. The managed Northstar AI and data-broker intelligence can be upgraded server-side while preserving the existing client API. Compatible installed CAD/Field builds receive those improvements when connected. A new desktop installer, Android APK or Apple app update is still required when the corresponding client application itself changes.