AM 4 Feature Requests

Let Sim Innovations know about your Air Manager experience and let us know about your dream feature addition

Moderators: russ, Ralph

Message
Author
User avatar
Sling
Posts: 5237
Joined: Mon Sep 11, 2017 2:37 pm
Contact:

Re: AM 4 Feature Requests

#31 Post by Sling »

yeah vector is definitely the way to go but quite some work to implement. If this comes it will be a big feature for AM.

User avatar
Corjan
Posts: 2936
Joined: Thu Nov 19, 2015 9:04 am

Re: AM 4 Feature Requests

#32 Post by Corjan »

SimPassion wrote: Tue Apr 09, 2019 8:27 am Nice approach Corjan
we would expect it to be more efficient in term of graphics performances ?

Gilles
Performance was okay on my desktop system. It is also very depended on what kind of objects you want to draw.

Corjan

User avatar
Keith Baxter
Posts: 4674
Joined: Wed Dec 20, 2017 11:00 am
Location: Botswana

Re: AM 4 Feature Requests

#33 Post by Keith Baxter »

Corjan,

From the little I have researched over the last few days it is definitely beneficial to go vector based maps.

As you say and how I understand it, different layers can be created to show and hide. This gives an advantage that these layers can be created and implemented over time.

My thinking is..

So in the case where AM starts to implement the vector based system somewhere in AM4 or AM5 the basic map styles are created in both Mercator and Spherical views. Here the current AIRP, NDB, FIX, VOR layers are created along with a country and city name layers. I would then think that the next step would be the user points(hard runways, soft runways,empty airports, seaport, Helipad, obstacle, way-point, Point of interest, mountains, etc)

The following could then be add as and when time permits.

1) victor airways and jet airways layers.

2) flight plan, missed approaches, Aircraft trail, Compass rose, range rings, map grid, AI aircraft, AI ships etc
NOTE: the data for the flight-plan to be available for FMS use

3) Air spaces (Class A, Class B, Class C, Class D, Class E, Class F, Class G, Restricted, Prohibited, Danger, Glider Prohibited, Radar, Ground ,Departure, Approach etc)

4) Weather (Temporary flight restrictions, DROTAMs, Pilot reports,) Sigmets, Outlooks, Airmets(Icing, Turbulence, Instrument flight rules, Mountain obstructions, Radar, Satellite, Clouds, winds aloft)

5) Navigraph chart overlay layer.

6) Vertical navigation chart and data. Flight plan Elevation Profile.


This is everything I can think of off the top of my head right now and features that I would most likely be requesting down the line


I would think that doing it in a similar way AM users would be given the benefit of a map system that slowly evolves. For us to expect a map system in one big bang could take years to develop.


As a side, If users know the program then it might be beneficial for them to contribute to creating the layers. Just think out loud.

Keith
AMD RYZEN 9 5950X CPU, Corsair H80I cooler, ASUS TUF GAMING B550-PLUS AMD Ryzen Mother Board,  32Gb ram Corsair Vengeance 3000Mh, MSI GTX960 4G graphics card 

User avatar
Keith Baxter
Posts: 4674
Joined: Wed Dec 20, 2017 11:00 am
Location: Botswana

Re: AM 4 Feature Requests

#34 Post by Keith Baxter »

For me, I have been planning and working on this feature in my instrument for the longest time. :lol: :lol: :lol:

What I have posted in the previous post will accommodate most of what I would like to see.

This is a screen shot of the weather legends displaying on a map.
xm_legends.png
This is a screenshot of the XM weather menu.
xm_menu.png
Keith
AMD RYZEN 9 5950X CPU, Corsair H80I cooler, ASUS TUF GAMING B550-PLUS AMD Ryzen Mother Board,  32Gb ram Corsair Vengeance 3000Mh, MSI GTX960 4G graphics card 

User avatar
Keith Baxter
Posts: 4674
Joined: Wed Dec 20, 2017 11:00 am
Location: Botswana

Re: AM 4 Feature Requests

#35 Post by Keith Baxter »

Sling wrote: Tue Apr 09, 2019 10:31 am yeah vector is definitely the way to go but quite some work to implement. If this comes it will be a big feature for AM.
+1

