Replies: 2 comments
-
Just to have it recorded here in the discussion:
|
Beta Was this translation helpful? Give feedback.
-
Between those choices I think I'd rather have the clusters than fudge stuff. It's the data we have. Is there a concept of error that we should be supporting? I'm wondering if we need to have a bigger discussion around locations. At the moment I'm feeling like if we get a lat/long that's all we should need. I don't know what the current situation is with reverse geocoding, but that sure seems like what we should be doing if we can. If we could just get rid of the location selection stuff from the app that would be sweet. |
Beta Was this translation helpful? Give feedback.
-
When I talked with Steven Russell at NAMA 2023, I learned that he really likes maps. Currently we allow users to map observations, but it's kind of buried. Should we make this more prominent? Maybe even add it to project show page? Seems like some sort of heat mappy thing would be best, but we could certainly go with our current functionality. A potentially cheaper option would just be a map of any project constraint. Using the "First Fantastic Fungal Friends Foray Festival!" as an example, that would currently be something like, https://mushroomobserver.org/locations/358, which I don't find very satisfying. The map of observations is https://mushroomobserver.org/observations/map?q=1pcjX (but I'm not sure how long queries persist these days, so I'll also attach a screen grab) which is more satisfying.
Beta Was this translation helpful? Give feedback.
All reactions