20,741
edits
A NavDB web service: Difference between revisions
Jump to navigation
Jump to search
→Background
| Line 3: | Line 3: | ||
{{WIP}} | {{WIP}} | ||
--> | --> | ||
== Challenges == | |||
I think your use scenario highlights a fundamental problem with our scenery approach, in dealing with historical periods. We just have no good way to have most of the nav data be current, but some portions reflect the world as it was in 1960 or 1980. I would prefer we maintained some global historical data sets of nav data, but in principle this would also mean maintaining historical scenery and airports, and selecting / de-selecting models based on data ranges. (So buildings appear based on their construction / demolition date). Obviously that’s a colossal amount of work which is not going to happen without effort. <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35383393/ | |||
|title = <nowiki> Re: [Flightgear-devel] apt.dat - add local version ? </nowiki> | |||
|author = <nowiki> James Turner </nowiki> | |||
|date = Sep 21st, 2016 | |||
|added = Sep 21st, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
== Background == | == Background == | ||
{{Main article|Navdata cache}} | {{Main article|Navdata cache}} | ||