Open tgreco opened 2 years ago
@michaelklem this appears to be working on my end. It doesn't appear to be setup to use any configuration to make sure I'm within a certain area of the geofence alert. But it does correctly populate the map for me.
Should I proceed with making this use a configuration that specifies how close a user should be to receive the alert?
Yes. Default to 1000 feet.
On Tue, Jul 13, 2021, 6:11 PM tgreco @.***> wrote:
@michaelklem https://github.com/michaelklem this appears to be working on my end. It doesn't appear to be setup to use any configuration to make sure I'm within a certain area of the geofence alert. But it does correctly populate the map for me.
Should I proceed with making this use a configuration that specifies how close a user should be to receive the alert?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/michaelklem/alertwalker_mobile/issues/2#issuecomment-879506236, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEQIO65FTI5I2ID4SDIAVLTXTP5PANCNFSM5AKMXOUQ .
This is complete now. https://github.com/michaelklem/alertwalker_mobile/commit/357ac032bc5c7709b0033e1c2bb5be32314826b9
You will need to merge the backend changes to main branch as I committed them on master out of habit. https://github.com/michaelklem/alertwalker_backend/pull/new/master
The value for how close a user must be is stored in the configuration "MAP_DISPLAY_ALERT_RADIUS".
When location/map and location/geofence are called I now store the user's location in the user collection under the field "lastLocation".
Then when the backend is looking for nearby users to send the websocket message to it will filter on user.lastLocation.
I have only added this to the alertwalker-dev database. Should I add this to the other databases as well?