Download - 2012. Ice-wedge polygons geodatabase - poster

M. Lousada1, M. Jorge3 , C. Lira 1, J. Saraiva1,2 , P. Pina1, L. Bandeira1

1 CERENA/IST, Lisboa, Portugal.2 UNIS, Longyearbyen, Svalbard, Norway. 3 CEG/IGOT, Lisboa, Portugal

Polygonal networks are very common on the Martian surface, and their location has been correlated with the presence of ice in the soil.

The most accepted hypothesis for their origin takes into account their similarities to polygonal networks on Earth, which mostly occur in periglacial areas. Ice-wedge

polygonal networks are being studied in Svalbard, Norway, in the framework of project ANAPOLIS. Field study and characterization of these structures involves the local

detailed delineation of networks resulting in large amount and variety of data collected, with a common reference system. The construction of a GDB for the Adventdalen

data allowed linking the raster, vector and numeric data, making them available in an organized manner, offering a intuitive access to the multidisciplinary teams involved in

the project.

SVALBARD

GEODATABASE

Área

Área

Área

Geodatabase schema diagram

Point feature class Field measurements of polygons wedges,

(width and depth of contours).Field_measurements

Polygon feature class Footprints from rasters with poligons network

areas in Adventdalen.Network_areas_footprints

Line feature class lines representing incomplete polygons.

Opened_polygons

Point feature class

Polygons_centroid_coordinates_xy

Polygon feature class Poygon feature class representing contours

from all areas with networks in Adventdalen.

Subtypes point to respective ortophotomap by

color classification in the map.

Polygons_contours

Subtypes are Orto 143, Orto 144, Orto 145

Annotation feature class Feature linked annotation (polygon field

number). The text its placed on maps with

polygon contours, each piece of text stores its

own position, text string, and display properties.

Polygons_ContoursAnno

Line feature class Elevation contour lines generated from field

topography data obtaind in the 2010 campainTopography_contour_lines

Point feature class Field topography coordinates (x,y,z), obtaind

with a DGPS in the 2010 campainTopography_field_coordinates_xyz

Point feature class Polygons vertices coordinates (x,y,z), obtaind

with a DGPS in the 2010 campainVertices_field_coordinates_xyz

Polygon feature class Voronoi diagrams generated with polygons

centroid coordinates. Subtypes point to

respective ortophotomap by color

classification in the map.

Voronoi_diagrams

Subtypes are Orto 143, Orto 144, Orto 145

Polygons centroid coordinates.Table

polygons_centroid

Zonal statistics by polygon area, over a slope

(degrees) raster derived from topography field

data, includes standard deviations, average

and sum.

Table

Slope_zonal_statistics

Relationship class

One to One

Polygon_Field_nº

Relationship class

One to One

Polygons_centroid

Simple feature class

Network_areas_footprints Contains Z valuesContains M values

Geometry PolygonNoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allow nulls

OBJECTID Object ID

Shape Geometry Yes

id String Yes 10

Shape_Length Double Yes 0 0

Shape_Area Double Yes 0 0


Opened_polygons Contains Z values

Contains M values

Geometry PolylineNo

No


Allow nulls

OBJECTID Object ID

Shape Geometry Yes

Id Long integer Yes 0



Polygons_centroid_coordinates_xy Contains Z valuesContains M values

Geometry PointNoNo


Allow nulls

OBJECTID Object ID

Shape Geometry Yes


Área Double Yes 0 0

Field_ID Long integer Yes 0

x_centroid Double Yes 0 0

y_centroid Double Yes 0 0


Polygons_contours Contains Z valuesContains M values



Allow nulls

OBJECTID Object ID

Shape Geometry Yes


Área Double Yes area 0 0




Orto Short integer Yes 143 0



Default value

List of defined default values and domains for subtypes in this class

DomainField nameSubtype

Description

Default subtype

Subtype field

SubtypeCode

Subtypes of Polygons_contours

Orto

143

143 Orto 143 Área area



Annotation feature class

Polygons_ContoursAnno Contains Z valuesContains M values

Geometry

NoNo


Allow nulls

OBJECTID Object ID

