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 planned to add a new frequency to the Welt2000-"Database" when it came to my eye that the frequency in the Welt2000-format does only consist of 5 digits while we need 6 digits for the new 8,33 KHz standard to be displayed correctly.
In my opinion we either need one more digit in the format with all its consequences (neccessary changes in all glide computers which use the database) or we would need to define a standard on how to add new frequencies into the database.
Adding a digit would most likely be the much cleaner option whereas having a strategy for new frequencies (cut frequency after 5 digits vs. rounded frequencies) would work faster and wouldn't require gliding computer software to be adjusted.
What are your thoughts on this?
The text was updated successfully, but these errors were encountered:
The current format is problematic not just in terms of the frequencies. Ideally a whole different format would be used, e.g. something based on JSON. The only reason for the old format is keeping compatibility with existing tools that expect it like that.
Pehaps the quickest fix for 8.33KHz is to ignore the first digit. It's always '1' anyways?
A parser can easily check if a frequency is within the valid range (let's say 118-137MHz) and assume 8.33KHz and check again.
Hey there,
I planned to add a new frequency to the Welt2000-"Database" when it came to my eye that the frequency in the Welt2000-format does only consist of 5 digits while we need 6 digits for the new 8,33 KHz standard to be displayed correctly.
In my opinion we either need one more digit in the format with all its consequences (neccessary changes in all glide computers which use the database) or we would need to define a standard on how to add new frequencies into the database.
Adding a digit would most likely be the much cleaner option whereas having a strategy for new frequencies (cut frequency after 5 digits vs. rounded frequencies) would work faster and wouldn't require gliding computer software to be adjusted.
What are your thoughts on this?
The text was updated successfully, but these errors were encountered: