Load dataset from Hugging Face and pass to UrbanMapper

[soniacq]

Loading Data from Hugging Face

This example loads the "oscur/pluto" dataset from Hugging Face, selects the training split, and converts the first 1,000 rows into a pandas DataFrame for efficient analysis and exploration. The resulting DataFrame can then be loaded into UrbanMapper using from_dataframe().

[simonprovost]

Excellent! ☀️ That's gonna be highly highly useful throughout the UrbanMapper's workflow or any subsequent libraries coming out of OSCUR / VIDA! Thanks for this one.

Proposed some modifications. Finally, may you open a github issue's feature request, proposing the need for a from_oscur(.) / from_huggingface_oscur(.) throughout the Loader module to accelerate this process? While the feature request could or could never see the light of the day, at least it's written down and could be debated, with today's team and tomorrow's one.

Last suggestion, could you re work the commit's message please to follow Git Karma Convention: (1) https://karma-runner.github.io/6.4/dev/git-commit-msg.html, or you can look at the other commits we've done thus far (2) https://github.com/VIDA-NYU/UrbanMapper/commits/main/ ? Also explained here but as you know will soon be released in a proper documentation per #43 as soonish as I'm done with it ✅

Finally, one question, however; would you say we should include https://pypi.org/project/datasets/ within UrbanMapper? I would say yes and no. Yes because one of the example anyway's utilising it. No because we do not use it as part of the UrbanMapper's modules. What is your call here? If you believe it should be included, then you'll need to uv add datasets and commit the changes done to pyproject.toml.

Congrats for this PR! First contributor 🎉

[simonprovost]

Hey @soniacq ,

Do not forget to rebase with main now that #43 and #46 are merged into the main track. You may know how to do it, but in this case:

Make sure you have everything committed on you current work-based branch, including some dummy commits with names like save or any stash workflow. Then proceed to main and pull the latest. Git checkout back to your branch and run git rebase main to ensure you are "up to date" with main. If conflicts arise, it is possible because the docs PR (#43) we completed with @ctsilva was quite large; determine what should be kept based on what is coming and your changes. Feel free to message me if you are unsure, but you should be fine, trusting you on that it's no big deal ✅

To recap in action:

# Assuming you have nothing to commit
git checkout main
git pull
git checkout -
git rebase main

Tada 🎉

Cheers!

[soniacq]

@simonprovost I have addressed all your comments—thank you for the valuable insights. I believe this PR is now ready to be merged into the master branch. Please have a look when you get a chance. Thanks!

[simonprovost]

Thanks to @soniacq for this contrib! We needed this very much! Can't wait for #49 🎉