WI_GeMS_changelog: MUP: 1. Calculated fgdc symbols for fill color and changed 'symbol' in MUP to those respective numbers - originally used Sam's tool, but wrote a different one that doesn't use colormath and just rounds to the nearest fgdc step (30,40,etc) and is similarly close, so used those values mostly. Used Sam's tool due to non-repeating numbers in instances of a repeated symbol value. These are highlighted in DMU_colorsGuessed.xlsx 2. changed w label to water 3. a few colors came out wonky - so manually changed them to be as close as possible to original using CMY from colorpicker - o changed from 895 (was 895 from both Sam and I's scripts) to 465 - should be a brownish, but came out green - Rr change from 752 (was 752 for both Sam and I's scripts) to 352 - should be a brownish, but came out green. Changed from closest value (353) to 352 b/c se also is 353 4. several labels did not correspond to respective MapUnit - so changed those to == MapUnit (note these are original OID's, not the version I've edited, due to remaking polys) - OID 237 changed label from sn to lp - OID 260 changed label from sn to lp - OID 293 changed label from sn to lp - OID 7 changed label from Wb to We - OID 72 changed label from Wb to WeS - OID 94 changed label from Wb to We - OID 115 changed label from Wb to We - OID 118 changed label from Wb to We - OID 125 changed label from Wb to We 5. changed slightly the fgdc codes/colors used for units that had patterns (many had the same color as related units) 6. kept original AreaFillRGB values and AreaFillPatternDescription in DMU CAF: 1. symbol for all type == 'contact' changed from 'contact' to '01.01.01' (fgdc) 2. symbol for all type == 'uncertain contact beneath units rb and ru' changed to '01.01.06', 'contact - identity and existence questionable, location inferred' 3. changed all IsConcealed from 'N' to 'n' 4. reversed directions on OID 5527- 5529 so the '?' displays correctly 5. deleted 'Feature is only for legend swatch' feature 6. converted all contacts that ouch water to 'shoreline' instead of just 'contact' 7. symbols == 01.01.06 and 30.02.29 (questionable contact and shoreline, respectively), locationconfidencemeters changed to -9 CartographicLines: 1. 'ice flow direction indicated by drumlins and other streamlined landforms' changed symbol from 'ice flow' to '13.30', 'ice-molded landform' 2. 'meltwater flow direction indicated by general slope and relict channels' changed symbol from 'meltwater flow' to '13.09', 'meltwater channel' 3. 'spillway flow direction from major proglacial lakes' changed symbol from 'spillway' to '13.3', 'glacial-lake spillway' 4. 'subglacial flow direction indicated by eskers' changed symbol from 'subglacial flow' to '13.18', 'esker or ice channel deposit' (direction known) 5. 'wind direction indicated by dunes' changed symbol from 'wind direction' to '16.07', 'wind direction determined from dune forms' 6. changed all IsConcealed from 'N' to 'n' 7. wind direction and flow direction by drumlin put into OrientationPoints fc - used 'generate points along lines' tool set to 50%, no endpoints to get middle of line feature 8. deleted wind direction and flow direction by drumlins from CL FC 9. deleted 'Feature is only for legend swatch' features 10. moved all to GeologicLines FC OrientationPoints: 1. AZ calculated using start/end points of line features and a spatial join to attribute AZ to each point feature 2. OrientationSourceID and LocationSourceID all assigned to 'ThisReport' 3. PlotAtScale assigned to mapscale of 500000 4. OrientationConfidenceDegrees set to -9 for unknown/NA 5. OrientationPoints_ID calculated as 'OP001' - 'OP403' with sequential numbering script 6. calc'd label == Type 7. MapUnit calc'd using spatial join to MUP 8. Inclination set to '0', per GeMS compliance (no null, 0== horizontal, must be between -90,90) DataSourcePolys: 1. Created polys from us tiger line 2022 shapefile, projected into 5070, then selected out each DataSource for each 'county' dataset 2. non-county boundaries were georeferenced and digitized based on closest approximation from state boundaries - used trace functionality to reduce jagged polygons for datasourcepolys - trace was used for most of 'Northeast' - Just a rectangular poly was used for 'NorthernFox' - central and southern Fox were more complicatedly and likely are not highly accurate 3. one dataset was already in a digital GeMS format - this was dissolved into one polygon (superior region) Glossary: 1. Added 'map boundary' and definition from our database 2. deleted definitions from Cartographic lines - Subglacial meltwater flow direction indicated by eskers - Ice flow direction indicated by drumlins and other streamlined landforms - Meltwater flow direction indicated by general slope and relict channels - Wind direction indicated by dunes - Spillway flow direction from major proglacial lakes 3. removed 'uncertain contact between units rb and ru' DMU: 1. changed paragraph style to fit with NGS standards - Heading3 -> DMUHeading2 - Heading3-1A -> DMUHeading2 - superunit -> DMUHeading3 - subunit -> DMUUnit1 - standaloneunit -> DMUUnit1 2. for 'N/A' I added 'water' and changed to ParagraphStyle DMUUnit1, since in our representation we filled gaps with these polys to the state boundary. changed age to Holocene 3. Chopped first XXX off of HierarchyKey, since the parent in that spot was related to blocks of data, vs. overall representation of the data (unit/header relationships) - this required renumbering hierarchies in original 002 and 003 parent categories, since XXX numbers started at 001, again. symbols to add to NGS glossary: 13.03, glacial-lake spillway, line, certain, certain, definition: see Overflow channel: A channel or notch cut by the overflow waters of a lake, esp. the channel draining meltwater from a glacially dammed lake; an outlet of a proglacial lake. Proglacial Lake: A lake formed just beyond the frontal margin of an advancing or retreating glacier, generally in direct contact with the ice. (from WI definitions)