{ "product": "HelloGeo Suite", "reviewedAt": "2026-10-18", "capabilities": [ { "id": "rgb-mapping", "title": "RGB photogrammetry", "description": "Turn high-resolution aerial RGB imagery into orthophotos, point clouds, elevation models and textured 3D deliverables.", "requirements": [ "Processing needs a configured compatible processing node.", "High resolution is input- and hardware-dependent; no universal resolution or image-count promise was verified." ] }, { "id": "video-frames", "title": "Video-frame input", "description": "Use video-input controls and extracted RGB frame datasets for mapping workflows, with limits and resolution set through the connected engine.", "requirements": [ "video-limit and video-resolution are real option-group mappings.", "Available options are read from the selected processing node.", "No verified high-FPS throughput, live-stream mapping, per-frame real-time guarantee or universal codec list." ] }, { "id": "oblique", "title": "Oblique-image reconstruction", "description": "Plan nadir and oblique RGB capture for facade coverage and 3D reconstruction, with suitable overlap, camera calibration and processing settings.", "requirements": [ "General image reconstruction and camera/rolling-shutter options are implemented.", "No dedicated multi-head oblique OEM ingestion/calibration adapter was verified." ] }, { "id": "multispectral", "title": "Multispectral analysis", "description": "Map calibrated spectral bands, align imagery and derive vegetation, water, soil and red-edge products from the bands your sensor actually supplies.", "requirements": [ "Camera band order and radiometric/reflectance calibration matter.", "Primary-band, radiometric-calibration and band-alignment controls depend on engine support.", "Brand name alone does not guarantee camera firmware, raw-format or calibration compatibility." ] }, { "id": "hyperspectral", "title": "Hyperspectral datasets", "description": "Review georeferenced hyperspectral exports, wavelengths and calibration before selecting compatible bands and downstream spectral analysis.", "requirements": [ "Generic band-mapped raster entry points are present.", "No native ENVI cube reader, full spectral-cube workflow, atmospheric correction, spectral unmixing or endmember library was verified.", "Do not label every hyperspectral OEM or raw cube natively supported." ] }, { "id": "thermal", "title": "Thermal / LWIR analysis", "description": "Review thermal rasters and temperature products alongside RGB and multispectral context when suitable radiometric data and calibration are supplied.", "requirements": [ "Single-band L/LWIR and RGB+thermal filter layouts plus Celsius/Centikelvin formula entries exist.", "A colourized thermal JPEG is not a validated temperature raster.", "Raw radiometric OEM decoding, emissivity correction and absolute temperature accuracy were not independently qualified." ] }, { "id": "lidar", "title": "LiDAR and point clouds", "description": "Import LAS/LAZ, classify ground, generate DSM/DTM surfaces and inspect scalable EPT point clouds.", "requirements": [ "Requires PDAL/Entwine and configured workers.", "Ground classification uses terrain-specific CSF profiles; only the urban preset has a documented real-data comparison.", "No universal point-count capacity or sub-canopy recovery from photogrammetric clouds." ] }, { "id": "satellite", "title": "Satellite scene processing", "description": "Upload georeferenced satellite rasters or Sentinel-2 SAFE/JP2 bands, confirm band mapping and create analysis-ready map products.", "requirements": [ "Sentinel-2 SAFE is explicitly implemented; generic GeoTIFF/JP2 remains data-format dependent.", "No satellite-tasking, imagery-subscription, provider-download API or native SAR-processing adapter verified.", "Landsat/Planet/other providers require suitable georeferenced exports, bands and licence permissions." ] }, { "id": "spectral-catalogue", "title": "42 band-aware formula entries", "description": "Explore 35 spectral indices, five individual-band products and two temperature conversions; eligible outputs follow the input bands.", "requirements": [ "42 is the catalogue size, not the output count for every sensor.", "True NDVI needs NIR; MNDWI/NDBI/NDMI need SWIR1; NBR needs SWIR2.", "No blue band in a sensor's spectral product means blue-dependent spectral products need a separately suitable source." ] }, { "id": "change", "title": "Change and flood detection", "description": "Compare scenes across dates using visual change, elevation or index differences, land-cover transitions and flood/recession mapping.", "requirements": [ "Comparable georeferencing, datum, dates and appropriate bands are required.", "Some transition/formula comparisons are API/model capabilities rather than confirmed prominent UI options." ] }, { "id": "rgb-landcover", "title": "RGB land-cover screening", "description": "Screen RGB orthophotos for vegetation, water and bare-ground patterns, then review and export the classified layers.", "requirements": [ "This is rule-based visible-spectrum classification, not a trained AI model or a replacement for multispectral NDVI." ] }, { "id": "satellite-landcover", "title": "Satellite land-cover mapping", "description": "Produce vegetation, water, built-up, bare-ground and wetland layers with polygons and statistics; use supplied Sentinel-2 SCL for cloud/shadow exclusion.", "requirements": [ "Wetland is a proximity-based indicator; arid/bare ground can be confused with built-up areas.", "No general validated accuracy percentage." ] }, { "id": "ai-classification", "title": "AI-assisted point-cloud classification", "description": "Combine geometric point-cloud rules with optional imagery-model assistance for road, building and forest classification.", "requirements": [ "Requires a configured compatible ONNX model and usable RGB point data.", "This is not a verified universal AI denoising or noise-reduction service.", "Semantic classification and ML settings can be disabled; configured deployment status was not tested." ] }, { "id": "filter-sample", "title": "Point-cloud filtering and sampling", "description": "Tune point-cloud filtering, sampling and geometric checks through the processing engine's supported options.", "requirements": [ "pc-filter, pc-sample and pc-skip-geometric mappings are real UI code.", "Do not imply all filters are AI-driven; active support depends on the chosen engine." ] }, { "id": "volumes", "title": "Cut, fill and volume calculations", "description": "Measure cut, fill, net and total earthworks volume with six selectable base-surface methods, and save the measurement to your project.", "requirements": [ "Base methods: triangulated, fitted plane, average, custom elevation, highest and lowest.", "Quality depends on source DEM, units, datum and polygon/base selection.", "This does not validate automated stockpile quantities or certify a survey." ] }, { "id": "measurements", "title": "Saved 2D / 3D measurements", "description": "Save and revisit distance, area, height and volume measurements with project geometry and source context.", "requirements": [ "Correct projection and source geometry are required." ] }, { "id": "footprints", "title": "Building footprints", "description": "Extract and regularize building footprints from classified point clouds for reviewed urban mapping deliverables.", "requirements": [ "Semantic building classification is required.", "LOD2 solids and Unity-facing glTF export are explicitly future work in this module." ] }, { "id": "terrain-mining", "title": "Terrain and mining analytics", "description": "Explore slope, hillshade, benches, ramps and faces, with reviewed earthworks measurements.", "requirements": [ "Automatic stockpile volumes are explicitly not validated on a real mine in source comments; present them as provisional if exposed." ] }, { "id": "aoi", "title": "Areas of interest", "description": "Draw or import named project boundaries using GeoJSON, zipped Shapefile, GeoPackage or KML.", "requirements": [ "Inputs must carry valid geometry and a suitable coordinate reference." ] }, { "id": "datum", "title": "Coordinate and height references", "description": "Work with project CRS and vertical-datum handling, including EGM96 and optional EGM2008 geoid grids.", "requirements": [ "EGM2008 needs its configured grid; conversions do not establish survey accuracy." ] }, { "id": "delivery", "title": "GIS delivery and collaboration", "description": "Share permitted projects and deliver rasters, classification vectors, CSV statistics, measurements and 3D/point-cloud assets.", "requirements": [ "Source-level integration reviewed; no live export or permissions exercise in this audit." ] }, { "id": "retention", "title": "Source-data retention and archiving", "description": "Choose source-image retention, cloud archiving and restoration to manage local storage while preserving the selected project workflow.", "requirements": [ "Permanent image deletion/compaction is a separate destructive retention choice and prevents reprocessing from those images.", "Do not market data deletion as AI reduction." ] }, { "id": "large-data", "title": "Tiled and bounded processing", "description": "Use tiled raster/point-cloud processing, dedicated worker queues and supported split/merge settings for larger projects.", "requirements": [ "Deployment sizing, configured limits and real-data qualification remain necessary; do not claim unlimited scale." ] } ], "compatibility": [ { "family": "RGB & oblique", "examples": "DJI · Autel", "requiredData": "Supported image datasets; JPEG or prepared image exports with camera and capture metadata. DNG decoding depends on the processing engine.", "scope": "Image workflow" }, { "family": "Multispectral", "examples": "MicaSense RedEdge-P / Altum-PT · Parrot Sequoia / Sequoia+ · Sentera", "requiredData": "Calibrated TIFF / GeoTIFF, aligned bands, irradiance or panel context. Indices require the actual measured bands; no SWIR is inferred.", "scope": "Prepared-data compatibility" }, { "family": "Thermal / IR", "examples": "MicaSense Altum-PT · qualified thermal payloads", "requiredData": "Radiometric thermal input, sensor response, emissivity and reflected-temperature context. A coloured preview does not establish a temperature measurement.", "scope": "Data & engine qualification" }, { "family": "Hyperspectral", "examples": "Specim · Headwall · Resonon", "requiredData": "Manufacturer-prepared ENVI cubes or mapped georeferenced bands, wavelength and calibration metadata. Review conversion and processing adapters for each dataset.", "scope": "Integration assessment" }, { "family": "LiDAR", "examples": "RIEGL · Livox · Hesai", "requiredData": "Georeferenced LAS / LAZ handoff. Raw packets and PCD require suitable trajectory correction, conversion and calibration before import.", "scope": "Prepared point-cloud compatibility" }, { "family": "Sentinel-2", "examples": "Copernicus / ESA Sentinel-2", "requiredData": "SAFE ZIP, named JP2 bands or georeferenced GeoTIFF. Retain band mapping, acquisition date and supplied SCL masks.", "scope": "Documented ingestion route" }, { "family": "Landsat", "examples": "USGS / NASA Landsat", "requiredData": "Prepared GeoTIFF bands with the correct scale/offset, masks, georeferencing and acquisition metadata.", "scope": "Prepared-data compatibility" }, { "family": "Commercial satellites", "examples": "Planet · Airbus · Maxar", "requiredData": "Licensed, prepared georeferenced imagery and spectral metadata. Product level, available bands and licence determine the analysis; imagery ordering remains separate.", "scope": "Dataset qualification" } ], "guides": [ { "title": "Multisensor Mapping & OEM Compatibility | HelloGeo Suite", "url": "https://hellogeo.world/resources/multisensor-data-compatibility/" }, { "title": "Satellite Data Processing & Sentinel-2 | HelloGeo Suite", "url": "https://hellogeo.world/resources/satellite-data-processing/" }, { "title": "LiDAR, Point-Cloud Filtering & Volumes | HelloGeo Suite", "url": "https://hellogeo.world/resources/lidar-volume-and-ai-workflows/" }, { "title": "RGB, Oblique & Video Mapping | HelloGeo Suite", "url": "https://hellogeo.world/resources/rgb-oblique-video-mapping/" } ], "scope": "Product workflow reference. Availability depends on data, calibration, configured processing services and dataset acceptance." }