-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native Ecotyped Plant Discovery #1
Comments
taking a look at this tonight - will see if I can get something with rough edges working |
edit: bleh, it's down. This collection looks promising. |
It seems this data is not readily available with the granularity we need. There are a handful of native plant databases, but none have documented API access. I have some ideas, and I think it involves doing a bit of cross referencing results across the different databases. |
What are your thoughts on this: Seems like a cool open sauce solution |
It does! I'll check it out |
Addition Idea:
The app is intended to work as such:
Problem:
The Average person is pretty dumb, and 50% of them are dumber. They don't know what plants are native, what they look like, etc. I am software engineer, I don't know shit about plants, I'm the 50% here^.
It would be nice if we could have a ruby based API service that based off of the address of a development site (they each have an address in the data model) we could pull native plants with at least this data:
plant: {
plant_name: "",
plant_image_link: "",
plant_characteristics?: (here I'm uncertain, but any useful information in identifying plants so that people can know what to look for)
}
With this we can later build out views so someone can click "native species nearby" or something and see what a local ecosystem should look like.
The text was updated successfully, but these errors were encountered: