Compile the Next Edition Model Collection

Preparing the Next Edition Model Collection

All of the data wrangling discussed above has brought newmodels into the collection and many of the previously existing models have had their model status attributes updated. To finally produce the next edition of the model collection, all of these models need to be sorted into new feature classes according to their new status values. These newfeature classes can then be used to create new web scenes, published on-line or exported to tiled model collections.

Each editionof the collection also contains a model catalog -- a table of all of the models that is not segmented by status -- whcih can be used by applications that help model users discover updated models andmodels that have been retired or expunged.

Tasks and Tools for Publising the Next Edition

Produce NextEdition Tasks.

Produce Next Edition Tools.

The Produce Next Edition task group makes use of the tools inthe similarly named tool group. The basic workflow steps are outlined below:

  1. The Initialize Next Edition GDB Task Creates an geodatabase in the ModelMgt\NextEdition folder. The new geodatabase includes a set of empty feature classes based on the currentmodeltemplate ready to recieve the new collection. As discussed under the heading Lifecycle of the Model Management Workspace, the NextEdition folder can contain several updated editions of the model collections based off of the same PriorArchived collection. Each of these new editions is distinguished by a YYYYMMDD date stamp that reflects the date that the new edition was initialized.
  2. The task, Check for Bad Status Values should now be run to make sure that none of the Stage feature classes include non-standard values for Status. These can creep into the mix if aperson updates status values outside ofthe Attributes panel. The danger of letting badvaluespersistbefore the next step is that models with bad statusvalues will dissappear without a trace. (They can be recovered, but only after someone notices that they are missing.)

    This task will halt with an error if a bad status value is encountered. Looking through the task's messages will reveal which feature class has a bad status value.

  3. The task, Sort Models into New Feature Classes uses the geoprocessing tool, 5d. Status Router to iterate through eachof the multipatch feature classes inthe Stage geodatabase, selecting models according tostatus class, and appending each set to the appropriate feature class.
  4. The Copy Misc FCs and Create Building Footprints task copies the Issue Points and Development Log table from Stage into the next edition feature class. These are useful to include for reference. The building models from the Active_MP feature class (excluding walls) are alsorendered as apolygon feature class with this task.
  5. Finally, the Generate Model Catalog task produces the one-table comprehensive catalog of models. The table starts as a geodatabase point feature class, and is also rendered as a CSV table and a GeoJson file.