SHAPE Geometry Yes

FeatureID Long integer Yes 0

ZOrder Long integer Yes 0

AnnotationClassID Long integer Yes 0

Element Blob Yes 0 0 0

SymbolID Long integer Yes 0

Status Short integer Yes 0 AnnotationStatus 0

TextString String Yes 255

FontName String Yes 255

FontSize Double Yes 0 0

Bold Short integer Yes BooleanSymbolValue 0

Italic Short integer Yes BooleanSymbolValue 0

Underline Short integer Yes BooleanSymbolValue 0

VerticalAlignment Short integer Yes VerticalAlignment 0

HorizontalAlignment Short integer Yes HorizontalAlignment 0

XOffset Double Yes 0 0

YOffset Double Yes 0 0

Angle Double Yes 0 0

FontLeading Double Yes 0 0

WordSpacing Double Yes 0 0

CharacterWidth Double Yes 0 0

CharacterSpacing Double Yes 0 0

FlipAngle Double Yes 0 0

Override Long integer Yes 0

SHAPE_Length Double Yes 0 0

SHAPE_Area Double Yes 0 0


Topography_contour_lines Contains Z values

Contains M values

Geometry PolylineNoNo


Allow nulls

OBJECTID Object ID

Shape Geometry Yes

ARCID Long integer Yes 0

GRID_CODE Long integer Yes 0

FROM_NODE Long integer Yes 0

TO_NODE Long integer Yes 0



Topography_field_coordinates_xyz Contains Z valuesContains M values

Geometry PointNoNo


Allow nulls

OBJECTID Object ID

Shape GeometryYes

POINTID Long integerYes

0

GRID_CODE DoubleYes

0 0


Vertices_field_coordinates_xyz Contains Z valuesContains M values

Geometry PointNoNo


Allow nulls

OBJECTID Object ID

Shape Geometry Yes

POINTID Long integer Yes 0

x Double Yes 0 0

y Double Yes 0 0

z Double Yes 0 0

x_1 Double Yes 0 0

y1 Double Yes 0 0


Voronoi_diagrams Contains Z valuesContains M values



Allow nulls

OBJECTID Object ID

Shape Geometry Yes

FID_1 Long integer Yes 0

ID Double Yes 0 0

GRIDCODE Double Yes 0 0

FID_2 Long integer Yes 0

Id_1 Long integer Yes 0





Distance Double Yes 0 0

orto Long integer Yes 143 0



Default value

List of defined default values and domains for subtypes in this class

DomainField nameSubtype

Description

Default subtype

Subtype field

SubtypeCode

Subtypes of Voronoi_diagrams

orto

143

143 Orto 143

144 Orto 144

145 Orto 145

Table

polygons_centroid


Allow nulls

OBJECTID Object ID






Table



Allow nulls

OBJECTID Object ID

ID Long integer Yes 0

PolyFID Long integer Yes 0

ZSTATS_MIN Double Yes 0 0

ZSTATS_MAX Double Yes 0 0

ZSTATS_AVG Double Yes 0 0

ZSTATS_STD Double Yes 0 0

ZSTATS_SUM Double Yes 0 0

ZSTATS_CNT Long integer Yes 0

object_id Long integer Yes 0

Relationship class

Name

Primary key

Foreign key

Type

Cardinality

Notification

Forward label

Backward label

Polygon_Field_nº

Origin feature class Destination feature class

Composite

One to many

Forward

Polygons_ContoursAnno

Polygons_Contours

Polygons_contours

OBJECTID

FeatureID

Polygons_ContoursAnnoName

Relationship class

Name

Primary key

Foreign key

Type

Cardinality

Notification

Forward label

Backward label

Polygons_centroid

Origin table Destination feature class

Simple

One to one

None

Polygons_contours

polygons_centroid

polygons_centroid

x_centroid

x_centroid

Polygons_contoursName

Coded value domain

AnnotationStatusDescription

Field type

Split policy

Merge

policy

Valid annotation

state values.

Short integer

Duplicate

Default value DescriptionCode

0 Placed

1 Unplaced

Range domain

areaDescription

Field type

Split policy

Merge

policy