A huge feature for an allready great product,

Keith
AMD RYZEN 9 5950X CPU, Corsair H80I cooler, ASUS TUF GAMING B550-PLUS AMD Ryzen Mother Board,  32Gb ram Corsair Vengeance 3000Mh, MSI GTX960 4G graphics card 

JackZ
Posts: 2262
Joined: Mon Feb 22, 2016 1:02 pm

Re: AM 4 Feature Requests

#36 Post by JackZ »

Corjan wrote: Tue Apr 09, 2019 10:34 am
SimPassion wrote: Tue Apr 09, 2019 8:27 am Nice approach Corjan
we would expect it to be more efficient in term of graphics performances ?

Gilles
Performance was okay on my desktop system. It is also very depended on what kind of objects you want to draw.

Corjan
If AM is going through the vector based route, which makes sense, the use of a well established database is a must, as aviation Databases are constantly evolving.
One could suggest to offer an outdated database as a base, with the ability for the user to update its database via a subscription. Navigraph which relies on Jeppesen data is probably the best idea for vector based mapping. Most serious summers already use Navigraph or equivalent.

I nonetheless think that OpenMap features should remain for those that want to use the existing system, such as a ground based GPS, and who knows, if and when Ralph and Corjan will decide to create a plugin for racing simulators such as rFactor (in that case AM could be renamed AGM for Air/Ground Manager), it would be perfect.

Jacques
Jacques
My YouTube Chanel on the A320 (Real SOPs by an Airline Pilot IRL):
https://www.youtube.com/playlist?list=P ... 0Q6SBASRqJ

User avatar
Keith Baxter
Posts: 4674
Joined: Wed Dec 20, 2017 11:00 am
Location: Botswana

Re: AM 4 Feature Requests

#37 Post by Keith Baxter »

Jacques,

I would agree with you that OSM should not be discarded and that there should be a choice of which map system one wants to use.
However I do not think that too much time should be spent on the old Raster system other that to add a few extra base maps.

Keith
AMD RYZEN 9 5950X CPU, Corsair H80I cooler, ASUS TUF GAMING B550-PLUS AMD Ryzen Mother Board,  32Gb ram Corsair Vengeance 3000Mh, MSI GTX960 4G graphics card 

User avatar
Keith Baxter
Posts: 4674
Joined: Wed Dec 20, 2017 11:00 am
Location: Botswana

Re: AM 4 Feature Requests

#38 Post by Keith Baxter »

Moving on to Navigation and FMS data support.

Ralph had indicated that they were in discussion with Navigraph over flight plan data. I hope that that would include airport data and then charts at some stage.

The reason I have been pushing for the ability to write to and edit a JSON file is to create and edit flight plans.

I have created some airport, runway and radio JSON files from Navigraph data and use them in my instrument. It would be great if this information could also be available through AM. Yes the user would have to have a Navigraph subscription to access this information. ????


This is a video of what I have done so far regarding my FMS while anticipating what Navigraph data AM will make available.

So these features are requested for AM4 please.




Based on what is in the video, how close am I to what you have planed regarding navigation data from Navigraph,Corjan ?
Please give us your thoughts and an indication of timing.


Keith
AMD RYZEN 9 5950X CPU, Corsair H80I cooler, ASUS TUF GAMING B550-PLUS AMD Ryzen Mother Board,  32Gb ram Corsair Vengeance 3000Mh, MSI GTX960 4G graphics card 

User avatar
Keith Baxter
Posts: 4674
Joined: Wed Dec 20, 2017 11:00 am
Location: Botswana

Re: AM 4 Feature Requests

#39 Post by Keith Baxter »

Regarding Navigation data from Navigraph I am currently using data I have downloaded and converted from their sqlite file to JSON.

So the request I am making is if this data could be made available for navigation use.

My suggestion would be for AM to have it's own navigation datafefs that we could subscribe to.

Here is an example of an airport JSON that I currently use.

