Open www2000 opened 6 years ago
Thank you for the proposal. I'm already selecting a single frequency from the Navigraph data which is only a workaround so far. Compatibility is important. LNM usually checks if columns or tables exist or not if the schema is older. Alex
I have edit my early post to add a entry for 8.33 KHz communication channels
Removed from 2.4. This is too much work for such a small feature. If affects all database compiler including Navigraph and you cannot use the real world frequencies in the simulator anyway.
No problem with postpone so long that this is on the roadmap. Where can i read the code for the database compiler and if its public the Navigraph compiler?
Compiler code for all platforms (FSX, P3D, X-Plane and Navigraph) is in the atools library. The top level class used to compile is the navdatabase.h. You could think of it as a facade (pattern) to the rest. Database schema documentation is in the create_*.sql scripts in the resources folder. The Navdatareader is a command line tool that can be used to create scenery databases without LNM. Alex
He any updates on this issue?
No.
Hi i wand to report that there is is a problem that little navmap support only one frequency for Controll airspace, where for example Amsterdam CTR have 5 frequency for INF, 5 frequency for ACC, 1 frequency for VOL, 2 for MIL ACC, 1 for MIL INF and 5 for UAC. Where are 10 on the VHF frequency and 9 on UHF frequency. There are areas there are using frequency on the VF band.
My propose is that a new table be create call boundary_freq that have the foaling information: ID boundary_id name com_type freq freq_band mil Mandatory com_name min/max_altitude_type *min/max_altitude
*: i don't know the this is required information for use in this table the values for freq_band are H for the HF band (3000 kHz - 30,000 kHz)( this the encoding for 123.456MHz) V for the VHF band (30,000 kHz - 200 MHz) U for the UHF band (200 MHz - 3000 MHz) C For 8.33KHz communication channels
The values for freq are: HF band 12345 (12345 kHz) VHF 123456 (123.456MHz) UHF 123456 (1234.56MHz)
This can be backward compatible with older version of little navmap if nothing change in the "boundary" table. edit : add the mil and mandatory column