-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add field for azimuth #943
Comments
I'll admit, I've always wanted to azimuth field too, but never been quite sure how to do it well. I've wanted it so when people are setting up new nodes, they have some understanding about whether an antenna is pointing towards them, which seems useful. But I agree, without understanding the beamwidth too, it's not as useful. Now for many radios with built-in antennas, we actually know the beamwidths, but for some we don't and you'd have to enter it. Not a big issue, but makes the implementation a little more involved. |
The current implementation in meshmap only calculates the direction that a particular link is coming from and not where the antenna is actually pointing. When there are multiple links you get multiple angles displayed, some of those links could even come from a side or back lobe and does not accurately represent the azimuth of the antenna itself. |
Done |
Hello!
Under optional settings, where you enter the latitude and longitude of the antenna, could you add a field for antenna azimuth?
This can help us identify antennas that are close together and map servers could use the data to visualize it.
For example:
The text was updated successfully, but these errors were encountered: