|
From: merspieler <mer...@ai...> - 2018-05-06 19:05:26
|
James Turner:
> it’s implemented, and I think I remember testing it back in the day -
> indeed I think the airport diagram code uses it to extract the
> taxiways to renderer them? (For the Canvas-based airport diagram in
> the set airport location dialog)
>
> TAXI.symbol (in fgdata/Nasal/canvas/map) shows an example of iterating
over the data
I've tried that, it doesn't throw an error so far but it seems to be empty.
I've took a look at some groundnet xmls and EDDF has definitely taxiways
with names assigned. So I use that for testing.
my test code:
```
var apt = airportinfo("EDDF");
foreach( var taxi; apt.taxiways)
{
print(taxi.id);
}
```
This doesn't print anything.
(there it seems a bit in-consequently written... rwy code doesn't work
for twys and the other way around)
Sidi Liang:
> The read_airport_properties() is a function in io namespace.
> http://wiki.flightgear.org/Nasal_library/io#read_airport_properties.28.29
I've tried that too (on EDDF again) with the code example from the wiki:
```
var path = "/demo";
io.read_airport_properties("EDDF", "groundnet", path);
props.dump(props.globals.getNode(path));
```
This just creates an empty prop.
I've been running this on 2018.1 build with the d&c script with -s.
What I'd need is a list of taxiways containing the coordinates, the
heading and the id.
|