You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Many pins in the LAH map don't have a specific address assigned to them. Given how the MapQuest API geocodes these to a specific Lat-Long, this means that many pins on our map appear on the same location, and thus are indistinguishable. (An example of this would be multiple volunteers just entering "Chicago" as their location).
Describe the solution you'd like
Our solution is to "fuzz" these resource locations so that they no longer overlap each other. Client-side, we can add a small randomized offset to the Lat-Long coordinates so that they appear in the same area, but not the exact same location. Alternatively we can also randomize pins that do not have an address set upon creation.
Additional context
Add details, any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Many pins in the LAH map don't have a specific address assigned to them. Given how the MapQuest API geocodes these to a specific Lat-Long, this means that many pins on our map appear on the same location, and thus are indistinguishable. (An example of this would be multiple volunteers just entering "Chicago" as their location).
Describe the solution you'd like
Our solution is to "fuzz" these resource locations so that they no longer overlap each other. Client-side, we can add a small randomized offset to the Lat-Long coordinates so that they appear in the same area, but not the exact same location. Alternatively we can also randomize pins that do not have an address set upon creation.
Additional context
Add details, any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: