20,741
edits
mNo edit summary |
|||
| Line 16: | Line 16: | ||
== CanvasShapefile == | == CanvasShapefile == | ||
{{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> | |||
}} | |||
}} | |||
<references/> | |||
{{Custom_Canvas_Element | {{Custom_Canvas_Element | ||
| Line 23: | Line 40: | ||
|description=Stub for exposing OSG/GDAL shapefile support as a dedicated Canvas element | |description=Stub for exposing OSG/GDAL shapefile support as a dedicated Canvas element | ||
}} | }} | ||
== CanvasGeoTIFF == | == CanvasGeoTIFF == | ||