|
|
| Line 49: |
Line 49: |
| |author=<nowiki>Torsten</nowiki> | | |author=<nowiki>Torsten</nowiki> |
| |date=<nowiki>Mon Mar 17</nowiki> | | |date=<nowiki>Mon Mar 17</nowiki> |
| }}
| |
| }}
| |
|
| |
| {{FGCquote
| |
| |When we have vector road data at runtime, we can do the following:
| |
| * render it in moving-map displays - either real ones (Garmin G1000 / G430) or the map dialog
| |
| * use it to drive building outline creation as Thomas was suggesting
| |
| * animate traffic on the roads, as point lights at night or even meshes in daytime (the important one...)
| |
| * generate tile overlay textures dynamically (and based on view distance) to show the roads on the terrain surface. (And the detail of this texture can include road markings / borders based on distance from the viewer / view angle / etc)
| |
| |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33064873/
| |
| |title=<nowiki>Re: [Flightgear-devel] Future city terrain strategy</nowiki>
| |
| |author=<nowiki>James Turner</nowiki>
| |
| |date=<nowiki>2014-11-21</nowiki>
| |
| }} | | }} |
| }} | | }} |
| Line 73: |
Line 60: |
| |description=Stub for exposing moving map support as a dedicated Canvas element | | |description=Stub for exposing moving map support as a dedicated Canvas element |
| }} | | }} |
|
| |
|
| |
|
| |
|
| == CanvasGeoTIFF == | | == CanvasGeoTIFF == |