Re: [Flightgear-devel] navradio
On 11 Sep 2009, at 06:15, Ron Jensen wrote: ICAO Annex 10 Volume 1 gives a great amount of information on the nav radio system in general. Chapter 3 would be a good read for anyone working on the nav radio code. There is an online version here: http://www.scribd.com/doc/5509183/Annex10-ICAO Cheers Ron, that's a good link. Regards, James -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Glideslope/LOC reception improvements
I've updated both of your/John Denker's glideslope/LOC patches against current trunk, hopefully correctly, and done quite a bit more testing. It's good practice for my ILS approaches! I'm reasonably happy that all the numbers coming out are plausible, so my inclination at this point is to commit to trunk, and let people with more knowledge of the real world test. One major remaining issue is the nav-radio code picking the 'wrong end' LOC/GS, which is a separate mess. I'm going to verify that penaltyForNav() (in navlist.cxx) is behaving correctly, but that's a short term fix; longer term, I've some ideas to ensure only one end of a paired ILS installation is active. Current patch is attached, comments appreciated as always. Regards, James jsd-glideslopes.patch Description: Binary data -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
Please consider whether the snotty supercilious response you have just given is conducive to encouraging others to help. This project is only going to grow and will need all the help it can get at a variety of levels. Your attitude will do nothing to assist there. I humbly apologise for not picking up on the difference between colocation and frequency pairing. It would have been far better to have simply ignored my useless contribution but you took it upon yourself to issue a pointless smackdown. Luckily, I have been lurking here for a while and know that your attitude is not truly representative. Others may not be so fortunate. John Denker wrote: On 09/10/09 14:11, willie wrote: I think the pairing of a DME with a VOR is unchallenged. People (including me) are doubtful about the pairing of a DME with an NDB, Here's a real-world discussion showing that they really do exist. http://www.pprune.org/archive/index.php/t-77933.html It shows no such thing. The topic of this sub-thread is NDB/DME frequency pairing, not NDB/DME collocation. 1) There is no doubt that VOR and DME can be collocated. 2) There is no doubt that there is frequency pairing for collocated VOR/DME. The pairing scheme for DME/VOR, DME/MLS, and DME/ILS/MLS are documented starting on page 3-100 of ICAO Annex 10 Volume 1 Aeronautical Communications. 3) There is no doubt that NDB and DME can be collocated. 4) There is considerable doubt that any real-world ground station implements frequency pairing for NDB/DME. No evidence of such pairing has been adduced. 5) There is considerable doubt that any real-world cockpit instrument implements frequency pairing for NDB/DME. No evidence of such pairing has been adduced. If NDB/DME frequency pairing exists, perhaps somebody would be kind enough to tell us what the pairing scheme is, and/or give an example of a real-world instrument that implements such pairing. Otherwise we will continue to assume that the lack of any such pairing within FGFS is entirely realistic. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Best Regards Willie Fleming -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Error checking out CVS version of OpenSceneGraph
On Thursday 10 Sep 2009, Csaba Halász wrote: On Thu, Sep 10, 2009 at 6:13 PM, Randall Green randall.gr...@wright.edu wrote: These are the instructions for checking out CVS OSG that are given: cvs -d:pserver:anonym...@openscenegraph.cvs.sourceforge.net:/cvsroo t/openscenegraph login cvs -z3 -d:pserver:anonym...@openscenegraph.cvs.sourceforge.net:/cvsroo t/openscenegraph co -P modulename What is the modulename? I tried different things but nothing works. OSG has moved to SVN. Use this command: svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk OpenSceneGraph Note: it would have taken just a minute to go to the OSG web site and find this information for yourself. I think your 'note' is a little unfair: we should not provide instructions that don't work and then tell people who try to follow those instructions that they should have figured out the correct instructions for themselves. LeeE -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Error checking out CVS version of OpenSceneGraph
Where are the misleading instructions located? Thanks, Curt. On Fri, Sep 11, 2009 at 7:39 AM, leee wrote: On Thursday 10 Sep 2009, Csaba Halász wrote: On Thu, Sep 10, 2009 at 6:13 PM, Randall Green randall.gr...@wright.edu wrote: These are the instructions for checking out CVS OSG that are given: cvs -d:pserver:anonym...@openscenegraph.cvs.sourceforge.net:/cvsroo t/openscenegraph login cvs -z3 -d:pserver:anonym...@openscenegraph.cvs.sourceforge.net:/cvsroo t/openscenegraph co -P modulename What is the modulename? I tried different things but nothing works. OSG has moved to SVN. Use this command: svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk OpenSceneGraph Note: it would have taken just a minute to go to the OSG web site and find this information for yourself. I think your 'note' is a little unfair: we should not provide instructions that don't work and then tell people who try to follow those instructions that they should have figured out the correct instructions for themselves. LeeE -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://baron.flightgear.org/~curt/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sport-model nav-radio (was Re: GS sensitivity)
James Turner wrote: It adds false LOC and GS signals, a better GS deviation computation, and LOC sensitivity based on the runway dimensions. The last part I'm not totally sure about - it makes localizers *very* sensitive - maybe I've adapted the code incorrectly, but this doc: http://www.allstar.fiu.edu/aerojava/ILS.htm indicates that at 10nm, the beam should be approx 1m (statue or nautical, I don't know) wide (with some variation for the runway aspect formula) - and it feels much, much narrower than that to me, though I haven't tested this rigourously. Comments awaited with interest :) As a sanity check, I used the rule of thumb of 0.5 deg per dot = CDI pegs at 2.5 deg each side and x/10 = sin(2.5 deg) . So LOC full width at 10 nm from LOC antenna = 20*sin(2.5 deg) = 0.872 . Since this is approximate (i.e. from the rule of thumb), the statement in the link /The width of the navigational beam may/ be varied from approximately 3º to 6º, with 5º being normal. It is adjusted to provide a track signal approximately 700 ft wide at the runway threshold. The width of the beam increases so that at 10 NM from the transmitter, the beam is approximately one mile wide. passes this sanity check. I have not flown the patch yet. In this patch, does the region of reliable signal satisfy Figure 1-1-6 on page 503 of the 2008 AIM? That figure shows valid signals for two over lapped archs. Arch 1: +\-35 deg out to 10 nm. Arch 2: +\- 10 deg out to 18 nm. In real IFR flying, you are always looking for two events as you are intercepting the LOC. #1: the needle to come live with a valid morris code for the LOC, and #2 the needle to break away from the case (i.e.un-peg). #1 occurs well before #2 and relates to the AIM figure 1-1-6. #2 relates to the beam width. It would be great to have both well modelled. Dave P -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Error checking out CVS version of OpenSceneGraph
Although getting osg from cvs rang a bell with me, I'm not sure if those commands were ever on one of the FG sites: they relate back to when OSG was still hosted on sourceforge, as the link below shows... http://sourceforge.net/projects/openscenegraph/develop However, OSG moved from sourceforge to its own site in 2003. OSG was first discussed here during early August 2003, but I'm not sure if that was before or after OSG had moved from sourceforge to openscenegraph.org. In any case, Mathias Fröhlich didn't announce his work in porting it until late October 2006, so it's difficult to imagine why there would have been instructions on the FG sites for getting the 2003 sourceforge osg vintage when it would have already been hosted at openscenegraph.org for more than three years. I should apologise for suggesting that FG was providing faulty instructions, but I still think that the 'note' was unnecessary as all it achieved was to aggressively suggest that the poster was lazy or stupid. Sure, people can be lazy _and_ stupid, but I can't see that attacking them for being so is the best way to do anything about it. LeeE On Friday 11 Sep 2009, Curtis Olson wrote: Where are the misleading instructions located? Thanks, Curt. On Fri, Sep 11, 2009 at 7:39 AM, leee wrote: On Thursday 10 Sep 2009, Csaba Halász wrote: On Thu, Sep 10, 2009 at 6:13 PM, Randall Green randall.gr...@wright.edu wrote: These are the instructions for checking out CVS OSG that are given: cvs -d:pserver:anonym...@openscenegraph.cvs.sourceforge.net:/cv sroo t/openscenegraph login cvs -z3 -d:pserver:anonym...@openscenegraph.cvs.sourceforge.net:/cv sroo t/openscenegraph co -P modulename What is the modulename? I tried different things but nothing works. OSG has moved to SVN. Use this command: svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk OpenSceneGraph Note: it would have taken just a minute to go to the OSG web site and find this information for yourself. I think your 'note' is a little unfair: we should not provide instructions that don't work and then tell people who try to follow those instructions that they should have figured out the correct instructions for themselves. LeeE -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sport-model nav-radio (was Re: GS sensitivity)
On 11 Sep 2009, at 14:48, dave perry wrote: I have not flown the patch yet. In this patch, does the region of reliable signal satisfy Figure 1-1-6 on page 503 of the 2008 AIM? That figure shows valid signals for two over lapped archs. Arch 1: +\-35 deg out to 10 nm. Arch 2: +\- 10 deg out to 18 nm. In real IFR flying, you are always looking for two events as you are intercepting the LOC. #1: the needle to come live with a valid morris code for the LOC, and #2 the needle to break away from the case (i.e.un-peg). #1 occurs well before #2 and relates to the AIM figure 1-1-6. #2 relates to the beam width. It would be great to have both well modelled. The patches I'm adapting at the moment deal with #2 (and improve the accuracy there considerably). #1, and more generally modelling the reception volumes for LOC/GS, is a separate issue. At the moment, if you're tuned to a valid LOC frequency, and within range, I believe you will get the ident (including the more signal, depending on the specific aircraft's audio configuration) on any heading to the navaid (i.e 360 degree coverage). Clearly this needs to be improved, but it's a separate piece of work, and I greatly prefer to serialise these changes. Also, modelling radio reception is an area I know nothing about, so improvements in this area need someone to propose a model (and code!) that is consistent with the standards, but also with real-world behaviour, and hopefully of bearable complexity. The VOR/NDB/DME reception model is also quite crude, ideally someone with expertise (and a love of physics) would look into this whole area. (I worry that any 'accurate' model will be of fearful complexity, especially if it's physically based - clearly we can do line-of-sight checks from the aircraft to the navid, but I don't know how much beyond that might be necessary. Maybe I'm worrying about nothing - until someone proposes some code, it's academic) Regards, James -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Compiling newest CVS FlightGear/SimGear andgetting link errors
Vivian, Thank you very much for the reply. I'm afraid I'm somewhat unfamiliar with MSVC. I see how to add the existing files to a project but how do I know which project to add them to? Like for FGGyro I think would be added to the FlightGear Project, Lib_JBSSim but it has 4 folders under it: initialization, input_output, math models. Thanks, Randy Green - Original Message - From: Vivian Meazza vivian.mea...@lineone.net Date: Thursday, September 10, 2009 4:58 pm Subject: Re: [Flightgear-devel] Compiling newest CVS FlightGear/SimGear andgetting link errors To: 'FlightGear developers discussions' flightgear-devel@lists.sourceforge.net You need to include some recently added files to your projects. FGGyro.cxx/hxx, AIGroundVehicle.cxx/hxx, SGText.cxx/hxx. The clue is in the errors! That might make at least some of the problems go away. HTH Vivian -Original Message- From: Randall Green [mailto:randall.gr...@wright.edu] Sent: 10 September 2009 20:51 To: dFlightGear developers discussions Subject: [Flightgear-devel] Compiling newest CVS FlightGear/SimGear andgetting link errors Hi all, I'm compiling the newest CVS versions of FlightGear/SimGear and I'm getting the following link errors: Linking fgviewer, after this warning: LINK : warning LNK4098: defaultlib 'LIBCMTD' conflicts with use of other libs; use /NODEFAULTLIB:library 4simgear_d.lib(SGReaderWriterXML.obj) : error LNK2019: unresolved external symbol public: static class osg::Node * __cdecl SGText::appendText(class SGPropertyNode const *,class SGPropertyNode *,class osgDB::ReaderWriter::Options const *) (?appendt...@sgtext@@sapavn...@osg@@PBVSGPropertyNode@@p...@pbvoptions@readerwri...@osgdb@@@Z) referenced in function __catch$?sgLoad3DModel_internal@@yapavn...@osg@@abv?$basic_str...@du?$char_traits@d...@std@@v?$alloca...@d@2@@std@@pbvopti...@readerwriter@osgDB@@PAVSGPropertyNode@@@Z$0 And these 3 linking fgfs: FGFCS.obj : error LNK2019: unresolved external symbol public: __thiscall JSBSim::FGGyro::FGGyro(class JSBSim::FGFCS *,class JSBSim::Element *) (??0fgg...@jsbsim@@q...@pavfgfcs@1...@pavelement@1@@Z) referenced in function public: bool __thiscall JSBSim::FGFCS::Load(class JSBSim::Element *,enum JSBSim::FGFCS::SystemType) (?l...@fgfcs@JSBSim@@qae_npavelem...@2@w4systemt...@12@@Z) I am using openscenegraph-all-2.8.1-win32-x86-vc90sp1-Debug.zip 3AIManager.obj : error LNK2019: unresolved external symbol public: __thiscall FGAIGroundVehicle::FGAIGroundVehicle(void) (??0FGAIGroundVehicle@@q...@xz) referenced in function public: void __thiscall FGAIManager::processScenario(class std::basic_stringchar,struct std::char_traitschar,class std::allocatorchar const ) (?processscena...@fgaimanager@@qaexabv?$basic_str...@du?$char_traits@d...@std@@v?$alloca...@d@2@@std@@@Z) 3simgear_d.lib(SGReaderWriterXML.obj) : error LNK2019: unresolved external symbol public: static class osg::Node * __cdecl SGText::appendText(class SGPropertyNode const *,class SGPropertyNode *,class osgDB::ReaderWriter::Options const *) (?appendt...@sgtext@@sapavn...@osg@@PBVSGPropertyNode@@p...@pbvoptions@readerwri...@osgdb@@@Z) referenced in function __catch$?sgLoad3DModel_internal@@yapavn...@osg@@abv?$basic_str...@du?$char_traits@d...@std@@v?$alloca...@d@2@@std@@pbvopti...@readerwriter@osgDB@@PAVSGPropertyNode@@@Z$0 3C:\FG2\FlightGear\projects\VC90\Win32\Debug\fgfs.exe : fatal error LNK1120: 3 unresolved externals Any help will be apreciated. Randy Green - - Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Error checking out CVS version of OpenSceneGraph
I just want to make sure if we (flightgear) have some outdated documentation that gets identified and fixed. If someone managed to dredge up some really old information from some other site, there's not much we can do about that. Curt. On Fri, Sep 11, 2009 at 11:21 AM, leee wrote: Although getting osg from cvs rang a bell with me, I'm not sure if those commands were ever on one of the FG sites: they relate back to when OSG was still hosted on sourceforge, as the link below shows... http://sourceforge.net/projects/openscenegraph/develop However, OSG moved from sourceforge to its own site in 2003. OSG was first discussed here during early August 2003, but I'm not sure if that was before or after OSG had moved from sourceforge to openscenegraph.org. In any case, Mathias Fröhlich didn't announce his work in porting it until late October 2006, so it's difficult to imagine why there would have been instructions on the FG sites for getting the 2003 sourceforge osg vintage when it would have already been hosted at openscenegraph.org for more than three years. I should apologise for suggesting that FG was providing faulty instructions, but I still think that the 'note' was unnecessary as all it achieved was to aggressively suggest that the poster was lazy or stupid. Sure, people can be lazy _and_ stupid, but I can't see that attacking them for being so is the best way to do anything about it. LeeE On Friday 11 Sep 2009, Curtis Olson wrote: Where are the misleading instructions located? Thanks, Curt. On Fri, Sep 11, 2009 at 7:39 AM, leee wrote: On Thursday 10 Sep 2009, Csaba Halász wrote: On Thu, Sep 10, 2009 at 6:13 PM, Randall Green randall.gr...@wright.edu wrote: These are the instructions for checking out CVS OSG that are given: cvs -d:pserver:anonym...@openscenegraph.cvs.sourceforge.net:/cv sroo t/openscenegraph login cvs -z3 -d:pserver:anonym...@openscenegraph.cvs.sourceforge.net:/cv sroo t/openscenegraph co -P modulename What is the modulename? I tried different things but nothing works. OSG has moved to SVN. Use this command: svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk OpenSceneGraph Note: it would have taken just a minute to go to the OSG web site and find this information for yourself. I think your 'note' is a little unfair: we should not provide instructions that don't work and then tell people who try to follow those instructions that they should have figured out the correct instructions for themselves. LeeE -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://baron.flightgear.org/~curt/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Using shapefiles other than VMAP
Hey gang. I'm not sure if the answer to this will turn out to be retardedly simple, or ludicrously complex, but here goes. I've build scenery for the island of Newfoundland with very high resolution for the elevation. But now the low-res, VMAP0 looks awful. In many cases, it cuts canyons and builds wall through an otherwise rugged landscape. I can't find VMAP1 for Canada, but I found a set of vector data in some sort of shapefile format that is at 50,000:1 as opposed to VMAP0's 1,000,000. It's called CanVec. I've got a descriptive html file for one section of land attached to this e-mail. The question is, how do I format this data, or modify my build commands to use it? For one section of the smallest size the data is cut into, I have a file with a name of the format 001n10_2_0_BS_1250009_1 where: - 001n10 is the land area described in this file (this is the same numbering system that the elevation data I'm using used) - 2_0 is the same for every one I've got, I'm not sure what the significance is. - BS is a two letter code that varies from file to file. It might refer to the coverage described by the given shapefile. The others are EN, FO, HD, IC, LX, SS, TO, TR, and VE. Every section has some of each of these. - 1250009 is changes for each file name. But ALL file names end in 0009. So the 125, versus 176 or any other number is the distinctive thing in the file name. - some of the filenames have two or three copies, where the only difference is this last number. It's varries between 0, 1 and 2. - for EVERY file name, I have a .dbf, .prj, .shp, and .shx file. Every section is in it's own folder, so all the 001n10s are grouped together. In each group, is an html file like the one attached, which might tell you far more than I just have. If somebody could give me some tips, or point to some documentation as to how I could use this data to build my scenery in Terragear, it would be really helpful! Up till now, I've been using tgvpf, but that works directly on the VMAP0 stuff, so I'm guessing it won't work without some modification to structures, commands or parameters here. Thanks a lot guys! -cullam __ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Whoops: missing attachment
Sorry, here's the information contained in the html file to accompany my question: CanVec 001N10 1. Identification Information 2. Data Quality Information 3. Spatial Data Organization Information 4. Spatial Reference Information 5. Entity and Attribute Information 6. Distribution Information 7. Metadata Reference Information Identification Information Citation: Citation Information: Originator: Government of Canada, Natural Resources Canada, Earth Sciences Sector, Mapping Services Branch, Centre for Topographic Information - Sherbrooke Publication Date: 2008-04-15 Title: 001N10 Edition: 2.0 Geospatial Data Presentation Form: vector digital data Series Information: Series Name: CanVec Issue Identification: 1.0 Publication Information: Publication Place: Sherbrooke, Quebec, Canada Publisher: Government of Canada, Natural Resources Canada, Earth Sciences Sector, Mapping Services Branch, Centre for Topographic Information - Sherbrooke Online Linkage: http://www.geogratis.gc.ca Description: Abstract: CanVec digital topographical dataset of an area represented according to the National Topographic System (NTS). Purpose: CanVec aims to provide a standardized and up to date representation of topographical phenomena for the entire Canadian landmass. Supplemental Information: This product is subject to Discrepancies processing provided by the Centre for Topographic Information from Natural Resources Canada. A discrepancy is defined as any deviation from the product's Standards and Specifications. To explore the status of discrepancies related this dataset, see the Discrepancies Web Site from the Centre for Topographic Information (http://www.ctis.nrcan.gc.ca/cit/servlet/CIT/site_id=01page_id=1-005-010.html). Time Period of Content: Time Period Information: Range of Dates/Times: Beginning Date: 1985 Ending Date: 2007-05 Currentness Reference: ground condition Status: Progress: Complete Maintenance and Update Frequency: As needed Spatial Domain: Bounding Coordinates: West Bounding Coordinate: -53 East Bounding Coordinate: -52.5 North Bounding Coordinate: 47.75 South Bounding Coordinate: 47.5 Keywords: Theme: Theme Keyword Thesaurus: GCMD Theme Keyword: Earth Science Human Dimensions Infrastructure Buildings Theme Keyword: Earth Science Human Dimensions Infrastructure Communications Theme Keyword: Earth Science Land Surface Topography Contours Theme Keyword: Earth Science Human Dimensions Infrastructure Cultural Features Theme Keyword: Earth Science Human Dimensions Infrastructure Electricity Theme Keyword: Earth Science Land Surface Topography Terrain Elevation Theme Keyword: Earth Science Land Surface Land Use/Land Cover Theme Keyword: Earth Science Land Surface Topography Landforms Theme Keyword: Earth Science Human Dimensions Infrastructure Pipelines Theme Keyword: Earth Science Land Surface Topography Topographical Relief Theme Keyword: Earth Science Human Dimensions Infrastructure Transportation Theme Keyword: Earth Science Biosphere Vegetation Vegetation Cover Theme Keyword: Earth Science Hydrosphere Surface Water Wetlands Theme Keyword: Administratives Boundaries Theme Keyword: Buildings and Structures Theme Keyword: Energy Theme Keyword: Hydrography Theme Keyword: Industrial and Commercial Areas Theme Keyword: Places of Interest Theme Keyword: Relief and Landforms Theme Keyword: Toponymy/Place Names Theme Keyword: Water Saturated Soils Theme Keyword: Earth Science Human Dimensions Boundaries Administrative Divisions Place: Place Keyword Thesaurus: GCMD Place Keyword: Continent North America Canada Newfoundland and Labrador Place Keyword: ST. JOHN'S Place Keyword: 001N10 Access Constraints: None Use Constraints: Data are subject to the GeoGratis Licence Agreement for Unrestricted Use of Digital Data. Point of Contact: Contact
Re: [Flightgear-devel] Using shapefiles other than VMAP
cullam Bruce-Lockhart wrote: Hey gang. I'm not sure if the answer to this will turn out to be retardedly simple, or ludicrously complex, but here goes. I've build scenery for the island of Newfoundland with very high resolution for the elevation. But now the low-res, VMAP0 looks awful. In many cases, it cuts canyons and builds wall through an otherwise rugged landscape. I can't find VMAP1 for Canada, but I found a set of vector data in some sort of shapefile format that is at 50,000:1 as opposed to VMAP0's 1,000,000. It's called CanVec. I've got a descriptive html file for one section of land attached to this e-mail. The question is, how do I format this data, or modify my build commands to use it? For one section of the smallest size the data is cut into, I have a file with a name of the format 001n10_2_0_BS_1250009_1 where: - 001n10 is the land area described in this file (this is the same numbering system that the elevation data I'm using used) - 2_0 is the same for every one I've got, I'm not sure what the significance is. - BS is a two letter code that varies from file to file. It might refer to the coverage described by the given shapefile. The others are EN, FO, HD, IC, LX, SS, TO, TR, and VE. Every section has some of each of these. - 1250009 is changes for each file name. But ALL file names end in 0009. So the 125, versus 176 or any other number is the distinctive thing in the file name. - some of the filenames have two or three copies, where the only difference is this last number. It's varries between 0, 1 and 2. - for EVERY file name, I have a .dbf, .prj, .shp, and .shx file. Every section is in it's own folder, so all the 001n10s are grouped together. In each group, is an html file like the one attached, which might tell you far more than I just have. If somebody could give me some tips, or point to some documentation as to how I could use this data to build my scenery in Terragear, it would be really helpful! Up till now, I've been using tgvpf, but that works directly on the VMAP0 stuff, so I'm guessing it won't work without some modification to structures, commands or parameters here. Thanks a lot guys! -cullam shapedecode or ogrdecode should process those files for you - you just need to ensure the coordinates are wgs84 and not some other projection (if they are then they can be converted with the ogr2ogr tool from gdal/ogr) Jon -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Compiling newest CVS FlightGear/SimGear andgetting link errors
Randy,
I'm busy right now, but I'll try to sort that out for you later. Meanwhile,
the files pretty much go into the lib relating to their parent folder - so
you you might be able to work it out. The makefiles specify it for you, when
you identify the right one!
Vivian
-Original Message-
From: Randall Green [mailto:randall.gr...@wright.edu]
Sent: 11 September 2009 17:45
To: vivian.mea...@lineone.net; FlightGear developers discussions
Subject: Re: [Flightgear-devel] Compiling newest CVS FlightGear/SimGear
andgetting link errors
Vivian,
Thank you very much for the reply. I'm afraid I'm somewhat unfamiliar
with MSVC. I see how to add the existing files to a project but how
do I know which project to add them to? Like for FGGyro I think
would be added to the FlightGear Project, Lib_JBSSim but it has
4 folders under it: initialization, input_output, math models.
Thanks,
Randy Green
- Original Message -
From: Vivian Meazza vivian.mea...@lineone.net
Date: Thursday, September 10, 2009 4:58 pm
Subject: Re: [Flightgear-devel] Compiling newest CVS FlightGear/SimGear
andgetting link errors
To: 'FlightGear developers discussions'
flightgear-devel@lists.sourceforge.net
You need to include some recently added files to your projects.
FGGyro.cxx/hxx, AIGroundVehicle.cxx/hxx, SGText.cxx/hxx. The clue is in the
errors! That might make at least some of the problems go away.
HTH
Vivian
-Original Message-
From: Randall Green [mailto:randall.gr...@wright.edu]
Sent: 10 September 2009 20:51
To: dFlightGear developers discussions
Subject: [Flightgear-devel] Compiling newest CVS FlightGear/SimGear
andgetting link errors
Hi all,
I'm compiling the newest CVS versions of FlightGear/SimGear and I'm
getting the following link errors:
Linking fgviewer, after this warning:
LINK : warning LNK4098: defaultlib 'LIBCMTD' conflicts with use of other
libs; use /NODEFAULTLIB:library
4simgear_d.lib(SGReaderWriterXML.obj) : error LNK2019: unresolved
external symbol public: static class osg::Node * __cdecl
SGText::appendText(class SGPropertyNode const *,class SGPropertyNode *,class
osgDB::ReaderWriter::Options const *)
(?appendt...@sgtext@@sapavn...@osg@@PBVSGPropertyNode@@p...@pbvoptions@Reade
rwri...@osgdb@@@Z) referenced in function
__catch$?sgLoad3DModel_internal@@yapavn...@osg@@abv?$basic_str...@du?$char_t
ra...@d@std@@v?$alloca...@d@2@@std@@pbvopti...@readerwriter@osgDB@@PAVSGProp
ertyNode@@@Z$0
javascript:main.compose('new',%20't=__catch$sgLoad3DModel_internal@@YAPAVN
o...@osg@@abv?$basic_str...@du?$char_traits@d...@std@@v?$alloca...@d@2@@std@@PBV
opti...@readerwriter@osgDB@@PAVSGPropertyNode@@@Z$0')
And these 3 linking fgfs:
FGFCS.obj : error LNK2019: unresolved external symbol public: __thiscall
JSBSim::FGGyro::FGGyro(class JSBSim::FGFCS *,class JSBSim::Element *)
(??0fgg...@jsbsim@@q...@pavfgfcs@1...@pavelement@1@@Z) referenced in function
public: bool __thiscall JSBSim::FGFCS::Load(class JSBSim::Element *,enum
JSBSim::FGFCS::SystemType)
(?l...@fgfcs@JSBSim@@qae_npavelem...@2@w4systemt...@12@@Z
javascript:main.compose('new',%20't=l...@fgfcs@JSBSim@@qae_npavelem...@2@W
4systemt...@12@@Z') )
I am using
http://www.openscenegraph.org/downloads/stable_releases/OpenSceneGraph-2.8.
1/binaries/Windows/VisualStudio9/openscenegraph-all-2.8.1-win32-x86-vc90sp1-
Debug.zip openscenegraph-all-2.8.1-win32-x86-vc90sp1-Debug.zip
3AIManager.obj : error LNK2019: unresolved external symbol public:
__thiscall FGAIGroundVehicle::FGAIGroundVehicle(void)
(??0FGAIGroundVehicle@@q...@xz) referenced in function public: void
__thiscall FGAIManager::processScenario(class std::basic_stringchar,struct
std::char_traitschar,class std::allocatorchar const )
(?processscena...@fgaimanager@@qaexabv?$basic_str...@du?$char_traits@d...@std@@
v?$alloca...@d@2@@std@@@Z)
3simgear_d.lib(SGReaderWriterXML.obj) : error LNK2019: unresolved
external symbol public: static class osg::Node * __cdecl
SGText::appendText(class SGPropertyNode const *,class SGPropertyNode *,class
osgDB::ReaderWriter::Options const *)
(?appendt...@sgtext@@sapavn...@osg@@PBVSGPropertyNode@@p...@pbvoptions@Reade
rwri...@osgdb@@@Z) referenced in function
__catch$?sgLoad3DModel_internal@@yapavn...@osg@@abv?$basic_str...@du?$char_t
ra...@d@std@@v?$alloca...@d@2@@std@@pbvopti...@readerwriter@osgDB@@PAVSGProp
ertyNode@@@Z$0
3C:\FG2\FlightGear\projects\VC90\Win32\Debug\fgfs.exe : fatal error
LNK1120: 3 unresolved externals
Any help will be apreciated.
Randy Green
-
-
Let Crystal Reports handle the reporting - Free Crystal Reports
2008 30-Day
trial. Simplify your report design, integration and deployment -
and focus on
what you do best, core application coding. Discover what's new
with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Flightgear-devel
Re: [Flightgear-devel] Error checking out CVS version of OpenSceneGraph
On Fri, Sep 11, 2009 at 6:21 PM, leee l...@spatial.plus.com wrote: Sure, people can be lazy _and_ stupid, but I can't see that attacking them for being so is the best way to do anything about it. In case you missed it, I *have* provided the relevant information first. I don't think I can be rightly accused of being unhelpful, although people do try from time to time :) Anyway, if I have offended him, I apologize as it was not my intent. -- Csaba/Jester -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Error checking out CVS version of OpenSceneGraph
On Fri, Sep 11, 2009 at 2:15 PM, Csaba Halász wrote: On Fri, Sep 11, 2009 at 6:21 PM, leee wrote: Sure, people can be lazy _and_ stupid, but I can't see that attacking them for being so is the best way to do anything about it. In case you missed it, I *have* provided the relevant information first. I don't think I can be rightly accused of being unhelpful, although people do try from time to time :) Anyway, if I have offended him, I apologize as it was not my intent. Yeah, I think we are dicing words pretty finely here with large reactions to small bumps. Generally if you want to download and install some software XYZ, it works best to find the main web page for XYZ and follow the instructions there. But with goofy search engines sometimes spewing unpredictable results and archiving the entire history of the internet, I could see a person stumbling onto old info and getting confused if they haven't done much of this software building stuff. If you are running a linux distribution, often you can find a prepackaged version of whatever you are looking for and that will save you a ton of time. But be a little careful, because the packaged version of XYZ often can be dated and not the very latest version. Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Error checking out CVS version of OpenSceneGraph
Csaba, I am the one who posted the original question and I want to say that you did help me and I'm just mighty glad that I have all of you on this mailing list to answer my questions. I would have gotten nowhere without it. :) I would rather get a reply with a little chastising than to get no response at all. Randy Green - Original Message - From: Csaba Halász csaba.hal...@gmail.com Date: Friday, September 11, 2009 3:15 pm Subject: Re: [Flightgear-devel] Error checking out CVS version of OpenSceneGraph To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net On Fri, Sep 11, 2009 at 6:21 PM, leee l...@spatial.plus.com wrote: Sure, people can be lazy _and_ stupid, but I can't see that attacking them for being so is the best way to do anything about it. In case you missed it, I *have* provided the relevant information first. I don't think I can be rightly accused of being unhelpful, although people do try from time to time :) Anyway, if I have offended him, I apologize as it was not my intent. -- Csaba/Jester - - Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
