Has there been thought on how to officially support light phase in OpenFlight?
]]>We have vector data for an urban area comprising approx 30,000 footprints of buildings.
In previous terrain database formats these footprints have been extruded (based upon a ‘height’ atttribute) and textured (based upon a ‘building type’ attribute).
What is the crrently recommended way of representing this information in CDB?
The spec seems to suggest that the FACC codes associated with buildings should exist as point features rather than areal - but to achive correlation with our existing databases this would presumably require us to generate 30,000 geo-specific building models, which doesn’t sound like fun!
Is there a ‘correct ’ way to represent these individual buildings as areal features?
Thanks,
Andy Stannard
BAE SYSTEMS
It’s been a long time since I last posted…..but I hope someone can help me with my current issue:
I’ve written a stand-alone app using the 4.0 API (and subsequently the 4.2 API), but…..and here’s where things get weird…..if I point the environment variable PRESAGIS_CREATOR_PLUGIN_DIR to a directory that contains the openflightextensionmanager.dll, then a directory is created with a garbage name in the tool’s home directory. If I remove the offending dll, or point the env var to a directory without it in, then all is fine. This strange, empty, garbaged-name directory is created during the mgInit() call.
Can anyone relate to this? Any suggestions?
Thanks for your time,
MattN
]]>Here is a script presented that shows how to process multiple OpenFlight database files without using the Creator Pro command Batch Run Script. Note that you can use this technique to apply OpenFlight Script commands to your databases but you cannot invoke Creator Script commands in this way.
def ProcessNodeCB (db, parent, rec, userData):
# this "mgWalk" callback processes each node visited
type = mgGetCode (rec)
if (type == fltPolygon):
# do something to the polygon
print "Processing polygon:", mgGetName(rec)
return MG_TRUE
def ProcessOneFile (db):
print "Processing file:", mgRec2Filename(db)
mgWalk (db, ProcessNodeCB, None, None, MWALK_NOREADONLY)
outs = mgPromptDialogFile (None,
MPFM_OPEN,
MPFA_FLAGS, MPFF_FILEMUSTEXIST|MPFF_MULTISELECT,
MPFA_PATTERN, "OpenFlight Files|*.flt",
MPFA_TITLE, "Select OpenFlight Files to Process" )
status = outs[0]
if (MSTAT_ISOK(status)):
numFiles = outs[1]
fileNames = outs[2:len(outs)]
for fileName in fileNames:
db = mgOpenDb (fileName)
ProcessOneFile (db)
mgWriteDb (db)
mgCloseDb (db)
print "Finished"
else:
print "User Canceled"
Here is a script presented that shows how to use the Creator Script command Modify Attributes. It shows different ways to modify a node’s color. It also shows how to modify a nested attribute value using the Nested Record Code parameter.
# this script executes the Creator tool: Modify Attributes
# to demonstrate how to modify different attributes of selected nodes
# set the face/mesh Creator primary color index to 127
paramBlock = mgGetParamBlock ("Modify Attributes")
mgParamSet (paramBlock, "Nested Record Code", 0) # field is not nested
mgParamSet (paramBlock, "Attribute Code", fltPolyCreatorPrimeColor)
mgParamSet (paramBlock, "Integer Value", 127)
mgExecute ("Modify Attributes", paramBlock)
# set the face/mesh primary color index to 0 and primary color intensity to 1.0
# this is just a different way to set Creator primary color index of 127
paramBlock = mgGetParamBlock ("Modify Attributes")
mgParamSet (paramBlock, "Nested Record Code", 0) # field is not nested
mgParamSet (paramBlock, "Attribute Code", fltPolyPrimeColor)
mgParamSet (paramBlock, "Integer Value", 1)
mgExecute ("Modify Attributes", paramBlock)
# note that we can reuse the paramBlock and just change the
# necessary fields to set the intensity value
mgParamSet (paramBlock, "Attribute Code", fltPolyPrimeIntensity)
mgParamSet (paramBlock, "Double Value", 1.0)
mgExecute ("Modify Attributes", paramBlock)
# set the face/mesh draw type to solid
paramBlock = mgGetParamBlock ("Modify Attributes")
mgParamSet (paramBlock, "Nested Record Code", 0) # field is not nested
mgParamSet (paramBlock, "Attribute Code", fltPolyDrawType)
mgParamSet (paramBlock, "Integer Value", 0)
mgExecute ("Modify Attributes", paramBlock)
# set the vertex x coordinate to 5.0
paramBlock = mgGetParamBlock ("Modify Attributes")
mgParamSet (paramBlock, "Nested Record Code", fltCoord3d) # field is nested
mgParamSet (paramBlock, "Attribute Code", fltCoord3dX)
mgParamSet (paramBlock, "Double Value", 5.0)
mgExecute ("Modify Attributes", paramBlock)
Here is a script presented that shows how to use array type parameters in the parameter blocks you provide to commands in Creator Script.
We invite your questions or comments.
# this script executes the Creator tool: Polygon
# to create a simple square polygon
# get the database the script is running on
db = mgGetCurrentDb()
# get a parameter block that can be used for the Polygon tool
paramBlock = mgGetParamBlock ("Polygon")
# set up the tool parameters
# make a solid polygon
mgParamSet (paramBlock, "Type", "Solid")
# the "Points" parameter is an array type parameter of double3 values
# each point in the array represents vertex on the polygon to be created
# the order of the points is the order the vertices will be created
# and will determine the front/back of the polygon
# use mgParamSet to set the first point in the parameter array
# when you do this, the first item in the array is set and the length
# of the array is reset to one
mgParamSet (paramBlock, "Points", [ 0, 0, 0])
# use mgParamAppend to add subsequent points to the array
mgParamAppend (paramBlock, "Points", [10, 0, 0])
mgParamAppend (paramBlock, "Points", [10, 10, 0])
mgParamAppend (paramBlock, "Points", [ 0, 10, 0])
# set the modeling mode to polygon - this will create a face node
# for the new polygon below the current modeling parent
# if you set modeling mode to object (fltObject), an object node
# would be created above the new face (just like in Creator)
mgSetModelingMode (db, fltPolygon)
# execute the Polygon tool
mgExecute ("Polygon", paramBlock)
Here is a very simple script presented that shows how to use two Creator Script commands together. The first selects nodes to process (specifically, non-planar faces). The second processes the non-planar faces selected by triangulating them.
# select faces that are not planar
mgExecute ("Select Nonplanar Faces", None)
# invoke the Triangulate command to triangulate the
# non-planar faces selected
mgExecute ("Triangulate", None)