20,741
edits
Canvas tile element: Difference between revisions
Jump to navigation
Jump to search
→Motivation
m (→Motivation) |
|||
| Line 21: | Line 21: | ||
There is the long-standing idea to use FlightGear itself to render a map to a texture, e.g. based on the atlas/map source code (GPL compatible), quoting TorstenD: | There is the long-standing idea to use FlightGear itself to render a map to a texture, e.g. based on the atlas/map source code (GPL compatible), quoting TorstenD: | ||
: What I have in mind for the map is to render the map tiles (small 256x256px fragments of a map) from flightgear scenery data on the fly when the user requests them from within the map application. Thats how openstreetmaps works and I like the idea of reusing proven concepts. There is no need at all - in fact, it's not even desireable - to do that in the main loop. Running a standalone application (or call it process if you like) creating and serving the tiles will add no load to the FlightGear process, no matter how complex the map is.<ref>https://forum.flightgear.org/viewtopic.php?f=31&t=21972&p=203544#p203544</ref> | : What I have in mind for the map is to render the map tiles (small 256x256px fragments of a map) from flightgear scenery data on the fly when the user requests them from within the map application. Thats how openstreetmaps works and I like the idea of reusing proven concepts. There is no need at all - in fact, it's not even desireable - to do that in the main loop. Running a standalone application (or call it process if you like) creating and serving the tiles will add no load to the FlightGear process, no matter how complex the map is.<ref>https://forum.flightgear.org/viewtopic.php?f=31&t=21972&p=203544#p203544</ref> | ||
== Idea == | |||
{{See also|Canvas Image]} | |||
Given that we do have existing code to render such maps, and that the Canvas system does have support for loading raster images (sc::Image), this would be the most straightforward option to ensure that there is no mismatch between a moving map and a corresponding radar display, because it'd be using the same underlying terrain/vector data. | |||
== References == | == References == | ||
{{Appendix}} | {{Appendix}} | ||