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
Next revision Both sides next revision
start:meetingnotes [2020/03/11 19:42]
jeathey
start:meetingnotes [2020/03/11 20:37]
jeathey
Line 27: Line 27:
 Evan Evan
 =====October 7, 2019===== =====October 7, 2019=====
-Alaska DGGS [[https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:gems_CDEFG_mtg_06_Oct_1019.pptx|presented]] an overview of work to date on the enterprise multi-map database and system. Recording: https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:CDEFG_GeMS_multi-map_project_and_documentation_update-20191007_1804-1.mp4+AK DGGS [[https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:gems_CDEFG_mtg_06_Oct_1019.pptx|presented]] an overview of work to date on the enterprise multi-map database and system. Recording: https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:CDEFG_GeMS_multi-map_project_and_documentation_update-20191007_1804-1.mp4
 =====September 3, 2019===== =====September 3, 2019=====
 Joe Colgan, USGS and team members presented their FEDMAP project and geologic map database, "Geologic Framework of the Intermountain West." Recording: https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:cdefg_fedmap_project_presentation-20190903_1802-1.mp4 Joe Colgan, USGS and team members presented their FEDMAP project and geologic map database, "Geologic Framework of the Intermountain West." Recording: https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:cdefg_fedmap_project_presentation-20190903_1802-1.mp4
 =====August 12, 2019===== =====August 12, 2019=====
-DGGS staff [[https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:gems_cdefg_mtg_12_aug_1019.pptx|presented]] a project update and future work.+AK DGGS staff [[https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:gems_cdefg_mtg_12_aug_1019.pptx|presented]] a project update and future work.
 =====May 13, 2019===== =====May 13, 2019=====
