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
Right now the location of the incidents is set as "36N45W", for example.
Expected behavior
The new way of store will be latitue, longitude , latitude+','+longitude.
What is the motivation / use case for changing the behavior?
This is due to the param thaat google maps requests that is in that form, and if you consider the storage of the string of location that way, the work of the dashboard is easier, just calling the url for the google maps api.
Others:
Remember, that the incidents submitted by the sensors, must have the location of the sensor itself.
I'm submitting a...
Current behavior
Right now the location of the incidents is set as "36N45W", for example.
Expected behavior
The new way of store will be latitue, longitude , latitude+','+longitude.
What is the motivation / use case for changing the behavior?
This is due to the param thaat google maps requests that is in that form, and if you consider the storage of the string of location that way, the work of the dashboard is easier, just calling the url for the google maps api.
Others:
Remember, that the incidents submitted by the sensors, must have the location of the sensor itself.