How dealing with stopway ?

Hello,

I am trying to improve the realism of my favorite airport, with taxidraw.
I use Terragear to check the result before submitting the change to Robin=
 Peel
Database.

Unfortunaltely one of my main problem is that Terragear do not take into =
account
the stopways.

My runway is well defined in the Robin Peel data base (X-Plane 8.10 and l=
ater
based upon DAFIF/AIRAC cycle 200510), exactly like defined in official
documents.
But the two stopways don't appears in FligtGear.

I could transform "stopway" distance in "Displaced Threshold" distance, t=
he
result is very closed to real world (with the good mark on the stopways),=
 but i
don't like the idea of modifying the data base to bypass a TerraGear "bug=
".

I propose the following modifications to Terragear code.
It works for one airport, I don't know for others.
It should, but perhaps people won't agree with this solution depending on=
 what
they want to see at the place of the stopway.
In my case aerial photography show it like a Displaced Threshold.
Nowday, there is absolutly nothing at the place of stopway in FG.

I hope someone more accurate than me with this project, will propose the =
right
and definitive solution, to solve this problem.

Thanks to all of you, for the great job done, to develop and maintain,
FlightGear
and others tools.

Regards,
GBo.

-------
$ diff build.cxx.org build.cxx
420a421,448
>
>               // To bypass the fact that Terragear do not care of stopw=
ay.
>               // Now a stopway is consider like a Displaced Threshold"
>               if( (rwy.stopway1>0) || (rwy.stopway2>0) ){
>                       rwy.disp_thresh1+=3Drwy.stopway1;
>                       rwy.disp_thresh2+=3Drwy.stopway2;
>                       rwy.length+=3Drwy.stopway1+rwy.stopway2;
>                       double alt=3D0., lat1=3D0., lon1=3D0., az1=3D0.,
shift_distance=3D0., lat2=3D0., lon2=3D0., az2=3D0.;
>                       lat1=3Drwy.lat;
>                       lon1=3Drwy.lon;
>                       shift_distance=3D(rwy.stopway2-rwy.stopway1) / 2 =
*
SG_FEET_TO_METER;
>                       az1=3Drwy.heading;
>                       // Give a shift to the runway to keep it at the s=
ame
place in case stopway's lenght are not symetric
>                       geo_direct_wgs_84 (alt, lat1, lon1, az1,
shift_distance,&lat2, &lon2, &az2);
>                       // I don't understand what apt_lat/lon are for
>                       // but I'am doing this correction to be transpare=
nt
>                       apt_lat -=3D rwy.lat;
>                       apt_lon -=3D rwy.lon;
>                       rwy.lat=3Dlat2;
>                       rwy.lon=3Dlon2;
>                       apt_lat +=3D rwy.lat;
>                       apt_lon +=3D rwy.lon;
>                       // To prevent doing anything else with this now
>                       rwy.stopway1=3D0.;
>                       rwy.stopway2=3D0.;
>               }


_______________________________________________
Terragear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/terragear-devel
2f585eeea02e2c79d7b1d8c4963bae2d