Skip to content

Feat/Public AI Predictions#496

Open
jeafreezy wants to merge 27 commits intohotosm:developfrom
Spatialnode:feat/ai-predictions
Open

Feat/Public AI Predictions#496
jeafreezy wants to merge 27 commits intohotosm:developfrom
Spatialnode:feat/ai-predictions

Conversation

@jeafreezy
Copy link
Copy Markdown
Collaborator

@jeafreezy jeafreezy commented Mar 23, 2026

What Does This PR Do ?

This PR introduces a public-facing Public AI Predictions page and completes the publish/retract workflow for offline predictions.

On the public side, it adds a new ‎/ai-predictions route, exposes it under the “Explore Datasets → AI Predictions” navbar menu, and wires it through ‎NuqsAdapter so search, ordering, layout, pagination and map state are all synced via query params. The page supports grid, list and data-table layouts, plus a map view that renders clustered centroids with MapLibre; clicking a map point selects the corresponding prediction.

Screenshots

Screen.Recording.2026-03-23.at.08.52.32.mov

How To Test

https://fair-dev-spatialnode.vercel.app/

@jeafreezy jeafreezy marked this pull request as ready for review March 24, 2026 16:29
@kshitijrajsharma
Copy link
Copy Markdown
Member

Minor fixes :

Datasets Dropdown to :

Training datasets
AI Predictions

Remove this Blue bar on hover as it doesn't match with with the color theme :

image

lets make the grid to be clickable similar design with datasets page and models page

Upon click we can show the details , download result options or all info that is available from the API

image

@jeafreezy
Copy link
Copy Markdown
Collaborator Author

Thanks for the review. All changes have been made @kshitijrajsharma.

WRT to this:

lets make the grid to be clickable similar design with datasets page and models page

We all agreed to the current design before implementation. Having the card clickable will require a design for the information panel and we can do that. Let's double check with @omranlm for the way forward.

@kshitijrajsharma kshitijrajsharma requested review from omranlm and removed request for kshitijrajsharma March 27, 2026 08:05
@omranlm
Copy link
Copy Markdown
Contributor

omranlm commented Apr 1, 2026

when I view MS project from public AI prediction and try to see MS results .. it is downloading the mbtiles ..
while from Prediction request under my profile, it is showing MS prediction on a popup .. which is the proper approach
@jeafreezy

@omranlm
Copy link
Copy Markdown
Contributor

omranlm commented Apr 1, 2026

From user perspective

When we select specific model ID 150 for example and then we run prediction request using a selected model in the menu like YOLO base model, when we submit the prediction request we need to save the base model used in this request ... and it should show the used model in the AI predictions public page

Documented in details publicly here https://drive.google.com/file/d/1c1oiZfKQsYm8PoTsdMicIwugFboZGfwS/view?usp=sharing
CC: @kshitijrajsharma , @jeafreezy

@omranlm
Copy link
Copy Markdown
Contributor

omranlm commented Apr 1, 2026

Thanks for the review. All changes have been made @kshitijrajsharma.

WRT to this:

lets make the grid to be clickable similar design with datasets page and models page

We all agreed to the current design before implementation. Having the card clickable will require a design for the information panel and we can do that. Let's double check with @omranlm for the way forward.

sure, no worries for this public release we can keep it as cards only ... then when we support multiple features, we would need to design a page to show different type of features and more meta data coming with the used model. such as solap panels tags, other rooftops .. seagrass ... etc.

Bug fix: Mapswipe result is downloading mbtiles instead of opening results modal
@jeafreezy
Copy link
Copy Markdown
Collaborator Author

when I view MS project from public AI prediction and try to see MS results .. it is downloading the mbtiles .. while from Prediction request under my profile, it is showing MS prediction on a popup .. which is the proper approach @jeafreezy

This has been resolved.

@jeafreezy jeafreezy marked this pull request as draft April 8, 2026 08:24
@jeafreezy jeafreezy marked this pull request as ready for review April 12, 2026 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants