Re: [Flightgear-devel] Helipad thresholds

[TheFGFSEagle <the...@gm...>]

> But this would make the NavCache build much much slower
No thanks, it's slow enough ! ;)

Am Di., 4. Juli 2023 um 17:59 Uhr schrieb James Turner <ja...@fl...
>:

>
>
> On 1 Jul 2023, at 18:24, Florent Rougon <f.r...@fr...> wrote:
>
> AFAIK, the supported types of XML files in this context are:
>
>  groundnet, ils, procedures, runway_rename, threshold, twr
>
> I'm wondering whether to apply the rule to all of them or if, say,
> “procedures” would be better with an exception. I assume a few people
> have $FG_SCENERY like so:
>
>   some_custom_sceneries:procedures:terrascenery
>
> with the “procedures” folder containing a gazillion *.procedures.xml
> files (possibly obtained from Navigraph). If we strictly apply the
> proposed rule, said procedure files wouldn't be used for airports that
> have an apt.dat snippet in some_custom_sceneries. Of course,
> some_custom_sceneries could ship appropriate procedure files, though.
>
> Would it make sense to let XMLLoader::findAirportData() work as it does
> now for the special case of procedure files? That would be a bit more
> complicated, of course…
>
>
> Yes I’m pretty sure procedures needs to be special cased because we have
> ‘procedures only’ scenery dirs. Sorry.
>
> Another option could be to process the ‘extension’ XML files
> (runway_rename, ils, threshold, twr) when building the NavCache, when the
> apt.dat path is known? But this would make the NavCache build much much
> slower.
>
> The ground-net and procedures files are different because they add in new
> data, rather than overriding apt.dat  data
>
> Kind regards,
> James
>
>
> _______________________________________________
> Flightgear-devel mailing list
> Fli...@li...
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>