Moving Toward 3D Geologic Data 13 April 2020 Alaska Division of Geological amp Geophysical Surveys 3354 College Rd Fairbanks AK 99709 Mike Hendricks Jen Athey Trish Ekberg Chris Wyatt et al ID: 920758
Download Presentation The PPT/PDF document "Layer Support in AK GeMS" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Layer Support in AK GeMS Moving Toward 3D Geologic Data13 April 2020
Alaska Division of Geological & Geophysical Surveys
3354 College Rd, Fairbanks AK 99709
Mike Hendricks, Jen Athey, Trish Ekberg, Chris Wyatt, et al
Slide2AgendaQuick Update of AK GeMS Development StatusLayer Support in AK GeMS
Slide3Key Aspects of AK GeMSGreater focus on modeling Geologic Features (as opposed to graphic elements) to better support not only quality map production, but also database queries & web deliveryBased on federal
GeMS standard & supports exports to this standard for delivery to USGSSupports multiple maps in an
enterprise database (PostGreSQL)Supports multiple layers (i.e. bedrock, surficial, others)Designed with existing AK DGGS Databases (GERILA) & Procedures in mindFormalized Pick Lists (Attribute Domains) and Glossary“Well”
Documented
Slide4Data
store
ArcServer
ArcGIS Enterprise
federated
Hosting
Server
Other Content
Collaborations
https://geoportal.dggs.dnr.alaska.gov
DGGS
Portal
AK GEMS
PostgreSQL
x2
In Production
Maps
Geologic
Data
(
GERILA
)
Basemap
Data
(GIS)
Field Geology Support System
Station, samples, etc.
Older
Published
Maps
Supporting
GeoDatabases
many
convert
Public
DGGS Website
GeMS
-DGGS
MulitMap
Gems-DGGS Database
Schema: gems
Datum: NAD83
Projection: AK Albers
All Individual Map Features.
Single gems schema
Edge Issues &
Overlap NOT adjusted
PUBLISH
AK
GeMS
focused Geologic Mapping System
Map pdf & single map
GeMS
File Geodatabase
Converted
& loaded
load
Reference
Join &
Relate
load
to AK
GeMS
AK GEMS
File
GeoDB
Slide5DGGSWebsite
Alaska DGGS Geologic Mapping System Products
Single Map
GeMS
Archive
Geodatabase
Single Map
GeMS
Production
Geodatabases
Multi Map
GeMS
Repository Geodatabase
Single Map
GeMS
Archive
Geodatabase
Geologic
Feature
Services & Apps
Field Event
Geodatabases
To
USGS
Mapping
Process
Print, pdf,
&
Rasterize
Geologic
Map
Image Service
Convert
Load
Export
Cartographic Product
Product Web PageAlaska DGGS
Alaska DGGSAlaska DGGS
USGSAlaska DGGS
QualityControlDocumentationCurrently ManualWorking with ESRI to develop
Data Reviewer Rule Sets & ProceduresFuture: Maybe ESRI Data InteroperabilityExtension?Future: Maybe ESRI Data Interoperability Extension?
Slide6Key Differences between AK GeMSSingle Map and
Multi-Map
Feature_IDs true UUID Field types (as opposed to Text) and populated with UUIDsDomains and domain fields are type IntegerData Sources Many-to-Many Relationship Classes builtNo
Cross Section Feature Datasets
No Correlation of Map Units Feature DatasetStatewide Projection: Alaska Albers Equal Area
Multi Map
GeMS
Repository Geodatabase
Geologic
Feature
Services
Load
Alaska DGGS
Slide7Moving Toward 3D Geologic DataLayer Support in AK GeMS
Slide8Geomaterial
dictionary table
descr
map units
table
map_unit_polys
map_unit_lines
map_unit_points
orientation_points
station_points
geochron_points
fossil_points
contacts_and_faults
product_info
cartographic_polys
cartographic_lines
cartographic_points
data_sources
geologic_polys
geologic_lines
geologic_points
overlay_polys
data_source_polys
glossary
structure_polys
structure_lines
iso_lines
= AK
GeMS
addition
Map Units and their boundaries
Structure info
Other geologic
Info
Cartographic
features
Thematic points
symbol_info
table
confidence lookup tables
Combined ‘map unit’ and ‘other’ overlay polys
includes ‘generic points’
Alaska DGGS
GeMS
Production
GeodatabaseSchema
Currently only modeling Layers in
Map Units and their boundaries
Slide9Some of the issuesGeMs Specifies that as part of the Map Graphic the requirement for “map-unit polygons (that cover the mapped area without gaps or overlaps…”
This assumes (a) single conceptual surface being modeled, and (2) as result a geodatabase “Planar Topology” (Note the importance of Planar
) can adequately check for logical inconsistenciesCartographically as part of a “Map Graphic” this can make sense, but breaks down when attempting to generate logically consistent robust geologic data with a map that includes both bedrock and surficial unitsThe Topologic Rule Must not have gaps dictates that the ‘known’ bedrock polygon under surficial polygons must be deleted to ensure a valid topology
A human geologic map reader understands that the dashed hidden contacts means that the bedrock continues under the surficial unit (with some level of certainty). The current data model cannot do this.
Top
of Bedrock
“surface”
Top of Surficial “surface”
Slide10Allowing for Overlapping “Layers”Bedrock Layer
Surficial Layer
Planar topology
Planar topology
Layer field
1
-1
Surficial Layer
2
Planar topology
Allows for additional layers as needed
Experimented with the use of the layer field set as a subtype in Arc, but currently am not employing subtypes
Slide11Example: A Conversion Map in Progress2. Pattern Draw as feature in
cartographic_polys
1. Tephra Region stored as a map unit in layer 2
Note: We
also added layer to DMU table
Slide12Contacts and Faults Layers
Challenging!We think we can calculate contour layer from
map_unit_poly’s layer value & map unit polygon topology
B1
S1
S1
Layer
1
-1
B2
S2
Type
Category
Concealed
B
M
N
0
B
M
C
G
N
1
F
G
Y
-1
C
G
Y
-1
F
G
N0C
G
N
1
CG
N1CG
N1
N0
SBBB BBSBSBSSAlternate symbol (symbol_alt) required if switching between surficial ON or OFF
CategoriesB – BoundaryC – ContactF – FaultTypeM – MapG – GenericSB – Surficial/Bedrock
SS – Surficial/Surficial
BB – Bedrock/Bedrock