Service scope and implementation plan
direction numberD48
Demand scenario8 items
main inputSatellite/airborne TIR L5; TIR+multispectral+GIS; TIR+meteorology+multispectral; day and night TIR+multispectral
Typical routeT14、T08、T13、T20
The project scope is determined based on samples, equipment, working conditions and written indicators; general modules, special models and multi-sensor integration are configured according to the evaluation results.
Application scenarios and development content
IR377Surface temperature LST retrieval and heat island analysis
- Minimum input and technical route
- Satellite/airborne TIR L5;T14
- target output
- LST, heat island intensity and mass layer
- Implementation
- Requires atmosphere/emissivity model
- critical acceptance
- Compare with ground station/high-resolution images, RMSE
IR378Urban thermal risk, green space and impervious surface associations
- Minimum input and technical route
- TIR+multispectral+GIS;T14
- target output
- Thermal risk zoning and related statistics
- Implementation
- Requires spatio-temporal statistics
- critical acceptance
- Consistent time/space scale, explanation of confounding factors
IR379Evapotranspiration and farmland water consumption estimation
- Minimum input and technical route
- TIR+meteorology+multispectral;T14
- target output
- ET estimates and plot statistics
- Implementation
- energy balance model
- critical acceptance
- Contrast with eddy covariance/water balance
IR380Soil moisture and drought thermal inertia proxies
- Minimum input and technical route
- Day and night TIR+multispectral;T14
- target output
- Thermal inertia/humidity proxies and changes
- Implementation
- Need soil true value
- critical acceptance
- Versus probe/sampling control, soil type stratification
IR381Remote sensing of fires, lava and industrial heat sources
- Minimum input and technical route
- MWIR/TIR；T08+T14
- target output
- Thermal anomalies, radiant power proxies and changes
- Implementation
- Requires saturation/atmospheric correction
- critical acceptance
- Versus event/ground station
IR382Multispectral analysis of snow, ice, frozen soil and melt boundaries
- Minimum input and technical route
- NIR/SWIR/TIR；T14
- target output
- Snow and ice index, surface temperature and change area
- Implementation
- Requires atmospheric/terrain correction
- critical acceptance
- Compare with site/high score images
IR383Mine area, tailings and surface disturbance change detection
- Minimum input and technical route
- SWIR/TIR multi-phase;T13+T14
- target output
- Material/Temperature Anomalies and Changes Layer
- Implementation
- ground truth required
- critical acceptance
- Registration error, change area IoU
IR384Multi-source satellite, drone and ground thermal image scale fusion
- Minimum input and technical route
- L4/L5；T14+T20
- target output
- Fusion layers, scale transformations and uncertainty
- Implementation
- Requires spatiotemporal model
- critical acceptance
- Cross-scale error, temporal matching, and quality layers
Implementation and delivery methods
- Project input confirmationCheck camera, spectral band, bit depth, SDK, environmental conditions, sample and acceptance true value.
- Sample verificationVerify key processing links, applicable conditions and abnormal working conditions, and determine the development scope and acceptance methods.
- Algorithm development and integrationImplement data parsing, algorithms, quality gating, interfaces and target platform deployment.
- Test acceptance and handoverRetest according to the agreed test set and target platform, and hand over the deliverables, test results and applicable conditions.
- Requirements and technical solutions, input and output and interface field definitions
- Algorithm library, model or SDK/API; delivery form is confirmed in the project plan
- Sample program, parameter configuration, error status and calling instructions
- Test set version, indicator definition, stratification results and failed sample records
- Target platform adaptation, resource usage and running delay records
- Version, dependencies, license, reproduction steps and applicable conditions description
Acceptance design
Each scenario establishes independent test cases according to "key acceptance". When sharing models across scenarios, results are reported separately for each scenario, distance, load, environment, and target size, supplemented by overall statistics.
When high-risk alarms or controls are involved, the algorithm output is used for review or linkage judgment; safety functions, regulatory responsibilities, and automatic disposal require separate design and acceptance.
Frequently Asked Questions for Enterprise Customers
Can I purchase directly based on one of the scenes?
Can be evaluated first as a separate work package. The formal scope should describe the device, data, target objects, environment, interfaces, delivery form, and acceptance thresholds.
Can it be started when there are no abnormal samples?
The data interface, normal baseline, acquisition plan and simulation/controlled test design can be completed first; the abnormal detection rate and fault classification effect can be evaluated after obtaining sufficient abnormal true values.
Can the algorithm directly trigger alarms or equipment actions?
Duration, deduplication, quality gating, manual review, communication failure and safety interlocking need to be designed based on business risks. High-risk actions should be activated after completion of independent safety mechanisms and on-site acceptance.