Conversation
|
|
||
| ### ❌ Options to Avoid | ||
|
|
||
| **FastAPI Admin**: Requires Tortoise ORM (you use SQLAlchemy) |
| **Starlette Admin Limitations:** | ||
| - No built-in mapping UI | ||
| - Can display WKT/coordinates in forms, but not interactive maps |
There was a problem hiding this comment.
This is a significant limitation that is not just a nice to have. Allowing a user/admin to visualize the location on a map is an essential quality control and validation component.
There was a problem hiding this comment.
was this supported in MS Access?
| --- | ||
|
|
||
| #### ✅ **Keep OcotilloUI If:** | ||
| - Staff **cannot tolerate** deferred features (maps, forms) |
| ├─ YES → No Admin UI (use pgAdmin/psql temporarily) | ||
| └─ NO → Continue | ||
|
|
||
| Can staff tolerate deferred features (maps, forms) for 2-4 months? |
There was a problem hiding this comment.
@jirhiker they've already been waiting 5+ months, correct? I think this is a yes?
There was a problem hiding this comment.
No, not really. We are nearing the end of our runway on this. There are multiple other significant priorities that need to be tackled this year. Geospatial visualization and subsetting are fundamental needs. If data is not displayable on a map, users will require the data to be exported to a GIS-compatible format so that they can view it in ArcGIS.
That said, high-quality forms have been deferred in favor of data entry by the Data Services Team.
There was a problem hiding this comment.
👀 #333. This will allow Ocotillo to support ocotilloui, gqis, even ArcGIS.
2 participants
DO NOT MERGE
for discussion purposes