Canvas Maps: Difference between revisions

Jump to navigation Jump to search
m
No edit summary
Line 54: Line 54:




== A Prototype replicating the hard coded Map dialog ==
== Moving Maps ==
We need to keep in mind that once the hard coded Map dialog is getting ported, there will be lots of overlapping functionality with similar "displays", like the NavDisplay, agradar, wxradar - all of these are basically about mapping a geo-position to 2D screen space (horizontal currently).
Basically, a moving map terrain view would require support for accessing the FG tile manager, so that a orthographic view of the scenery can be rendered.
 
It might be easier to use OSG's GeoTIFF support instead and require people to add GeoTIFF images for the region of interest?
The Canvas system's mapping mode loosely follows the ideas from ARINC 661.
Overall, I feel that would be better implemeneted as a separate mode (implemented in C++)?
The current hard coded NavDisplay is really an ARINC 661 display - it takes a list of symbols, a list of items and combines then using a projection to create a final  display. The only additional code is to deal with special things that can't easily be described by a simply symbol, especially the flight-plan/route path.
I think it would be better to use the same elevation data that is used for rendering, so that you don't have to create and provide the same data two times. Rendering an orthographic view would come for free if we implement support for multiple cameras. If we don't want to do it with rendering we can use a cached list of terrain intersections. I have seen such an implementation in one of the aircrafts in the forum (I think it was the 787).
 
Yes, that's true - that's been discussed previously, but there was talk about using a dedicated scene graph for such moving map displays on the devel list.


== Canvas Groups/Layers (Implemented) ==
== Canvas Groups/Layers (Implemented) ==

Navigation menu