20,741
edits
Canvas tile element: Difference between revisions
Jump to navigation
Jump to search
m
→Problem: https://forum.flightgear.org/viewtopic.php?f=31&t=37158#p364650
m (→Idea: https://forum.flightgear.org/viewtopic.php?f=31&t=37158) |
m (→Problem: https://forum.flightgear.org/viewtopic.php?f=31&t=37158#p364650) |
||
| Line 1: | Line 1: | ||
{{Stub}} | {{Stub}} | ||
== Intro == | |||
tiled web maps are obviously great for many reasons, but people without a broadband internet connection may still want to use a different tool, or even an offline solution in general. | |||
And like I said, there is the issue of mismatching data - FlightGear has never been particularly good at this, but there is now an increasing tendency to rely on "online functionality", i.e. there is a growing assumption that people do have an internet connection, and that they're online while using FlightGear - depending on whom you ask, that is not just controversial, but increasingly problematic.<ref>https://forum.flightgear.org/viewtopic.php?f=31&t=37158#p364650</ref> | |||
== Problem == | == Problem == | ||
Thanks to the Canvas system, we now have an increasing number of MFDs/avionics that use so called "slippy" maps - there remains the obvious issue that such a "slippy map" will usually be based on very different geo data than FlightGear's terrain (i.e. mismatching data).<ref>https://forum.flightgear.org/viewtopic.php?p=364640#p364640</ref> | Thanks to the Canvas system, we now have an increasing number of MFDs/avionics that use so called "slippy" maps - there remains the obvious issue that such a "slippy map" will usually be based on very different geo data than FlightGear's terrain (i.e. mismatching data).<ref>https://forum.flightgear.org/viewtopic.php?p=364640#p364640</ref> | ||