Code: Select all

	{
		"file_id": 1,
		"ident": "FAOR",
		"name": "O.R. Tambo Intl",
		"city": null,
		"state": null,
		"country": "AFR",
		"region": "FA",
		"fuel_flags": 0,
		"has_avgas": 0,
		"has_jetfuel": 0,
		"has_tower_object": 0,
		"tower_frequency": 118100,
		"atis_frequency": 126200,
		"awos_frequency": null,
		"asos_frequency": null,
		"unicom_frequency": null,
		"is_closed": 0,
		"is_military": 0,
		"is_addon": 0,
		"num_boundary_fence": 0,
		"num_com": 10,
		"num_parking_gate": 0,
		"num_parking_ga_ramp": 0,
		"num_parking_cargo": 0,
		"num_parking_mil_cargo": 0,
		"num_parking_mil_combat": 0,
		"num_approach": 18,
		"num_runway_hard": 2,
		"num_runway_soft": 0,
		"num_runway_water": 0,
		"num_runway_light": 0,
		"num_runway_end_closed": 0,
		"num_runway_end_vasi": 0,
		"num_runway_end_als": 0,
		"num_runway_end_ils": 4,
		"num_apron": 0,
		"num_taxi_path": 0,
		"num_helipad": 0,
		"num_jetway": 0,
		"num_starts": 0,
		"longest_runway_length": 14505,
		"longest_runway_width": 197,
		"longest_runway_heading": 15.532999992370605,
		"longest_runway_surface": null,
		"num_runways": 2,
		"largest_parking_ramp": null,
		"largest_parking_gate": null,
		"rating": 1,
		"is_3d": 0,
		"scenery_local_path": null,
		"bgl_filename": null,
		"left_lonx": 28.234342575073242,
		"top_laty": -26.111906051635742,
		"right_lonx": 28.257278442382812,
		"bottom_laty": -26.164770126342773,
		"mag_var": -18.718067169189453,
		"tower_altitude": null,
		"tower_lonx": null,
		"tower_laty": null,
		"transition_altitude": 8000,
		"altitude": 5558,
		"lonx": 28.242317199707031,
		"laty": -26.133693695068359
	},
	"geometry": null

And this is the coms JSON file that the set of radio frequencies are obtained for an airport.

