| | |
|---|
| | | ## Engineering Rules |
|---|
| | | |
|---|
| | | - Prefer existing project patterns and `geoai-py` APIs over new abstractions. |
|---|
| | | - Do not start, control, or use a browser to inspect local-console visual output. For UI, map, image, or 3D-model visual acceptance, state the exact view or interaction that needs checking and ask the user to provide screenshots; use non-browser build, HTTP, artifact, and automated tests independently. |
|---|
| | | - Preserve geospatial coordinates only when the input has a valid CRS and transform. Ordinary JPEG results remain pixel coordinates. |
|---|
| | | - Report false positives, misses, runtime, and unsupported classes honestly. Do not hide limitations by lowering thresholds. |
|---|
| | | - Do not batch-run large datasets until a representative validation indicates that the approach is suitable. |
|---|