-Jen Athey, AK DGGS presented a [[https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:dmt2019_athey_gemsenterprise.pptx|preview]] of her 2019 Digital Mapping Techniques talk and showed a [[https://geoportal.dggs.dnr.alaska.gov/portal/apps/webappviewer/index.html?id=8f63d03f39024da1b9f2124c4a3ebe96|demo]] of DGGS' multi-map database implementation.+Jen Athey, AK DGGS presented a [[https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:dmt2019_athey_gemsenterprise.pptx|preview]] of her 2019 Digital Mapping Techniques talk and showed a [[https://geoportal.dggs.dnr.alaska.gov/portal/apps/webappviewer/index.html?id=8f63d03f39024da1b9f2124c4a3ebe96|demo]] of DGGS' multi-map database implementation. Mike Hendricks previewed his [[https://ngmdb.usgs.gov/Info/dmt/docs/DMT19_Hendricks1.pdf|presentation]] on incorporating geologic layers in GeMS. [[https://dggs.alaska.gov/oldgemswiki/en/Meeting_Notes.html#May_13.2C_2019|More information]]
 =====March 11, 2019===== =====March 11, 2019=====
-AK DGGS presentation included general CDEFG project update, topological lessons learned, and [[https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:gems_bedrock_surficial_topological_considerations.pptx|information on geological surfaces]] (surficial, bedrock, basement, other), responses from geological surveys about how they handle bedrock and surficial units on maps, possible database solutions, and tweaks to the draft database model. +AK DGGS presentation included general CDEFG project update, topological lessons learned, and [[https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:gems_bedrock_surficial_topological_considerations.pptx|information on geological surfaces]] (surficial, bedrock, basement, other), responses from geological surveys about how they handle bedrock and surficial units on maps, possible database solutions, and tweaks to the draft database model. [[https://dggs.alaska.gov/oldgemswiki/en/Meeting_Notes.html#March_11.2C_2019|Minutes and files]] 
- +=====February 11, 2019===== 
-Minutes for March 11, 2pm ET\\ +Meeting included presentation by Esri on Data Reviewer and a [[https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:presentation20190211.pptx|presentation]] by Jen AtheyAK DGGS on bedrock and surficial map data in multi-map databaseRecording: https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:cdefg_data_reviewer_and_more-20190211_1903-1.mp4 [[https://dggs.alaska.gov/oldgemswiki/en/Meeting_Notes.html#February_11.2C_2019|More information]] 
-1. Roll callTracey, Andy Cyr, Jen, Chris H, Chris W, Etienne, Amber, Charlie, AGS Andrew and Laura, Lina\\ +=====January 14, 2019===== 
-2General CDEFG project update: From Nov 2018 - Feb 2019 we converted four geologic maps to the GeMS format, concentrating on parsing the data and filling out the attributes correctlyConversion appears to take about 4 weeks for a data-rich 1:63,360 mapWe'll share some of what we've learned nextFrom March - June 2019, we'll be testing the multi-map database by creating three maps in GeMS format and creating a compilation map from them.\\ +Meeting about the multi-map database GeMS feature classes and attributes to discuss potential adds/deletes to the schemaFeedback during the meeting was collected in this [[https://dggs.alaska.gov/gemswiki/lib/exe/fetch.php?media=start:gems_delta_feature_classes_comments.docx|document]][[https://dggs.alaska.gov/oldgemswiki/en/Meeting_Notes.html#January_14.2C_2019|More information]]
-3. Topological lessons learned +
-  *Sub-millimeter-scale dangles and gaps. We discovered in an ArcInfo-era dataset we were converting that there were many tiny dangles and gaps in multipart features and other multipart feature oddities. We are not sure if the topological errors were introduced later or if it was problem from the original datasetAside from manually fixing the errors, we experimented with other Esri solutions, particularly changing the topology cluster tolerance, which actually moves and fixes the topological errorsWith topological errors this small, we were wondering how the community feels about fixing them versus leaving themMore information at topology lessons learned.pdf. +
-  *Amber said that creating data in ArcPro using Network Analyst might have advantages with topology. Other folks on the line said they haven't used anything other than the default topology cluster tolerance. They would rather have the dataset be manually cleaned upparticularly if any analysis will be run on the data layers. The data should be meaningful, which wouldn't be the case for random sub-millimeter arcs. It was suggested to draw lines first and then build polygons from them, which might result in fewer topological errors. +
-4. Geological surfaces (surficial, bedrock, basement, other) +
-  * Responses from geological surveys about how they handle bedrock and surficial units on maps. Eastern US states and Canada are more likely to keep mapping, map presentation, and GIS files separate for bedrock and surficial data. Some factors that may influence this could be that East Coast geology is already complicated and having surficial on top gets too complicated for 2D map, and the mid-continent geology is often only surficial unitsAnother factor for the western states could be the cost-savings of putting surficial and bedrock together to cover large areas. (http://137.229.113.30/jamwiki/en/File:Mapping_bedrock_and_surficial_%281%29.png, http://137.229.113.30/jamwiki/en/File:Bedrock_and_surficial_presentation.png, http://137.229.113.30/jamwiki/en/File:Bedrock_and_surficial_GIS.png) +
-  * Possible database solutions. DGGS is strongly considering separating bedrock and surficial GIS to minimize data loss and allow for more rapidly changing surficial data. (GeMS Bedrock Surficial Topological Considerations.pptx) Andrew suggested another method would be to have a single table for the polygons that references another table with cartographic, unit, stratigraphic, and other informationAlthough this might be more complicated, it is not unusual to have a middle step negotiating between the database and webGIS data, for example. Amber said it will be important to get this right since it has implications for data curationIn Andy Cyr's surficial database, they keep track of what bedrock units are under the surficial and subordinate units, but they don't keep track of contacts under the surficialAmber is working with Andy and Kevin Schmidt to format their data into GeMS. +
-5. Tweaks to the draft database model(draft db model.pdf) DGGS is considering accepting additional database formats in the psdb Geologic Maps "Quarantine" step prior to the psdb Geologic Data "multi-map" databaseThere's not enough DGGS database administrator time available to correctly manage and train all of the geologists in using a Postgres database from the get-goFor projects that don't require multi-user editing and other enterprise database functionality, it might be acceptable to use file geodatabases insteadWe see this part of the enterprise GeMS database conforming to the needs and resources of the particular organizationMaps would still need to be migrated to Postgres to be entered into the psdb Geologic Data "multi-map" database. +
- +