GeMS Wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
start [2020/03/11 20:46]
jeathey
start [2023/02/10 23:38] (current)
jeathey
Line 3: Line 3:
 =====Collaborative Database Effort for Geology=====  =====Collaborative Database Effort for Geology===== 
 ==Building a multi-map, multi-user GeMS database== ==Building a multi-map, multi-user GeMS database==
-The Alaska Division of Geological & Geophysical Surveys (DGGS) has undertaken the challenge of developing a multi-map, multi-user database model based on the single-map Geologic Map Schema (GeMS) developed by the USGS and state geological surveys. The multi-map model is intended for national use. A multi-map geodatabase will help DGGS meet the future goal of a 1:100,000-scale Alaska compilation, and provide a vehicle for other geologic surveys and agencies to organize and share their own geologic data. DGGS is seeking interested individuals to take part in discussions via teleconferences to provide input on the needs of geologic surveys and other organizations, help develop the specifications of the database model and data-sharing protocol, and share ideas to help the community.\\+The Alaska Division of Geological & Geophysical Surveys (DGGS) has undertaken the challenge of developing a multi-map, multi-user database model based on the single-map Geologic Map Schema (GeMS) developed by the USGS and state geological surveys. The multi-map model is intended for national use. A multi-map geodatabase will help DGGS meet the future goal of a 1:100,000-scale Alaska compilation, and provide a vehicle for other geologic surveys and agencies to organize and share their own geologic data. DGGS is seeking interested individuals to take part in discussions via teleconferences to provide input on the needs of geologic surveys and other organizations, help develop the specifications of the database model, and share ideas to help the community.\\
 ----------------- -----------------
  
 \\ \\
-Telecons or Webex will usually be held the 2nd Monday of the month. <color #ed1c24>**The next meeting is tentatively scheduled for __Monday, April 13, 2020, 2pm ET__.**</color>+Telecons or Webex will usually be held the 2nd Monday of the month. <color #ed1c24>The next meeting is scheduled for __Monday, March 13, 2023, 2pm ET__</color>.
  
-__Draft April 13, 2020 Agenda__ +Agenda for March 13 
-  - Roll call +  * Introductions and comments 
-  - Looking for two states to talk about their 3D extensions to GeMS or general 3D work +  Next CDEFG meeting date is likely March 13Topic TBD.
-  - Next meeting tentatively May 11Don Sweetkind will present on his 3D work and ideas.+
  
 +Possible topics for future meetings
 +  *  Geologic map production at state geological surveys and USGS programs
 +  *  Presentation: Attribute Rules and Dictionary Symbology in ArcGIS Pro Help Streamline Geologic Map Compilation in GeMS, by Tracey Felger, USGS
 +  * Implications of switching from ArcMap to ArcPro for the public, file types, USGS deliverables, etc.
 +  * How to conduct GIS and geologic reviews of GIS files
 +  *  Use cases of feature templates, domains, and attribute rules
 +  * Field-to-archive deep dive into each geological survey's staffing, processes, data management, publications, etc.
 +  *  Implementation and Migration of ArcEnterprise Portal: James Amato, Wyoming State Geological Survey
 +  * Follow up talk—Best Practices for Removing Collars of No Data from ArcMap: James Amato, Wyoming State Geological Survey
 +  * Efficient methodologies for heads-up digitizing and GeMS attribution: Tracey Felger, USGS
 +  *  NRCan's image database schema and exif header metadata: Étienne Girard, NRCan
 +  * "Best of CDEFG" from Alaska geological survey: Mike Hendricks, DGGS
 +  * Using Esri's ArcGIS Hub to deliver GIS data to users
 + 
 __Table of Contents__ __Table of Contents__
   *  [[start:meetingnotes|Meeting Notes]]   *  [[start:meetingnotes|Meeting Notes]]