These are the landclasses (that we take mostly either from Corine or V0). In addition, It contains specification for the textures applied to different faces of such triangulation. You'll see such 3d structure is composed of a rather large collection of triangulations. It is actually a 3d object, that you can appreciate if you lauch the ufo and look at the mesh, not the object. Terrain contains both the 3d mesh of the terrain (think of it as the horizon line, or the terrain ripples as it crumbles and deeps in your horizon). Terrain seems to me to be something that doesn't belong either in a database or in a repository - maybe the source files but the output can just remain on disk and be merged with the rest. (instead the are maintained in xml files in Airports/I/C/A/ICAO_file.xml => more about this later) This means, OSM is not (nor intended) stored is a separated external source.Īnd more importantly, xml configuration files for airports are not incorporated in this QGis database. So, i n reality, beyond what may seem obvious in the first place, the actual database interpreted by FG includes lots of specification for many structures within scenery (including OSM2City). Signs (Like taxisigns) ARE specified in the STG database (OBJECT_SIGN) Airports ARE specified in the STG database (OBJECT_BASE)Ĩ. Terrain Tiles ARE specified in the STG database (OBJECT)ħ. (Stuart with the moderator hat on, actually just recently commited changes that allow the FG STG reader to interpret additional "verbs", in addition to OBJECT, OBJECT_BASE, OBJECT_SHARED, OBJECT_SIGN, and OBJECT_STATIC)Ħ. OSM2City objects: ARE specified in the STG database. 3d model objects populating the world ARE specified in the STG database. Artificial Intelligence traffic files: are not specified in the STG databaseĤ. Scenery is the configuration files for airports, (xml files) are not specified in the STG database.ģ. Not another one.Ī database should be used for 2,3,4 in your list above.Ģ. STG format (a GIS database on its own right) contains several fields: including object qualifier, name (absolute location in hard drive space), location (absolute lat, lon, elevation location), and turn in degrees (true heading) and pitch (rotation angle).Ī GIS database in that format IS understood by FG. The GIS database that flightgear reads/uses is contained in a format, namely STG. Accepted.īut that database IS NOT what FlightGear Software reads. This database found in the website is a collective of Shared and Static models, and its associated GIS information. OSM data should be handled separately as it's an external source and the database should only contain our own creations.įundamentally, the GIS database that comprises FG scenery is not the "scenery database" found here: Approaching scenery from the point of view of a data modelling exercise it's obvious to me that a database should be used for 2,3,4 in your list above.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |