You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While we're on parking radii, it appears that the radius of the stand and the shape of the stand differ. flightgear-airports does not see the error, but "travis" does.
In the first pic there are no radius intersects during edit mode and the check process doesn't generate an error.
This is same spot after save:
But I believe that the final check on the terrasync pull sees it like the second pic.
The text was updated successfully, but these errors were encountered:
Ahh! Maybe this is the reason so many airports I've worked on don't show "intersection" issues in FGAirports but fail for this reason on the new groundnet checker.
While we're on parking radii, it appears that the radius of the stand and the shape of the stand differ. flightgear-airports does not see the error, but "travis" does.
![Screen Shot 2020-07-08 at 11 12 20 AM](https://user-images.githubusercontent.com/67807217/86970912-f0faf100-c10b-11ea-8c39-f2bbd0542386.png)
![Screen Shot 2020-07-08 at 11 12 07 AM](https://user-images.githubusercontent.com/67807217/86970920-f5bfa500-c10b-11ea-8078-0cce3b3a18bf.png)
In the first pic there are no radius intersects during edit mode and the check process doesn't generate an error.
This is same spot after save:
But I believe that the final check on the terrasync pull sees it like the second pic.
The text was updated successfully, but these errors were encountered: