Re: [Flightgear-devel] TaxiDraw-0.1.0 available.
On 12/10/03 at 7:05 AM Ivo wrote: On Monday 08 December 2003 12:00, David Luff wrote: http://www.nottingham.ac.uk/~eazdluf/TaxiDraw-0p1p0-src.tar.gz Source [74K], requires wxWindows to compile (wxGTK-dev on Linux). I tried it for the first time today, and I ran into some strange things: http://ivop.free.fr/fgfs/taxidraw.0.1.0.ksfo.png http://ivop.free.fr/fgfs/taxidraw.0.1.0.eham.png All runways and taxiways seem to get centered around the center of the airport and not where they are supposed to be. I also tried v0.0.8, upgraded wxWindows to v2.4.2 (instead of 2.4.0, which I had already installed on my system), but all combinations ended up with the same result. I'm running Linux, kernel 2.4.21, gcc 3.2.2 and glibc 2.3.1. I used runways.dat from a cvs checkout on december 2nd 6.31am. Am I missing something, as in how to use this program, or can this be considered a bug? Its definately a bug :-( Unfortunately I can't replicate it - I compile and run it on both Linux (using gcc-3.2.x where x is a number I don't know off-hand!) and Windows and I've not had this problem. As you say, everything is being drawn on the airport center instead of its own center. Its really hard to debug stuff I can't replicate - I'll have a look at the code and try and spot something. Do you mind if I send you a version offline with some extra debugging output enabled? Also, while viewing KSFO, I get a segfault when I zoom out 33 times with gridlines enabled, but not if they're disabled. File-Exit never works for me, whether I have an airport loaded or not. I always have to kill the window. Yes, there's various ways to kill it! In this case you've run up against the hard-coded limit to the number of gridlines. Switching to UTM projection before loading an airport, or switching to OSGB36 (UK) projection whilst in the US is also likely to seg-fault it. At the moment the program is young and I'm more concerned with bug-fixes and feature additions that affect normal operation. Thanks for the feedback, Cheers - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] TaxiDraw-0.1.0 available.
On 12/10/03 at 9:50 AM David Luff wrote: Its definately a bug :-( Unfortunately I can't replicate it - I compile and run it on both Linux (using gcc-3.2.x where x is a number I don't know Oops, no, I use 3.2 for FlightGear, but I'm pretty sure I used the stock Woody compiler for TaxiDraw, which I think is 2.95.x. However, David Megginson has reported compiling it with gcc-3.3 with only minor fixes needed which are in from 0.0.7 onwards. Not sure what Jon Stockill uses. Cheers - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] TaxiDraw-0.1.0 available.
On 12/8/03 at 11:00 AM David Luff wrote: http://www.nottingham.ac.uk/~eazdluf/TaxiDraw4.jpg The fifth shows that one of the FG runways extends beyond the runway in the photo. Either the FG data for this runway is wrong, or it's been extended since the photo was taken. Can anyone who knows KDPA tell me which is currently correct? OK, Google had the answer - the runway has been extended since the photo was taken. Having looked at some of the other US airports this is a not uncommon problem - several runways have been extended since the photography was taken, and at least two major runways are completely absent from the photos in the 20 or so airports I looked at. Use with caution when the runways don't match and don't assume the photo is always right!!! I couldn't find the date the photo's were taken during a cursory search, but I did find the copyright again: The U.S. Geological Survey (USGS) provides the Microsoft® TerraServer site with images and maps of the United States. The images are in the public domain, and are freely available for you to download, use and re-distribute. If you download and use any images, the TerraServer team and the USGS appreciate a reference to our work on this project. Perhaps we should add Micros... to the thanks file ;-)) Cheers - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] TaxiDraw-0.1.0 available.
On Wed, 10 Dec 2003, David Luff wrote: On 12/10/03 at 9:50 AM David Luff wrote: Its definately a bug :-( Unfortunately I can't replicate it - I compile and run it on both Linux (using gcc-3.2.x where x is a number I don't know Oops, no, I use 3.2 for FlightGear, but I'm pretty sure I used the stock Woody compiler for TaxiDraw, which I think is 2.95.x. However, David Megginson has reported compiling it with gcc-3.3 with only minor fixes needed which are in from 0.0.7 onwards. Not sure what Jon Stockill uses. gcc version 3.2.2 (on slackware 9.1) -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] TaxiDraw-0.1.0 available.
David Luff writes: I couldn't find the date the photo's were taken during a cursory search, If you click on the info button when in the interactive mode you will get some meta-data to include the 'date' of the photos For example Image Info Info: Digital Ortho-Quadrangles (digitized and othro-rectified aerial photographs Provider: U.S. Geological Survey. To find out more about this image, visit the USGS's Digital Backyard. Image Size: 600 pixels wide by 400 pixels high. Resolution: Each pixel represents 16 meter resolution by 16 meter resolution of earth. Date: Photographed on 10 Mar 1995 digitized on 12 May 1998 Projection: The data below is projected in the Universal Transverse Mercator (UTM) Zone 19 projection using the North American datum of 1983. The decimal latitude and longitude in degrees and the UTM coordinates in meters are shown for each image tile. Source File: H.hyannis_MA.ver_1.O4107022.SWS.916731 received on tape/group 294 Load Date: 2/22/2000 8:42:16 PM via job DOQ-Tape-294 HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] TaxiDraw-0.1.0 available.
On Monday 08 December 2003 12:00, David Luff wrote: http://www.nottingham.ac.uk/~eazdluf/TaxiDraw-0p1p0-src.tar.gz Source [74K], requires wxWindows to compile (wxGTK-dev on Linux). I tried it for the first time today, and I ran into some strange things: http://ivop.free.fr/fgfs/taxidraw.0.1.0.ksfo.png http://ivop.free.fr/fgfs/taxidraw.0.1.0.eham.png All runways and taxiways seem to get centered around the center of the airport and not where they are supposed to be. I also tried v0.0.8, upgraded wxWindows to v2.4.2 (instead of 2.4.0, which I had already installed on my system), but all combinations ended up with the same result. I'm running Linux, kernel 2.4.21, gcc 3.2.2 and glibc 2.3.1. I used runways.dat from a cvs checkout on december 2nd 6.31am. Am I missing something, as in how to use this program, or can this be considered a bug? Also, while viewing KSFO, I get a segfault when I zoom out 33 times with gridlines enabled, but not if they're disabled. File-Exit never works for me, whether I have an airport loaded or not. I always have to kill the window. Taxidraw looks very good and the screenshots I saw of Jon Stockill's work on UK airports were very impressing! --Ivo ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] TaxiDraw-0.1.0 available.
On Wednesday 10 December 2003 07:05, Ivo wrote: [...] installed on my system), but all combinations ended up with the same result. I'm running Linux, kernel 2.4.21, gcc 3.2.2 and glibc 2.3.1. I used runways.dat from a cvs checkout on december 2nd 6.31am. I tried the Win32 binary of v0.1.0 on Windows 98(FE) in VMware and it works great. It displays the airport as it is supposed to be. Am I missing something, as in how to use this program, or can this be considered a bug? Also, while viewing KSFO, I get a segfault when I zoom out 33 times with gridlines enabled, but not if they're disabled. File-Exit never works for me, whether I have an airport loaded or not. I always have to kill the window. TaxiDraw does 'segfault' (the windows equivalent) while zooming out, but it takes one more zoom. Might be because my VMware window is 1024x768 and X runs at 1152x864. EHAM, for example, takes 31 zooms, probably because the airport is larger. --Ivo ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] TaxiDraw-0.1.0 available.
TaxiDraw-0.1.0 is now available from: http://www.nottingham.ac.uk/~eazdluf/TaxiDraw-0p1p0-w32bin.zip Windows binary [375K] and http://www.nottingham.ac.uk/~eazdluf/TaxiDraw-0p1p0-src.tar.gz Source [74K], requires wxWindows to compile (wxGTK-dev on Linux). *** Summary of changes from 0.0.8 to 0.1.0: Added support for displaying a background image to guide taxiway position. Fixed the bug where accelerater keys (Ctrl+...) wouldn't work under GTK if the same key was used for a non-Ctrl shortcut. Added surface type to rwy properties dialog (display only - can't be edited currently). Added a lurid-colour option to make the taxiways and runways show up better against photographic backgrounds - off by default. Added an option to disable solid-shading and display the taxiway/runways as outline only - off by default. Probably more stuff I can't think of! *** A series of screenshots showing the background display in action are at: http://www.nottingham.ac.uk/~eazdluf/TaxiDraw0.jpg http://www.nottingham.ac.uk/~eazdluf/TaxiDraw1.jpg http://www.nottingham.ac.uk/~eazdluf/TaxiDraw2.jpg http://www.nottingham.ac.uk/~eazdluf/TaxiDraw3.jpg http://www.nottingham.ac.uk/~eazdluf/TaxiDraw4.jpg The first shows the current FG runways for DuPage (KDPA) overlaid on USGS 1m/pixel photography. The second shows some taxiways added. The third is a close up of the taxiways. The forth shows the outline shading option. The fifth shows that one of the FG runways extends beyond the runway in the photo. Either the FG data for this runway is wrong, or it's been extended since the photo was taken. Can anyone who knows KDPA tell me which is currently correct? How to use the Background Image function. ___ First you need an image, obviously! Public domain images from the USGS at 1m/pixel are available for the entire USA from terraserver-usa.com as far as I can see. Note the '-usa' in the url - the similarly named terraserver.com has nothing better than 8m/pixel for free. For other countries, the only ortho images available are likely to be non-redistributable. I am not a copyright lawyer (in fact I'm not a lawyer full stop :-)), and have absolutely no idea whereabouts using a copyrighted, non-redistributable image to guide creation of an entirely different and separate redistributable image falls between legitimate use of reference material to create an original work and non-legitimate creation of a derivative work from copyrighted material. Obviously each user will have to make their own call on this, but it might be considered prudent to avoid displaying screenshots of taxiways overlaid over copyrighted images. At the moment, the calibration function only calibrates position from one point and requires manual entry of the scale, so you need an image in one of the supported projections, and need to know the scale in meters per pixel. Currently supported projections are UTM (hardwired to NAD83) which is what the USGS photography is in, and OSGB36 (UK grid) which is what most (all?) UK ortho-photography is likely to be in. Some available photography is therefore currently unusable, such as the Massachusetts GIS photography, which is in the Mass State Plane coordinate system. I plan to add the ability to calibrate rotation and scale from two points in the future, to allow any ortho-photography to be used. So... load an image using the load image function. Only jpegs are currently supported. Load an airport. Set the projection as appropriate. Click 'calibrate image' from the 'Background' menu. You will be prompted for the scale in meters/pixel. Then you will be prompted to click one point on the FlightGear airport, followed by the corresponding point on the background. Before the first calibration the image can't be moved or scaled, so you probably can't get the same point, but calibration can be performed as many times as desired, and the image can be scaled and panned on subsequent calibrations. The scale prompt is not-rerun, so if you get it wrong you need to reload the image, which resets the state to uncalibrated. When happy, the calibration can be saved, and then reloaded on a subsequent session. Acknowledgements The UTM implementation came from Fred Bouvier, who says he got it from Norman Vine, and was apparently written by one Fred M. Erickson, so thanks to all of those! Disclaimer There will be bugs!!! I know about the one where the grid can spew random lines across the screen when the right hand line slants of the edge of the screen, which it can do now the extra projections have been added - as a temporary workaround this can be eliminated by resizing the window. I distinctly remember when I wrote it thinking 'this will break if the line ever slants off the edge of the screen' but I can't now remember why! Doh! Now I know why my wife bought me Homer Simpson socks last Christmas! Have fun! Cheers - Dave
