20,741
edits
No edit summary |
|||
Line 13: | Line 13: | ||
James originally implemented the a moving navigational [[Map]] as a custom [[PUI]] widget - it's *not* an Atlas-replacement, or an [[MPMap]] replacement, i.e. not intended to also display terrain elevation <ref>https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27097.html</ref> | James originally implemented the a moving navigational [[Map]] as a custom [[PUI]] widget - it's *not* an Atlas-replacement, or an [[MPMap]] replacement, i.e. not intended to also display terrain elevation <ref>https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27097.html</ref> | ||
An Atlas- style renderer as another layer is possible, it'd also let | An Atlas- style renderer as another layer is possible, it'd also let people builda 'map' dialog box with navaids and airways overlaid, like the map UIs in MSFS / X-Plane / Fly. <ref>https://sourceforge.net/p/flightgear/mailman/message/20012110/</ref> | ||
In order to feed imagery from tools like Atlas or moving maps in general from a network server, you'd want to look at protocols like WMS and the servers which | In order to feed imagery from tools like Atlas or moving maps in general from a network server, you'd want to look at protocols like WMS and the servers which |