The Spot-Growth
Database Administration Application was used to load some 'SPB'
and 'ASP' files--old formats of Spot-Visit data, and then
save the information from those multiple files as a single
SpotGrowth
schema Xml file containing every bit of information that was
made available--the result SpotGrowth Xml file is a
mini-database of verified, from-the-field, data.
That data was also saved, using the SGDB Admin app, as Excel
format Xml. Windows/Office will recognize a file with this
content, named 'anything.xml', as an Excel spreadsheet.
The SpotGrowth data was then loaded using the other desktop
application, the SharpHog Southern Pine Beetle Infestation
Model Administration Application. This powertool is ready to
read SpotGrowth Spot-Visits, and uses Xslt internally to turn that
into SharpHog input Batches and Frames. This dataset was saved, and
is a SPBModel
schema file containing only Input.
The input dataset could be loaded and run through the model
as-is, or tweaked, or changed altogether, rearranging frames and
batches before running through the model. The result (output) will
be another dataset, still subscribing to the SPBModel Schema, this
time, though, there is output calculations alongside the input.
The Output dataset was then transformed into an Html Table
summarizing the results. This parsing of the SharpHog
Output depends on the fact that the original data-source was
SpotGrowth data, and the Batches and Frames of the SharpHog Input
therefore mirror a Spot-Visit format. It simply wouldn't make
sense to apply this transform to data calculated from input not
based on actual field data.
-
SharpHog uses latitude and longitude along with day of the year,
to calculate a temperature at that spot and time.
There are two sets of information presented here, but only the
first is currently used. The first set of States Data comes
directly from values used by previous spb models for Average
Latitude and Average Longitude. These original values only
exist for the twelve Southeastern states originally covered by the
HogModel.
Don't miss the Disclaimer Page.
Technically, though, any latitude below 60 is acceptable to the
model, and there are pine beetles in other areas of the country
also. The second set of data was collected from some online
source somewhere, and the values for the states that the two lists
have in common
-
The Spot-Growth Database Project uses
an Xml Schema Definition called SpotGrowth.xsd to define the
structure, types, values, and relationships allowed in SpotGrowth
xml. When field data is loaded from other formats using the
Spot-Growth Database
Administration Application for Windows Desktop, it can from
there be saved in the new SpotGrowth format.
Right-Click to Save the
SpotGrowth Sample Set
Our sample set of data looks like this in SpotGrowth xml.
-
As stated elsewhere, All Modern Applications Use Xml.
Every computing environment has numerous avenues for creating
documents on the computer. Text files, for example, can be
written in standard ASCII to be recognized be text editors on
Linux, Macs, or Windows machines. It took a while, but the
international community has settled on an International Standard
for other common documents: word-processing application documents,
spreadshet documents, presentation documents--in short, Office
Documents.
While the topic is not
without contention, an international standard multi-part
specification for office documents includes the Office Open Xml specification.
Right-Click to Save the
Excel Workbook to Your Desktop
When the SPBField to Excel Xslt has been
applied to our sample Spot Growth xml, the result looks
like this. The Open Office
-
The SharpHog Southern Pine Beetle Infestation Model
Administration Application for the Windows Desktop can load Xml
formatted to the Spot-Growth Database project's SpotGrowth Xml
schema, and convert it to a SharpHog dataset containing only input
for the model, based on the Spot-Visits in the source data.
Right-Click to Save the Sample
SharpHog Model Input DataSet
Data from the Spot and Visit tables (SharpSpb Xml has been
designed to mimic traditional data-tables) of the Spot-Growth
Database information have been transformed into data for the Batch
and Frame tables of the SPBModel Schema. The third table in
the SharpHog Model's SPBModel schema is the EngineOuput table.
This example xml contains Input data for SharpHog only, so
there is no data yet in the EngineOutput table (no EngineOutput
-
Here is what the important parts of an SPBModel xml file look
like, after the model has been run on the input. In this
case, only one Frame of the shown Batch is marked for inclusion in
the runs.
-
Here is a sample Value Request, a bit of Xml used internally by
SharpHog, and defined by the ValueRequest.xsd schema. Each hour
the model sends a Request for all the Values that come from the
Xslt equations, then stores them for use during the iteration.
This sample only requests the the EggDensity, the
EggActivity, the EggMortality, and the EggDevelopment Rates for
this moment. Provided with the Request are the Spot
conditions used to calculate the rates, and the Initial Tree Counts
(which are used currently only in Initial Population
equations).
