Arquisoft / Arquisoft/InciManager_i3a
Possible improvement for submitting incidents
- Dominant language
- Java
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
## I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[X] Feature request
[ ] Documentation issue or request
## Current behavior
The agent (person or entity) must write the location of the incident, but following the implementation that will be done for closing issue #68 , writting latitude and longitude can be problematic.
## Expected behavior
What would be perfect is: the person or the entity, can click on a google maps' map the location of the incident. The latitude and longitude will be stored and sent in the incident's location. (always following the format explained in #68 )
## What is the motivation / use case for changing the behavior?
An easier behaviour of the aplication and the incident creation for the agent creating the report (the incident)
Others:
Remember taht, the sensor will send it's own location, so the location selection won't be necessary.
Contributor guide
Research direction
Start by reading issue #68 and the incident-submission flow. Determine where the agent enters an incident location and how location data is stored and sent. Done means the agent can select a location on a Google Maps map, with latitude and longitude sent in the format required by #68, while sensor-provided locations do not require selection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100