MapPackageModelWriter.Convert Method
Converts the input model data and writes the result to the GeoPackage table.
Convert()
Converts the input model data and writes the result to the GeoPackage table.Syntax
public System.Boolean Convert ()Return Value
True if the write operation completed successfully; otherwise, False.
Remarks
This method loads the input model data set, converts it to a format suitable for visualization in a GlobeView, and writes the result to the GeoPackage table with which this MapPackageModelWriter was created.
See the main documentation page for MapPackageModelWriter for an example of how to use this method.
The detail level of the resulting models can be adjusted using the detail settings properties on MapPackageModelTable: MapPackageModelTable.LevelOfDetailMultiplier and MapPackageModelTable.LevelOfDetailMultiplier. You can also apply an elevation offset using MapPackageModelTable.ElevationOffset.
To automatically deduce appropriate detail settings for the input model data, invoke DeduceDetailSettings before calling Convert.
You can also use Estimate to get calculate estimate of the resulting detail density per tile level given the current detail settings. This lets you test your settings without taking the full time to convert with Convert.
If you are implementing model export in a GUI application, calling this method directly on the GUI thread is probably not a good solution, since that will block the whole application during the duration of this call. The recommended approach is to start a background thread, pass it a reference to the MapPackageModelWriter instance, and call this method on the background thread. Meanwhile, the GUI thread of the application can monitor the progress, by using a timer and regularly checking the Progress property and updating the GUI accordingly.
This way, you can also let the user abort the operation, for instance with a push button that, when clicked, calls the Abort method. That will make the call on the background thread return as soon as possible.
Let the background thread signal the main thread when the job is done in whichever manner suits your application best. As a simple example, the background thread could set an "isDone" atomic boolean variable that is shared with the main thread to True, after Convert has returned.
If invoked on a large input model data set, this process can take a long time and a lot of memory. Therefore, it is best suited for workstation computers.
Platforms
Windows, Linux, Android