AM 4 Feature Requests

[Keith Baxter]

Jacques,

Unfortunately I cannot share the navigraph data. However I have sent you a PM on how to do it. You will need a navigraph subscription so that you can download the data and use it for your own use..

Once you see what data can be obtained, you will understand what awesomeness AM will become if this data is made available via AM.
Let us know how you get on and your thoughts.

Keith.

[Keith Baxter]

Jacques,

As i have said a few posts back. For me I have the data available to do most of the flight plans. I just don't want to go to all the trouble of coding using the data set i have reworked and then next week AM has it's own navigraph data set where the files have a different structure.

Keith

[Sling]

Next week ? I know Corjan is fast but be reasonable, give him 2 weeks at least.

[Keith Baxter]

Next week ? I know Corjan is fast but be reasonable, give him 2 weeks at least.

Ha Ha

[Keith Baxter]

Corjan,

I have been thinking about how AM could provide Data for us to use in our instrument lua.

The answer could be a live_data function

example of data regarding AIRPORTS

live_arip_data=arip_data(icao,field[], field[],....)--This creates a live record based on the ICAO filter with the fields chosen from the airp_data field list.

Then like we do to change the base map in the map function we do

airp_icao(icao) changes the airp ICAO

This will give us a record to use with the relevant ICAO


This is what the field list could look like. OPs might like to add fields that I may have missed.

Code: Select all

airp fields list might look something like this.

	"icao" 						--The airport icao identifier
	"name" 						--the airport name
	"city" 						--the airport city
	"state" 						--the airport state 
	"country" 						--the country
	"region" 						--The region
	"airport_type"					--The type of airport
	"has_avgas" 					--Has avgas
	"has_jetfuel" 					--Has jet fuel
	"has_tower_object" 				--has tower object
	"tower_frequency" 				--The tower frequency
	"atis_frequency" 				--The atis frequency
	"awos_frequency" 				--The awos frequency
	"asos_frequency" 				--The awos frequency
	"unicom_frequency" 				--The unicom frequency
	"is_closed" 					--Is the airport closed
	"is_military" 					--Is the airport military
	"num_com" 					--Number of communication radios
	"num_parking_gate" 				--Number of Parking gates
	"num_parking_ga_ramp"			--Number of parking_ga ramps,
	"num_parking_cargo"				--Number of cargo parking
	"num_parking_mil_cargo" 			--Number of military cargo parking
	"num_parking_mil_combat"		--Number of military combat parking
	"num_approach" 				--Number of approaches
	"num_runway_hard" 				--Number of hard runways
	"num_runway_soft" 				--Number of soft runways
	"num_runway_water" 			--Number of waterways
	"num_runway_light" 				--Number of light runways
	"num_runway_end_closed" 		--Number of end runways closed
	"num_runway_end_vasi" 			--Number of end runways vasi
	"num_runway_end_als" 			--Number of end runways als
	"num_runway_end_ils" 			--Number of end runways ils
	"num_apron" 					--number of aprons
	"num_helipad" 					--Number of helipads
	"num_jetway" 					--Number of jetways
	"num_starts" 					--Number of starts
	"longest_runway_length" 			--longest runway length in meters
	"longest_runway_width" 			--Longest runway width in meters
	"longest_runway_heading" 		--Longest runway heading
	"longest_runway_surface" 			--Longest runway heading
	"num_runways" 					--Number of runways
	"largest_parking_ramp"			--Longest parking ramp Id
	"largest_parking_gate" 			--Longest parking gate id
	"rating" 						--Airport rating
	"mag_var" 					--Magnetic variance
	"tower_altitude" 				--altitude of the tower
	"tower_lonx" 					--Tower longitude
	"tower_laty" 					--Tower Latitude
	"transition_altitude"				--The transition altitude
	"altitude" 						--The airport altitude
	"lonx" 						--The airport longitude
	"laty" 						--The airport latitude

We could then also add others.

Here is an example of airport frequencies.

live_radio_data=radio_data(ICAO, field[], field[],.....)--This creates a live file of records based on the ICAO filter

Now we want to change the airport.

radio_icao(icao) changes the radio ICAO

Here you will get a number of records with the fields selected from the radio_data field list.

Code: Select all

	"icao"			--The airport ICAO
	"type"			--The type of radio(atis, tower, ils, apron, etc)
	"purpose"			--The purpose of the radio (information, Communication, Navigation, etc
	"frequency"		--The radio frequency
	"name"			--The name

Other types could be,,,,
live_rnwy_data
live_navaids_data
live_nerst_airp_data
live_nerst_navaids_data
live_on_route_arip_data
live_plightplan_data
live_vertical_profile_data
live_winds_data
live_lightening_data
live_turbalance_data
live_storms_data
live_arip_weather_data
live_cloud_tops_data
live_echo_tops_data
live_ice_level_data
live _precipitation_level_data

And the list go's on

Keith

[Keith Baxter]

Interesting Keith! You’ve turned this raw data into a real nice airport directory!

For the last record (Boundary) data, from what I read I think this is not for map vector drawing but instead to define a boundary box of the Airport sector with the minimum sector altitude of this box and the coordinates of this box, pretty much like in an approach plate. The Geometry field puzzles me though...

Jacques

Jacques,

Having done some detective work, I have come up with the following deduction. The Boundaries file is definitely the airspace's file that draws the airspace on a map and also provides data for the label.
This video is my take and hope that it gives some appetite and AM will take this path.

If we are going to get the additional base maps in AM3.6 I would hope that the airspace's and airways come next. As I see it, it is the easiest to implement.




Keith

[Keith Baxter]

Perhaps my comment in the video about moving a waypoint with a mouse applies to the minority. Most users probably will not build hardware to drive their instrument, so to them it would be a super feature.

For me to use that feature I would have to move it with an encoder or voice to text.

Just making it clear so that peep's do not get the wrong impression.

Keith

[SimPassion]

Just as a reminder in the Map feature area, for potential future usage
some available data here (already used in LittleNavMap) :
https://www.ngdc.noaa.gov/mgg/topo/gltiles.html
https://www.ngdc.noaa.gov/mgg/topo/glstiles.html

Gilles

[Keith Baxter]

Just as a reminder in the Map feature area, for potential future usage
some available data here (already used in LittleNavMap) :
https://www.ngdc.noaa.gov/mgg/topo/gltiles.html
https://www.ngdc.noaa.gov/mgg/topo/glstiles.html

Gilles

100% Gilles,

All the data is available from both Navigraph for airways and air spaces, and Noaa for weather, nexrad and radar,

It is simply a matter of creating map layers with the data as a first step.

Later the same data can be used to creat navigation and weather info for use as creating flight plans and weather reports and queries.


Keith

[Ralph]

I had a look at the suggest maps by Keith.

OpenStreetMap - Already implemented
OpenMapSurfer - I don't see (much) difference between the basic OSM layer and this map
OpenTopoMap - Looks a bit chaotic and the server seems to be a bit slow
Staman Terrain - Looks good, some tiles throw errors, so a bit questionable, but we have it implemented
CARTO Dark - Part of carto.com which is a commercial party, I can't find the maps on their website, nor can I find license information
CARTO Light - Same story