Geofencing coverage area #141

Closed
opened 2018-06-11 16:43:27 +00:00 by jankstudio · 9 comments
jankstudio commented 2018-06-11 16:43:27 +00:00 (Migrated from gitlab.com)

Geofencing feature for resq

  1. create a table / entity that will store the supported areas. store them as geo types in the database, possibly polygon type

  2. make a symfony service where you can send long/lat coordinates to and it will return true or false depending if the point is in the supported areas. use contain function in the db?

  3. figure out a way to have a gui to create the supported area polygons. maybe draw them in google map (free) then export. then we import whatever format they export to.

Geofencing feature for resq 1. create a table / entity that will store the supported areas. store them as geo types in the database, possibly polygon type 2. make a symfony service where you can send long/lat coordinates to and it will return true or false depending if the point is in the supported areas. use contain function in the db? 3. figure out a way to have a gui to create the supported area polygons. maybe draw them in google map (free) then export. then we import whatever format they export to.
jankstudio commented 2018-06-16 04:43:30 +00:00 (Migrated from gitlab.com)
created branch [`141-geofencing-coverage-area`](https://gitlab.com/jankstudio/resq/compare/master...141-geofencing-coverage-area)
jankstudio commented 2019-02-27 06:18:24 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
korina.cordero commented 2019-02-28 07:55:01 +00:00 (Migrated from gitlab.com)

created merge request !221 to address this issue

created merge request !221 to address this issue
korina.cordero commented 2019-02-28 07:55:01 +00:00 (Migrated from gitlab.com)

mentioned in merge request !221

mentioned in merge request !221
jankstudio commented 2019-03-10 14:34:15 +00:00 (Migrated from gitlab.com)

mentioned in commit d24be90314

mentioned in commit d24be90314dae75eec943a4f84c2c4977e75e90f
jankstudio commented 2019-03-10 14:34:15 +00:00 (Migrated from gitlab.com)

mentioned in commit 2ffc856b10

mentioned in commit 2ffc856b10f50f6b9665a4a788388001ae74b295
jankstudio commented 2019-03-10 17:33:48 +00:00 (Migrated from gitlab.com)

mentioned in commit 27372264e9

mentioned in commit 27372264e9a638e01f26a56d3229fb2b4e4b3b9b
jankstudio commented 2019-03-10 17:34:18 +00:00 (Migrated from gitlab.com)

closed via merge request !221

closed via merge request !221
jankstudio commented 2019-03-10 17:34:18 +00:00 (Migrated from gitlab.com)

mentioned in commit a1408c618c

mentioned in commit a1408c618c4778a62aa64fac5f0c897ce832767f
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: rgutierrez/resq#141
No description provided.