Code: Select all

	"type": "Feature",
	"properties":
	{
		"airport_id": 3015,
		"type": "A",
		"frequency": 119700,
		"name": "CAPE TOWN"
	},
	"geometry": null
},
{
	"type": "Feature",
	"properties":
	{
		"airport_id": 3015,
		"type": "A",
		"frequency": 120050,
		"name": "CAPE TOWN"
	},
	"geometry": null
},
{
	"type": "Feature",
	"properties":
	{
		"airport_id": 3015,
		"type": "ATIS",
		"frequency": 127000,
		"name": null
	},
	"geometry": null
},
{
	"type": "Feature",
	"properties":
	{
		"airport_id": 3015,
		"type": "C",
		"frequency": 122100,
		"name": "CAPE TOWN"
	},
	"geometry": null
},
{
	"type": "Feature",
	"properties":
	{
		"airport_id": 3015,
		"type": "DIR",
		"frequency": 124350,
		"name": "CAPE TOWN"
	},
	"geometry": null
},
{
	"type": "Feature",
	"properties":
	{
		"airport_id": 3015,
		"type": "G",
		"frequency": 121900,
		"name": "CAPE TOWN"
	},
	"geometry": null
},
{
	"type": "Feature",
	"properties":
	{
		"airport_id": 3015,
		"type": "RMP",
		"frequency": 122650,
		"name": "CAPE TOWN"
	},
	"geometry": null
},
{
	"type": "Feature",
	"properties":
	{
		"airport_id": 3015,
		"type": "T",
		"frequency": 118100,
		"name": "CAPE TOWN"
	},


So from these JSON files I am able to create the Airports module that give me this information.

This is the Airport coms info
arip_coms.png
This is the Airport Runway info
arip_rwy.png
This is the Airports nearest information
arip_nearest.png

So if this and other navigation information could be made available to other users.

I have not got round to the other FMS data that is for flight plans yet, but here is an example of what is available.
This is the approach leg JSON record set.

Code: Select all


	"type": "Feature",
	"properties":
	{
		"approach_id": 68864,
		"is_missed": 0,
		"type": "IF",
		"approach_fix_type": null,
		"alt_descriptor": "A",
		"turn_direction": null,
		"fix_type": "W",
		"fix_ident": "ASPIK",
		"fix_region": "FA",
		"fix_airport_ident": null,
		"recommended_fix_type": null,
		"recommended_fix_ident": null,
		"recommended_fix_region": null,
		"is_flyover": 0,
		"is_true_course": 0,
		"course": 0.0,
		"distance": 0.0,
		"time": 0.0,
		"theta": 0.0,
		"rho": 0.0,
		"altitude1": 0.0,
		"altitude2": 0.0,
		"speed_limit_type": "-",
		"speed_limit": 210
	},
	"geometry": null
},
{
	"type": "Feature",
	"properties":
	{
		"approach_id": 68864,
		"is_missed": 0,
		"type": "TF",
		"approach_fix_type": null,
		"alt_descriptor": "A",
		"turn_direction": null,
		"fix_type": "W",
		"fix_ident": "D275H",
		"fix_region": "FA",
		"fix_airport_ident": null,
		"recommended_fix_type": null,
		"recommended_fix_ident": null,
		"recommended_fix_region": null,
		"is_flyover": 0,
		"is_true_course": 0,
		"course": 0.0,
		"distance": 0.0,
		"time": 0.0,
		"theta": 0.0,
		"rho": 0.0,
		"altitude1": 0.0,
		"altitude2": 0.0,
		"speed_limit_type": null,
		"speed_limit": null
	},
	"geometry": null
},
{
	"type": "Feature",
	"properties":
	{
		"approach_id": 68864,
		"is_missed": 0,
		"type": "VM",
		"approach_fix_type": null,
		"alt_descriptor": "A",
		"turn_direction": null,
		"fix_type": "A",
		"fix_ident": "FACT",
		"fix_region": "FA",
		"fix_airport_ident": null,
		"recommended_fix_type": null,
		"recommended_fix_ident": null,
		"recommended_fix_region": null,
		"is_flyover": 0,
		"is_true_course": 0,
		"course": 10.0,
		"distance": 0.0,
		"time": 0.0,
		"theta": 0.0,
		"rho": 0.0,
		"altitude1": 0.0,
		"altitude2": 0.0,
		"speed_limit_type": null,
		"speed_limit": null
	},
	"geometry": null

Using this data I will be able to create flight plans.


Whilst I am not certain, I think that the boundary JSON is used to draw the vectors for the map.
This is what one record looks like.

Code: Select all

	"type": "Feature",
	"properties":
	{
		"file_id": 1,
		"type": "CC",
		"name": "CAPE TOWN CTA B",
		"com_type": null,
		"com_frequency": null,
		"com_name": null,
		"min_altitude_type": "MSL",
		"max_altitude_type": "MSL",
		"min_altitude": 14500,
		"max_altitude": 20000,
		"max_lonx": 29.206329345703125,
		"max_laty": -31.868764877319336,
		"min_lonx": 20.974029541015625,
		"min_laty": -34.508495330810547,
		"geometry": "0000001F41D8F350C2001FAE41DB9940C1FF4BD141DE7160C1FEF36D41DE95D0C1FEF33B..."
	},


From my side it is not imperative that this navigation data be made available to all. But I do want to share this instrument I am creating when done. But due to Navigraph licencing I cannot do so without infringing on my Navigraph subscription.

Keith
AMD RYZEN 9 5950X CPU, Corsair H80I cooler, ASUS TUF GAMING B550-PLUS AMD Ryzen Mother Board,  32Gb ram Corsair Vengeance 3000Mh, MSI GTX960 4G graphics card 

JackZ
Posts: 2262
Joined: Mon Feb 22, 2016 1:02 pm

Re: AM 4 Feature Requests

#40 Post by JackZ »

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...

As for the other records, they are probably more related to the missed approach procedure, by defining a waypoint and the way it has to be flown (overflown or not, radials to/from the next waypoint, etc...).

Interested to know how you translated the SQLite to JSON.
Could you please send me the JSON by MP so I can have a look?

Jacques
My YouTube Chanel on the A320 (Real SOPs by an Airline Pilot IRL):
https://www.youtube.com/playlist?list=P ... 0Q6SBASRqJ

Post Reply