Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Changes

Jump to: navigation, search

FG1000

2,165 bytes added, 20:42, 15 October 2017
Layers
Following is the list of layers displayed by the G1000 system (see page 153 of the 190-00498-07 Rev. A), and mapping to the equivalent MapStructure Layer.
Many of these would also be good to have for other avionics/GUI dialogs, including the NavDisplay framework, which is currently re-implementing this functionality separately, i.e. not yet using MapStructure.
 
== Layers ==
 
Following is the list of layers displayed by the G1000 system (see page 153 of the 190-00498-07 Rev. A), and mapping to the equivalent MapStructure Layer.
{| class="wikitable"
|-
! Layer !! MapStructure Layer !! Status !! Page || Notes
|-
| Flight Plan Route Lines || RTE.lcontroller || Requires styling || 190 ||
|-
| Flight Plan Route Waypoints || WPT.lcontroller RTE || Requires styling || 190 ||
|-
| Rivers/Lakes || VFRChart || || 148 || Currently using downloaded raster from web. shapefiles ?Perhaps generate similarly to Atlas, or could be vector data from scenery.
|-
| Topography Data || VFRChart || Synthetic || 145 || Height-map at chart-resolution. shapefiles Perhaps generate similarly to Atlas?
|-
| International Borders || || || shapefiles 148 || Vector data from scenery?
|-
| Track Vector || || || 156 || Forward looking display of track. Look-ahead time selectable.
|-
| Navigation Range Ring || || || the NavDisplay contains helpers to create range rings158 || Straightforward extension of APS.
|-
| Fuel Range Ring || || || 159 || Straightforward extension of APS.
|-
| Terrain Data || || || probably a dedicated Canvas element364 || Should be straightforward, or just a GeoTIFF/raster image for starters ?with exception of obstacles. Profile view also required.
|-
| Traffic || TFC.lcontroller || || 394,423 || Various options, each with different iconography and data displayed.
|-
| Airways || VFRChart || || 154 || Needs to be replaced with vector data
|-
| NEXRAD || || || 282 || Heaps of weather data with complex symbology.
|-
| XM Lightning Data || WXR || Change to symbol for lightning? || 294 || Optional usual caveat of using an online web service for fetching live data that is not in sync with the in-sim environment
|-
| Airports || APT.lcontroller , RWY || Require re-style based on size || 149, 163 ||
|-
| Runway Labels || RWY || || Needs to be added to RWY symbol. anything involving labels, may need decluttering supportShould be straightforward
|-
| Restricted || OpenAIP || || 182 || Currently using downloaded rasters. Would be better replaced with vector data
|-
| MOA (Military) || OpenAIP || || 182 || Currently using downloaded rasters. Would be better replaced with vector data
|-
| User Waypoints || || ||
|-
| Latitude/Longitude Grid || GRID || || would be also good to have for map-canvas.xml as well as the shuttle's trajectory map
|-
| NAVAIDs || APT, VOR, FIX, NDB || {{done}} Requires styling || 162 ||
|-
| Class B Airspaces/TMA || OpenAIP || || 182 || Currently using downloaded rasters. Would be better replaced with vector data
|-
| Class C Airspaces/TCA || OpenAIP || || 182 || Currently using downloaded rasters. Would be better replaced with vector data
|-
| Class D Airspaces || OpenAIP || || 182 || Currently using downloaded rasters. Would be better replaced with vector data
|-
| Other Airspaces/ADIZ || OpenAIP || || 182 || Currently using downloaded rasters. Would be better replaced with vector data
|-
| TFRs || || || 310 ||
|-
| Obstacles || OpenAIP || || 182 || Currently using downloaded rasters. Would be better replaced with vector data
|-
| Land/Country Text || || || shapefiles148 || Currently using raster data from web. Replace with POI?
|-
| Cities || VFRChart || || shapefiles?148 || Currently using raster data from web. Perhaps generate similarly to Atlas, or could be vector data from scenery.
|-
| Roads || VFRChart || || shapefiles?148 || Currently using raster data from web. Requires vector data from scenery
|-
| Railroads || VFRChart || || shapefiles?148 || Currently using raster data from web. Requires vector data from scenery
|-
| State/Province Boundaries || VFRChart || || shapefiles?148 || Currently using raster data from web. Requires vector data from scenery
|-
| River/Lake Names || VFRChart || || 148 || Currently using raster data from web. Replace with POI?|-| Selected Altitude Intercept Arc || || || 161 || Simple extention to APS|-| SafeTaxi (Optional) || RWY, TAXI || || 493 || We don't currently have the data to display taxiway identifier or holding points|-| ChartView (Optional) || || || 503 || Rendering of PDFs. Might be possible to integrate with NaviGraph chart data?|-| FliteChart (Optional) || || || 521 || Rendering of PDFs. shapefilesMight be possible to integrate with NaviGraph chart data?
|}

Navigation menu