Skip to content
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

VHF channels erroneously labeled as frequencies #310

Closed
thumax opened this issue Aug 9, 2023 · 2 comments
Closed

VHF channels erroneously labeled as frequencies #310

thumax opened this issue Aug 9, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@thumax
Copy link

thumax commented Aug 9, 2023

Throughout openAIP VHF channels are suffixed by “MHz” which suggests they are frequencies. They are not. When operated in 8.33 kHz channel spacing the “frequency” displayed on your radio is a channel number and not the actual center frequency.

Examples:

  • EDDB Tower is listed as “118.805 MHz”, actual center frequency is 118.8000 MHz
  • EDMD Info is listed as “133.010 MHz”, actual center frequency is 133.0083 MHz
  • EDHO Info is listed as “127.560 MHz”, actual center frequency is 127.5583 MHz

Easy fix: just don’t add “MHz” to channel numbers.

@reskume reskume self-assigned this Aug 9, 2023
@reskume reskume added the enhancement New feature or request label Aug 9, 2023
@reskume
Copy link
Contributor

reskume commented Aug 10, 2023

Thanks for the heads up! Yes, we are aware of the fact that this is may not be correct in some cases - for countries that don't use 8.33 kHz spacing this is still valid. The current implementation is simply from the "time before 8.33 kHz" spacing in several countries.

For now, I admit it's a simple fix to remove the "MHz" suffix for the frequencies in the UI. The main big pain point is the backend and the API which still outputs frequencies with unit MHz. This is a big refactoring which in the end will result in a V2 API schema. I have created another issue to track the API schema refactoring here #311.

I would close the ticket for now if this is OK and we can keep track on the API v2 ticket instead.

@thumax
Copy link
Author

thumax commented Aug 11, 2023

Sure, thanks for the info!

@thumax thumax closed this as completed Aug 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

No branches or pull requests

2 participants