Re: [Flightgear-devel] Pacific Northwest Scenery Available
If you want to get 'really' fancy, rwy_prec.cxx and rwy_visual.cxx should also be updated at line 101 with the same fix. Cheers John -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Pacific Northwest Scenery Available
It seems to me, on line 97 of rwy_nonprec.cxx, the current line: double length = rwy_info.length / 2.0 + 2.0; should be: // we also check for the displaced threshold, which may make the runway too short (old KVUO bug). double length = ((rwy_info.length - (rwy_info.disp_thresh1 + rwy_info.disp_thresh2)) / 2.0) + 2.0; Please let me know if I am wrong, I am not all that great with C++. For instance, it looks to me as if this just prints an error message, but if this is tripped the function should break and print basic markings instead. Yours John Holden -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Pacific Northwest Scenery Available
Ron Jensen wrote: Martin: Can we PLEASE ungzip apt.dat in the repository so we can track changes to it! The GIT repository you mean ? Ask those who decided do put a compressed file there, _I_ am just continuing an old tradition. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Pacific Northwest Scenery Available
Martin wrote: Ron Jensen wrote: Martin: Can we PLEASE ungzip apt.dat in the repository so we can track changes to it! The GIT repository you mean ? Ask those who decided do put a compressed file there, _I_ am just continuing an old tradition. Don't we unzip all the navaids stuff on the fly? I put carrier_nav.dat and TACAN-freq.dat in there as zipped files on that understanding. A long time ago, mind, I might have it all wrong. Vivian -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Pacific Northwest Scenery Available
Martin Spott wrote: Ron Jensen wrote: Martin: Can we PLEASE ungzip apt.dat in the repository so we can track changes to it! The GIT repository you mean ? Ask those who decided do put a compressed file there, _I_ am just continuing an old tradition. BTW, are you still referring to this one ? http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg28068.html Please consider my response c) here: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg28111.html before blaming me/us on behalf of your private adventure. _I_ still consider FG as sort of a collaborative work, so if _you_ are taking a different position in this very context of the 'apt.dat' file, tell me why I should care. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Pacific Northwest Scenery Available
On Friday 08 April 2011 13:44:49 Martin Spott wrote: Martin Spott wrote: Ron Jensen wrote: Martin: Can we PLEASE ungzip apt.dat in the repository so we can track changes to it! The GIT repository you mean ? Ask those who decided do put a compressed file there, _I_ am just continuing an old tradition. BTW, are you still referring to this one ? http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg28068 .html Yes Please consider my response c) here: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg28111 .html before blaming me/us on behalf of your private adventure. _I_ still consider FG as sort of a collaborative work, so if _you_ are taking a different position in this very context of the 'apt.dat' file, tell me why I should care. 1. Well, someone updated KVUO with a 'bad' runway marking type. Without a history we can't know who, so we can't ask why. Perhaps _you_ have a record, but that is not 'collaborative work.' 2. I have played with many airports while working on genapts (and yes, I have shared the genapts changes back.) The work I've done on the airports may or may not reflect real life so those changes should not be necessarily propagated back to the master data. 3. Without a git copy of apt.dat I can't tell what I've changed and what I have not, so I'm not sure what to 'share' back. Simply gunzipping the current binary blob and diff-ing doesn't do it, because I don't know what in the blob changed externally and what I changed while playing. So by keeping the entire file gzipped you are blocking me (and others) from effectively collaborating. 4. I think I have shared a few airports back through Robin (KHIF, 42U, CYKF, CNC4 come to mind) 5. Just because I prefer to _not_ use your scenery and roll my own does not make me an un-collaborative person. V/r Ron -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Pacific Northwest Scenery Available
Ron Jensen wrote: On Friday 08 April 2011 13:44:49 Martin Spott wrote: Please consider my response c) here: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg28111 .html before blaming me/us on behalf of your private adventure. _I_ still consider FG as sort of a collaborative work, so if _you_ are taking a different position in this very context of the 'apt.dat' file, tell me why I should care. 1. Well, someone updated KVUO with a 'bad' runway marking type. Without a history we can't know who, so we can't ask why. Perhaps _you_ have a record, but that is not 'collaborative work.' As already stated several times (on this list), the collection which I started and which is now available via the file at: http://mapserver.flightgear.org/apt.dat.gz and the list at: http://mapserver.flightgear.org/Apt.Dat.txt isn't maintained in the style like Robin's airport collection is. It's just a minimal solution for the sole purpose of preserving the various updates and additions, which were floating around in forum- or mailing list posts or on random websites, from getting lost in space and to make all of them available to everyone with as little effort as possible. It's far from being perfect but I think it's serving this minimal requirement pretty well. Indeed, if there were the need to identify the author of a particular airfield layout (may it be for licensing issues) I _am_ able to track it down - but I hope I'll never have to. But that's not the point. If you're identifying whichever issue concerning one of the layouts, I think the best you can do is to post the finding on this very list, as you did in the current case. We don't necessarily have to identify the author or a particular layout just for the simple purpose of applying an obvious fix. I the case of KVUO the airfield layout was directly exported from TaxiDraw and the tool to import the file into a PostGIS database didn't complain, thus I assume there's a mismatch between the logic in TaxiDraw and the specific requirements of 'genapts'. I assume - but I didn't verify ;-) BTW, if anyone would like to nicely maintain the 'apt.dat' file in a different, better (TM :-) way than I do, I'll happily hand the 'job' over to whomever volunteers, I'm happy about every responsibility I can shove off my shoulders. I can offer webspace, processing- and download bandwidth to the future maintainer, if that's an issue, thus keeping a public copy of the file at it's current 'home' is an option but not a requirement. 3. Without a git copy of apt.dat I can't tell what I've changed and what I have not, so I'm not sure what to 'share' back. Simply gunzipping the current binary blob and diff-ing doesn't do it, because I don't know what in the blob changed externally and what I changed while playing. So by keeping the entire file gzipped you are blocking me (and others) from effectively collaborating. Oh, because _you_ are unable to version your own !! local copies of the file, _I_ am blocking you and others Are you serious ? 4. I think I have shared a few airports back through Robin (KHIF, 42U, CYKF, CNC4 come to mind) Excellent, did you check wether Robin has incorporated these updates into his release until August 2008 ? 5. Just because I prefer to _not_ use your scenery and roll my own does not make me an un-collaborative person. I'm not talking about using 'my' Scenery, I'm talking about sharing airfield layout updates. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Pacific Northwest Scenery Available
Arnt Karlsen wrote: On Wed, 6 Apr 2011 20:06:40 -0700 (PDT), J. wrote in message This scenery product is released under the GPLv2. ..thank you both, but _which_ GPLv2, GPLv2-only or GPLv2-and-later? Can we stop this ? GPLv2 is pretty unambiguous: GPLv2 ! Oh my Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Pacific Northwest Scenery Available
Martin: Can we PLEASE ungzip apt.dat in the repository so we can track changes to it! On Wednesday 06 April 2011 21:06:40 J. Holden wrote: First and foremost, a huge THANK YOU goes out to Martin Spott. Without his help, including giving access to resources I otherwise would not have, I would have not been able to create the underlying data for this scenery much less generate it. So thank you, Martin. This scenery product is released under the GPLv2. There are over eight square degrees of scenery to download - I believe eight times the area of the Innsbruck scenery. For the most part, I think it is fantastic, especially compared to the area's current scenery build. SRTM-1 is used for elevation. There are some problems with elevation, especially around airports, so this should be treated as a beta product. Also, stream and road data is largely still vmap0 data and not as accurate as the rest of the scenery, so some odd placement is probable. There are also some other minor problems with the scenery the majority of users will not notice. Developers of genapts should note KVUO - a part of the runway does not appear in either the current scenery or the new scenery, probably due to a bug in this program. The problem is in the definition of KVUO in apt.dat. It is specified as having non-precision markings, but there is not room for those marking. It should have basic marking instead. The runway is 3263 feet minus 762 feet for the overrun so its only 2500 feet left for the runway. We need something like 2600 feet to draw non-precision markings. 1 25 0 0 KVUO PEARSON FLD - 10 45.620454 -122.656491 08x 98.220 3263 .0762 . 60 231331 01 0 2 0.25 0 0300.0300 + 10 45.620454 -122.656491 08x 98.220 3263 .0762 . 60 231331 01 0 1 0.25 0 0300.0300 http://data.x-plane.com/file_specs/Apt810.htm#RwyMarkingCodes Also, it is very important to clean up before running genapts. The following directories need to be manually purged. $work/APTBoundary/ $work/AirportArea/ $work/AirportObj/ Right now your *.stg files have two instances of each airport because you ran genapts twice. That is probably the source of your elevation problem around the airports since it looks like you had no elevation data on the first run. Thanks, Ron -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Pacific Northwest Scenery Available
On Thursday 07 April 2011 10:52:54 Ron Jensen wrote: The problem is in the definition of KVUO in apt.dat. It is specified as having non-precision markings, but there is not room for those marking. It should have basic marking instead. The runway is 3263 feet minus 762 feet for the overrun so its only 2500 feet left for the runway. We need something like 2600 feet to draw non-precision markings. 1 25 0 0 KVUO PEARSON FLD - 10 45.620454 -122.656491 08x 98.220 3263 .0762 . 60 231331 01 0 2 0.25 0 0300.0300 + 10 45.620454 -122.656491 08x 98.220 3263 .0762 . 60 231331 01 0 1 0.25 0 0300.0300 http://data.x-plane.com/file_specs/Apt810.htm#RwyMarkingCodes BTW, the aerial views at http://www.bing.com/maps/?cp=45.620453|-122.656488style=hlvl=17v=1 And http://mpmap02.flightgear.org/?ll=45.6204,-122.656z=17 both show basic markings and http://www.airnav.com/airport/KVUO says basic markings as well. Ron -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Pacific Northwest Scenery Available
Ron: Thanks for the help with the airports, I'll recompile the scenery to fix the problem. I'm still learning my way around TerraGear. Is the problem with KVUO's definition, or rather within the program? While a quick aerial check of KVUO shows the runway does have basic markings, no reason why there shouldn't be a check in the program to make sure there is length to draw non-precision markings, since there may be other problem airports in the world. Cheers John -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