polygon_area

Double

Geometry ratio

Sum values

Maximum valueMinimum value

0.1 1000000

Geodatabase Data Model Summary

Relationship class

One to One

Slope_statistics

Relationship class

Name

Primary key

Foreign key

Type

Cardinality

Notification

Forward label

Backward label

Slope_statistics

Origin table Destination feature class

Simple

One to one

None

Polygons_contours



OBJECTID

OBJECTID

Polygons_contoursName

Polygon feature classes

Topology_rules

Topology ruleFeatures intarget feature class Features in comparison feature class

Polygons_centroid_coordinates_xy

Field_measurements

Vertices_field_coordinates_xyz Polygons_contours

Must be Covered by Boundary Of

Must not Self Overlap

Polygons_contoursMust Be Properly InsidePolygons_contours

Must be Covered by Boundary Of

Polygons_contours Polygons_contours

Custer tolerance 0.000000001

Point feature classes

Line feature classes

Tables

Annotation feature class

Topology

Domains

Point feature class representing the polygons

xy centroid


Field_measurements Contains Z valuesContains M values

Geometry PointNoNo


Allow nulls

OBJECTID Object ID

Shape Geometry Yes


Field_ID_1 Long integer Yes 0

I. IDENTIFY PURPOSE

Reference Sistem: WGS_1984_UTM_Zone_33N

Projection: Transverce MercatorZone 33N

Datum: WGS_1984

V. EDITING METADATA

Orthophotomaps (0.2 m/pixel) /Topographic and

Geomorphologic map/Aereal images Geokolibri/ Field

Topography Grid / Field data, coordinates, width and depth

of polygons contours.

II. IDENTIFY THE DATA

Raster - Georeferencing, Orhorectifing, Mosaicing Orthos into

raster Dataset

Vectorial and numeric - Editing Data, Generating new data

(Zonal statistics by polygon area Voronoi diagrams, etc.) .

Description/Spatial Reference /Status of the

data/Publication Information .

Store a large collection of raster , vectorial and

numeric , spatial data in a centralized location so that

it could be accessed by the multidisciplinary teams

involved in the project.

VIII. REVERSE ENGINEERING A GEODATABASE TO A DIAGRAM AND A DIAGRAM TO A GEODATABASE

CASE TOOLS

XML DOCUMENT

ARCCATALOG® The computer-aided software engineering (CASE) tools subsystem allows to create blueprints of

the structure of the geodatabase using a graphical language—the Unified Modeling Language (UML).

The use of GDB has many advantages, it ensures that no excess (or duplicate) information is stored, has much faster raster visualization

The Svalbard GDB schema was exported to Microsoft Visio® with the use of Geodatabase Diagrammer tool, the graphics are automatically generated in MS Visio® to construct the data model.

with pyramid building and data occupies less space on disk. The Svalbard uncompressed GDB, occupies 12.6 GB of space disk, the same data in a normal windows

folder, occupies 28.8 GB. A GDB is designed for maintenance and performance. Using topology, network rules and spatial relationships it was possible to add behavior to

the GDB. Additionally the interoperability with CASE Tools has been of great value in the construction and updating of the Svalbard GDB.

VII. SHARING AND MAINTAINING

VI. ADDING BEHAVIOR TO THE GEODATABASE

AND ENFORCING THE INTEGRITY OF THE DATA

Sub-types - Setting a default value for the respective Ortophotomap number that

will automatically apply when creating new polygons features.

AtributesDomains defining a logic range for the areas field attribute of

Polygons_contours.

Split policy - for polygons areas field attribute - Geometry ratio.

Merge policy - for polygons areas field attribute - sum.

Relationships - defining how rows in Polygons_contours table can be associated

with rows in Polygons_centroid table, with a direction of cardinality, one-to-one.

Topology rules - Polygons-contours -( Must Not Self Overlap).

Feature-linked geodatabase annotation - If the feature polygons_contours is moved

or deleted, the annotation with field nº moves with it or is deleted.

INTRODUCTION

METHODS

RESULTS

CONCLUSION

III. SETING SPATIAL REFERENCE

IV. PREPARE THE DATA