MerginMaps / MerginMaps/mobile

A framework for notification (geofencing)

Open
#2,920 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C++
Stars
388
Forks
87
Avg merge
2d 7h
Merged PRs (30d)
20

Description

It would be good to have a framework to notify users based on their location. Currently, it is possible to see geofencing only in the forms when you try to capture new data.

A new notification framework can inform users about their position in connection with some other existing layers. Real-life example of such use-cases are:

  • Users enters a hazardous zone: there will be a hazard zone polygon and the app will notify users if their GPS falls within the polygon
  • Users exceed a certain speed: e.g. in navigation, a boat exceeds a certain speed limit and users get notified about the speed restriction within a polygon.
  • Combined with tracking options: two users are within the same area.

The configuration for these geometry aggregation with GPS can be set in the MM QGIS plugin. A notification aggregator can be also added (as a GeoPackage) and synced with the MM server, so the admins can possibly hook it up with their own server to take some actions.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by mapping the existing geofencing shown in forms and the tracking and synchronization paths in the mobile app. Define the notification framework's scope, configuration flow from the MM QGIS plugin, GeoPackage synchronization, and notification behavior before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, cpp, ios
Domain
mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.