|
From: merspieler <mer...@ai...> - 2018-05-07 17:45:53
|
James Turner:
>
>
>> On 6 May 2018, at 20:05, merspieler <mer...@ai...> wrote:
>>
>> 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 <http://taxi.id/>);
>> }
>> ```
>> This doesn't print anything.
>
> But when you look at EDDF in the ‘set airport location’ dialog, do you see taxiways? We need to establish if this is a date problem or a code problem :)
>
> if you /do/ see taxiways in the dialog’s airport diagram, then you have data for EDDF, and it’s something in the code, which we can debug. But if you don’t see taxiways for EDDF in the dialog, trying to debug your code above (which looks okay to me from a quick glance) is not going to get us far.
my dialog looks like this: https://s20.postimg.cc/xshhp0y8d/EDDF.png
my EDDF.groundnet.xml contains lines like these:
<arc begin="159" end="160" isPushBackRoute="0" name="L" />
I guess these are the taxi ways... not all of my *groundnet.xml files
have something in the name.
Another thing that could make a change is if TerraSync or TerraGit is
used. As for me, I use TerraSync.
Sidi Liang:
Both code snippets give me at ZBAA the same results like on EDDF
|