You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repository and believe that this is not a duplicate.
Summary
Currently to update the location of a gateway manually, you have to drag a map marker by hand along a map to where the gateway is installed if it is not installed in your current location.
There is no address lookup as you might expect from a map interface, nor is there a latitude/longitude input
Improve the experience for users who use the feature
Implementation description
Having a dialog box where one could input an address would be ideal (I’m guessing OpenStreetMap has an address API).
A way to input latitude/longitude would also be useful and likely very simple given that's how the location is encoded on the backend
Can you implement this by yourself and make a pull request?
I would if I felt more comfortable with go and frontend
The text was updated successfully, but these errors were encountered:
Summary
Currently to update the location of a gateway manually, you have to drag a map marker by hand along a map to where the gateway is installed if it is not installed in your current location.
There is no address lookup as you might expect from a map interface, nor is there a latitude/longitude input
re: https://forum.chirpstack.io/t/improve-manual-gateway-location-positioning/13788?u=safrone
What is the use-case?
Improve the experience for users who use the feature
Implementation description
Having a dialog box where one could input an address would be ideal (I’m guessing OpenStreetMap has an address API).
A way to input latitude/longitude would also be useful and likely very simple given that's how the location is encoded on the backend
Can you implement this by yourself and make a pull request?
I would if I felt more comfortable with go and frontend
The text was updated successfully, but these errors were encountered: