Buffer → intersect → difference
Create a route corridor, intersect it with threat and restriction layers, subtract cleared areas, then save the remaining review geometry for the mission plan.
2D topology + 3D scene operations
Run the analysis offline.
Return an answer.
Use local DuckDB Spatial operations to filter, measure and compare mission features without a network round trip. Carry the results into terrain-aware 3D scenes, extruded geometry, streamed 3D Tiles, locally placed models or AR/VR delivery profiles.
TopologyBuffer · intersect · union · difference
ProximityDWithin · nearest · distance
RelationshipsContains · crosses · overlaps · touches
3D scene pathExtrude · place · transform · stream LOD
BufferCreate a corridor or standoff area around points, lines or polygons.
IntersectReturn the geometry common to an operational layer and an area of interest.
UnionMerge multiple coverage areas or selected features into one result.
DifferenceSubtract exclusions, no-go areas or prior coverage from a geometry.
Within distanceTest which assets fall inside a supplied proximity threshold.
NearestRank candidate resources by distance and apply an optional search limit.
DistanceMeasure separation between supplied geometries in the selected spatial reference.
Area + lengthCalculate footprint, coverage, perimeter or route length.
CentroidCreate a representative point for labels, staging or summary markers.
SimplifyReduce vertex count while preserving topology for display or tiling.
Contains + touchesTest containment or boundary adjacency between features.
Crosses + overlapsEvaluate route crossings and partial shared coverage.
Repository-backed mapping: buffer, intersect, union, difference, DWithin, nearest, distance, centroid, area, length, simplify, contains, crosses, overlaps and touches are present in the active FeatureServer spatial-analysis handler. Coordinate transformation and geometry export are also present in the local data layer.
Inputs, outputs and context
More than a list of function names.
Each operation needs a defined geometry, coordinate system, unit model and output contract.
| Analysis family | Representative input | Returned result | Operational use |
|---|---|---|---|
| Geometry construction | Point/line/polygon geometry, distance and units; or two input geometries | Buffer, intersection, union or difference geometry with operation metadata | Route corridors, threat rings, combined coverage, exclusion zones and change polygons |
| Proximity | Search geometry, maximum distance, result limit and candidate layer | Matching features plus distance or nearest-order context | Closest medical point, assets within a hazard radius, nearby infrastructure or staging candidates |
| Measurement | Geometry and a verified projected/geographic spatial reference | Distance, area, length or centroid values and geometry | Route distance, site acreage, perimeter, coverage summaries and label placement |
| Topological relationship | Subject geometry and comparison geometry or target layer | Boolean relationship and/or matching feature set | Boundary violations, route crossings, overlapping jurisdictions and adjacent parcels |
| Preparation | Geometry, tolerance, source CRS and target CRS | Simplified or transformed geometry suitable for the next stage | Reduce draw cost, normalize incoming feeds and prepare dynamic vector tiles |
Representative handler calls
Analysis can be invoked as part of the local service contract.
The application can call these handlers in process. A validated embedded transport can also expose equivalent loopback routes to a local client.
BUFFER A PLANNED ROUTE
GET /arcgis/rest/services/Mission/FeatureServer/4/buffer
?geometry={route-geometry-json}
&geometryType=esriGeometryPolyline
&distance=500
&units=meters
&outSR=3857The working CRS must use an appropriate linear unit. Buffering unprojected longitude/latitude coordinates without a defined geodesic policy can produce misleading distances.
FIND NEAREST RESOURCES
GET /arcgis/rest/services/Mission/FeatureServer/7/nearest
?geometry={incident-point-json}
&geometryType=esriGeometryPoint
&maxDistance=10000
&limit=10
&outSR=4326Attribute filters, status rules and travel-network cost are separate concerns. This nearest operation is geometric distance unless a routing/network adapter is selected.
Offline mission workflow
Chain operations without sending the data to a cloud service.
A local GeoPackage, DuckDB layer or approved mission dataset can stay on the device throughout the analysis sequence.
01Select + validateLayer, geometry type, fields, CRS and data quality
02FilterExtent, attributes, time, team or mission status
03AnalyzeTopology, proximity, measurement or transformation
04PersistLocal result layer, GeoJSON export or mission state
05Visualize + share2D, terrain-aware 3D, TAK context, briefing or XR
Filter → DWithin → nearest
Filter locally available resources by type and status, find those inside the response radius, rank the candidates by geometric distance, and inspect them in the scene.
Union → difference → area
Union current collection footprints, subtract the previous coverage, measure the new area and export the result for after-action review.
3D and 2.5D scene operations
Connect analytic geometry to the three-dimensional operating picture.
GeoVerse3D combines spatial analysis with content and scene operations. It is important to distinguish 2D topology from true volumetric 3D analysis.
| 3D operation | Current pathway | What it enables | Boundary |
|---|---|---|---|
| Extrude a footprint Repository backed | Apply a height to valid 2D GeoJSON geometry and carry extrusion metadata into the scene workflow. | Building massing, zones, columns and height-coded operational volumes. | This is 2.5D extrusion, not a general solid-geometry Boolean engine. |
| Load + place 3D models Repository backed | Import supported model content, then store position, rotation, scale and geographic placement metadata. | Vehicles, infrastructure, equipment, landmarks and scenario assets. | Model-format fidelity, materials, units, georeferencing and device GPU cost are validated per asset set. |
| GLB to B3DM Repository backed | Validate GLB bytes, wrap them in B3DM, cache conversions and process files or directories. | Prepare local model content for a selected 3D Tiles content pipeline. | Conversion does not create a complete spatial tileset hierarchy by itself. |
| Stream 3D Tiles + I3S SDK pathway | Load tileset or scene-layer metadata and stream spatial LOD through the selected Unity SDK. | City-scale buildings, integrated meshes and large 3D environments. | Direct SLPK packages, offline tilesets, authentication and cache policy require the delivery-specific adapter. |
| Advanced terrain analysis Delivery extension | Integrate elevation sampling plus selected algorithms for line-of-sight, viewshed, terrain profile or 3D distance. | Observation planning, communications studies and terrain-aware movement analysis. | These are not claimed as active baseline functions until the selected terrain engine and accuracy tests are integrated. |
Accuracy is part of the function.
Every analysis profile records the source CRS, target CRS, linear and angular units, vertical datum where relevant, geometry validity rules, tolerance, simplification policy and expected result checks. A function name without those controls is not an operational capability.
Bring the questions
and expected answers.
We’ll run representative offline analysis cases against the actual data, compare results with a trusted GIS reference, and validate the 2D/3D presentation on the target device.
Plan a spatial evaluation