NoPublic, bureaucrat, administrator
6,632
edits
Changes
no edit summary
[[Image:Staging_Area_Model_Hazard.png|center|700px]]
For more on column names in the Staging area, see [[Name Rules Staging Area]], and for post-processing, see [[Post Processing SQL Scripts]].
===Special table===__NOEDITSECTION__
{| class="wikitable" width="1000'"
|-
|}
==Geographical data in the IMSMA staging area==__NOEDITSECTION__
{{Under construction| This section is under construction}}
When polygon/polyline is linked with the main object the properties from the main object applies to the entire object. This also applies to calculated area and length e.g. if Land-35 has three polygons with (total) calculated area 200 m2 then 200 is repeated on the three polygon rows.
===Point, Polyline and Polygon tables===__NOEDITSECTION__
If the option of generating geodata has been chosen on the [[Staging Area Generator]] interface, then three related tables with geodata are generated for every main object/table (ACCIDENT, VICTIM, QM, HAZARD (Land), etc.):
A series of database views are pre-defined on the staging area, three for each object: <OBJECT>_POINT_VIEW, <OBJECT>_POLYGON_VIEW and <OBJECT>_POLYLINE_VIEW - where <OBJECT> is HAZARD, GAZETTEER, MRE, etc. - each object that potentially has associated geodata. Each view is defined as an '''INNER JOIN''' between the <OBJECT> table, e.g. HAZARD, and each of the three geodata tables. The inner join means that data from e.g. the HAZARD table that has '''no''' polygon associated will not be found in the HAZARD_POLYGON_VIEW. Depending on the use case, either the tables or the views can be accessed.
{{NavBox Business Intelligence}}
[[Category:VIE]]
