Register a COG and the in-process server exposes it through an ArcGIS REST ImageServer surface — exportImage, identify, computeHistograms, getSamples — with server-side raster math for spectral indices, sensor-aware rendering templates, AI object detection that returns FeatureSets, and mensuration with stated confidence. No pre-computation, no cloud, no per-analysis wait.
The ImageServer facade is compatible with the ArcGIS JavaScript SDK and existing GIS infrastructure — the exploitation endpoints analysts expect, served from one workstation.
exportImage — rendered windows with a renderingRule raster function, from true color to burn severity.identify — pixel values at a point, straight off the source raster.computeHistograms & getSamples — statistics and sample extraction for quantitative work.# NDVI, computed server-side at request time GET .../ImageServer/exportImage ?renderingRule={"rasterFunction":"NDVI", "rasterFunctionArguments": {"NIRBandId":8,"RedBandId":4}} # exploitation surface GET .../ImageServer/identify GET .../ImageServer/computeHistograms GET .../ImageServer/getSamples POST .../ImageServer/detectObjects → FeatureSet GET .../ImageServer/dlModels
Server-side raster functions and a curated template catalog turn multispectral COGs into analysis views in one call.
NDVI, NDWI, NBR and more — including EVI, SAVI, MNDWI, NDBI, and NDSI — computed via server-side raster math on any registered COG.
Pre-configured visualizations spanning natural color, color infrared, vegetation health, water and moisture, burn severity (dNBR), urban, geology, snow/ice, and thermal views.
Sensor-aware defaults with automatic detection — Sentinel-2 (13 bands), Landsat 8/9 (11 bands with thermal), Landsat 7, and generic multispectral sources are recognized on registration.
createComposite builds mosaic, time-series, and band-composite virtual rasters as lightweight XML pointing at the source COGs — no data duplication, lazy reads.
Stack temporal scenes into a time-series service and compare periods — including burn-severity mapping with dNBR between pre- and post-event imagery.
createDynamic watches a directory with a filename pattern and auto-refreshes the service as new scenes arrive.
The YOLO-E detection pipeline is wired directly into the ImageServer: render a COG window to PNG, run zero-shot detection, geo-reference the pixel boxes back to polygon rings, and return a spec-conformant ArcGIS FeatureSet any Maps SDK client can draw.
POST .../ImageServer/detectObjects with bbox, size, threshold, and classLabels; GET works too.f=json returns the FeatureSet; f=image returns an annotated PNG.GET .../ImageServer/dlModels lists available detection models.{available:false, detections:[]} and the app keeps working.// COG window → PNG → detect → geo-reference POST .../ImageServer/detectObjects { "bbox": [...], "size": [...], "threshold": 0.5, "classLabels": [...] } → FeatureSet (f=json · polygon rings + class + confidence) → PNG (f=image · annotated) // sidecar down? honest degrade: { "available": false, "detections": [] }
Exploitation ends in a product — annotated graphics with measurements the reader can trust.
Indices, detections, annotations, and mensuration on the same map as your radar tracks and blue force — served from one desktop, consumable by any ArcGIS REST client.