Limitations
Current Limitations (v0.1.x)¶
This page summarizes user-facing limitations in the current implementation.
1) Spatial input CRS¶
BBoxandPointBuffercurrently requirecrs="EPSG:4326".- Other CRS inputs are not accepted at the API boundary.
2) Temporal behavior for on-the-fly models¶
- Most on-the-fly adapters treat
TemporalSpec.range(start, end)as a window filter and build one composite image (medianby default). - This is not an automatic single-scene selection by acquisition date.
3) Temporal constraints are model-specific¶
gsecurrently requiresTemporalSpec.year(...).copernicuscurrently supports only year2021.- Some precomputed models may ignore finer temporal granularity.
4) Grid output is not always georeferenced raster space¶
- For ViT-like models,
OutputSpec.grid()is often a token/patch grid(D, H, W). - Treat it as model-internal spatial structure, not as guaranteed geo-aligned pixel coordinates.
5) Optional dependency surface is large¶
- Different models/providers require extra packages (
earthengine-api,torch,rshf,torchgeo, etc.). - Missing optional dependencies will fail at runtime for the corresponding model path.
6) Known edge case: tessera tile boundary mosaic¶
- Near some UTM-zone boundaries, fetched tiles may have different CRS/resolution and strict mosaic can fail.
- If this occurs, try shifting ROI slightly or using a smaller ROI/window.