WEBVTT

1
00:00:00.001 --> 00:00:08.840
Robert Marvinney, DACF: Alright, I think we will get started so welcome everyone Thank you have a good afternoon thanks for joining this northeast GSA short course to digital geologic map schema.

2
00:00:09.620 --> 00:00:20.210
Robert Marvinney, DACF: And i'm Bob marvin I am the state geologist at the main geological survey and i'm going to be the moderator for this session today.

3
00:00:21.290 --> 00:00:24.860
Robert Marvinney, DACF: And we will have several.

4
00:00:26.270 --> 00:00:27.350
Robert Marvinney, DACF: presenters.

5
00:00:29.090 --> 00:00:31.340
Robert Marvinney, DACF: On our program this afternoon.

6
00:00:33.170 --> 00:00:47.270
Robert Marvinney, DACF: Talking about various aspects of our gems geologic map schema and i'm going to introduce our presenters briefly and then and then i'll speak a little bit about the agenda for today.

7
00:00:48.560 --> 00:00:59.810
Robert Marvinney, DACF: And that we plenty of opportunities for questions first a couple of logistics, as we go along, I see everyone's pretty used to zoom now you have your.

8
00:01:00.200 --> 00:01:16.220
Robert Marvinney, DACF: mics off, which is good, so please keep them off unless you're intending to speak, most of you have your cameras off, which is fine, you can do that or not, I know I know it helps with bandwidth in some places, if you turn that video off.

9
00:01:17.720 --> 00:01:22.700
Robert Marvinney, DACF: Please use the chat for questions there'll be opportunities as we go along to.

10
00:01:24.260 --> 00:01:38.690
Robert Marvinney, DACF: To ask questions directly, if you want to using the raise hand functions which i'm sure you're all familiar with, by now, you can also turn on your video and just wave your hands wildly if nobody's paying attention to you.

11
00:01:40.730 --> 00:01:47.180
Robert Marvinney, DACF: So, and there will be breaks in between some presentations to for questions and discussion.

12
00:01:49.730 --> 00:01:59.390
Robert Marvinney, DACF: So let's see with that, so our session is being recorded by GSA just so you know and we've got this closed caption at the bottom, which does pretty well.

13
00:02:00.350 --> 00:02:14.660
Robert Marvinney, DACF: But we invite you to pay attention to the speakers, and let me, let me introduce folks now so again i'm Bob marketing i've been state geologists here for 26 years.

14
00:02:15.230 --> 00:02:30.380
Robert Marvinney, DACF: been with the survey since 1987 and I was hired by the previous state y'all just to help move the main geological survey into the GIs world, which was pretty new at that time.

15
00:02:31.880 --> 00:02:36.800
Robert Marvinney, DACF: Also, presenting today from the main geological survey is Chris homestead.

16
00:02:37.940 --> 00:02:41.780
Robert Marvinney, DACF: he's been with us for almost a decade and.

17
00:02:43.670 --> 00:02:59.870
Robert Marvinney, DACF: As our director of earth's resources information he manages our GIs and databases and ensures that we are using the latest state of the art GIs and all our you know our digital functions.

18
00:03:00.950 --> 00:03:03.770
Robert Marvinney, DACF: Next Dave soller Dave are you there.

19
00:03:06.290 --> 00:03:09.050
Robert Marvinney, DACF: turn on your camera Dave so we can all see you there's Dave.

20
00:03:09.170 --> 00:03:10.070
David Soller: Yes, I am.

21
00:03:10.160 --> 00:03:20.510
Robert Marvinney, DACF: dave's with the usgs he's been there for at least as long as i've been state geologist and his focus has been on developing the national geological map database.

22
00:03:20.990 --> 00:03:38.060
Robert Marvinney, DACF: and developing this gems schema that we're going to talk about today, and he also organized and has been very involved in the DM team meetings starting decades ago Dave I don't know how many, but so that that's up thanks for being here today Dave.

23
00:03:39.800 --> 00:03:46.610
Robert Marvinney, DACF: brown Ralph haggard is also with the usgs in the civic Northwest good morning Ralph.

24
00:03:47.990 --> 00:03:49.430
Ralph Haugerud: morning Bob yeah.

25
00:03:50.060 --> 00:03:57.860
Robert Marvinney, DACF: and actually Ralph has been with the usgs to exactly as long as i've been with the main geological survey he's been.

26
00:03:59.180 --> 00:04:04.880
Robert Marvinney, DACF: Conducting mapping projects in the Pacific Northwest and became an early advocate of.

27
00:04:06.200 --> 00:04:15.710
Robert Marvinney, DACF: lidar and its application to the especially glacial mapping that he was doing in in that region of the country.

28
00:04:16.490 --> 00:04:36.200
Robert Marvinney, DACF: And began working on this digital schema back in 2008 along with Dave so thanks Ralph and Evan tom's from the usgs in Alaska heaven i'm sorry I don't know a lot about you, except you do a lot of GIs work and and jumps work.

29
00:04:37.190 --> 00:04:38.870
Evan Thoms: yeah sure that's enough.

30
00:04:39.380 --> 00:04:41.450
Robert Marvinney, DACF: Great well thanks.

31
00:04:41.720 --> 00:04:45.890
Robert Marvinney, DACF: So we are all the presenters my role is going to be to.

32
00:04:46.940 --> 00:05:04.490
Robert Marvinney, DACF: Keep an eye on the chat keep people on time and help with any technical issues that might come up at this time, it would be really helpful for for us as presenters to know a little bit about all you folks who are participating in this.

33
00:05:05.600 --> 00:05:06.890
Robert Marvinney, DACF: In this short course.

34
00:05:08.000 --> 00:05:21.560
Robert Marvinney, DACF: And i'm going to i'm going to read off the names from the from the list that I have, and when I do if you'll just open your MIC and, if you want to turn on your camera that's great, but what we want to know is, where you're from and.

35
00:05:22.910 --> 00:05:32.690
Robert Marvinney, DACF: And what what drew you to this short course today so starting at the top of the list is rosanna bear.

36
00:05:34.310 --> 00:05:47.270
Rosie Behr: yeah i'm with the Pennsylvania geological survey and i'm a field mapper and we produce our maps on a GIs platform and need to make them gems compliant for state map.

37
00:05:48.050 --> 00:05:50.480
Robert Marvinney, DACF: Great good you're in the right place.

38
00:05:52.670 --> 00:05:54.860
Robert Marvinney, DACF: Next, Alan send them off.

39
00:05:57.800 --> 00:05:58.730
Robert Marvinney, DACF: down here.

40
00:06:00.290 --> 00:06:01.400
Robert Marvinney, DACF: Look at the list.

41
00:06:03.980 --> 00:06:06.290
Robert Marvinney, DACF: Okay we'll move on Julia boils.

42
00:06:07.670 --> 00:06:19.430
Julia Boyles: hi i'm Julia boils i'm with the Vermont geological survey and similar the previous speaker i'm here, because we need to make our maps gems compliant for statement so i'm just looking to learn more about camps.

43
00:06:20.150 --> 00:06:22.910
Robert Marvinney, DACF: Very good, thanks john brooks.

44
00:06:25.310 --> 00:06:38.240
John Brooks: I from Wolfsburg new Hampshire semi retired consulting geologists and doing some sufficient mapping for the state of new Hampshire so just wanted to find out a little bit more about gems, like the other people.

45
00:06:39.230 --> 00:06:40.760
Robert Marvinney, DACF: Okay let's see uh john.

46
00:06:42.350 --> 00:06:45.350
Robert Marvinney, DACF: vince CC my friend vince how our events.

47
00:06:49.490 --> 00:06:52.160
Robert Marvinney, DACF: Since we can't hear you vince if you're trying to talk.

48
00:06:55.580 --> 00:07:01.490
Robert Marvinney, DACF: And I don't see a problem with your MIC so Okay, I see you're trying to connect to the audio.

49
00:07:06.050 --> 00:07:10.790
Robert Marvinney, DACF: Right now you're muted vince maybe if you turn that off we'll hear you.

50
00:07:15.590 --> 00:07:19.070
Robert Marvinney, DACF: Okay, well, I guess we'll move on to vince to Craig ebersole.

51
00:07:20.750 --> 00:07:21.590
Craig Ebersole: hi everybody.

52
00:07:22.850 --> 00:07:33.200
Craig Ebersole: I work at the Pennsylvania geological survey with rosanna we're on opposite ends of the building, but we talk with each other, a lot, I am in the GIs division.

53
00:07:34.370 --> 00:07:48.050
Craig Ebersole: So I take a lot of the data, the field matters make including resentenced data and turn it into a nice map plates, so I am i've been recently designated as the gems point person in our brl so i'm here to.

54
00:07:49.730 --> 00:07:50.960
Craig Ebersole: get a crash course in this.

55
00:07:52.280 --> 00:07:56.060
Robert Marvinney, DACF: Great okay well thanks Craig in enders.

56
00:07:57.740 --> 00:08:11.780
Ian Enders: Hello everyone, I mean i'm i'm a student at central Connecticut State University and i've taken a lot of classes and GIs both the geology and geography courses and I just want to learn more about different techniques, including gems.

57
00:08:12.950 --> 00:08:17.450
Robert Marvinney, DACF: Great okay thanks about Chelsea Hernandez.

58
00:08:22.610 --> 00:08:23.720
Robert Marvinney, DACF: No okay.

59
00:08:24.980 --> 00:08:26.930
Robert Marvinney, DACF: Karen eisenberg.

60
00:08:28.880 --> 00:08:31.280
taryn isenburg: hi i'm tearing our.

61
00:08:32.330 --> 00:08:41.660
taryn isenburg: Connecticut geological survey and i've been working there for a couple of years and we've been trying make maps and gems here to learn some more.

62
00:08:42.230 --> 00:08:45.140
Robert Marvinney, DACF: Great okay zach clang.

63
00:08:47.900 --> 00:08:51.380
Zach Klang: Hello everyone I work with taryn at the Connecticut geological survey I.

64
00:08:52.400 --> 00:08:58.280
Zach Klang: Also, work on creating new maps and gems or digitizing maps making gems compliant digital maps.

65
00:08:59.600 --> 00:09:00.530
Robert Marvinney, DACF: Okay, great.

66
00:09:01.610 --> 00:09:02.480
Robert Marvinney, DACF: Steve maybe.

67
00:09:03.260 --> 00:09:13.490
Stephen Mabee - MA: I speak, maybe a State geologists for Massachusetts and I need to learn as much as I can about gems in order to begin conversions and.

68
00:09:14.600 --> 00:09:17.810
Stephen Mabee - MA: Also, new mapping to be gems compliant.

69
00:09:19.220 --> 00:09:22.790
Robert Marvinney, DACF: Okay, thanks Steve Jason you late.

70
00:09:26.570 --> 00:09:28.100
Robert Marvinney, DACF: Jason are you here.

71
00:09:30.380 --> 00:09:32.360
Robert Marvinney, DACF: Okay, moving on Tyler petty.

72
00:09:35.270 --> 00:09:35.900
Tyler Petty: we're doing.

73
00:09:38.060 --> 00:09:55.160
Tyler Petty: Perfect um i'm Tyler petty i'm from in Duchess county in New York, I just recently graduated with my undergraduate in geology i'm here because I have no idea what gems is, and I was interested in learning because i'm here at the Convention, so why not.

74
00:09:56.300 --> 00:09:56.750
Tyler Petty: Great.

75
00:09:56.960 --> 00:10:04.970
Robert Marvinney, DACF: Okay, thanks and i'll apologize if I pronounce this incorrectly incorrectly blocking cf side.

76
00:10:09.080 --> 00:10:13.100
Robert Marvinney, DACF: Now okay we'll move on as Elizabeth spielman.

77
00:10:17.780 --> 00:10:18.890
Robert Marvinney, DACF: So Elizabeth here.

78
00:10:20.750 --> 00:10:23.930
Robert Marvinney, DACF: Okay Roberts students oh.

79
00:10:24.920 --> 00:10:26.990
Robert Stuetzle: yeah Robert students Lee I am.

80
00:10:27.350 --> 00:10:28.580
Robert Stuetzle: hydrogeologist I work.

81
00:10:28.640 --> 00:10:38.210
Robert Stuetzle: For the Dow Chemical company actually but i'm here on a personal interest I like to see how people manage and create data visualizations.

82
00:10:38.870 --> 00:10:43.010
Robert Marvinney, DACF: Great okay thanks thanks for joining us Margaret Thomas.

83
00:10:49.250 --> 00:11:03.770
Margaret Thomas: hi Margaret Thomas, I am Connecticut state geologists you've already heard from a couple of my young staff they've been working zach and Karen and others have been working in gems now for a couple of years.

84
00:11:05.000 --> 00:11:20.390
Margaret Thomas: Where we're always interested in trying to catch up with new tools and as the software evolves and applying jams to to new mapping so going right from the field into the database.

85
00:11:22.490 --> 00:11:30.800
Margaret Thomas: And we're hoping to go to Arc pro so we're here to find out as much as we can, about the new tips and tricks.

86
00:11:32.480 --> 00:11:35.750
Robert Marvinney, DACF: Okay, thanks Margaret Stephen psychosis.

87
00:11:37.100 --> 00:11:43.100
stephen tzikas: Yes, hi i'm an environmental engineer, this is a continuing education class for me so it's all new material.

88
00:11:43.940 --> 00:11:44.900
Robert Marvinney, DACF: All right, great.

89
00:11:46.010 --> 00:11:47.540
Robert Marvinney, DACF: David Volterra.

90
00:11:50.360 --> 00:11:51.230
Robert Marvinney, DACF: Stephen on.

91
00:11:54.500 --> 00:11:56.840
Robert Marvinney, DACF: Okay we'll move on Lee whoo.

92
00:11:58.790 --> 00:12:02.780
Lei Wu: Hello everyone i'm i'm i'm working with university in.

93
00:12:03.800 --> 00:12:21.830
Lei Wu: him on trail so i'm a painter magnetic and i'm working a lot on play reconstruction pay the geographic project and i'm here to learn something about Joe database management, and you know or a database construction something like that.

94
00:12:23.030 --> 00:12:28.250
Robert Marvinney, DACF: Very good, thank you so that's my list we have a pretty good cross section of.

95
00:12:28.790 --> 00:12:40.640
Robert Marvinney, DACF: variety of different types of users or people who are just interested in understanding more about this schema so in terms of what we're going to do today.

96
00:12:41.240 --> 00:13:01.550
Robert Marvinney, DACF: i'll just give you a brief outline first will be an introduction to this schema by Dave soller that will follow with Ralph haggard who will give us an introduction, how to get started in gems and then we'll proceed with.

97
00:13:02.960 --> 00:13:12.890
Robert Marvinney, DACF: an overview of digitizing a map and then also translating and six existing digital map into the gems format.

98
00:13:13.700 --> 00:13:26.570
Robert Marvinney, DACF: And following that so that that's going to be the bulk of the afternoon here, and then, following that we'll have a discussion of the geologic names check function in gems by Evan.

99
00:13:27.380 --> 00:13:44.630
Robert Marvinney, DACF: And then we'll have a discussion of bedrock and superficial geologic maps in gems and how we might deal with them several different ways and then and then an open discussion at the end, but there will be time in each part of this.

100
00:13:45.980 --> 00:13:50.090
Robert Marvinney, DACF: For discussion so i'm going to stop sharing my screen now.

101
00:13:51.680 --> 00:13:58.790
Robert Marvinney, DACF: And Ralph if you're ready, I mean Dave sorry Dave if you're ready, we can go ahead with your introduction.

102
00:14:00.590 --> 00:14:01.460
David Soller: Thank you, Bob.

103
00:14:07.910 --> 00:14:09.590
David Soller: You can see the screen I hope.

104
00:14:09.950 --> 00:14:10.580
David Soller: it's good.

105
00:14:11.030 --> 00:14:18.140
David Soller: Okay, good so um as Bob mentioned, and we wanted to give an introduction to this this gem schema.

106
00:14:20.120 --> 00:14:28.610
David Soller: I like to start with an explanation of why the national geologic map database is involved in this, our acronym at the bottom is n G imdb.

107
00:14:29.390 --> 00:14:49.130
David Soller: that's our website as well, so this is a genuine Xerox low quality of the geologic mapping act of 1992 it establishes the geologic map database as a cooperative between the State surveys and the usgs and key to this afternoon's discussion is is a very unique.

108
00:14:50.660 --> 00:14:53.330
David Soller: In the mind of the.

109
00:14:54.500 --> 00:15:13.310
David Soller: The other surveys of the world that i've talked with this is a and valuable item which is the mass contributed to the national archives must be standardized so that gives us the the motivation, as well as the mandate to to do what we're going to describe today.

110
00:15:14.690 --> 00:15:26.390
David Soller: Where to begin by just reviewing how we got to the stage, so this is a big under the mapping act again I said usgs and the State surveys are collaborating.

111
00:15:27.770 --> 00:15:40.700
David Soller: This effort has gone on through since the mid to late 1990s and partially through the digital mapping techniques annual workshops or D amp T that started in 1997.

112
00:15:42.980 --> 00:15:46.640
David Soller: But you know many of us who are around at the beginning of.

113
00:15:48.080 --> 00:15:50.450
David Soller: Art with us today because they've retired.

114
00:15:51.470 --> 00:16:08.810
David Soller: or they've moved on to other jobs and so many of you are new to the process i'm really glad that there's just an interest in learning more about this and you know, please ask questions either either here or or at the the gems email alias that we set up so to begin quickly.

115
00:16:09.830 --> 00:16:15.950
David Soller: In 96 the state surveys and nj mtb had a meeting in St Louis we set up a.

116
00:16:17.120 --> 00:16:23.390
David Soller: Data model working group we published a design, known as version 4.3 in 1999.

117
00:16:24.530 --> 00:16:30.890
David Soller: That then evolved into the North American data model Steering Committee and activity with the Canadian survey.

118
00:16:31.490 --> 00:16:45.140
David Soller: And we published the so called any DM multimap enterprise level design in 2004 That was a monumental effort, which has been continued in some form.

119
00:16:45.980 --> 00:17:03.440
David Soller: Internationally, but it was it was too aggressively scoped for the needs of of our geological surveys initially conventionally but, but it was a big first step kind of in a visioning exercise.

120
00:17:04.490 --> 00:17:07.580
David Soller: The documents for any DM are still online.

121
00:17:08.720 --> 00:17:16.400
David Soller: If you're interested I can point you there, so we then entered in a hiatus in the development of have a database design.

122
00:17:17.600 --> 00:17:36.620
David Soller: For a variety of reasons and in 2008 Peter little the then program coordinator for the national cooperative geologic mapping program asked me to work with Ralph to develop a single map database design for their very big project in the Pacific Northwest.

123
00:17:37.790 --> 00:17:42.050
David Soller: That design Evan TOMS Ralph haggard Steve Richard.

124
00:17:43.100 --> 00:17:50.420
David Soller: We develop that design and presented it at DM team meetings, the last time was in 2009.

125
00:17:51.590 --> 00:18:03.020
David Soller: Where it was published as the nc gop or nine schema and then how based on discussions in subsequent years at the 2013 tmt.

126
00:18:03.830 --> 00:18:14.510
David Soller: We had a group discussion on progress report on the implementation was released so it's you know it's eight years ago, but it has some really interesting.

127
00:18:15.410 --> 00:18:25.370
David Soller: insights into the process, the struggles to work together to develop a design that's going to work sufficiently for everyone.

128
00:18:25.820 --> 00:18:37.580
David Soller: And so many of the comments made during that discussion, and in this informal report still have relevance, so I might suggest that you, you search that one out or contact me.

129
00:18:39.200 --> 00:18:40.400
David Soller: So continuing.

130
00:18:41.690 --> 00:18:52.190
David Soller: After nc gop a nine came out there was a an extensive period of evaluation of testing in the state surveys and usgs there were many, many.

131
00:18:54.050 --> 00:19:03.020
David Soller: conference calls advisory working groups discussions at TNT it went on for about three years.

132
00:19:04.070 --> 00:19:13.190
David Soller: in which all the major issues that had come to light at that point to that point were discussed and resolved as best we could.

133
00:19:13.790 --> 00:19:34.760
David Soller: So then, in early 2017 we released version two events, a champion nine, fortunately, with a with a much easier one syllable name gems and then in 2020 gems had moved its way through the usgs publication process and is published as a technique methods chapter.

134
00:19:35.960 --> 00:19:42.560
David Soller: It was a very big step for us we're very proud of it didn't expect you to read all the texts or any of it but.

135
00:19:43.640 --> 00:20:02.360
David Soller: This gives you the sense that Yes indeed, it is real and the time then came for the usgs for the national cooperative geologic mapping program and also the NGO mtb project to work with the state's on how this would could be implemented.

136
00:20:06.680 --> 00:20:08.150
David Soller: So here's some caveats.

137
00:20:09.830 --> 00:20:16.940
David Soller: For those of you who aren't familiar with gems it's designed to content and topology of a single geologic map.

138
00:20:19.100 --> 00:20:28.280
David Soller: It is eXtensible will evolve over time, it will evolve over time, but we're not eager to to see significant changes to it at the.

139
00:20:29.510 --> 00:20:33.350
David Soller: need to get started to implement Community.

140
00:20:34.370 --> 00:20:50.900
David Soller: It really serves well the tradition that we have a publishing individual geologic maps and you know many of us will say well geologic maps are passe we need databases Well, yes, we do, but we're still publishing individual maps and we need to manage the well.

141
00:20:53.090 --> 00:21:02.480
David Soller: The the gems design is will eventually incorporate the ability to manage multiple maps in a single database.

142
00:21:04.370 --> 00:21:05.150
David Soller: But again.

143
00:21:06.290 --> 00:21:16.550
David Soller: One experience we learned from the enemy DM exercise is that you better take small steps and move the Community along encourage the Community, a step at a time.

144
00:21:17.660 --> 00:21:25.610
David Soller: So also gems is not necessarily recommended for capturing geologic data and observational information in the field.

145
00:21:27.620 --> 00:21:33.650
David Soller: So point for me is the chief of the MGM db is is the next point.

146
00:21:34.730 --> 00:21:37.760
David Soller: standardization of all types, is critical.

147
00:21:38.810 --> 00:21:56.780
David Soller: If we're going to manage archive and not lose map data or data of any kind, so their efficiencies and mass migration of these standardized gems files that will enable MGM db and other systems state systems, for example, to manage geologic map data for future use.

148
00:22:00.200 --> 00:22:19.250
David Soller: The commonly stood and expressed a stand is equally valid or so equally valid least and that's to provide the public with a predictable format for the geologic map data that they are.

149
00:22:20.660 --> 00:22:31.790
David Soller: downloading they're consuming from various agencies or from one agency, over time, one of the reasons I think, a very big reason for the success of the soils map database.

150
00:22:32.420 --> 00:22:45.260
David Soller: Is that it is standardized across the country, so you always know what you're getting you're familiar with the data, whether you're an Oregon or maine and that's one of the major goals of course of objects.

151
00:22:46.280 --> 00:22:57.710
David Soller: And finally gems is indeed art Center because that's the standard currency in usgs and the State surveys, but it does not preclude implementation in open source GIs.

152
00:22:59.420 --> 00:23:08.600
David Soller: So final final comment, Bob mentioned Evan tom's is going to be discussing validating gems files prior to re positing them.

153
00:23:09.350 --> 00:23:19.610
David Soller: These are the two scripts that will be discussed, we can address questions about you know how these scripts and the workflow for compliance.

154
00:23:20.030 --> 00:23:32.180
David Soller: Are need to be done if you choose it's not the most you know engaging subject it's not like geologic mapping itself, but we will have time at the end to discuss that but first.

155
00:23:32.810 --> 00:23:39.350
David Soller: Ralph is going to show us how to create the gems file database and how to migrate existing databases into gems.

156
00:23:41.090 --> 00:23:42.770
David Soller: So thank you for your time.

157
00:23:45.770 --> 00:23:46.100
Thanks, thank you.

158
00:23:47.420 --> 00:24:00.920
Robert Marvinney, DACF: I just want to make sure I don't see any questions in the chat right now, but anyone if you've got a question raise your hand or turn on your video or something to give us a sign that you have a question.

159
00:24:03.980 --> 00:24:08.540
Robert Marvinney, DACF: Okay, I think we can move on, then Ralph are you ready to go.

160
00:24:11.420 --> 00:24:14.120
Ralph Haugerud: I think i'm ready to go here um.

161
00:24:15.710 --> 00:24:31.880
Ralph Haugerud: I decided to pre record my presentation, so that I can watch the chat and answer questions in real time, as this is going on it's been more of a learning exercise than I expected and I would not hire myself as video producer I hope you'll be kind let's see if this will work.

162
00:24:34.070 --> 00:24:37.790
Talk about getting started with gems, these are the topics I will cover.

163
00:24:39.710 --> 00:24:44.300
Ralph Haugerud: Jim gems is a schema for encoding the contents of the geologic map and a GIs database.

164
00:24:45.050 --> 00:24:53.180
Ralph Haugerud: is not a schema for encoding and geologic map image for that you might want adobe illustrator norris and a schema for encoding the geology of the world.

165
00:24:53.720 --> 00:25:01.550
Ralph Haugerud: and opportunity to reimagine how we see the world it's focused on archiving and publication data for a single map in digital form.

166
00:25:02.270 --> 00:25:18.020
Ralph Haugerud: It may not be the optimal schema for field notes or for publication quality photography or for multimap database, it may be useful in providing clues towards such databases, though in gems is at the moment unapologetically our GIs centric.

167
00:25:19.910 --> 00:25:28.070
gems closely defines table structure and field names that are geologic map database, it has only three embedded vocabularies.

168
00:25:28.820 --> 00:25:38.600
is concealed and attribute of contacts and faults has value some knowing yes GEO material which is attached to map your descriptions has about 100 values.

169
00:25:39.170 --> 00:25:49.520
and geo material conference three values high medium and low all other terms if user database, such as betting contact vision track date fault fully ation of questionable.

170
00:25:49.940 --> 00:25:58.040
If they're using the database are defined in the glossary table and map the answer define the discussion mapping, there are resources online.

171
00:25:58.880 --> 00:26:07.790
For using jams to understanding the most important one, the one remember is the MGM db gems page, which has links to other resources listed here.

172
00:26:08.780 --> 00:26:15.890
The standard itself is usgs publication is whether dry reading, but I recommend the introduction to you, and some of the dependencies.

173
00:26:16.550 --> 00:26:35.180
we're going to spend much of the afternoon talking about the gems toolbox and github I won't talk about that you can build a gems database from scratch, you can open up the documentation see what the database schema looks like make a new database, make a feature data set inside of it.

174
00:26:36.260 --> 00:26:41.300
look to see which feature classes belong intended feature data set what the fields are how they're defined.

175
00:26:41.780 --> 00:26:52.730
And then plug away so you can do this from scratch, and you can manipulate the database that generic our tools, but this is the hard way with a closely defined schema shared tools become practical.

176
00:26:54.080 --> 00:27:10.340
Over the last several years Evan TOMS and I and a few others have built such a library of shared tools that make it much easier to work with the gem schema well let's fire up your favorite search engine and type into it U s G s gems.

177
00:27:12.020 --> 00:27:12.680
tools.

178
00:27:14.750 --> 00:27:17.210
And we're looking for the github site.

179
00:27:20.210 --> 00:27:37.970
there's the landing page scroll down some here there's a readme that explains what we're looking at this is a repository of Python scripts that run inside of archie is for creating manipulating and validating gems databases their installation instructions.

180
00:27:39.530 --> 00:27:41.150
So many advice on getting help.

181
00:27:42.380 --> 00:27:43.820
A plea for collaboration.

182
00:27:44.960 --> 00:27:48.080
And discussion in a few known issues.

183
00:27:49.280 --> 00:27:51.140
We go back up at the top of the page.

184
00:27:52.280 --> 00:28:09.320
This here is the wiki that I put together a couple of years ago for an earlier version this short course offered at a dmc workshop in 2018 if you get excited about gems and like to write and learn how to use it would like to work on the monkey that'd be wonderful.

185
00:28:12.260 --> 00:28:19.910
let's go back, we want to pick up the toolbox and, in general, you generally you want the latest release click the link.

186
00:28:20.990 --> 00:28:22.160
grab the zip file.

187
00:28:24.230 --> 00:28:33.080
And it takes a little while for github to wake up and start shipping it to us the file and won't take long to download right now, this file is about 30 megabytes.

188
00:28:36.230 --> 00:28:36.860
And it's done.

189
00:28:38.210 --> 00:28:39.320
We can.

190
00:28:40.370 --> 00:28:41.690
Open the containing folder.

191
00:28:43.280 --> 00:28:44.510
grab a zip file.

192
00:28:46.040 --> 00:28:52.820
I like to keep my code in a code directory so it's separate from my data, I mean I paste this here.

193
00:28:54.710 --> 00:29:02.990
If I look inside it contains a folder I don't want a folder that's inside of a folder so let's go back and.

194
00:29:04.280 --> 00:29:05.210
extract all.

195
00:29:19.670 --> 00:29:20.900
After a few seconds.

196
00:29:22.670 --> 00:29:23.390
The toolbox.

197
00:29:25.340 --> 00:29:27.890
A brief caution, this is the gym standard.

198
00:29:29.060 --> 00:29:43.850
The toolbox is not the gym standard but validate databases intended to follow standard as closely as we can, in other cases, if there's conflict between the toolbox, and the standard the standard should be honored.

199
00:29:46.580 --> 00:29:48.140
A brief note on directory structure.

200
00:29:49.400 --> 00:29:58.490
Unless you're customizing the gems toolbox, it is easily replaced, you need not be backed up your GIs data and project files are near you're replaceable.

201
00:29:59.000 --> 00:30:06.650
They should be backed up frequently, and for that reason, keep your gems toolbox one place your data and project files or another don't mix them up.

202
00:30:08.510 --> 00:30:14.720
let's configure Arc map, I find the default configuration doesn't work for me, as well as it could, so I could make a few changes.

203
00:30:15.530 --> 00:30:30.980
i've already opened dark map let's go in here, we want to go to customize our MAC options and make sure that make relative past the default for new map documents is checked i'd already done this, but in general, when you open a park map it's not checked.

204
00:30:32.180 --> 00:30:41.600
The next thing you want to do is see the got your tool bars of choice and I like to work with this set advanced editing editor I don't like the layout tool.

205
00:30:43.970 --> 00:30:50.210
don't want I do want snapping I do want standard I want tools and I want the apology available.

206
00:30:53.480 --> 00:30:54.800
extensions are not critical.

207
00:30:56.000 --> 00:31:01.850
For my GIs work I find it's very handy to have 3D analyst and spatial analyst available without thinking about it.

208
00:31:03.950 --> 00:31:06.920
And then there's a sticky move tolerance and.

209
00:31:07.970 --> 00:31:11.960
want to go to the editor and editing options.

210
00:31:13.040 --> 00:31:22.490
and make sure this is set for some nonzero number otherwise when you select features it's possible to move them inadvertently, and the most.

211
00:31:23.270 --> 00:31:34.700
Most sticks and you've messed up your database, you want to make a soup going to make a definite move before Arc net recognizes that something is going to be someplace else so about 20 pixels is a good answer.

212
00:31:36.410 --> 00:31:40.190
And then you want to install the Ark toolbox and let's see, let me.

213
00:31:41.930 --> 00:31:47.810
Open up the our toolbox window right click on empty spot in their ad toolbox.

214
00:31:49.190 --> 00:32:01.370
navigate to where you install the toolbox go into the directory, and if you're in our 10 five or higher you grab this one if you're in our 10 or 10 to you grab the other.

215
00:32:04.070 --> 00:32:05.270
takes a few seconds.

216
00:32:06.380 --> 00:32:07.370
But it should pop up.

217
00:32:08.450 --> 00:32:17.930
There it is, and then you can right click to save settings to default and maybe the next time you open this and next to the toolbox will still be there.

218
00:32:19.220 --> 00:32:19.730
And that's it.

219
00:32:31.490 --> 00:32:33.680
Robert Marvinney, DACF: Okay, thanks thanks Ralph.

220
00:32:34.820 --> 00:32:44.300
Robert Marvinney, DACF: For that intro to how to get started and gems i'm sure there's a lot there for people to absorb if you haven't.

221
00:32:45.440 --> 00:32:50.180
Robert Marvinney, DACF: had any experience with gems, are there any questions.

222
00:32:57.050 --> 00:33:10.370
Robert Marvinney, DACF: Okay, so i'm just confirming that this session is being recorded and this recording will be available through GSA at some point, after the meeting, so you can review this.

223
00:33:11.480 --> 00:33:13.790
Robert Marvinney, DACF: When you when you want to or need to.

224
00:33:16.130 --> 00:33:25.490
Ralph Haugerud: Okay, and I think it's likely to check with Dave on this, we can probably post the PowerPoint presentations someplace really accessible and pass that link to people.

225
00:33:26.180 --> 00:33:27.890
Robert Marvinney, DACF: is great yes.

226
00:33:28.520 --> 00:33:33.680
David Soller: We can do that and, if possible, the recording as well yeah.

227
00:33:34.070 --> 00:33:35.870
Robert Marvinney, DACF: I hope so okay.

228
00:33:36.350 --> 00:33:40.550
Ralph Haugerud: And i'm discovering I can't see the chat but I videos playing i'm not sure what i've.

229
00:33:41.090 --> 00:33:45.620
Robert Marvinney, DACF: lost but okay they're The only question was about recording so.

230
00:33:45.740 --> 00:33:46.040
Ralph Haugerud: Okay.

231
00:33:46.100 --> 00:33:47.840
Robert Marvinney, DACF: we're good we're good to move ahead.

232
00:33:49.070 --> 00:33:59.240
Ralph Haugerud: Okay um you need to sharpen the gems by digitizing an analog map we're going to work from a published paper map image.

233
00:33:59.810 --> 00:34:09.320
Ralph Haugerud: But it's essentially the same processes, making new geology landscapes new geology and seven map image we have field notes that have been scan we have air photos we have typography.

234
00:34:10.190 --> 00:34:20.390
Ralph Haugerud: But it's the same thing you're looking at an image and you're drawing lines on it processes are very similar will do this and steps with breaks for discussion between each step will start by assessing the.

235
00:34:20.390 --> 00:34:29.750
David Soller: source map figure we need making an empty database putting a map outline a box to draw inside of and begin digitizing contacts and making mapping polygons.

236
00:34:32.210 --> 00:34:48.410
David Soller: Right now i'm sitting at home in the West edge of wenatchee in the Center of Washington state, I thought i'd work on something local so we're going to look at the geologic map of the walking for southeast quadrangle by john wet and published in 1980s the usgs and waterfowl report.

237
00:34:51.710 --> 00:35:01.880
here's a view of part of the map it's a pretty ugly thing it was pretty clearly no done as a blueprint type process and then later scan it's aged in the library.

238
00:35:02.840 --> 00:35:15.740
The nice thing is that the national judgment database has a God and we don't need to do reference this image to make life simple we're going to do the south east one night of the map, so that there's a chance of getting through in the next few minutes.

239
00:35:18.200 --> 00:35:25.340
The first step is to inventory what's on the map what kinds of features of present what features classes will be needing the database to capture them.

240
00:35:26.960 --> 00:35:32.840
We can see their contacts and, interestingly, none of them are dotted or concealed.

241
00:35:33.950 --> 00:35:36.020
or dashed approximate they're all.

242
00:35:37.160 --> 00:35:55.010
Contacts well located there mapping of polygons and they've got several different units que El que El que El es and then tcs, which is an ESC conglomerate sandstone of the jumpsuit formation, none of these lines here.

243
00:35:57.620 --> 00:36:08.780
Solomon dotted dashes solid with ornamental on it, and these are labeled this is T ta this number here is T T These are tough beds.

244
00:36:10.910 --> 00:36:13.310
And there's some question as to how they can be treated.

245
00:36:14.930 --> 00:36:26.780
Tough beds like this key beds don't participate in mapping or topology that's they don't belong in the context and false they could be stored in jams in either geologic lines or map your lights, the questions which is appropriate.

246
00:36:27.830 --> 00:36:37.040
And it's a matter of how they're defined geologic lines are identified by type they're defined to the glossary table and the paper map.

247
00:36:37.580 --> 00:36:47.660
You look for the definition of that line and the exploration of symbols MAC you know lines are lines that are mapped units and their their meaning is to find in the description, the map units table.

248
00:36:48.770 --> 00:37:02.750
And the paper maps would see them in the DM you on this map these shale air show up on the CMU the correlation diagram and they are listed under seal layers tough players they're listed as parts of the conglomerate sandstone package.

249
00:37:04.190 --> 00:37:08.060
they're defined in the damn us so they get stored in map unit lines in the gems database.

250
00:37:09.500 --> 00:37:13.850
We also have striking didn't mission it's a fair number of them a lot of them quite hard to read.

251
00:37:14.870 --> 00:37:29.810
to capture these we need for future classes, we need contacts and faults and mapping apologies, and these are required any gems geologic map database and we also need makinen lines and orientation points which are as needed future classes put them in when you need them.

252
00:37:31.490 --> 00:37:49.070
here's a recipe we're going to make an empty database we're going by opening Arc map we're going to add reference layers to the map composition, including the scan of the map or digitizing we're going to save our next D file as map name dash.

253
00:37:50.840 --> 00:38:00.530
My experiences that editing and plotting typically need different reference layers and different civilization that's I use to St files for a map i'm working on one for editing one for plotting.

254
00:38:01.910 --> 00:38:04.220
we're going to run the create new database script.

255
00:38:05.870 --> 00:38:07.580
That we're going to add a map outline to it.

256
00:38:08.930 --> 00:38:15.050
we're going to transfer the map outline into contacts and false fill out its attributes and get rid of the map outline.

257
00:38:16.430 --> 00:38:20.870
Then we're going to add a pre packaged layer file that gives us digitizing templates.

258
00:38:21.890 --> 00:38:24.770
and begin digitizing the line work we'll come back to this.

259
00:38:26.450 --> 00:38:28.640
So here is.

260
00:38:29.840 --> 00:38:35.840
The scan of the truck and for southeast quadrangle i've added some reference layers.

261
00:38:37.610 --> 00:38:41.030
For example here scan usgs toes off of the.

262
00:38:42.050 --> 00:38:48.230
base map collection and I happen to have lidar data for the area on my hard drive, so I had that also.

263
00:38:49.580 --> 00:39:03.620
Part of the reason for doing this as I get really nervous about where things are located, do you referencing mine and others in more than one occasion I found that stuff isn't right thought it was and so let's go look at the corner of this map right here.

264
00:39:05.120 --> 00:39:07.250
turn the light on or off the.

265
00:39:08.300 --> 00:39:15.800
scan I made partially transparent, if we look at the base map the scan total maps, we can see the scene in here.

266
00:39:17.240 --> 00:39:25.190
Where the scan this quadrangle was trying to this quadrangle this one to this one is seen in through here the quadrangle boundaries are in and 27.

267
00:39:26.420 --> 00:39:38.450
This is the nad at three tick and it's about 97 meters to the East, North East of the corner of the quad boundaries and it's this this place with humanity three and 27 that is a bugaboo so let's put the.

268
00:39:39.950 --> 00:39:45.020
scan a German snap on top of here and hooray that corner is roughly.

269
00:39:46.670 --> 00:39:48.710
Where the corner, is in the base layer

270
00:39:50.210 --> 00:39:54.620
We can also go look at the lidar and I have a fair bit of faith that the lidar is where.

271
00:39:55.670 --> 00:39:56.690
it's supposed to be.

272
00:39:57.800 --> 00:40:12.140
And we can turn this off and look for example at this little re entered in here the valley wall and yeah again it's about the right place, so I think the scan is properly to reference we're okay proceeding.

273
00:40:15.050 --> 00:40:23.570
On the next step is to make an empty database, and so we want to open up the Ark map toolbox create a new database.

274
00:40:25.160 --> 00:40:28.280
Go to the output workspace and it's.

275
00:40:29.570 --> 00:40:32.750
to walk them for se we're gonna call this.

276
00:40:37.520 --> 00:40:38.150
and

277
00:40:39.500 --> 00:40:45.440
ordinarily I would say copy the reference framework from.

278
00:40:46.820 --> 00:40:48.080
The input base map.

279
00:40:49.670 --> 00:40:57.740
But net 27 is a bad actor, for many people so let's not do that i'm going to copy it from the lidar data in here one of the lidar data sets is in many three.

280
00:40:59.180 --> 00:41:00.890
ut and Canada let's use that.

281
00:41:03.410 --> 00:41:14.690
We need feature classes elements that are beyond the standard required gems minimum we figured out that we needed to have geologic lines sorry map, you know lines.

282
00:41:16.910 --> 00:41:22.520
And orientation points we don't want to cross section we're not going to enable at a tracking.

283
00:41:23.390 --> 00:41:35.000
we're not gonna use cutter representations, we do want to add l type in PT type and we'll see why shortly and, in general, we want the standard competence values i'm certain and questionable added the database also.

284
00:41:36.740 --> 00:41:41.360
Like Okay, the runs multi very long, we can sit here and watch it.

285
00:41:44.570 --> 00:41:45.800
it'll tell you what it's doing.

286
00:41:46.850 --> 00:41:54.500
To keep you entertained but also about coding, this was nice and what was working what wasn't and if you get an error in this.

287
00:41:55.580 --> 00:42:02.600
Evan and I, who have done most of the coding would very much like to hear about it, and the best thing you can do is give us a screengrab.

288
00:42:03.980 --> 00:42:05.300
Of this output.

289
00:42:06.320 --> 00:42:07.610
So we can see where the error occurred.

290
00:42:09.710 --> 00:42:11.780
One minute and eight seconds later it's done.

291
00:42:12.980 --> 00:42:16.520
And we can close this window and.

292
00:42:17.630 --> 00:42:21.380
Close the toolbox for the moment, and we can add data to our map.

293
00:42:23.330 --> 00:42:27.260
here's our database and we want to add the contacts and faults.

294
00:42:28.280 --> 00:42:32.030
And makin outlines future classes to the map composition.

295
00:42:33.050 --> 00:42:47.690
they're empty nothing shows the next step is to make a map outline have a box draw inside and there's a tool here that makes that easy the challenges the map outlines are roughly rectangles been in detail, they are not, they need lots of points to control them.

296
00:42:48.980 --> 00:42:49.820
We want to know.

297
00:42:55.700 --> 00:42:58.670
We want to know where the the box is going to be.

298
00:42:59.960 --> 00:43:22.190
For that we look at our map very conveniently it's got a nice even coordinates the southeast longitude is West minus 120 30 minutes Point five southeast latitude is 47.57 and a half minutes is the full quadrangle with.

299
00:43:23.330 --> 00:43:28.160
we're going to be two and a half minutes to get a ninth of the quad, but if we put this in here, it will think that.

300
00:43:30.800 --> 00:43:36.530
Those less than 5% to be in degrees will get a two and a half degree box, so we need to value that is in.

301
00:43:37.940 --> 00:43:52.640
decimal degrees, and for that it's time for the calculator and 2.5 divided by 60 equals 0.04167.

302
00:44:01.130 --> 00:44:02.330
and

303
00:44:05.900 --> 00:44:09.560
We don't care about tix pasting the output is indeed.

304
00:44:11.270 --> 00:44:14.180
nad 27 the output you database.

305
00:44:15.260 --> 00:44:17.840
We can write this to the database we're building things in.

306
00:44:23.810 --> 00:44:25.340
The output coordinate system.

307
00:44:26.540 --> 00:44:27.740
We want to use.

308
00:44:31.790 --> 00:44:33.410
You tm Ken.

309
00:44:34.430 --> 00:44:41.960
And the scratch workspace we have an empty folder here we're going to use that, and this should run it's done.

310
00:44:45.980 --> 00:44:47.930
You should be able to open the catalog.

311
00:44:49.580 --> 00:44:50.330
and

312
00:44:55.100 --> 00:44:59.420
here's our map outline you can add our map outline to the composition.

313
00:45:04.730 --> 00:45:07.370
And there is a thin red line let's make it a little thicker.

314
00:45:16.670 --> 00:45:32.000
We do not need our reference layer that just slows us down so The next step is to transfer this map outline to contacts and faults and there are several ways to do it, we can copy and paste we can load copy and paste works pretty well, so we want to make this.

315
00:45:34.040 --> 00:45:34.670
editable.

316
00:45:35.690 --> 00:45:38.000
And selected copy.

317
00:45:39.170 --> 00:45:39.680
paste.

318
00:45:40.760 --> 00:45:42.830
paste it into contacts and faults.

319
00:45:45.770 --> 00:45:52.070
We can turn this off and there it is in contacts and false let's give us some attributes.

320
00:45:53.420 --> 00:45:54.680
So the type.

321
00:45:55.820 --> 00:45:56.180
Is.

322
00:45:57.380 --> 00:45:58.040
need line.

323
00:45:59.120 --> 00:46:00.290
it's not concealed.

324
00:46:01.490 --> 00:46:06.410
We calculated its location, so we know exactly where it is we're certain.

325
00:46:07.640 --> 00:46:08.630
That it exists.

326
00:46:13.100 --> 00:46:21.500
we're certain what it is and, at the moment we don't care what the label of the symbol is and let's leave the data source it blank also for the time being.

327
00:46:26.990 --> 00:46:30.290
Now we've got a box we've got something to digitize we're looking at.

328
00:46:31.610 --> 00:46:39.950
let's make this easy we're going to add a a layer of templates that allow us to digitize features, without having to.

329
00:46:41.090 --> 00:46:45.500
figure out too closely what other attributes are and we're going to go to add data.

330
00:46:46.700 --> 00:46:57.320
and go back to the gems toolbox, which is living here and into the resources layer and find contacts and full 24 K and added.

331
00:47:00.290 --> 00:47:11.300
contacts and false 24 K references contacts and false layer it doesn't know which one so there's a problem here, we need to click on one of the layers data repair data source.

332
00:47:12.530 --> 00:47:14.510
and go back to our new database.

333
00:47:17.870 --> 00:47:19.850
and select the contacts and faults layer

334
00:47:21.350 --> 00:47:38.990
Everything now knows where it's from these layers each one is visualizing a different attribute of contacts and false this one's telling us what the type is this one's being civilized on the basis of existence confidence, this one identity confidence.

335
00:47:42.530 --> 00:47:43.100
and so on.

336
00:47:45.290 --> 00:47:49.970
And the nice thing about this later also let's move in and zoom a little bit in here.

337
00:47:53.330 --> 00:47:55.130
If we decide to.

338
00:47:56.840 --> 00:47:58.310
Start digitizing.

339
00:47:59.930 --> 00:48:01.910
let's see where editable okay.

340
00:48:05.030 --> 00:48:05.690
We want.

341
00:48:09.260 --> 00:48:10.340
Great features window.

342
00:48:11.690 --> 00:48:13.130
We want to remove.

343
00:48:15.620 --> 00:48:17.360
contacts and faults from here.

344
00:48:18.890 --> 00:48:21.140
We want to remove map unit.

345
00:48:25.730 --> 00:48:26.390
lines.

346
00:48:31.280 --> 00:48:33.800
Stop editing yes.

347
00:48:40.790 --> 00:48:42.440
So, if we look at one of these here.

348
00:48:44.690 --> 00:48:46.460
it's got a name it's align.

349
00:48:47.840 --> 00:48:59.180
It makes a new feature for us of its kind of type of contact it's not concealed it's got a certain existence and identity competence values as location confidence meters value of 100.

350
00:49:00.440 --> 00:49:01.010
And it's.

351
00:49:03.260 --> 00:49:05.930
references and hill type of contact 100 meters.

352
00:49:06.980 --> 00:49:08.420
that's why i'm seeing here on this main.

353
00:49:10.190 --> 00:49:11.570
So I can take this.

354
00:49:14.360 --> 00:49:24.530
Now let's back up this is the 24,000 scale map, these are all certainly located contacts, interestingly, we put the base map in.

355
00:49:27.080 --> 00:49:34.340
You may be able to see here that the contact on the scan does not line up exactly with the contact and then the line.

356
00:49:37.340 --> 00:49:44.600
scan 24 K I think what this is showing is a measure of the distortion involved in making a map.

357
00:49:46.070 --> 00:49:49.640
pretty good on paper string in the library and scanning it again.

358
00:49:50.570 --> 00:49:58.610
So features have been shifted by the the history of this map and i'm reluctant to say that we know where things are within one millimeter map scale in this.

359
00:49:58.940 --> 00:50:08.420
So i'm going to digitize these all is having a 30 meter location conference meters let's start by digitizing this contract right here, we can start click.

360
00:50:15.440 --> 00:50:17.810
And you hit our contact me to the next.

361
00:50:18.980 --> 00:50:19.430
line.

362
00:50:23.540 --> 00:50:27.260
And as you may notice i'm snapping is enabled.

363
00:50:28.280 --> 00:50:28.880
This is the.

364
00:50:30.620 --> 00:50:32.480
Ark map configuration, we set up in the.

365
00:50:33.980 --> 00:50:35.240
First bit here earlier.

366
00:50:44.720 --> 00:50:48.230
I know this is really exciting to watch I won't bore you too much more.

367
00:50:51.500 --> 00:51:00.680
I can turn on the lstm layer and here grey grey halos showing us on the map, what a 30 meter location competence meter value looks like.

368
00:51:02.930 --> 00:51:12.500
It may be that I been to conservative and we call these 20 meter i'll see him there almost certainly not 10 if we don't like this, we could.

369
00:51:14.780 --> 00:51:18.770
Open the table and change these values.

370
00:51:20.990 --> 00:51:21.680
That 10.

371
00:51:27.740 --> 00:51:29.060
And the handles are skinnier.

372
00:51:30.380 --> 00:51:41.630
I don't think those lines of that located let's stick with 30 so let's see edit a new database role change and Edit a dangerous road change Rebecca 30.

373
00:51:45.350 --> 00:51:46.070
We have.

374
00:51:47.120 --> 00:51:48.020
The map boundary.

375
00:51:49.430 --> 00:51:54.260
And this contact that makes a close Polygon and this contact me so close Polygon.

376
00:51:56.600 --> 00:51:59.420
We can make polygons now, before we do that.

377
00:52:01.700 --> 00:52:05.660
i'd like to see what we have selected here so let's.

378
00:52:10.460 --> 00:52:11.810
zoom is like the features.

379
00:52:13.820 --> 00:52:15.680
If we build polygons from this.

380
00:52:17.450 --> 00:52:18.170
Well let's do it.

381
00:52:20.660 --> 00:52:22.040
In pawleys oh.

382
00:52:23.630 --> 00:52:28.400
We need to have Polygon features in here Polygon layer to make polly's into it so let's add mapping apologies.

383
00:52:32.720 --> 00:52:33.920
Now we can build polly.

384
00:52:36.380 --> 00:52:38.570
And this will build polly's inaccurate police.

385
00:52:39.800 --> 00:52:42.440
And we do not want that Polygon.

386
00:52:44.150 --> 00:52:48.650
That was sort of the the local universe, we can keep.

387
00:52:50.870 --> 00:52:59.840
deleting those when we ever we build polygons or we can chop them that boundary up a little pieces so when they graduate we don't grab all of it by here, we want.

388
00:53:05.840 --> 00:53:13.130
Okay that'll work let's do one more line here piece of aligned again we're going to call us a 30 meter contact.

389
00:53:25.130 --> 00:53:27.050
We can select a map boundary.

390
00:53:28.310 --> 00:53:29.330
select contact.

391
00:53:31.340 --> 00:53:32.210
build pawleys.

392
00:53:33.800 --> 00:53:41.120
Okay, that Polygon look at its attributes, that is, like everything else in here map unit.

393
00:53:42.290 --> 00:53:43.730
ti si es.

394
00:53:46.580 --> 00:53:47.570
it's like this one.

395
00:53:51.710 --> 00:53:52.700
looks like this one.

396
00:53:56.270 --> 00:53:57.170
let's do.

397
00:54:00.230 --> 00:54:04.010
One other map unit here one of the Polygon.

398
00:54:05.060 --> 00:54:05.930
And again.

399
00:54:07.760 --> 00:54:10.970
One of my my template 30 meters.

400
00:54:20.900 --> 00:54:22.460
Now it's not going to snap.

401
00:54:23.600 --> 00:54:32.750
Because we have not enabled snap a sketch, we enable that we can connect to the language is true we didn't so let's connect this now let's snap.

402
00:54:34.190 --> 00:54:35.450
there's a closed Polygon.

403
00:54:36.590 --> 00:54:37.490
and select that.

404
00:54:39.470 --> 00:54:40.610
construct polygons.

405
00:54:42.440 --> 00:54:43.130
That one.

406
00:54:46.640 --> 00:54:47.390
Co.

407
00:54:49.100 --> 00:54:50.060
We can now.

408
00:54:51.410 --> 00:54:58.790
Double Click on this go to the assemblage of biology field symbolized by unique values of Matthew.

409
00:55:00.230 --> 00:55:06.350
And let's pick some colors that makes sense to us that's a nice ese so i'm going to call it, green.

410
00:55:07.760 --> 00:55:07.910
and

411
00:55:10.220 --> 00:55:10.850
gold color.

412
00:55:12.620 --> 00:55:13.130
orange.

413
00:55:16.640 --> 00:55:31.100
Eventually, will call the map, based on the symbol field, but while we're building the map that's inconvenient it's not easy to transfer symbol values from the DM meteor so in the early stages of building a map I typically symbolize directly on mapping and and change it later.

414
00:55:33.590 --> 00:55:38.840
i'm gonna stop recording this and go digitize the rest of the map and we'll come back later.

415
00:55:50.420 --> 00:55:51.290
Robert Marvinney, DACF: Thanks Ralph.

416
00:55:53.450 --> 00:56:03.590
Robert Marvinney, DACF: there's first of all I know, it seems, some people were having some trouble with the video freezing and i'm guessing that's a bandwidth problem and.

417
00:56:04.070 --> 00:56:14.900
Robert Marvinney, DACF: It looks like everybody has the video turned off that's usually the solution to improve that so I don't know if there's any any solution, beyond that, right now.

418
00:56:16.190 --> 00:56:22.940
Robert Marvinney, DACF: Ralph one question in the chat is why not digitizing unit as polygons.

419
00:56:24.350 --> 00:56:30.920
Ralph Haugerud: Basically, these we want to make sure that the unit boundaries lineup with contacts and false the contact her directly on top of them.

420
00:56:31.430 --> 00:56:42.740
Ralph Haugerud: Also, if we digitize you to polygons it means digitizing every boundary twice, but the unit on each side of it, and so, in general, much easier to digitize the line work and build polygons from it.

421
00:56:45.380 --> 00:56:45.950
Robert Marvinney, DACF: Okay.

422
00:56:47.660 --> 00:56:52.130
Robert Marvinney, DACF: Any any other questions folks Is this a good time to.

423
00:56:53.930 --> 00:56:59.930
Robert Marvinney, DACF: If you've got any other questions to unmute yourself and just ask Ralph directly.

424
00:57:06.860 --> 00:57:22.100
Robert Marvinney, DACF: yeah i'm sure there's a lot of things coming out everybody, particularly if you're not familiar with this gems work unfortunately there's the recording and i'm sure Ralph would be happy to respond offline to your questions as well.

425
00:57:24.770 --> 00:57:26.480
Robert Marvinney, DACF: So Ralph are you continuing then.

426
00:57:27.500 --> 00:57:30.230
Ralph Haugerud: Yes, let me share my screen again.

427
00:57:30.500 --> 00:57:30.950
Okay.

428
00:57:33.590 --> 00:57:36.080
Ralph Haugerud: and start the next one.

429
00:57:41.120 --> 00:57:53.840
So I have digitized all the contacts in this area, I built polygons and color them by backyard looks pretty good from here, we still have two more classes of features to digitize the the tough beds.

430
00:57:55.070 --> 00:58:05.150
Robert Marvinney, DACF: Across the map and the strikes and deployments Institute in many places hard to read before we dive into that let's look at the recipe for that process.

431
00:58:06.140 --> 00:58:18.860
Robert Marvinney, DACF: we're going to add the feature class rather feature class to our map composition we're going to set some crude civilization for orientation points simple betting symbol we're going to set the symbols to rotate via the as midfield.

432
00:58:20.420 --> 00:58:29.660
We digitize the bedding location, we grabbed the edit tool and select that in future we can right click and get attributes and key and the inclination value.

433
00:58:30.290 --> 00:58:40.940
So we can click on the rotate tool and the editor toolbar grabbed a symbol and rotated around until matches the underlying image, this will set the as much value will repeat for each one.

434
00:58:43.220 --> 00:58:44.000
need to add.

435
00:58:45.140 --> 00:58:47.420
The orientation points feature class.

436
00:58:49.580 --> 00:58:51.050
You said some civilization.

437
00:58:55.040 --> 00:58:58.250
And here's a bunch of things and I want to use the F CDC civilization.

438
00:58:59.420 --> 00:59:00.260
Oh, I forgot.

439
00:59:04.010 --> 00:59:05.270
set it to rotate.

440
00:59:06.320 --> 00:59:10.280
By the as the midfield say okay.

441
00:59:12.620 --> 00:59:16.370
And let's see what else um let's try one here.

442
00:59:17.540 --> 00:59:18.560
So you can zoom in.

443
00:59:19.700 --> 00:59:20.180
let's.

444
00:59:21.260 --> 00:59:22.430
Start editing.

445
00:59:24.650 --> 00:59:27.260
We find him as a template we can grab.

446
00:59:29.240 --> 00:59:32.000
digitize the point grab the edit tool.

447
00:59:33.170 --> 00:59:38.120
Right click attributes, this has got a 45 degree dip.

448
00:59:40.190 --> 00:59:42.800
And then we can grab the rotation tool.

449
00:59:44.000 --> 00:59:55.340
And rotate this around until it matches but I can't see that you can't see it, so we need to fix our civilization there a couple of things, one is we go to the data frame properties.

450
00:59:56.420 --> 00:59:58.910
and set the reference scale to be 24,000.

451
01:00:00.590 --> 01:00:03.200
And then we zoom in.

452
01:00:06.020 --> 01:00:07.070
The symbols bigger.

453
01:00:08.090 --> 01:00:11.150
And I think i'm going to make the symbol of bright color so I can see it.

454
01:00:16.190 --> 01:00:22.010
and see if that helps and I can see it, and I can see, I didn't get the rotation quite right so let's take this.

455
01:00:24.500 --> 01:00:36.800
And there's the as of value 170 8.7 we can be finicky and say oh that was probably a 179 or something again proving the value, I personally don't see the point to it you're welcome to do so.

456
01:00:38.840 --> 01:00:39.950
Now we can go on.

457
01:00:42.020 --> 01:00:42.920
To the next one.

458
01:00:44.060 --> 01:00:46.010
And we grabbed the template.

459
01:00:49.490 --> 01:00:54.410
The editor toolbar the attributes that has a.

460
01:00:56.780 --> 01:00:58.730
I believe a 40 degree inclination.

461
01:01:01.460 --> 01:01:03.380
And we can grab the rotate tool.

462
01:01:06.410 --> 01:01:08.300
rotate until it lines up.

463
01:01:10.850 --> 01:01:13.520
Back to create features rabbit template.

464
01:01:17.390 --> 01:01:19.400
i'm using the scroll wheel, a change by zoom.

465
01:01:24.710 --> 01:01:28.640
attributes that's got a 60 degree inclination.

466
01:01:31.760 --> 01:01:32.870
grab the rotate tool.

467
01:01:34.580 --> 01:01:37.100
Around till it lines up.

468
01:01:44.900 --> 01:01:53.240
It helps to this systematically i'm not going to bore you with it, there is one of the thing to show you about this we've built up several points here.

469
01:01:54.230 --> 01:02:02.510
Natural table they've got as some US and inclinations but now i'm gonna have to type value, and we do use the field calculator at some point and say that these are all.

470
01:02:03.680 --> 01:02:03.980
bedding.

471
01:02:07.790 --> 01:02:11.660
And, as I didn't take very well let's try this again feel the calculator.

472
01:02:12.710 --> 01:02:14.390
And they have double quotes on both sides.

473
01:02:21.890 --> 01:02:22.100
yeah.

474
01:02:24.800 --> 01:02:29.150
i'm i'm going to give you a break and go to the rest of these will come back in a minute.

475
01:02:32.780 --> 01:02:38.030
i've digitized all the strikes and dips I think next step is to do map, you know lines.

476
01:02:39.110 --> 01:02:42.980
So we need to add the magnetic lines feature class the map composition.

477
01:02:44.300 --> 01:02:47.240
We can go over here and starting this little one here.

478
01:02:49.610 --> 01:02:52.730
And I want to something stop editing.

479
01:02:53.840 --> 01:02:54.470
Yes.

480
01:02:58.670 --> 01:03:05.750
And this should bring up a template for nappy two minds, and I can go in here and digitize.

481
01:03:09.020 --> 01:03:10.520
This short piece of.

482
01:03:15.920 --> 01:03:16.580
piece of.

483
01:03:17.840 --> 01:03:19.520
Tough bed T T.

484
01:03:20.780 --> 01:03:25.580
And so the attributes map unit is T T.

485
01:03:26.660 --> 01:03:28.070
it's not concealed.

486
01:03:29.960 --> 01:03:35.600
it's a dashed line which makes me think that location conference meters at the scale of about 100 is appropriate.

487
01:03:37.010 --> 01:03:39.020
That appears to be certainly there.

488
01:03:40.190 --> 01:03:44.930
And certainly identified i'm gonna leave the other attributes blank for the time being.

489
01:03:47.600 --> 01:03:48.650
and come to the West.

490
01:03:50.930 --> 01:03:51.710
and

491
01:03:53.060 --> 01:04:03.170
This line this tough bet is continuous but it's got a concealed and not concealed part portions parts or dash and parts that are not dashed so start here.

492
01:04:06.410 --> 01:04:08.780
next piece goes across the valley.

493
01:04:14.030 --> 01:04:15.410
start a continuous piece.

494
01:04:20.630 --> 01:04:25.250
And my guess is is continuous through this striking difference broken only so striking to put show.

495
01:04:40.100 --> 01:04:49.850
You can see i'm i'm starting an ending ending and starting line wherever the line character changes from concealed to dash continuous.

496
01:04:53.060 --> 01:04:54.680
Again i'm zooming.

497
01:04:55.940 --> 01:04:57.140
Using the scroll wheel.

498
01:05:00.110 --> 01:05:00.950
My mouse.

499
01:05:08.750 --> 01:05:13.220
Now i've done a whole bunch of lines, and these are all tough bed.

500
01:05:15.410 --> 01:05:16.490
T T.

501
01:05:20.030 --> 01:05:27.410
See I believe let's open up the attribute table and collect all of these lines that are not labeled.

502
01:05:28.580 --> 01:05:33.920
and say that these are map unit T T C.

503
01:05:41.330 --> 01:05:42.440
and

504
01:05:43.820 --> 01:05:46.070
Now it gets a little more interesting.

505
01:05:51.050 --> 01:05:53.390
I want to select the ones that are concealed.

506
01:05:54.410 --> 01:05:55.100
That REACH.

507
01:05:56.240 --> 01:05:58.550
This reach this REACH.

508
01:05:59.600 --> 01:06:00.230
This one.

509
01:06:02.390 --> 01:06:02.840
and

510
01:06:04.520 --> 01:06:06.500
This one and again.

511
01:06:07.670 --> 01:06:10.970
back to the actual table and the field calculator.

512
01:06:12.080 --> 01:06:13.790
knows all are.

513
01:06:17.000 --> 01:06:17.870
concealed.

514
01:06:20.600 --> 01:06:21.500
The remainder.

515
01:06:22.700 --> 01:06:23.600
Of this easy way.

516
01:06:29.450 --> 01:06:30.350
didn't get those.

517
01:06:34.370 --> 01:06:35.420
Are his concealed.

518
01:06:37.940 --> 01:06:38.570
was no.

519
01:06:44.900 --> 01:06:48.650
Now, if we can see this, we had certain length.

520
01:06:51.680 --> 01:06:55.010
That were continuous lines well located there's one.

521
01:06:58.250 --> 01:07:00.800
Any shift and select again there's another one.

522
01:07:13.940 --> 01:07:14.960
there's another one.

523
01:07:17.030 --> 01:07:17.930
there's one there.

524
01:07:19.670 --> 01:07:21.470
You can open up the attribute table.

525
01:07:24.050 --> 01:07:29.510
And these are the ones that well located so their location conference leader should be fairly small.

526
01:07:31.430 --> 01:07:33.890
And on this map I think well locators probably.

527
01:07:35.000 --> 01:07:35.480
30.

528
01:07:42.080 --> 01:07:45.830
remainder or not well located and i'm going to stick with a value.

529
01:07:47.870 --> 01:07:51.980
Of 100.

530
01:07:54.260 --> 01:07:58.670
And I hope in the discussion someone will ask me how I chose those values and how I defend them.

531
01:08:02.000 --> 01:08:02.690
um.

532
01:08:03.980 --> 01:08:06.740
let's see let's clear selection.

533
01:08:11.810 --> 01:08:14.240
Everything has existence confidence is certain.

534
01:08:16.850 --> 01:08:19.550
And everything has an identity confidence that certain.

535
01:08:24.350 --> 01:08:31.100
Everything on this map can be plotted it at a 24,000 scale and i'm going to say let's say we can plot it.

536
01:08:33.650 --> 01:08:37.490
All skills that are larger than one 200,000.

537
01:08:38.810 --> 01:08:44.300
So plot at scale is the denominator of the smallest scale of each can be plotted out.

538
01:08:47.510 --> 01:08:48.230
thousand.

539
01:08:49.880 --> 01:08:59.810
And we haven't defined data sources, yet, but i'm going to say that the data source for stuff that I digitize from john wooden's map is da s one.

540
01:09:09.740 --> 01:09:12.470
problem is now in symbolizing these.

541
01:09:13.610 --> 01:09:27.920
And if this were contacts and faults, we have code to make it easy to go from the conflation of location competence meters existence competence identity confidence and the macular type to tell us how to draw these that we don't.

542
01:09:29.210 --> 01:09:32.900
So I am going to stick in a.

543
01:09:34.160 --> 01:09:35.090
dummy value.

544
01:09:38.450 --> 01:09:40.040
Which means I need to stop editing.

545
01:09:43.850 --> 01:09:45.500
i'm going to add a field here.

546
01:09:49.040 --> 01:09:55.880
Call it l type because I learned js in menlo park in the 90s, and we all did all a cart which use the old type for lines.

547
01:09:57.440 --> 01:09:59.750
of text and let's see that 50.

548
01:10:01.940 --> 01:10:03.680
So let's start here.

549
01:10:05.630 --> 01:10:07.130
On is concealed.

550
01:10:10.160 --> 01:10:10.610
Sorry.

551
01:10:12.350 --> 01:10:14.630
And then sort by location competence meters.

552
01:10:17.690 --> 01:10:18.380
And so.

553
01:10:45.770 --> 01:10:51.140
So for those that have that are not concealed and have a well located we're going to call those.

554
01:10:54.020 --> 01:10:54.560
The bed.

555
01:11:03.290 --> 01:11:04.130
Continuous.

556
01:11:06.830 --> 01:11:10.040
Are these here that are not concealed but or not well located.

557
01:11:11.540 --> 01:11:13.190
In all those key bed.

558
01:11:16.850 --> 01:11:17.570
dashed.

559
01:11:20.840 --> 01:11:23.360
And for these that are concealed.

560
01:11:24.500 --> 01:11:26.480
we're going to call them key bed.

561
01:11:27.590 --> 01:11:28.070
garden.

562
01:11:34.880 --> 01:11:36.260
And at this point.

563
01:11:40.280 --> 01:11:44.000
We can symbolize these on those categories.

564
01:11:47.720 --> 01:11:52.520
categories field is l type at all values.

565
01:11:54.770 --> 01:11:56.000
And we can search for.

566
01:12:00.410 --> 01:12:01.070
Key bed.

567
01:12:02.120 --> 01:12:02.750
and

568
01:12:06.680 --> 01:12:07.940
I think I want to use that one.

569
01:12:16.640 --> 01:12:17.750
that's the dashed one.

570
01:12:24.800 --> 01:12:27.560
And here's a dotted key bed.

571
01:12:31.790 --> 01:12:39.410
Now this is kind of a kludge and reflects the reality that gems is not focused on civilization it's focused on the concepts behind the symbols.

572
01:12:40.640 --> 01:12:42.080
little bit clumsy in this case.

573
01:12:44.000 --> 01:12:50.270
Matthew the lines or something that i've not digitized her coated many of inside not bother to figure out an easy way to do this.

574
01:12:52.190 --> 01:12:53.180
selection.

575
01:12:56.240 --> 01:13:02.450
We can turn on mapping a polly's and turn off this and this begins to look like a geologic map.

576
01:13:06.650 --> 01:13:25.070
next step is to check the topology of our digitizing we can build a standard Arc map topology and find out if the contacts lie on top of the Polygon boundaries and find dangles both kind of limited what we can do that way, and so we worked up a tool for checking the topology of.

577
01:13:26.210 --> 01:13:38.810
A geologic map database that goes into things a little more detail now, I think my digitizing is pretty good and i'm not sure there are any errors in here, but I want to find some so i'm going to make an error, just to make sure we have something to do look at your.

578
01:13:40.400 --> 01:13:41.480
want to.

579
01:13:44.630 --> 01:13:46.130
Take this line here.

580
01:13:47.360 --> 01:13:47.780
Ah.

581
01:13:50.930 --> 01:13:53.870
i'm going to extend that contact so it's got a dang.

582
01:13:55.130 --> 01:13:58.550
And for that matter, it doesn't lie on top of the Polygon boundary there.

583
01:13:59.930 --> 01:14:05.330
And i'm going to go back to the PowerPoint when you save my edits here.

584
01:14:09.230 --> 01:14:20.330
The topology check tool looks the geologic map topology and more details to anadarko apology can um it is written, especially to get snapping errors in contacts and faults.

585
01:14:20.870 --> 01:14:32.960
It also will pick up some in line attribution errors some fault direction at fault line direction errors and it does a standard dark topology looking for whether or not contacts and false cover all Polygon boundaries on.

586
01:14:34.790 --> 01:14:43.310
Whether there are lines that cross themselves, and if there are duplicate lines So these are some of the kinds of errors that topology check and find that the Ark apology both.

587
01:14:43.910 --> 01:14:52.430
places where the contact misconceived continuation don't align places where they do align but the break isn't it the value or contact.

588
01:14:55.010 --> 01:14:59.630
places or four units meet at one point which is geologically implausible.

589
01:15:00.890 --> 01:15:02.240
faults, with no offset.

590
01:15:04.700 --> 01:15:15.410
And a tricky one we use the the direction of a fault line to say what's the upper plate and lower play on a thrust fall and if we get the directionality of the lines wrong.

591
01:15:18.590 --> 01:15:26.210
and put the teeth on the wrong side, and so we want to see the fault lines don't change their every two seconds of a front, we don't have a two to two or a founder from direction.

592
01:15:28.100 --> 01:15:35.090
ology check also builds tables showing what map units are on what side of certain classes of contact and fault.

593
01:15:35.750 --> 01:15:49.970
So this is a table for all the concealed contacts and false in the database, or in the feature class Peter data set and all of the entries should be on the diagonal concealed contacts or false should always have the same thing on each side.

594
01:15:51.470 --> 01:15:57.380
there's a similar context not concealed table, which should have no values in the day, and we should all be out here on the science.

595
01:15:59.090 --> 01:16:01.250
there's also a false nuts and sealed table.

596
01:16:02.450 --> 01:16:09.650
Put in here, because if there's a fault in very young material these units are ordered from roughly from young to old young to old.

597
01:16:11.360 --> 01:16:23.300
Look at it closely, we don't want to go scaring anybody saying that we've got you know false in the movie where there are such things to do this, we need to have map units that are ordered by hierarchy a rough approximation age.

598
01:16:24.590 --> 01:16:33.020
And so we need a skeleton DM you that has map you're an Iraqi in it, and we need to go build that right now so let's go back to the.

599
01:16:34.130 --> 01:16:34.610
map.

600
01:16:35.750 --> 01:16:37.190
and add this to the.

601
01:16:41.240 --> 01:16:46.010
map composition open it and we're going to edit it so.

602
01:16:47.240 --> 01:16:52.610
Start editing our map units from top to bottom, or que Al.

603
01:16:58.550 --> 01:16:59.480
To oil.

604
01:17:05.720 --> 01:17:08.000
tcs and.

605
01:17:09.980 --> 01:17:13.100
we're going to leave all the other stuff like for the time being.

606
01:17:15.740 --> 01:17:19.610
National turn the description field off want to see.

607
01:17:20.690 --> 01:17:26.810
hierarchy and i'm going to say there's one dash.

608
01:17:27.830 --> 01:17:28.400
one.

609
01:17:29.450 --> 01:17:31.460
Special one one dash to.

610
01:17:32.960 --> 01:17:33.470
dash.

611
01:17:34.610 --> 01:17:35.270
three.

612
01:17:37.700 --> 01:17:38.720
and two.

613
01:17:39.740 --> 01:17:41.180
We can sort this in.

614
01:17:42.260 --> 01:17:45.920
versus sending order and screw it up, let me start by hierarchy.

615
01:17:47.210 --> 01:17:50.870
and get back the order, we want the strategy, what are the map, yes.

616
01:17:52.790 --> 01:17:57.020
With this done, you can save our edits and stop editing.

617
01:17:58.190 --> 01:18:00.620
and run the topology check tool.

618
01:18:02.090 --> 01:18:08.930
and wants to know which feature data set working on and we're going to work on the geologic map feature data set there isn't other ones database.

619
01:18:09.590 --> 01:18:26.840
And we're going to say that, yes, ah key values are less than to consider growing and dotted line or anything this tool will tell us where we've missed concealed contacts we could draw in contacts and faults it won't tell us anything about concealed mapping of mines, unfortunately.

620
01:18:29.690 --> 01:18:30.350
We can run it.

621
01:18:33.440 --> 01:18:37.670
And oh yeah every recently added to the tool kira a little bit of a.

622
01:18:38.810 --> 01:18:43.910
really nice thing if you're connected to the Internet, when you run one of these tools it checks.

623
01:18:45.380 --> 01:18:50.030
Back at the github repository and sees that there's a new newer version and tells you, which is nice to know.

624
01:18:52.190 --> 01:18:58.250
So the first thing we're doing is building a standard topology invalidated we find the errors we export them, so you can look at them later.

625
01:19:01.820 --> 01:19:15.170
Then it goes and does some hard work where we're identifying contacts and false with Mexican apologies to find out which Polygon what map unit is on each side of every line segment and contacts and faults.

626
01:19:16.550 --> 01:19:20.240
Then we're looking at the directionality at the beginning and ending so you can figure out how the.

627
01:19:21.590 --> 01:19:28.160
Line segments go around each node and doing a lot of fancy logic and.

628
01:19:32.720 --> 01:19:42.080
Catherine which nodes look like it might be bad ones and it's done okay so close this and we can go add some data.

629
01:19:45.560 --> 01:19:50.780
The topology check tool makes a new folder and puts a new database incited.

630
01:19:52.520 --> 01:19:52.850
and

631
01:19:54.290 --> 01:19:55.190
And those two.

632
01:20:00.020 --> 01:20:02.120
I think that's all we need here.

633
01:20:04.070 --> 01:20:13.010
And so, the first thing is, we had topological errors and I find I can see those best if I make the Nice big fat red lines.

634
01:20:14.330 --> 01:20:16.310
and put them underneath.

635
01:20:20.180 --> 01:20:25.370
The lines of my my database, the good ones and most of these.

636
01:20:26.660 --> 01:20:27.380
Are the.

637
01:20:28.910 --> 01:20:42.830
One line around the printer and, for some reason, I guess, because there's a gap on the outside this always shows up as an error in the apology you ignore it, but there's one over in here.

638
01:20:44.090 --> 01:20:45.080
Where there's a problem.

639
01:20:46.370 --> 01:20:47.570
That we knew we were going to have.

640
01:20:53.360 --> 01:20:58.670
Where the Polygon boundary is no longer underneath the contacts remove the contact.

641
01:21:01.430 --> 01:21:08.570
If we turn on our arrows bad nodes good to bad notes in here also looking to see what those are.

642
01:21:11.930 --> 01:21:13.730
And one of them here.

643
01:21:16.730 --> 01:21:17.600
let's see.

644
01:21:19.460 --> 01:21:23.900
Sorry dangling contact and the other is a case where four lines.

645
01:21:27.680 --> 01:21:28.580
meet at a point.

646
01:21:30.860 --> 01:21:34.760
And that's geologically implausible if we fix the line work.

647
01:21:39.020 --> 01:21:41.030
I need to edit this here.

648
01:21:43.130 --> 01:21:44.600
And features start editing.

649
01:21:46.070 --> 01:21:55.100
We put this thing back where it belongs, we should be able to rerun the topology check tool and find there are no errors no bad notes here and no on.

650
01:21:56.330 --> 01:21:59.480
Areas where well here let's look at this.

651
01:22:05.720 --> 01:22:07.700
Where the boundary was covered by a line.

652
01:22:36.770 --> 01:22:38.960
Ralph Haugerud: looks like that's the end of my video.

653
01:22:40.430 --> 01:22:42.020
Robert Marvinney, DACF: Okay Ralph.

654
01:22:46.040 --> 01:22:48.050
Robert Marvinney, DACF: One question in the chat at this point.

655
01:22:49.580 --> 01:22:56.810
Robert Marvinney, DACF: Whether you have an opinion on using auto complete Polygon to digitize map uni pawleys.

656
01:22:57.890 --> 01:23:03.860
Ralph Haugerud: The answers I don't have an opinion it's not a tool i've used very much i'm not real familiar with it and.

657
01:23:05.720 --> 01:23:13.730
Ralph Haugerud: I have had so much trouble with line work polygons not matching line work that that I am Los to do anything other than.

658
01:23:14.990 --> 01:23:16.580
Ralph Haugerud: Make the polygons from the lines.

659
01:23:19.400 --> 01:23:26.510
Robert Marvinney, DACF: Okay anyone else have any questions right now for Ralph.

660
01:23:29.060 --> 01:23:30.770
Christian Halsted: So this is Chris.

661
01:23:32.180 --> 01:23:44.990
Christian Halsted: I am going to prompt Ralph to talk a little bit more about some of those value judgments that go into entering the each level metadata around a confidence interval or confidence values and whatnot.

662
01:23:47.960 --> 01:23:48.830
Ralph Haugerud: Certainly.

663
01:23:50.120 --> 01:23:57.020
Ralph Haugerud: So for line work, there are three confidence values we care about existence confidence identity confidence and location competence meters.

664
01:23:57.860 --> 01:24:04.550
Ralph Haugerud: and on our maps traditionally if there's a question about the existence or identity alliance queried.

665
01:24:05.270 --> 01:24:11.000
Ralph Haugerud: And so, if the lines not query dynamic check questionable on those they're always certain if the line is query.

666
01:24:11.930 --> 01:24:28.940
Ralph Haugerud: Our traditional symbolic it doesn't always tell us whether the geologists thought the existence was uncertain or the identity and oftentimes with line work context can tell us that but you've got to use some judgment their location confidence meters is the hard one.

667
01:24:30.080 --> 01:24:31.550
Ralph Haugerud: And the basic rule of thumb.

668
01:24:32.690 --> 01:24:40.760
Ralph Haugerud: is, at least if you're usgs is if the lines continuous it's where out to be within plus or minus one millimeter at map scale.

669
01:24:41.870 --> 01:24:43.580
Ralph Haugerud: But it's surprising how.

670
01:24:44.990 --> 01:24:54.050
Ralph Haugerud: Variable that's interpreted and one of the things that drove me to think we need to be explicit about how actually located on lines are.

671
01:24:54.530 --> 01:25:02.270
Ralph Haugerud: was talking to a senior colleague who worked in the dense forest of the Oregon and Washington coast ranges for many, many years.

672
01:25:02.960 --> 01:25:13.820
Ralph Haugerud: Who basically said in that terrain, this is pre GPS, it was so hard to tell where you were that if you know what things are within a quarter of an inch on the map so that's six millimeters it was a continuous line.

673
01:25:14.510 --> 01:25:26.690
Ralph Haugerud: And he knew that but none of his mapreduce did, and so I came to the conclusion that it was worth trying to be explicit, especially for our maps should be used, not by geologists but by county planners.

674
01:25:28.370 --> 01:25:43.190
Ralph Haugerud: Other resource specialist outside of geology, so I think it's important to us a number, and not just say accurate or or approximate nor inferred The question then is how to get a number and the first thing to realize is that.

675
01:25:44.660 --> 01:25:54.110
Ralph Haugerud: an approximate numbers okay that we know so much others know so little that even our guesstimate if, within a factor of two is probably going to be pretty useful for people.

676
01:25:54.830 --> 01:26:02.090
Ralph Haugerud: I prefer to use a floating Point number for this, because it is a real world quantity, where the we're measuring estimating.

677
01:26:03.200 --> 01:26:10.670
Ralph Haugerud: And then, for this map I said the contacts were drawn as certain so usgs map it's in dry country.

678
01:26:11.240 --> 01:26:22.160
Ralph Haugerud: I think that means there plus and minus one millimeter which is 24 meters for that scale scale, but there's some location problems, some registration problems because the math Paper itself has worked apparently.

679
01:26:23.330 --> 01:26:24.320
Ralph Haugerud: And so I went to 30.

680
01:26:26.570 --> 01:26:38.810
Ralph Haugerud: That explains the certain the the is it's for things that were dashed wants to be some value that's that's bigger than that and that comes from.

681
01:26:40.430 --> 01:26:53.300
Ralph Haugerud: A combination both of field experience in this terrain know how well, can you guess where things are and also looking at the the value part of the maps that Gray HALO and seeing is that reasonable.

682
01:26:54.950 --> 01:26:58.220
Ralph Haugerud: I hope that's some a useful answer Chris.

683
01:26:59.360 --> 01:27:10.580
David Soller: Ralph is is Dave If I could just add a few comments to that in in the general documentation we recognize that the idea of location confidence meters.

684
01:27:11.480 --> 01:27:31.640
David Soller: Is a real visceral issue for many people, especially when we're when you're you're digitizing the map for whom the geologist is no longer available for consultation, so we were expressing that the location confidence meters can be thought of someone as a relative.

685
01:27:32.720 --> 01:27:47.960
David Soller: comparison you know so 20 meters versus 50 versus 100 is not exactly 2050 and 100 but it's a it's a it gives it connotes the the relative certainty versus the uncertainty in the numbers.

686
01:27:49.280 --> 01:27:58.100
David Soller: Then the other point is, I know many of us are kind of unfamiliar with you know why do we use existence and identity confidence.

687
01:27:58.790 --> 01:28:20.510
David Soller: This was not created for nc gop on nine jen's It was following on the the federal federal geographic data committees digital standard for cartography where where these ideas were first articulated so we're essentially meshing the the the thinking with the previous standard.

688
01:28:21.800 --> 01:28:22.160
Next.

689
01:28:24.230 --> 01:28:32.180
Ralph Haugerud: And i'd like to add, there are times when you simply cannot figure out what an appropriate value is and we're going to get to one of those shortly, when I translate.

690
01:28:32.990 --> 01:28:50.090
Ralph Haugerud: Existing database has a cross section, with very few clues as to how well located things are, and for that cross section I decided that it was simply not reasonable to guess, and I put in a no value minus 999, which is a nice way to say no, for a floating point value.

691
01:28:51.710 --> 01:28:56.150
Ralph Haugerud: Because I find it simply wasn't reasonable to hypothesize how well located those lines were.

692
01:29:02.600 --> 01:29:03.020
Robert Marvinney, DACF: Okay.

693
01:29:05.330 --> 01:29:10.880
Robert Marvinney, DACF: there's a question in the chat for john brooks john you can just unmute and ask this question directly.

694
01:29:17.120 --> 01:29:18.620
John Brooks: There we go i'm.

695
01:29:20.630 --> 01:29:27.290
John Brooks: really like I like what you're this program and the gyms is first time i've seen in our in our company we created an internal.

696
01:29:28.010 --> 01:29:46.730
John Brooks: database, and this is much more sophisticated than anything we ever had one of the one of the things I wonder is, can you know in our work, we have a relatively limited number of data types lines or polygons or as you digitize some lines and points.

697
01:29:48.170 --> 01:30:03.860
John Brooks: Is it possible, just to create a template kind of our company template to all those are already those layers are inserted, and then the properties are defined, and then you just kind of remove the layers that you don't want, in the end, so that.

698
01:30:04.910 --> 01:30:09.170
John Brooks: The you know it seems like the setup processes fairly time consuming.

699
01:30:10.580 --> 01:30:15.260
John Brooks: I didn't know if there be discontinuity of file locations, or something like that what.

700
01:30:17.450 --> 01:30:28.370
John Brooks: what's what's really referenced outside of the program once you insert those layers you all internally internal So if you open a template and then save it under new drive this everything transfer with it.

701
01:30:29.510 --> 01:30:42.350
Ralph Haugerud: If you load the layers and make a database a map composition and save it moved someplace else the layer information lives in the next D file I don't believe it goes with the database.

702
01:30:43.070 --> 01:30:43.760
Ralph Haugerud: And so, if you.

703
01:30:43.910 --> 01:30:47.600
Ralph Haugerud: Take the database alone and put it someplace else it will know how to symbolize itself.

704
01:30:49.250 --> 01:30:56.690
Ralph Haugerud: One of the templates anyway, if you put symbol values in and say use this style file that it does know how.

705
01:30:57.200 --> 01:31:01.460
Ralph Haugerud: But, but the the mx D is where that layer information is stored.

706
01:31:04.370 --> 01:31:12.830
Ralph Haugerud: And I don't think there'd be any problem well, there is no problem in making more layer files that have your standard items on the standard features that's what I do, I mean.

707
01:31:14.030 --> 01:31:24.380
Ralph Haugerud: When i'm digitizing i've got an orientation points 24 K layer that I stick in that allows me to pick affiliation or cleavage rich right or whatever, without having to type stuff in.

708
01:31:25.100 --> 01:31:33.260
Ralph Haugerud: Using these templates is a really nice way to make the transition from the way we think about features which typically is a category.

709
01:31:33.650 --> 01:31:49.190
Ralph Haugerud: A single descriptor contact approximate or poorly located poorly measured betting to the gems feature which resolves that in multiple attributes so it's bedding and it's got a large radiation competence degrees value.

710
01:31:50.720 --> 01:31:51.140
Ralph Haugerud: and

711
01:31:53.870 --> 01:32:02.330
Ralph Haugerud: You know those things are very recently handled with with feature templates those templates I would guess tend to be fairly idiosyncratic.

712
01:32:03.140 --> 01:32:09.800
Ralph Haugerud: And so the only one of them comes with the gems toolbox and that's the the contacts and false 24 K dot layer

713
01:32:10.490 --> 01:32:20.120
Ralph Haugerud: 24 K part is because the civilization what's l typing that symbols type of y'all type is set for 20 14,000 scale mapping.

714
01:32:21.020 --> 01:32:30.320
Ralph Haugerud: And if you zoomers in there doesn't change once you build a full gems database, you can recount like the symbol, based on a different map skill that will change this analogy.

715
01:32:32.540 --> 01:32:32.900
Thank you.

716
01:32:36.890 --> 01:32:40.460
Ralph Haugerud: And Stephen maybe has a question about stacking map units.

717
01:32:42.110 --> 01:32:44.240
Ralph Haugerud: That does not obey topology and.

718
01:32:45.290 --> 01:32:50.300
Ralph Haugerud: This question is an advanced gems question and I don't dare go there.

719
01:32:53.150 --> 01:33:00.710
Ralph Haugerud: it's been done, if you don't need to document well such a database in some ways, is unlikely to.

720
01:33:02.120 --> 01:33:06.740
Ralph Haugerud: pass muster it's got some problems again because mostly topological.

721
01:33:08.750 --> 01:33:15.260
Ralph Haugerud: And there are ways, you can build a multi layered map and gems putting each layer in a separate feature data set to do work.

722
01:33:15.980 --> 01:33:26.450
Ralph Haugerud: And I would suggest looking at I believe it's appendix it's a frequently asked question and appendix for in the gems documentation the talks about different ways to build layered maps and gems.

723
01:33:32.420 --> 01:33:34.880
Robert Marvinney, DACF: Right actually i'd like to ask a question Ralph.

724
01:33:37.880 --> 01:33:45.650
Robert Marvinney, DACF: i'm probably asking this from ignorance, because i've really stepped away from all my GS GIs activities and know.

725
01:33:46.370 --> 01:33:57.350
Robert Marvinney, DACF: Pretty not very much about how gems works, but I saw you spend a fair amount of time in that extra size, bringing in you know striking dip symbols.

726
01:33:58.010 --> 01:34:03.710
Robert Marvinney, DACF: And I know that my staff and others when they're out in the field they're often collecting.

727
01:34:04.250 --> 01:34:19.640
Robert Marvinney, DACF: That fabric information in into an electronic tablet of some sort and put it into a spreadsheet or database so So is there a tool that in gems allows you to kind of bulk load those into your GEO database.

728
01:34:22.520 --> 01:34:31.640
Ralph Haugerud: not particularly i've done some of that and my approach has been to write a small script that does the translation, from whatever format, the field tool works in.

729
01:34:32.240 --> 01:34:47.600
Ralph Haugerud: To the gems database The other thing you could do if you use as a collector you put your database online you download a piece of it into your tablet and you modify it, you know you basically collect gems attributes directly.

730
01:34:50.000 --> 01:34:57.530
Ralph Haugerud: I have, I tried collector several years ago and had some problems with the credit system and I don't know if I want to recommend it enough yeah.

731
01:34:57.560 --> 01:35:01.970
Robert Marvinney, DACF: Okay, so that might be a way for people who are oriented that way in the field to.

732
01:35:02.060 --> 01:35:15.110
Robert Marvinney, DACF: Yes, click directly, because you know we're trying to avoid the problem of you know, collecting it and transcribing it and putting on the map and then trying to automate it off the map those things.

733
01:35:15.200 --> 01:35:28.400
Ralph Haugerud: Oh yes, very good to solve that problem and if you've got a field software device that you find works reliably i'd love to know about it okay Come on, when i'm done back using paper field sheet and my compass and drawing lines and putting numbers next.

734
01:35:29.300 --> 01:35:30.950
Robert Marvinney, DACF: All right, okay.

735
01:35:31.070 --> 01:35:32.900
Christian Halsted: Oh i'll just jump in on that.

736
01:35:33.950 --> 01:35:37.340
Christian Halsted: I guess I should spend a little bit more time with Bob field.

737
01:35:39.680 --> 01:35:54.740
Christian Halsted: But we at ngs we are using collector and survey 123 Apps from SAP and we're using them in our GIs online as the hosting platform for the field staff and.

738
01:35:55.640 --> 01:36:06.440
Christian Halsted: Just as you described Ralph we have a we have a Python script that runs that staff can run when they get back in the office and it basically just copies the.

739
01:36:06.920 --> 01:36:14.330
Christian Halsted: Data out of the schema that sitting in rgs online and puts it in our database schema so it's.

740
01:36:15.260 --> 01:36:25.790
Christian Halsted: Pretty efficient process, it is it's a very straightforward script I think most people you know most GIs analysts, you know working in art today could put something together like that pretty quick.

741
01:36:29.570 --> 01:36:30.770
Robert Marvinney, DACF: Good okay.

742
01:36:32.690 --> 01:36:35.060
Robert Marvinney, DACF: Any other any other questions at this point.

743
01:36:40.130 --> 01:36:40.820
Robert Marvinney, DACF: alright.

744
01:36:43.160 --> 01:36:52.250
Robert Marvinney, DACF: So next is it Ralph you and Chris are going to work on discussing an example of translating an existing map is that next.

745
01:36:52.610 --> 01:36:55.850
Ralph Haugerud: Well, actually i'm just going to go through and build the non spatial tables for.

746
01:36:55.850 --> 01:36:56.600
Robert Marvinney, DACF: This okay.

747
01:36:56.900 --> 01:36:57.140
Robert Marvinney, DACF: yeah.

748
01:36:57.380 --> 01:36:58.790
Ralph Haugerud: I think that's what's up here.

749
01:36:58.970 --> 01:37:01.160
Ralph Haugerud: You some civilization let's see what happens here.

750
01:37:02.000 --> 01:37:02.420
Okay.

751
01:37:04.250 --> 01:37:05.840
Ralph Haugerud: and share that.

752
01:37:11.690 --> 01:37:20.240
we've built an empty database digitize contacts made polygons we've digitized striking dips we digitize key beds, we checked topology.

753
01:37:21.260 --> 01:37:24.020
The next step is to click non spatial tables in the map.

754
01:37:26.000 --> 01:37:27.620
Ralph Haugerud: let's go look at our recipe here.

755
01:37:31.250 --> 01:37:42.170
gems prescribes three non spatial tables other essentially internal metadata a data sources table that tells for data scribes were data comes from.

756
01:37:42.740 --> 01:37:52.190
A description of happiness table that describes the map units and a glossary that defines a number of values type values competence values us too many points in the database.

757
01:37:53.690 --> 01:38:00.140
we're not going to do the DM you that's done the next exercise but let's fill out the data sources in Gloucester table for this map.

758
01:38:03.290 --> 01:38:05.450
first thing to do is to add.

759
01:38:11.030 --> 01:38:11.750
tables.

760
01:38:14.300 --> 01:38:14.870
one.

761
01:38:16.700 --> 01:38:17.390
Excuse me.

762
01:38:21.440 --> 01:38:24.890
To the map and then let's go open.

763
01:38:27.590 --> 01:38:28.430
Open one of them.

764
01:38:30.530 --> 01:38:31.730
And the.

765
01:38:35.150 --> 01:38:38.600
table is partly filled, because the gems schema.

766
01:38:40.340 --> 01:38:48.770
uses some terms everywhere that need definition and they're they're built it's built into the database, the database, make it.

767
01:38:52.580 --> 01:38:53.270
Smaller.

768
01:38:55.490 --> 01:39:02.810
However, we know that we use some other sources for the data in this map in particular there's john wet and so far.

769
01:39:03.980 --> 01:39:04.940
So we need to.

770
01:39:06.350 --> 01:39:07.160
edit this.

771
01:39:08.720 --> 01:39:09.890
And now we can.

772
01:39:12.740 --> 01:39:13.490
Stick in.

773
01:39:14.570 --> 01:39:18.050
The source, but typing into these fields is a pain.

774
01:39:19.160 --> 01:39:24.680
Very difficult to do it accurately and well, and so what i've done is typed up.

775
01:39:29.570 --> 01:39:30.740
Some data sources.

776
01:39:32.360 --> 01:39:32.930
externally.

777
01:39:34.190 --> 01:39:35.960
And I can take this.

778
01:39:37.100 --> 01:39:42.170
I can copy it one of this field and paste in there it is.

779
01:39:44.240 --> 01:39:46.490
For data sources, especially when we digitize.

780
01:39:48.980 --> 01:40:06.110
it's nice if we include some notes about who did the digitizing plan and what, if any, they have added to the data set in a particular we've i've attribute a number of confidence values that have very little.

781
01:40:07.460 --> 01:40:11.660
definition in the source data there my judgment, naturally recorded so let's.

782
01:40:13.010 --> 01:40:13.820
copy that.

783
01:40:14.990 --> 01:40:16.670
and put that in the notes field.

784
01:40:20.690 --> 01:40:27.950
And there's a an optional field or an as needed field, the URL this report is available on the web.

785
01:40:30.620 --> 01:40:32.300
So let's put that in here.

786
01:40:35.300 --> 01:40:40.790
And we need something to call this, and one thing we could call it.

787
01:40:42.890 --> 01:40:48.020
Is data source number one it's the primary data source that works.

788
01:40:49.340 --> 01:41:03.590
any number of tokens are possible gems is set up to use very short text tokens or very long ones that are global unique identifiers, the only important thing is that within any given database these ids need to be unique.

789
01:41:08.360 --> 01:41:11.540
we're also going to stick in a few other sources.

790
01:41:12.650 --> 01:41:19.850
And i'm just gonna stick them in here for now right, so I can we're going to use the glossary of geology is a source for some definitions.

791
01:41:21.230 --> 01:41:22.070
and

792
01:41:24.260 --> 01:41:26.030
That we're going to describe here.

793
01:41:27.080 --> 01:41:34.550
we're not going to use it as is, I chose to modify some of the definitions and so this is.

794
01:41:35.630 --> 01:41:37.610
modified from glossary geology.

795
01:41:41.330 --> 01:41:43.460
And I think i'm going to stop right there, we can.

796
01:41:45.470 --> 01:41:46.250
Close this.

797
01:41:47.780 --> 01:41:51.890
save our edits and move on to the glossary table.

798
01:41:53.630 --> 01:41:56.840
And again, it comes pre populated with a couple of terms.

799
01:41:58.400 --> 01:42:02.120
We want to add some more we know we have type contact in here.

800
01:42:03.140 --> 01:42:05.420
That needs a definition when we have tight bedding.

801
01:42:08.240 --> 01:42:15.260
And my first inclination is to go to the glossary geology and get definitions for these things so let's do that.

802
01:42:16.370 --> 01:42:17.060
and

803
01:42:18.680 --> 01:42:23.690
there's a picture I took on my cell phone yesterday my trusty glossary of geology I opened to the contact.

804
01:42:26.300 --> 01:42:36.170
And I find the definition number is one that's relevant is unsatisfactorily because there's, not a single contact on this map that probably digitize that meets this definition.

805
01:42:36.830 --> 01:42:45.860
All the contacts are between rock and deposits or between deposits there, none of them that are rock to rock, so we need a different definition.

806
01:42:47.390 --> 01:42:48.350
and

807
01:42:52.640 --> 01:43:03.740
i'm really lazy so rather than write one from scratch, I went to the last nap but I worked on it took the definition of it, and there we defined a contacts, the surface of separates to map units that is not a halt.

808
01:43:19.340 --> 01:43:23.240
And the source for that was I usgs.

809
01:43:24.620 --> 01:43:28.100
si am 3443 which we're going to.

810
01:43:29.390 --> 01:43:39.680
That is a shorthand we now clearly have a need for another data source or that there and then we can go to the other thing we have bedding.

811
01:43:40.730 --> 01:43:41.270
and

812
01:43:42.530 --> 01:43:44.150
I like the glossary of geology.

813
01:43:45.770 --> 01:43:57.980
description fairly well but not quite so I modified it I also prefer to modify these definitions and as i'm concerned about copyright issues if we wholesale copy and paste out of mastery geology there's bedding.

814
01:44:05.870 --> 01:44:07.730
And that's going to be G or g.

815
01:44:09.020 --> 01:44:10.400
Fifth edition modified.

816
01:44:15.380 --> 01:44:18.050
We now have a need for new data sources entries.

817
01:44:22.700 --> 01:44:23.750
gog five m.

818
01:44:27.140 --> 01:44:28.790
We need Sim 3443.

819
01:44:30.200 --> 01:44:31.670
God fight and it's here already.

820
01:44:32.810 --> 01:44:34.400
Sim 3443.

821
01:44:35.540 --> 01:44:37.850
And a long title or long reference.

822
01:44:44.270 --> 01:44:45.740
also has a URL.

823
01:44:53.330 --> 01:44:55.670
yeah and we need the token that defines it.

824
01:45:03.650 --> 01:45:04.010
Now.

825
01:45:05.540 --> 01:45:10.190
I think we've actually got this fairly well under control.

826
01:45:11.270 --> 01:45:13.250
We filled out on spatial tables.

827
01:45:15.890 --> 01:45:18.980
we've got our spatial stuff done oh.

828
01:45:21.080 --> 01:45:25.670
We left some fields unpopulated let's go through these here those open orientation points.

829
01:45:26.690 --> 01:45:29.510
there's a bunch of points in here and.

830
01:45:32.210 --> 01:45:34.130
None of them have a confidence values.

831
01:45:35.750 --> 01:45:41.060
or a data source or additions data sources so let's step through here i'm.

832
01:45:42.800 --> 01:45:58.490
All of these things come up this map and we decided to think this map is not that well located on its own, if it were a clean scale stable 24,000 map that 24 meters would be the right answer or llc and it's not so let's use 30.

833
01:46:01.940 --> 01:46:10.040
Identity confidence I trusted john wet and plot everything that he said was betting was betting, no question, or he would have told us so.

834
01:46:12.080 --> 01:46:13.820
So that's certain.

835
01:46:18.410 --> 01:46:36.050
My experience, having used a compass for many years, and having taught field camp and having students test themselves to see how well they can measure orientations, is that a well you'll the compass can routinely to achieve two or three degrees reproducibility and if we go for five.

836
01:46:37.070 --> 01:46:39.860
we're we're, certainly including the answer here.

837
01:46:40.880 --> 01:46:41.360
On.

838
01:46:43.340 --> 01:46:53.690
plot at scale is the denominator at the scale smaller than which you shouldn't plot this thing because the symbols get too crowded this map is not crowded i'm gonna.

839
01:46:55.220 --> 01:46:57.590
i'm gonna leave this will run a script later to calculate that.

840
01:46:59.390 --> 01:47:07.790
station ID these things don't have stations map unit we're actually we could populate that right now, all of these are inside.

841
01:47:08.960 --> 01:47:10.100
unit tcs.

842
01:47:11.210 --> 01:47:19.520
More typically they're inside many units and we would intersect the orientation points feature class with the mapping apologies future class and fill out mapping that that way.

843
01:47:25.190 --> 01:47:28.430
location source is from the map, we just digitized.

844
01:47:35.840 --> 01:47:37.250
And the orientation source.

845
01:47:40.430 --> 01:47:41.120
Is the same.

846
01:47:43.760 --> 01:47:44.870
No notes on these.

847
01:47:46.580 --> 01:47:57.320
orientation points idea we're going to cap it with a script in a few minutes and PT tapers that actually we're not going to use it, it was a convenience for translating data from all the car.

848
01:47:58.430 --> 01:48:00.110
So we can say that's done.

849
01:48:01.910 --> 01:48:03.920
We can go to map, you know lines.

850
01:48:05.510 --> 01:48:07.820
And do some of the things data sources populated.

851
01:48:08.930 --> 01:48:10.040
existence confidence.

852
01:48:11.720 --> 01:48:12.500
we're good there.

853
01:48:15.260 --> 01:48:16.580
contacts and faults.

854
01:48:18.740 --> 01:48:21.650
Well, this locally, open up the contacts and bolts to attribute table.

855
01:48:24.170 --> 01:48:30.860
everyone's got a type it's coming as concealed valued as an existence confidence value identity confidence location confidence meters.

856
01:48:33.230 --> 01:48:37.610
We are good, except for the data source ID.

857
01:48:38.960 --> 01:48:42.470
And i'm going to stop here, these three lines.

858
01:48:43.490 --> 01:48:47.900
The neat line, we did not get out of john wooden's mouth so that's got to be something else.

859
01:48:59.660 --> 01:49:00.590
rest of these.

860
01:49:01.970 --> 01:49:02.600
All came.

861
01:49:04.670 --> 01:49:06.620
From which welcome for southeast.

862
01:49:10.460 --> 01:49:11.030
quad.

863
01:49:20.960 --> 01:49:28.640
And we have gone through oh Matthew nepalis what's that very confidence, nothing was queried.

864
01:49:34.340 --> 01:49:35.390
These are all certain.

865
01:49:37.790 --> 01:49:39.830
Data source ID was again.

866
01:49:52.220 --> 01:49:56.690
And again, p type as a convenience for translating from all a cart and we're not going to use it here.

867
01:49:59.720 --> 01:50:06.170
At this point, the next step is to calculate the ID values for all these features.

868
01:50:15.500 --> 01:50:18.590
Open the gyms tools go to set ID values.

869
01:50:31.190 --> 01:50:35.000
We don't want to reset our data source ids we we like what they look like.

870
01:50:44.990 --> 01:50:45.740
that's done.

871
01:50:47.450 --> 01:50:50.330
We can see what happened by opening up say one of these here.

872
01:50:52.640 --> 01:50:54.140
Over there.

873
01:50:55.370 --> 01:50:56.240
This is populated.

874
01:50:57.890 --> 01:50:59.720
And it will be that in all the tables in here.

875
01:51:01.820 --> 01:51:14.570
Now, probably we didn't get everything and typically We run the validate database script repeatedly to find out what needs polishing what little holes need filling what needs what needs fixing.

876
01:51:15.410 --> 01:51:22.640
it's not something you do just at the end of the process, but oftentimes in building the database we're going to stick in again are talking per se database.

877
01:51:24.320 --> 01:51:35.300
And let's leave it apology checks in that's as an option skip them because they can take a long time and if you're trying to figure which tables need to filling that's a nuisance.

878
01:51:35.990 --> 01:51:48.140
we're not going to delete any news source rose rose, although we could and we don't need to refresh GEO material decay that's an issue if you're working with an older database being brought up to the current version of gems.

879
01:51:52.160 --> 01:52:07.970
This script does a lot of work it's about 1000 lines of code and some things that checks twice both the Level two and Level three it brings up an answer back four levels of compliance the gym standard level one is basically your energy is with no.

880
01:52:09.020 --> 01:52:21.860
Expectations of what field names are a future class names Level two is basically, could you got your contacts and policies in your your mapping apologies to your contacts and false right level three has to be across all of your t's and dotted all of your eyes.

881
01:52:25.550 --> 01:52:31.430
And at this point we're not concerned about compliance levels were concerned about the error messages and what else needs it filling out in the database.

882
01:52:33.470 --> 01:52:34.310
Okay.

883
01:52:35.810 --> 01:52:36.860
let's close this.

884
01:52:38.690 --> 01:52:46.820
Go to the directory window that the outputs written to which is the directory that our input database was in open up the validation script.

885
01:52:49.610 --> 01:52:52.310
Since we have some problems not surprising.

886
01:52:54.020 --> 01:52:54.560
Okay.

887
01:52:55.670 --> 01:52:59.360
We have one term missing and glossary one missing data sources.

888
01:53:03.020 --> 01:53:08.000
So we didn't stick in data source to that we need need line.

889
01:53:09.980 --> 01:53:19.010
interest of sitting time I won't ask you to watch me fix all the errors identified by validate database know that typically I step through the validation report.

890
01:53:19.550 --> 01:53:34.550
fix each of the errors, I can see rerun the validation script find more errors fix those until report comes back clean at that point i'm ready to work on civilization for the BAT pick up colors record them in the DM you.

891
01:53:35.600 --> 01:53:37.790
I prefer to use the fgc.

892
01:53:39.980 --> 01:53:43.190
color set which is available online.

893
01:53:44.960 --> 01:53:46.490
Each of these colors has.

894
01:53:47.750 --> 01:53:51.830
An identifier, which was in this case, a text string which can be keyed into the DM you.

895
01:53:53.540 --> 01:53:55.880
use other symbols values also.

896
01:53:56.960 --> 01:54:05.900
If you use the FTC colors you can use the symbol, the rgb scripts to get area fill rgb values, otherwise you may have to go find that eyedropper and.

897
01:54:06.350 --> 01:54:12.530
illustrator or something like that to or use the art style manager to read the rgb values and keep those in.

898
01:54:13.340 --> 01:54:22.790
So you can use other symbols sets and if you do that you want to provide the style file with the to database and you give it to others, and you want to document with study used in your poor little better data.

899
01:54:24.260 --> 01:54:39.290
You can then run the set symbol values script which works with the fgc symbolic to set some line symbols in accord with their attributes their confidence values and the map scale so.

900
01:54:40.580 --> 01:54:49.610
If you change the map scale used to be rerun the set symbols value script in a different map scale and it will change dashed lines to continuous wants to scale smaller.

901
01:54:51.290 --> 01:54:59.780
It also will set orientation symbols and and some of those that will choose to use different symbols to getting in with the orientation confidence degrees value is.

902
01:55:00.920 --> 01:55:08.390
The mapping of type is concealed and the confidence values to symbol values is described in the file.

903
01:55:09.440 --> 01:55:20.030
Type F CDC symbol textures and the resources directory the gems toolbox, and this is that file and it's got a list of type values and.

904
01:55:21.080 --> 01:55:39.200
An FTC symbol identifier, and the some FTC symbols arranged such you can from the identifier for these certain accurate symbol calculate what the queried certain grade accurate or certain approximate or query approximate values are.

905
01:55:41.630 --> 01:55:42.260
And this.

906
01:55:43.280 --> 01:55:52.400
file can be edited to extend the list of types in the symbol and visit here, this is not a complete set ones that i've had occasion, he is.

907
01:55:56.450 --> 01:56:15.980
As you run the festival value script it has an option to set label values in Matthew nepalis by conflating the label field in the new table with the existence come identity conference field in makin points feature class and the sense in the low your script can be.

908
01:56:19.040 --> 01:56:32.030
runs on a feature data set and modifies contacts and faults orientation points geologic lines makin apologies long, and you can run it on a cross section feature data set run a correlation makin a diagram speech your data Center.

909
01:56:33.740 --> 01:56:39.470
When you've done this already your transition to presentation quality graphics and.

910
01:56:42.920 --> 01:56:44.900
want to move to a new plot file.

911
01:56:46.760 --> 01:56:49.970
So we want to save as two different xd.

912
01:56:51.680 --> 01:57:03.980
You want to change how we symbolize the contacts false layer really delete the fourfold civilization that we use for digitizing and add contacts and false as a single layer

913
01:57:05.750 --> 01:57:07.940
step through each layers and set the symbolic.

914
01:57:09.080 --> 01:57:11.990
And mostly use categories master symbols and style.

915
01:57:13.010 --> 01:57:16.910
symbol field and match it to the FTC style.

916
01:57:18.110 --> 01:57:22.010
We want to label the mapping apologies feature to us, we add a new.

917
01:57:23.060 --> 01:57:39.050
map unit polly's layer we set the symbolic to know outline no filter color so we're not going to see anything, there were a definition query to exclude units we don't want to label and you know areas that are too small, then label features, with the label field.

918
01:57:40.370 --> 01:57:55.220
If we have map units that are be pattern, we can again clone the mapping apologies layer join it to the DM you the map unit and symbolize the area full patent description and that may require some hunting defined area fills that are appropriate that description.

919
01:57:56.480 --> 01:58:04.430
We can get nicely place dip numbers by first running set plat scale values which goes to the structure symbols and looks for the ones that are.

920
01:58:05.300 --> 01:58:19.430
too close together and picks one and says don't plot, the other, and it does this by setting plot at scale number, which is the denominator of the map scale at larger than which it's okay to plot that symbol.

921
01:58:20.990 --> 01:58:38.060
And so, if you put in 500,000 that symbol plots at any scale large, of the one to 500,000 you put in 10,000 you've got to zoom in to see it once you've done that but inflammation numbers which calculates where the dip or plunged already placed.

922
01:58:39.440 --> 01:58:42.140
makes it in point and rights.

923
01:58:43.400 --> 01:58:44.720
Rights the dip number on top of it.

924
01:58:47.210 --> 01:58:49.100
And I think that's it.

925
01:58:51.290 --> 01:59:03.290
I haven't done that, for this snippet of the chocolate for se quadrangle i've turned the poly phil to be transparent, but on top of the lidar and it now looks something like a geologic map.

926
01:59:12.710 --> 01:59:14.990
Robert Marvinney, DACF: Alright well thanks for that Ralph.

927
01:59:16.640 --> 01:59:18.200
Robert Marvinney, DACF: Any questions from anybody.

928
01:59:21.410 --> 01:59:23.600
Robert Marvinney, DACF: we're right right on schedule Ralph.

929
01:59:28.730 --> 01:59:30.140
Ralph Haugerud: Is it time for a short break.

930
01:59:30.650 --> 01:59:33.860
Robert Marvinney, DACF: yeah I think we ought to take a five minute break here and.

931
01:59:35.030 --> 01:59:39.350
Robert Marvinney, DACF: Back at 3053 or six something like that folks.

932
01:59:42.080 --> 01:59:40.000
Robert Marvinney, DACF: Okay.

933
01:59:40.001 --> 01:59:44.600
Robert Marvinney, DACF: Okay, well, I guess, we could get underway again Ralph.

934
01:59:46.520 --> 01:59:48.080
Robert Marvinney, DACF: Now this section is going to be.

935
01:59:48.170 --> 01:59:51.260
Robert Marvinney, DACF: Ralph you and Chris working on.

936
01:59:52.280 --> 01:59:56.090
Robert Marvinney, DACF: translating the existing digital map that correct.

937
01:59:56.480 --> 02:00:01.850
Ralph Haugerud: yeah if Chris would want to start by saying just a little bit about what he sent me I could take it from there.

938
02:00:05.270 --> 02:00:06.890
Christian Halsted: Sure, no problem so.

939
02:00:08.480 --> 02:00:29.150
Christian Halsted: We Ralph and I decided to use the Lisbon false self quadrangle bedrock math that we published, I think, two years ago, and obviously that map was was born digital so we had a database sitting behind that math and.

940
02:00:30.230 --> 02:00:41.000
Christian Halsted: We we mean we do have a an enterprise GEO database and it is a multi quad database, so we actually did an export.

941
02:00:42.410 --> 02:00:53.210
Christian Halsted: From that and put a file GEO database, together with our raw data from all the feature classes that went into making our map and sent that to Ralph and.

942
02:00:54.530 --> 02:00:56.150
Christian Halsted: He started working on it and then.

943
02:00:56.150 --> 02:00:56.600
Ralph Haugerud: We just.

944
02:00:57.110 --> 02:00:58.160
Christian Halsted: kind of went back and forth on.

945
02:00:58.160 --> 02:01:10.490
Christian Halsted: Some questions that Ralph had and trying to translate our data and our naming conventions and our feature codes and whatnot into the gems format.

946
02:01:13.730 --> 02:01:16.820
Ralph Haugerud: Thank you, Chris Let me share my screen here.

947
02:01:20.360 --> 02:01:21.530
Ralph Haugerud: and start playing.

948
02:01:22.820 --> 02:01:39.110
Our second exercise is to translate an existing digital map and the process starts out similar to digitize an analog now need to make a plan, where they're going to transfer features and translate attributes stop and talk about it move on and on special tables.

949
02:01:42.140 --> 02:02:00.560
Chris halstead sent me planning for this course a database that's a sample of grabbed from their corporate database of the data for a single segment quadrangle in Southwestern maine, and this is what he sent me again say database lots of future classes it's the tables.

950
02:02:01.910 --> 02:02:05.360
It corresponds to a published map has been falls South quadrangle.

951
02:02:06.980 --> 02:02:18.380
over here Southwest main the map well you can't see it at the scale so let's assume yet it's got obviously a map of lots of structural data and outcrop information.

952
02:02:19.520 --> 02:02:20.780
it's kind of Title block.

953
02:02:23.030 --> 02:02:27.830
author, who did the cryptography who just he just was publication date.

954
02:02:28.700 --> 02:02:38.750
it's kind of an explanation, the map units looks very familiar it's got headings and sub headings, you know descriptions, some of which are subsidiary to other descriptions brackets to organize it.

955
02:02:39.710 --> 02:02:47.270
it's got an explanation of lines, we see that there's an antique line on the cross section only as a cross section on this kind of.

956
02:02:48.440 --> 02:02:53.720
woke me up a contact of uncertain origin, maybe it's right after contact reformed and interesting symbol.

957
02:02:54.860 --> 02:03:02.660
And lots and lots of points symbols and I would note here that some of these are unrelated they're they're about outcrops.

958
02:03:04.310 --> 02:03:10.610
Excuse me, some of them are about more about outcropping photo locations so on, and many are oriented.

959
02:03:13.010 --> 02:03:17.150
And there's a very short geology table two samples two locations.

960
02:03:18.200 --> 02:03:19.490
interpretive cross section.

961
02:03:20.660 --> 02:03:29.780
And as well in the map does explanatory text references the geologic timescale photographs and captions figures plots of structural data straight up plots and captions.

962
02:03:31.520 --> 02:03:36.290
Ralph Haugerud: With the exception of the marginal notes, most of this other stuff doesn't have already home in Champs.

963
02:03:38.090 --> 02:03:42.920
But the explanation of units explanation of symbols, the gop on table the Cross section all due.

964
02:03:44.660 --> 02:03:52.310
to capture these data in jams, we need a geologic map feature data set that is required element with mapping, a policy of contacts defaults.

965
02:03:52.850 --> 02:04:07.880
We also need as needed elements orientation points and geo json point so it's your standard gems feature classes, we probably also need an outcrop points feature class to capture all the non oriented outcrop data a photo points feature class for the photo locations.

966
02:04:08.960 --> 02:04:12.170
We need a cross section feature data set.

967
02:04:13.190 --> 02:04:21.830
With the mapping of policies and contacts and faults again standard gems features that the client access it shows in the cross section.

968
02:04:22.640 --> 02:04:36.170
needs a geologic lines feature class in the cross section that we're gonna have to put together ourselves, and we also need standard tables data sources description map units glossary and miscellaneous map information.

969
02:04:38.780 --> 02:04:50.150
So this is my recipe and i'm going to drag this off the side and do my best to follow it, but we have art map open when Michelle go toolbox and let's look at things.

970
02:04:51.890 --> 02:04:54.080
Chris very kindly pointed me at.

971
02:04:55.280 --> 02:05:02.360
A web map service that the main GS runs that makes images of their published maps available.

972
02:05:04.070 --> 02:05:10.940
Inside the GIs GEO referenced framework, and this is a very handy things and they can directly look at the database on top of the.

973
02:05:12.680 --> 02:05:24.350
mapping map image and better understand what the content, the database is i'm going to put a little bit of the database in here let's add some data we're in that GEO database and let's add contacts.

974
02:05:25.400 --> 02:05:27.920
And then rock units will start with their.

975
02:05:30.980 --> 02:05:44.300
And Oh, the Web services on top let's put on the bottom, and there we can see things nicely, we could turn this off and have just the contacts on top of the Roadmap service so i'm going to create a new.

976
02:05:45.920 --> 02:05:47.150
Open up the toolbox.

977
02:05:50.120 --> 02:05:51.500
Why is this so slow.

978
02:05:57.260 --> 02:05:58.460
For a new database.

979
02:06:00.920 --> 02:06:02.660
I want to put it in.

980
02:06:05.270 --> 02:06:06.740
No it's not where I want to put it.

981
02:06:18.380 --> 02:06:19.520
database is going to be.

982
02:06:22.970 --> 02:06:38.900
This would fall South here i'm going to copy the Special reference information and from what's in the compositional already and that's the Web map services, the Web MERCATOR I don't want that I want the ut zone 19 us by the main survey for their database.

983
02:06:40.640 --> 02:06:47.150
And we have some optional things we want to add, we need to cartographic lines, we need.

984
02:06:48.350 --> 02:06:50.360
A miscellaneous map information.

985
02:06:51.440 --> 02:06:53.030
We need orientation points.

986
02:06:55.670 --> 02:07:05.420
And we want one cross section we don't want edit tracking we don't want this, we do want to type in PT type and one standard confidence values.

987
02:07:07.310 --> 02:07:07.940
and proceed.

988
02:08:32.840 --> 02:08:33.410
it's done.

989
02:08:35.810 --> 02:08:38.960
Now, go to the catalog window.

990
02:08:40.460 --> 02:08:44.900
To load the data into this newly main database and.

991
02:08:48.680 --> 02:08:50.240
We have a geologic map.

992
02:08:52.670 --> 02:08:55.370
let's look at the bedrock eunice layer before we begin here.

993
02:08:56.840 --> 02:08:57.920
Sorry feature class.

994
02:08:59.120 --> 02:09:03.770
It has, in it, Edit tracking information that we don't need.

995
02:09:06.530 --> 02:09:12.920
Information about patterns that are on top of the polygons colors the polygons on the map unit.

996
02:09:14.600 --> 02:09:15.260
Under unit.

997
02:09:16.280 --> 02:09:16.880
and

998
02:09:17.900 --> 02:09:29.960
That looks like the information in there, we want to load unit into map unit, we want to load symbologist into symbol and we're going to ignore the symbolic overlay for the moment.

999
02:09:31.280 --> 02:09:38.240
So let's right click on MAC nepalis load load data next.

1000
02:09:40.040 --> 02:09:41.450
Go look for.

1001
02:09:44.870 --> 02:09:50.000
Our data set we're going to go for bedrock units open add next.

1002
02:09:51.650 --> 02:09:59.780
Next, and mapping it wants to have unit put in it and synergy wants to have symbol, and that is yet.

1003
02:10:05.300 --> 02:10:09.200
It looks like everything is there let's load, the new.

1004
02:10:14.510 --> 02:10:16.280
feature class into Arc.

1005
02:10:18.650 --> 02:10:25.880
and open up the attribute table, and we have mapping that we have symbol and a bunch of other attributes.

1006
02:10:26.930 --> 02:10:32.630
Looking at the map, none of these mapping of polygons or query so conference for everything.

1007
02:10:34.160 --> 02:10:34.790
is certain.

1008
02:10:43.970 --> 02:10:49.100
Everything has come from the same data source, the main database we're going to call that data source one.

1009
02:10:57.500 --> 02:10:58.430
and

1010
02:11:00.440 --> 02:11:05.660
I don't think we need to do anything else here right now.

1011
02:11:07.970 --> 02:11:13.910
We can proceed to load contacts and false let's look at those first.

1012
02:11:15.920 --> 02:11:26.240
Now, here again, all the edit tracking you don't need comments the information here, I see is in two.

1013
02:11:29.690 --> 02:11:31.130
Two fields symbolic.

1014
02:11:33.080 --> 02:11:37.280
which has values of contact dash contact dotted.

1015
02:11:38.750 --> 02:11:41.120
Contact regular and non plotting.

1016
02:11:42.200 --> 02:11:43.490
And in the draw field.

1017
02:11:44.810 --> 02:11:45.980
Which is either yes.

1018
02:11:47.840 --> 02:11:48.560
or no.

1019
02:12:00.380 --> 02:12:13.370
So let's see, I think we want to capture symbologist and when we can stop there, oh the quad name it's interesting here that some of these quads things fall in those mid fall South quad and summer shared edge.

1020
02:12:15.140 --> 02:12:16.640
To just maybe they're mad boundaries.

1021
02:12:18.050 --> 02:12:19.010
So let's load.

1022
02:12:20.150 --> 02:12:21.740
stuff into contacts and faults.

1023
02:12:27.380 --> 02:12:27.800
Sorry.

1024
02:12:35.540 --> 02:12:37.190
Next next.

1025
02:12:39.920 --> 02:12:43.310
we're going to load symbolic into l type.

1026
02:12:45.080 --> 02:12:51.770
Because we're going to use them that value to figure out what the gems attributes of type and confidence and so on are.

1027
02:12:53.510 --> 02:12:57.020
On we're not going to put anything in there and i'm going to put.

1028
02:12:58.070 --> 02:13:00.200
draw in the notes field just relax.

1029
02:13:02.360 --> 02:13:03.770
tell me what to leave type empty.

1030
02:13:05.150 --> 02:13:07.310
Next next next.

1031
02:13:10.850 --> 02:13:13.190
When you should be able to add.

1032
02:13:14.420 --> 02:13:14.930
The.

1033
02:13:19.700 --> 02:13:21.860
contacts and faults here.

1034
02:13:23.420 --> 02:13:34.820
and open the attribute table and see the type, these are all empty, but we have lt that's populated and the notes field as the roster.

1035
02:13:36.110 --> 02:13:40.520
We can say right now that all of this again is coming from data source one.

1036
02:13:43.580 --> 02:13:44.330
let's do that.

1037
02:13:46.070 --> 02:13:48.710
And I think we'll stop with that.

1038
02:13:54.980 --> 02:13:58.250
let's see what's the recipe say I do next okay.

1039
02:13:59.840 --> 02:14:00.260
um.

1040
02:14:02.690 --> 02:14:09.200
I want to go to the the non plotting lines in contacts and faults find out what they are.

1041
02:14:10.880 --> 02:14:13.220
Okay i'm back here to the contacts and faults.

1042
02:14:15.170 --> 02:14:16.790
So wrong button.

1043
02:14:18.980 --> 02:14:20.150
Open attribute table.

1044
02:14:21.620 --> 02:14:23.690
And we want to go to.

1045
02:14:25.160 --> 02:14:31.250
Contact certainly sending here the non plotting lines, the ones that aren't contacts.

1046
02:14:37.760 --> 02:14:46.280
With those and I want to zoom the selected features and sure enough there the map boundary.

1047
02:14:50.480 --> 02:14:53.270
And this line down the middle of the map which intrigues me.

1048
02:14:55.340 --> 02:14:56.480
So let's turn off.

1049
02:14:57.500 --> 02:15:12.950
Happy nepalis and turn off contacts and faults to not better eye contact, and this is that funny dash two dots dash two dots line, maybe a contact and maybe a fault so i'm going to go back to.

1050
02:15:16.070 --> 02:15:17.300
contacts and faults.

1051
02:15:18.320 --> 02:15:19.220
and find.

1052
02:15:20.600 --> 02:15:22.640
Just those two lines, I want.

1053
02:15:26.900 --> 02:15:27.350
No.

1054
02:15:29.600 --> 02:15:31.310
need to be editing to do this.

1055
02:15:33.500 --> 02:15:34.190
About one.

1056
02:15:35.540 --> 02:15:41.540
And I wanted to zoom see how much I got there's a little bit of that same line out here.

1057
02:15:43.130 --> 02:15:56.330
But I haven't gotten and that's going to disappear some zoom into far but shift and split that also and if I bring the athlete table back, we can see that it's these two lines here.

1058
02:15:58.250 --> 02:16:04.940
And i'm going to say that they aren't simply non plotting lines and at the same as others and i'm going to call them.

1059
02:16:07.010 --> 02:16:08.420
fault question mark.

1060
02:16:09.920 --> 02:16:12.200
And that better be inside double quotes or remote work.

1061
02:16:18.620 --> 02:16:22.700
And with these values from the main database somewhat modified.

1062
02:16:23.810 --> 02:16:33.080
I can now go to a gems toolbox script that uses the lt value to drive the setting of all these others.

1063
02:16:38.480 --> 02:16:43.700
So in the gems toolbox, and I want to go to attribute by key values.

1064
02:16:45.710 --> 02:16:47.930
And it might be worth looking at what this does.

1065
02:16:52.430 --> 02:17:06.890
It steps through a few of the feature classes in the geologic map feature database feature data set and for the independent field l type calculates multiple dependent fields press it's going to be type location competence meters existence competence, etc.

1066
02:17:08.030 --> 02:17:09.620
And we need to give it a database.

1067
02:17:11.000 --> 02:17:12.590
Which is the one we're working on.

1068
02:17:14.660 --> 02:17:27.230
And it means a key value file and here's a brief description of this it's a text file that describes the mapping from the independent attribute to the dependent attributes and there is a.

1069
02:17:34.010 --> 02:17:36.710
One of these in the.

1070
02:17:37.760 --> 02:17:39.590
Oh, I didn't pull it up here.

1071
02:17:42.020 --> 02:17:43.670
In the gems toolkit.

1072
02:17:45.200 --> 02:17:46.400
And the resources folder.

1073
02:17:47.750 --> 02:17:50.300
there's An example of this file.

1074
02:17:52.910 --> 02:18:02.840
is designed to rework things and contacts and bolster annotation points and it's got a very limited number of things to remap I have copied this file.

1075
02:18:04.010 --> 02:18:04.520
To.

1076
02:18:08.870 --> 02:18:10.730
My local working directory and renamed it.

1077
02:18:12.620 --> 02:18:19.670
And added stuff to it and modified it and so i've got the values.

1078
02:18:23.450 --> 02:18:23.840
Of.

1079
02:18:29.330 --> 02:18:30.800
became up the main database.

1080
02:18:31.850 --> 02:18:33.140
and the one that I invented.

1081
02:18:34.820 --> 02:18:36.230
That say that if.

1082
02:18:37.700 --> 02:18:38.420
l type.

1083
02:18:40.040 --> 02:18:43.220
Is a fault question mark then it's type.

1084
02:18:46.250 --> 02:18:56.780
Is a fault its location conference meters is 50 existence confidence is certain identity confidence is questionable and it's not concealed.

1085
02:18:58.490 --> 02:19:07.190
Similarly, if it just somebody non plotting it's a neat line we know exactly where it is because it was calculated by somebody and we know what it is we're certainly we're certainly there.

1086
02:19:09.350 --> 02:19:14.930
We can take this file we've ever save X I made some changes and.

1087
02:19:16.220 --> 02:19:16.940
figured out.

1088
02:19:19.700 --> 02:19:22.070
and run the script.

1089
02:19:24.800 --> 02:19:26.000
It tells us what it's doing.

1090
02:19:32.000 --> 02:19:35.360
And it's not finding anything and orientation points because it's empty then it's done.

1091
02:19:36.710 --> 02:19:37.610
We can open.

1092
02:19:39.740 --> 02:19:45.020
contacts and faults and look you'll see them as populated distance conference and type is populated.

1093
02:19:48.320 --> 02:19:49.730
We don't need this anymore.

1094
02:19:55.070 --> 02:20:02.540
we're now ready to load data into the Cross section feature classes let's start by adding the Cross section data from the source database.

1095
02:20:04.640 --> 02:20:09.320
To the map composition, we want lines, and we want units.

1096
02:20:10.610 --> 02:20:11.210
and

1097
02:20:13.250 --> 02:20:16.850
let's zoom glare and see where they are looks good.

1098
02:20:18.410 --> 02:20:19.700
If we look at the lines.

1099
02:20:24.800 --> 02:20:25.670
pretty much.

1100
02:20:26.960 --> 02:20:31.370
All the information appears to be in the symbologist field and that's basically the line type.

1101
02:20:32.630 --> 02:20:41.870
So we can open cross section, you can go to their load load data next select the input data.

1102
02:20:47.360 --> 02:20:54.140
And you don't want to put that there you don't want that we do want to put somebody.

1103
02:20:56.270 --> 02:20:56.990
In the light.

1104
02:21:03.590 --> 02:21:07.130
We should be able to take this now and put it in our map composition.

1105
02:21:09.530 --> 02:21:23.420
and turn these off and find we have the same lines that are new cross section eight contacts and faults feature class some of these lines don't belong in this feature class in particular it's open the table and look for.

1106
02:21:26.540 --> 02:21:31.670
sort of sending an anticlimax this which does not participate in.

1107
02:21:32.930 --> 02:21:38.180
The mapping topology that should be in a different feature class well.

1108
02:21:42.980 --> 02:21:47.090
And we need to select this by from.

1109
02:21:48.440 --> 02:21:50.390
Cross section, a context in the faults.

1110
02:21:52.190 --> 02:21:54.830
Line type equals get unique values.

1111
02:21:58.580 --> 02:22:03.500
On a selected, we should be able now to export this.

1112
02:22:04.520 --> 02:22:05.630
selected features.

1113
02:22:07.370 --> 02:22:13.490
And let's make sure we're in the same right place take three Lisbon Paul South cross section a.

1114
02:22:20.630 --> 02:22:21.320
lines.

1115
02:22:23.960 --> 02:22:35.480
Yes, if we turn off contacts and false and look at geologic like it's in there, good we can go back to contacts and faults and go to the selected feature let's see.

1116
02:22:37.160 --> 02:22:38.630
edit this start editing.

1117
02:22:40.940 --> 02:22:42.170
and delete it.

1118
02:22:44.270 --> 02:22:48.500
Now geologic lines future classes one line, and we also have.

1119
02:22:49.850 --> 02:23:05.600
These lines in here that are the elevation ticks on the cross section which are kind of line that does not perspective topology either, and they really ought to be in a cartographic lines feature class in the cross section so i'm selecting them.

1120
02:23:15.620 --> 02:23:17.810
I want to label them something different, so I can.

1121
02:23:27.050 --> 02:23:29.300
Contact regular but maybe.

1122
02:23:34.190 --> 02:23:35.150
elevation tick.

1123
02:23:39.200 --> 02:23:42.590
Okay, say that it's stop editing.

1124
02:23:44.420 --> 02:23:48.800
select by attributes and we want to select one a clear this one.

1125
02:23:58.220 --> 02:24:01.520
i've selected these want to export those.

1126
02:24:02.780 --> 02:24:03.950
Data export data.

1127
02:24:05.750 --> 02:24:08.180
And again i'm.

1128
02:24:25.430 --> 02:24:27.320
hey there there if we turn off.

1129
02:24:28.730 --> 02:24:30.020
The geologic lines.

1130
02:24:37.100 --> 02:24:38.240
We still see it in here.

1131
02:24:41.360 --> 02:24:44.060
We can go back now to the contacts and faults.

1132
02:24:46.250 --> 02:24:48.290
feature class and.

1133
02:24:50.090 --> 02:24:50.990
The attribute table.

1134
02:24:52.280 --> 02:24:54.980
And we have these selected and delete them.

1135
02:24:57.110 --> 02:24:58.370
Rest the lines are still there.

1136
02:24:59.750 --> 02:25:11.120
If we turn off the car gathered lines could there God, one could argue that these extensions to the side box are also karthik lines but they're the same kind of line is this here, which is neat line.

1137
02:25:11.690 --> 02:25:16.940
and participates in the map unit polygons and contacts and faults topology so i'm going to leave that in there.

1138
02:25:19.460 --> 02:25:25.220
we've got some cleanup to do let's go into here now and.

1139
02:25:31.940 --> 02:25:34.490
let's see, we have a fighting Gray line that's thin.

1140
02:25:35.870 --> 02:25:40.730
That is, I suspect the ground surface so let's.

1141
02:25:42.980 --> 02:25:43.670
call that.

1142
02:25:45.680 --> 02:25:46.760
Round surface for the type.

1143
02:25:47.870 --> 02:25:48.230
it's.

1144
02:25:51.230 --> 02:25:58.070
not concealed and we know where it is within a few feet this map has a 10 foot contra hon.

1145
02:25:59.300 --> 02:26:10.190
us just standard is that a total Matthew she will read elevations within one third or contractor bowl which would be three and a third feet that's about a meter that's our location carpets meters.

1146
02:26:11.720 --> 02:26:14.090
On a clear the selection.

1147
02:26:15.800 --> 02:26:18.020
Every line on here is not concealed.

1148
02:26:19.760 --> 02:26:20.780
So we can say.

1149
02:26:26.690 --> 02:26:28.040
Most of these lines.

1150
02:26:33.980 --> 02:26:35.900
With the exception of the one who just labeled.

1151
02:26:37.940 --> 02:26:48.860
We don't really know how well look here they are we know where they are at the ground surface where they intersect the map line but up in the air down in the ground don't know the civilization on the.

1152
02:26:49.880 --> 02:27:00.230
source map Pluto does not attempt to say how well located they are instead the lines in the air eroded away or dashed lines below ground or continuous so i'm going to say we don't know.

1153
02:27:01.040 --> 02:27:08.180
What location conference meter is meters here is and for numeric fields, a good no value is minus nine or minus 999.

1154
02:27:16.970 --> 02:27:19.790
We know where every one of these.

1155
02:27:21.140 --> 02:27:22.220
That it exists.

1156
02:27:30.980 --> 02:27:41.780
And we're pretty sure the identity of nearly every line on here, with one exception, so let's do this, then go to the exception, this is our line and two dots, this is the.

1157
02:27:44.660 --> 02:27:49.220
line that may be lines that may be false or maybe contacts and so those.

1158
02:27:50.450 --> 02:27:53.270
Well, we can use this way here, those are questionable.

1159
02:27:56.810 --> 02:28:00.920
And those have an l type we're using dimension here that their.

1160
02:28:02.060 --> 02:28:04.700
main part of the map, we call them false question.

1161
02:28:10.640 --> 02:28:15.200
And everything on this map is from data source number one on this cross section.

1162
02:28:20.600 --> 02:28:21.860
What else can we say here.

1163
02:28:23.090 --> 02:28:25.220
We need some symbols.

1164
02:28:29.630 --> 02:28:30.920
And i'm here.

1165
02:28:35.150 --> 02:28:36.800
The dashed lines.

1166
02:28:40.430 --> 02:28:48.890
I happen to know in my head what the symbol for a dash contact is in the fgc symbol said simply implement by the jsc.

1167
02:28:56.000 --> 02:28:56.870
These.

1168
02:29:02.360 --> 02:29:02.990
Are.

1169
02:29:04.100 --> 02:29:05.300
Continuous lines.

1170
02:29:10.430 --> 02:29:12.110
On the ground, surface we.

1171
02:29:14.600 --> 02:29:17.660
don't know what the surface, with the symbol is i'm going to call it, this for now.

1172
02:29:19.520 --> 02:29:20.390
These lines.

1173
02:29:21.410 --> 02:29:25.580
Summer dash some or not that's the below ground one it's solid.

1174
02:29:26.660 --> 02:29:32.030
I believe that's a 2.1 Point two.

1175
02:29:34.640 --> 02:29:35.690
And I think.

1176
02:29:49.340 --> 02:29:50.420
Say that it's.

1177
02:29:52.370 --> 02:29:53.600
let's see if we got this right.

1178
02:29:56.510 --> 02:29:58.610
let's go to properties.

1179
02:30:00.200 --> 02:30:10.460
Symbolic categories match the symbols in a style use the symbol field match to the FTC Jesse and.

1180
02:30:13.730 --> 02:30:14.450
Alice pretty good.

1181
02:30:15.620 --> 02:30:16.580
So we wanted to get.

1182
02:30:18.530 --> 02:30:19.460
And then, if we add.

1183
02:30:22.010 --> 02:30:24.200
cartographic lines geologic lines.

1184
02:30:27.230 --> 02:30:28.010
we're in good shape.

1185
02:30:29.090 --> 02:30:32.960
We also have the Cross section polly's to add.

1186
02:30:34.160 --> 02:30:35.930
And let's look at the source material.

1187
02:30:38.930 --> 02:30:39.590
We have.

1188
02:30:41.840 --> 02:30:44.150
unit missing biology.

1189
02:30:46.580 --> 02:30:47.600
So let's.

1190
02:30:48.890 --> 02:30:49.820
Go back to.

1191
02:30:51.740 --> 02:30:54.440
Cross section a nappy nepalis.

1192
02:30:55.580 --> 02:31:02.270
load load data next input data is cross section units open.

1193
02:31:03.890 --> 02:31:05.660
Next next.

1194
02:31:07.970 --> 02:31:12.050
Symbolic it's symbolic EG and map unit gets unit.

1195
02:31:17.840 --> 02:31:18.800
that's done.

1196
02:31:22.640 --> 02:31:25.130
We should do sorry I forgot to add that, to the composition.

1197
02:31:31.370 --> 02:31:32.300
Remove.

1198
02:31:35.120 --> 02:31:37.460
We can open this go to symbolic.

1199
02:31:38.600 --> 02:31:45.170
categories bashes symbols in the style use the symbol field let's match to the main.

1200
02:31:46.250 --> 02:31:47.030
GS.

1201
02:31:48.410 --> 02:31:53.330
And it works at least we get answers and it looks about right.

1202
02:31:55.580 --> 02:31:57.590
got a few things to clean up in here.

1203
02:31:59.210 --> 02:32:05.000
you'll in no queries in here everything appears to be certain as to what its identity is.

1204
02:32:10.280 --> 02:32:12.620
Everything came from data source number one.

1205
02:32:20.030 --> 02:32:20.840
and

1206
02:32:22.790 --> 02:32:23.570
I think.

1207
02:32:25.820 --> 02:32:26.360
that's it.

1208
02:32:28.130 --> 02:32:29.030
So we've loaded.

1209
02:32:30.680 --> 02:32:32.270
The future feature classes in.

1210
02:32:33.860 --> 02:32:39.680
The geologic map and the Cross section feature datasets, with the exception of her point Dale and we're going to stop right here.

1211
02:32:51.890 --> 02:32:57.020
Ralph Haugerud: i've got about 10 or 12 minutes more on point data.

1212
02:32:58.370 --> 02:33:02.750
Ralph Haugerud: And the non spatial tables, but if there are questions now we happy to address them.

1213
02:33:05.810 --> 02:33:12.170
Robert Marvinney, DACF: We don't see anything in the chat right now somebody has a question just go ahead and unmute and ask it.

1214
02:33:18.290 --> 02:33:35.570
Christian Halsted: A Ralph something that we've had considerable discussion about in maine is trying to translate our colors and are symbolic to the FTC standard and.

1215
02:33:37.610 --> 02:33:41.720
Christian Halsted: You know geologists are pretty attached to colors especially better archaeologists.

1216
02:33:43.400 --> 02:33:44.270
So what we've.

1217
02:33:48.530 --> 02:33:50.960
Christian Halsted: What we've decided to do is.

1218
02:33:52.130 --> 02:34:00.170
Christian Halsted: Create we've created a sort of an internal crosswalk so we have we have our MDS color and you know we've matched to the closest.

1219
02:34:01.430 --> 02:34:07.910
Christian Halsted: FTC matching color and some cases as an exact match some cases it's you know a little bit off.

1220
02:34:08.990 --> 02:34:12.350
Christian Halsted: We actually decided that we would put a custom field.

1221
02:34:14.120 --> 02:34:17.840
Christian Halsted: into the math unit polly's that would have.

1222
02:34:19.010 --> 02:34:26.000
Christian Halsted: The symbolic from our database and we would use the symbol field, we will populate that with the FTC value.

1223
02:34:26.690 --> 02:34:41.600
Christian Halsted: And then we would just make sure that our style set our MPs styles that included in the final submission what's your take on that did did we did we create more work for ourselves, did we add confusion.

1224
02:34:42.800 --> 02:34:45.860
Christian Halsted: Was that a good idea or somewhere along that spectrum.

1225
02:34:46.760 --> 02:34:49.580
Ralph Haugerud: I think you're doing fine my sympathies are completely with you.

1226
02:34:51.320 --> 02:35:04.640
Ralph Haugerud: It was an eye opener one day to realize that I just been part of three PhDs in a corner, for the last half an hour arguing over a certain shade of pink for a futon and thinking about the salary costs that decision, but we all care very much.

1227
02:35:06.350 --> 02:35:14.390
Ralph Haugerud: I actually well as a as a good number of MGM db I think it's pretty helpful if we all use the FTC.

1228
02:35:15.710 --> 02:35:27.020
Ralph Haugerud: Simple set that makes life a lot simpler, I personally don't think in those colors and I learned map color in HST space and used to picking out just whatever numbers work for me.

1229
02:35:28.460 --> 02:35:41.720
Ralph Haugerud: And i've had a couple of raging battles with usgs pubs over those colors and i've lost every time and so i've given up and I now work in the FTC colors, even though they have our first my own, they are not my first choice.

1230
02:35:42.830 --> 02:35:46.400
Ralph Haugerud: I think carrying two sets of similar values is a very reasonable compromise.

1231
02:35:47.960 --> 02:35:58.790
David Soller: This is Dave I agree with that, when we built the FTC standard, the focus mainly on the on the line and points and biology, with the colors recommended.

1232
02:35:59.840 --> 02:36:09.350
David Soller: So I don't feel nearly like like you I don't feel nearly as strongly about adherence to to the colors for the FTC scattered, as I do about the symbols.

1233
02:36:15.260 --> 02:36:19.520
Ralph Haugerud: should also notice, especially for the line and point markers symbols.

1234
02:36:21.230 --> 02:36:28.700
Ralph Haugerud: When we put together nc GMP oh nine we understood that people were not going to be totally happy with the symbol set, but things didn't work for them.

1235
02:36:29.150 --> 02:36:39.200
Ralph Haugerud: And we raised the possibility of using a symbol in appropriately, this is the marker you want, but it's not put the concept that it's attached to in the CDC guide.

1236
02:36:39.800 --> 02:36:49.850
Ralph Haugerud: And there's actually a gems define table called repurpose symbols to document, those that repurchasing of symbols most X we'd like to find out where the fgc symbol sets not working.

1237
02:36:52.430 --> 02:36:52.550
well.

1238
02:36:54.710 --> 02:36:56.090
Ralph Haugerud: David you want to add to that.

1239
02:36:58.130 --> 02:37:14.870
David Soller: No, I, I think that was a you know, an excellent idea to to allow people to repurpose symbols that was encouraged in the FTC standard, but it was buried so far on the documentation that I doubt anyone saw it yeah Oh, it was good idea to highlight it and gems.

1240
02:37:15.380 --> 02:37:24.920
Ralph Haugerud: Okay sounds like oh one of the things, some of you may have noticed, I did, for the first time, just now, watching this, I made a mistake in the cross section lines.

1241
02:37:26.000 --> 02:37:33.980
Ralph Haugerud: I failed to pull out the neat lines and label them separately from not contacts right now they're in the database as contacts regular.

1242
02:37:34.460 --> 02:37:43.160
Ralph Haugerud: And they aren't contacts there exactly located because we just chose to put them there and then the lines around the Cross section box and should have a different type value.

1243
02:37:45.470 --> 02:37:46.310
Ralph Haugerud: let's see if I can.

1244
02:37:48.680 --> 02:37:51.350
Ralph Haugerud: let's talk about the Jews and non specialty.

1245
02:37:56.000 --> 02:37:58.010
Ralph Haugerud: Okay share my screen.

1246
02:38:01.190 --> 02:38:02.000
Ralph Haugerud: share.

1247
02:38:06.950 --> 02:38:07.340
Its.

1248
02:38:08.480 --> 02:38:19.340
First point features, the main database is fully normalized and optimized for photography point attributes are spread across three tables observation symbols locations and inclusion values.

1249
02:38:20.540 --> 02:38:27.740
This is because, in some cases there's more than one observation of the location, the separate tables and in many observation to one location relation.

1250
02:38:28.250 --> 02:38:41.150
is the best way to store these data allows for the most precise editing with the least possibility for the schema also allows for exact positioning symbols for observations and fully ation some joints etc.

1251
02:38:42.350 --> 02:38:49.370
And in the database, the oriented features features litigation attitudes and not oriented features like pigmented outcrops observations.

1252
02:38:50.060 --> 02:39:02.750
are in the same set of tables gems is not fully normalized each observation of a joint fully ation are betting carries its location and if you've made more than one observation that station for locations are repeated.

1253
02:39:03.830 --> 02:39:11.720
To translate the main database into gems was complicated, but I will not take you through all of it but here's the recipe I use.

1254
02:39:13.070 --> 02:39:22.820
Basically, I took the observations feature class and add of the fields, from the other feature classes to it, I added X, Y values to that.

1255
02:39:23.570 --> 02:39:34.190
location feature class I joined the observation that your class location feature class and transfer the field values, including the X, Y locations same thing for the feature class see.

1256
02:39:35.030 --> 02:39:44.060
I loaded the then the feature class a that's been modified as X, Y data using the point excellent point why from the attics white tool.

1257
02:39:44.540 --> 02:39:54.470
And then export that as a point feature class D and point feature class and this had the virtue of basically turning one observation location into many instances of the same thing.

1258
02:39:55.490 --> 02:40:05.090
I can then load feature class D into orientation points I ran it by key values to translate the main types to jumps types data source ids and confidence values.

1259
02:40:05.600 --> 02:40:20.840
I ran set symbol is to calculate symbols and I said ID values, then I selected and copied the non Korean features from orientation points and outcrop points and deleted them and then I validated the database and fixed a bunch of stuff enough.

1260
02:40:22.460 --> 02:40:33.800
Non spatial tables were still kind of fill out data sources, the glossary miscellaneous map information and the CMU and the basic problem here, as most of you know, is the editing tabular text in Arc map is awful.

1261
02:40:35.150 --> 02:40:50.510
It works, a little better to edit your tablet texts in excel and load the excel tables and Arc nap very smooth process but xml box and large fields, here we description field is not transcripts come across this blog and you can look into that.

1262
02:40:51.860 --> 02:41:06.350
The solution is very straightforward I built tables and word I copy paste them into excel I saved them a csv and the csv file loads directly into an Arc table with no problems glossary.

1263
02:41:07.550 --> 02:41:13.640
sentence map information data sources are pretty easy to do that away description a map units needs a little more discussion.

1264
02:41:14.660 --> 02:41:18.590
let's start with the published map which has an explanation of map units in the legend.

1265
02:41:19.490 --> 02:41:36.620
Such an explanation is an essential part of any geologic map it's rare that a map user can under the expected understand without some sort of guide what PG or C D G is these explanations are fairly formalized each element of the description has.

1266
02:41:38.300 --> 02:41:38.900
A name.

1267
02:41:40.520 --> 02:41:42.290
A description descriptive text.

1268
02:41:43.640 --> 02:41:53.870
A label some sort of text format and text the plot, and on top of the Polygon on the map and assemble which here, in this case it is a salmon color with random great dashes.

1269
02:41:54.320 --> 02:42:05.360
These things go into the DM new table, we need a key to tie these elements back to makkah nepalis name doesn't work as a key because it may not be unique there two names of grant in this table.

1270
02:42:06.290 --> 02:42:13.310
it's hard to enter a color fill the color salmon keyboard into the BAT Peter Paul a stable so symbolism work.

1271
02:42:14.030 --> 02:42:24.920
labeled as a poor choice here, it would work fine, but in many cases we use special characters, for example, up carrot for the run together tr and formatting instructions like make this lowercase.

1272
02:42:25.550 --> 02:42:37.280
to drive the labeling that are hard to type in hard to read, so we invent another field, which we call mapping so short plain ascii token in this case ctg.

1273
02:42:37.760 --> 02:42:44.300
and use that to label the magnet police and tie them to the relevant row in the search the mappings table describes what those policies are.

1274
02:42:46.760 --> 02:42:54.320
The explanations are maps are typically strongly hierarchical this case we have stratified locks is the first order heading.

1275
02:42:55.070 --> 02:43:04.280
underneath that is first child as a parent as a child is the vast number of group bracket which is parent to sleep or in addition question mark.

1276
02:43:04.880 --> 02:43:14.330
Which is parents have vessel broke group undifferentiated so it's a heading to heading of a kind the heading, this is a description of map unit paragraph style.

1277
02:43:14.840 --> 02:43:23.300
And it's of the first order and its parent to for description, the mapping and paragraph styles, the second word shown by the indentation.

1278
02:43:25.310 --> 02:43:30.920
hierarchy in this explanation is shown by font and by indentation and.

1279
02:43:31.760 --> 02:43:44.570
Not all maps use the same set of fonts and invitation brackets appendix three in the gym specification has several examples that might make it a little unclear how to read hierarchy, or how we do the hierarchy from these explanations.

1280
02:43:46.040 --> 02:44:02.900
Well, in gyms we described the hierarchy, with two fields two attributes one is the hierarchy or HQ, which is a tech string of numbers and separate years and the other is a paragraph style, which is also a text string and let's go through this.

1281
02:44:04.190 --> 02:44:19.400
In the D new table headings get their own road, so the first row is intrusive rocks second row is permian the third row is granted permission as a child intrusive rocks and grants a child of permian, so this is one, this is one dash one dash one dash one.

1282
02:44:20.810 --> 02:44:31.070
And i've gone through here and assigned HQ values to every feature, nothing is stratified rocks this bracket here is the first child of stratify rocks this brackets, the second child.

1283
02:44:32.300 --> 02:44:38.750
That we were to take our DNA new table and sorted, for example on name vassal bro group or on.

1284
02:44:40.160 --> 02:44:48.380
map your sob you would get an order that wouldn't affect us at all if we resort on the hierarchy key things go back into order.

1285
02:44:48.950 --> 02:44:55.100
In some dn us there are ambiguities about whether a row is meant to be treated.

1286
02:44:55.880 --> 02:45:12.140
As a heading or as a map, you know some maps us mapping those headings, so this is uncertain, so we reinforce the hierarchy and resolve these ambiguities a recording paragraph style, and these are example values paragraph style values, need to be defined in the glossary.

1287
02:45:13.190 --> 02:45:26.060
So let's go look at the explanation of units on the Lisbon fall South BAP, this is a close up, we can go in here and grab the description text.

1288
02:45:30.860 --> 02:45:37.130
And copy it and bring in a word, document and copy and paste that description text.

1289
02:45:38.690 --> 02:45:39.620
And we get this.

1290
02:45:40.910 --> 02:45:42.560
And, with a little bit of hand editing.

1291
02:45:43.610 --> 02:45:47.300
We can translate that into this, which is our map your description.

1292
02:45:48.950 --> 02:46:08.090
We can take this text here and paste it into a table we built in word and here is that same text and add the other elements, but I shared the new to this and I need to make this a little smaller So you can see, and i've done this for every unit every heading.

1293
02:46:10.040 --> 02:46:11.180
And every bracket.

1294
02:46:12.350 --> 02:46:13.790
In the explanation of units.

1295
02:46:16.010 --> 02:46:24.200
The color values I read off of the bedrock units table in the map database Chris hall said Kenny supplied the main.

1296
02:46:24.500 --> 02:46:42.830
style to me from that I was able to go into the windows file manager and read out the rgb values for each those colors and enter those and I put in a verbal description of the patterns on some of the units building this table here took about an hour all told not too bad.

1297
02:46:43.850 --> 02:46:44.780
That point.

1298
02:46:47.570 --> 02:46:48.860
I can copy the table.

1299
02:46:50.330 --> 02:46:51.050
Control see.

1300
02:46:53.330 --> 02:46:54.530
and go to.

1301
02:46:57.020 --> 02:47:06.170
excel control V there's a table with long text descriptions and I can file save as.

1302
02:47:07.430 --> 02:47:07.940
and

1303
02:47:09.230 --> 02:47:13.100
I don't want to save this glossary I want to save this as a.

1304
02:47:15.680 --> 02:47:23.000
DM you and actually already done this already was been doing you ut of eight and save.

1305
02:47:24.020 --> 02:47:25.850
I can place it okay.

1306
02:47:27.170 --> 02:47:29.570
And I want just the only stack that you don't that's fine.

1307
02:47:32.270 --> 02:47:34.730
clothes word close this.

1308
02:47:37.370 --> 02:47:42.320
And I can go back to map composition open catalog.

1309
02:47:44.960 --> 02:47:55.130
and open my database i've been building go to the CMU and load load data next navigate to.

1310
02:47:57.140 --> 02:48:02.510
find my csv file open add next next.

1311
02:48:03.620 --> 02:48:06.740
All the fields map appropriately next.

1312
02:48:10.010 --> 02:48:11.840
And if I open this up.

1313
02:48:12.920 --> 02:48:24.920
there's my DNA and it has the long descriptions in it at this point we have nearly all the substance of the main database Elizabeth falls South quadrangle in gems.

1314
02:48:25.340 --> 02:48:35.750
there's still cleanup work to do, I need to run validate database and and fixed odds and ends a few fields need renaming and so on i've also failed to transfer.

1315
02:48:36.680 --> 02:48:44.780
build feature classes for photo points and for geodon points, and when I did this, I didn't add glossary definitions for the.

1316
02:48:45.290 --> 02:48:56.900
oriented endpoint feature types, the main database, but I got nearly complete database that I was then able to package up and send it to Evan and I think he's going to take it from here, thank you.

1317
02:48:59.660 --> 02:49:02.630
let's talk about points features and nonfiction tables.

1318
02:49:07.070 --> 02:49:12.440
Robert Marvinney, DACF: Okay, great thanks Ralph I don't know if anybody has any questions right now.

1319
02:49:16.790 --> 02:49:22.760
Robert Marvinney, DACF: Okay, not seeing any so Evan you're going to talk about validation is that right.

1320
02:49:24.830 --> 02:49:28.820
Evan Thoms: I think, because ralph's already shown it i'm not going to go into it.

1321
02:49:28.850 --> 02:49:33.230
Evan Thoms: In detail i'll talk about the geologic names check tool and and I also want to show.

1322
02:49:35.030 --> 02:49:44.210
Evan Thoms: Some other steps that you might be preparing to take at this point of what we call what you what you what you might call finalizing the database getting it ready for submission.

1323
02:49:45.650 --> 02:49:46.100
Robert Marvinney, DACF: Right.

1324
02:49:46.520 --> 02:49:48.530
Evan Thoms: Okay let's see how I can mention.

1325
02:49:56.240 --> 02:49:57.110
Evan Thoms: Alright, so.

1326
02:49:58.730 --> 02:50:10.130
Evan Thoms: To talk about this last step of getting ready to data getting the database ready i'm going to go to the wiki we maintain at the gems resources github repository.

1327
02:50:11.300 --> 02:50:14.480
Evan Thoms: open a web browser and search for usgs gems.

1328
02:50:15.590 --> 02:50:15.710
Evan Thoms: It.

1329
02:50:17.690 --> 02:50:24.170
Evan Thoms: won't probably won't see the gems resources it near the top of the results least until people start searching.

1330
02:50:25.610 --> 02:50:33.830
Evan Thoms: But you can go to either of the repositories for the tools APP or curious pro repository.

1331
02:50:36.410 --> 02:50:49.160
Evan Thoms: And at the top of the readme there is a badge called gems wiki there's also a patch to go directly to the get to the gems resources repository but i'm gonna jump over to the wiki itself.

1332
02:50:51.890 --> 02:50:56.390
Evan Thoms: So this wiki is living at the gems resources repository.

1333
02:50:58.070 --> 02:51:07.190
Evan Thoms: And I want to point out here a couple things so one is that all the tools have documentation here, you can go to gems tools documentation and there's a.

1334
02:51:07.700 --> 02:51:17.900
Evan Thoms: table that lists all the tools maintained in the repositories and the tools are categorized categorized according to the phase or phases of a typical workflow where they're intended to be used.

1335
02:51:18.710 --> 02:51:26.930
Evan Thoms: So we've been through the create and Edit database phase we've seen the cartography phase and we're we're getting into this finalized database phase.

1336
02:51:28.670 --> 02:51:29.060
Evan Thoms: and

1337
02:51:32.000 --> 02:51:37.340
Evan Thoms: here's a link to the validate database documentation, with some of these rules that we've already seen.

1338
02:51:41.270 --> 02:51:48.260
Evan Thoms: So let's see to back up, there is also a page last step to finalize database phase.

1339
02:51:49.970 --> 02:51:57.290
Evan Thoms: And so, as you get here, you might you might look at this validate database that tool bring the value database tool is one of six steps.

1340
02:51:57.920 --> 02:52:09.590
Evan Thoms: That we recommend you take in this order as you're getting a database ready for submission either to state map that map map or just having it confirmed as a gems compliant database.

1341
02:52:11.720 --> 02:52:12.110
Evan Thoms: So.

1342
02:52:13.520 --> 02:52:24.890
Evan Thoms: After running the value database tool and getting your database, up to a level three compliance there's one more step and that is doing a geologic names review.

1343
02:52:25.550 --> 02:52:34.100
Evan Thoms: So what does that it sounds like there's some people on the course who are not familiar with geologic name for you or geologic nomenclature.

1344
02:52:35.360 --> 02:52:43.430
Evan Thoms: So doing a geologic names review is checking to make sure that all of the map unit names that are used in the database.

1345
02:52:44.510 --> 02:52:54.770
Evan Thoms: Are following the rules for the naming of strata graphic nomenclature as spelled out by the North American strata graphic code, so that wasn't what yeah that's a mouthful.

1346
02:52:56.540 --> 02:53:06.770
Evan Thoms: Many of you are no doubt aware that there is a North American Commission Australia graphic nomenclature, which controls how map units are named and recognized.

1347
02:53:09.230 --> 02:53:17.450
Evan Thoms: And so geologic names review is just making sure that all the net new names are following the rules as spelled out in this document for the naming of happiness.

1348
02:53:18.620 --> 02:53:35.660
Evan Thoms: But the first step is not to go rule by rule and name by name and double check that everything matches up because the rules are a little complicated and you would not be faulted for not knowing them off the top your head, the first step towards making sure that your names.

1349
02:53:37.670 --> 02:53:42.380
Evan Thoms: And look them up in the US geological names lexicon, which is the big book.

1350
02:53:43.400 --> 02:53:48.200
Evan Thoms: of mapping of names in North America and starting in the US and US territories.

1351
02:53:49.820 --> 02:53:56.000
Evan Thoms: And so i'm going to show an example of doing this manually first so you get an idea of the results and things you check.

1352
02:53:56.960 --> 02:54:06.950
Evan Thoms: And that will help explain the design and outputs up the geologic names check tool, so the lexicon currently exists as a database called GEO lex.

1353
02:54:07.850 --> 02:54:17.660
Evan Thoms: And there's a nice website, you can go to to look a name up in, and so, for example, i'm just going to go down to the unit name here and enter Dakota one of the suggestions.

1354
02:54:21.770 --> 02:54:22.040
Evan Thoms: and

1355
02:54:23.180 --> 02:54:30.590
Evan Thoms: it's going to look at the results at the top of this, page under here units unit names, starting with the.

1356
02:54:32.900 --> 02:54:33.830
Evan Thoms: want to point out that.

1357
02:54:35.930 --> 02:54:55.250
Evan Thoms: Formal strata graphic unit names are compound that is there two parts there's a geographic term in this case Dakota followed by either a theology term sandstone a conglomerate or a strata graphic rank term we've got formation here and a group.

1358
02:54:56.720 --> 02:55:07.670
Evan Thoms: In jira lacks the first part of that compound name the geographic part that's recorded as a name that is a God next name.

1359
02:55:09.050 --> 02:55:19.100
Evan Thoms: Every name has one or more associated usages with it so usage is the compound name together because sandstone to put a formation Dakota conglomerate.

1360
02:55:20.330 --> 02:55:28.910
Evan Thoms: And i'm only kind of laboring this point because i'm just making I just want to make it clear that the way God uses the term name.

1361
02:55:29.450 --> 02:55:45.140
Evan Thoms: is not exactly the way that we use the term name in a descriptive happiness table in a chance to database if you're doing a geologic names with me you'd be comparing the name from CMU with a God likes usage.

1362
02:55:46.370 --> 02:56:01.970
Evan Thoms: So that's, the first thing you compare the gx usage, with the map unit name you compare the extent the area in which that name is recognized and used, and then you also check the age and if those three things match up and you're good with that name and you move on to the next one.

1363
02:56:04.550 --> 02:56:13.550
Evan Thoms: i'll, let me point out that you may have noticed, there are some non letter characters in these strings or asterisks and for some of these other usages down here there are.

1364
02:56:15.020 --> 02:56:17.150
Evan Thoms: Well, not finding any, but there are other.

1365
02:56:18.590 --> 02:56:22.520
Evan Thoms: Non letter characters described at the very bottom and scroll down.

1366
02:56:23.750 --> 02:56:31.970
Evan Thoms: It gives some attributes to the usage, so an asterisk, for instance, indicates that the usage is was published by usps authors.

1367
02:56:33.500 --> 02:56:41.780
Evan Thoms: Obsolete terms are also recorded in jira lex as denoted by no current usage, or you will see this little dagger symbol.

1368
02:56:43.910 --> 02:56:51.590
Evan Thoms: And slashes indicate, but a slash before name indicates, doesn't conform to to the nomenclature guidelines, so there are these.

1369
02:56:52.340 --> 02:57:03.500
Evan Thoms: Non letter characters that are thrown into the strings to give you more information about how that usage is used and those characters also appear in the results from the geologic needs check tool.

1370
02:57:06.740 --> 02:57:11.360
Evan Thoms: So let's go to our GIs pro and talk about.

1371
02:57:14.030 --> 02:57:17.090
Evan Thoms: The DM you and the structure of the DM you before you run it through the tool.

1372
02:57:18.830 --> 02:57:26.690
Evan Thoms: If you have a level three gems compliant GEO database then you're set your DM you we know it's good that you can start using the tool.

1373
02:57:27.890 --> 02:57:48.260
Evan Thoms: But you don't have to wait until that point you don't have to have a fully gems compliant the new table, you can start this process before you reach that level the tool just needs a few of the fields we've talked about in a chance required a chance compliant do we need hierarchy.

1374
02:57:49.460 --> 02:57:51.140
Evan Thoms: Now unit name.

1375
02:57:52.460 --> 02:57:54.650
Evan Thoms: full name and age, but no others.

1376
02:57:55.760 --> 02:58:06.080
Evan Thoms: And in fact you don't have to be working in a in a table in a file to database, you can supply the tool with an excel spreadsheet csv def.

1377
02:58:07.610 --> 02:58:09.650
Evan Thoms: Most any kind of table actually.

1378
02:58:12.290 --> 02:58:19.310
Evan Thoms: hierarchy is just for sorry because we want the results to appear in the same order that they would appear in a printed gmu or listen nap units.

1379
02:58:20.150 --> 02:58:33.500
Evan Thoms: map unit again it's just for reference is not evaluated in any way as I was kind of trying to make the point that the G at the deal is website it's this value in the field name it's really important this is what's going to be compared.

1380
02:58:34.910 --> 02:58:37.280
Evan Thoms: To the god likes database.

1381
02:58:39.470 --> 02:58:51.110
Evan Thoms: Or that said if if name happens to be empty or if no God next name is found in any of the strings or it found in the string.

1382
02:58:51.770 --> 02:59:04.490
Evan Thoms: being evaluated the tool does pop over to full name and then makes a check there as a backup just to try to catch any geologic names that might have been at least according to the gems schema have been placed in the wrong column.

1383
02:59:07.070 --> 02:59:24.230
Evan Thoms: age is reported on the report file in the report a spreadsheet but it's not evaluated that actually ends up being kind of a tricky thing to write the logic for so we leave age just there for a human reviewer to make the call on.

1384
02:59:26.060 --> 02:59:32.090
Evan Thoms: And I think i'm ready to run the tool or bring up the parameter fun anyway, let me go back to the catalog just.

1385
02:59:33.560 --> 02:59:34.250
Evan Thoms: cannot you.

1386
02:59:35.360 --> 02:59:37.730
Evan Thoms: So your name is chuck tool is.

1387
02:59:39.380 --> 02:59:45.620
Evan Thoms: In the toolbox, it has three parameters, you need a pass to.

1388
02:59:46.640 --> 02:59:47.300
Evan Thoms: DM you.

1389
02:59:50.600 --> 02:59:55.700
Evan Thoms: i'll put that in for the Lisbon falls South here database we've been looking at.

1390
02:59:56.990 --> 03:00:06.830
Evan Thoms: An estate extent you're working in a in a single state survey it's just one state abbreviation if you're mad crosses multiple state boundaries put those in comments are limited.

1391
03:00:07.940 --> 03:00:11.720
Evan Thoms: And then there's a checkbox to whether you want the excel spreadsheet to be open.

1392
03:00:18.140 --> 03:00:21.680
Evan Thoms: And the tool to progress with the messages.

1393
03:00:25.970 --> 03:00:26.270
Evan Thoms: and

1394
03:00:30.260 --> 03:00:37.160
Evan Thoms: i'm actually just going to go open a copy myself, because it doesn't take too long it takes a little time to run the.

1395
03:00:38.690 --> 03:00:43.130
Evan Thoms: spreadsheet is named after the database.

1396
03:00:44.480 --> 03:00:48.530
Evan Thoms: And is upended with the term underscore names check.

1397
03:00:50.450 --> 03:00:54.410
Evan Thoms: In an excel extension okay and ran so.

1398
03:00:58.940 --> 03:01:02.000
Evan Thoms: Okay, so this is a report that the author.

1399
03:01:04.160 --> 03:01:19.010
Evan Thoms: can use to or or a viewer can do us to do this names check, so there, there are three sections, the DM new contents in green is just verbatim from the inputs, the table and the extent string.

1400
03:01:22.070 --> 03:01:27.470
Evan Thoms: will expand name here with look at that we're not going to be concerned about full name very much at this point.

1401
03:01:29.870 --> 03:01:40.910
Evan Thoms: The Middle section is what's reported after going row by row through the dmv and sending this name straying off to an API at the geo lex website.

1402
03:01:44.690 --> 03:02:00.470
Evan Thoms: In the case of intrusive rocks or, for instance Granite or stratified rocks there are no lexicon names that appear in this name so it's blank there's nothing there, and in fact the author doesn't have to do anything with the Rose over here in Austin.

1403
03:02:02.630 --> 03:02:05.120
Evan Thoms: But let's go down to where we start to get some hits.

1404
03:02:06.560 --> 03:02:09.230
Evan Thoms: So here we've got Cox pinnacle granted.

1405
03:02:10.340 --> 03:02:16.850
Evan Thoms: And in the lexicon there is a name recorded Cox and there's one and there's one called pinnacle.

1406
03:02:18.140 --> 03:02:22.310
Evan Thoms: there's no less code name called clocks pinnacle and neither Cox nor pinnacle even.

1407
03:02:23.480 --> 03:02:32.720
Evan Thoms: or even found in maine So these are not hits are these are not matches that we are going to say correct, but the results are shown them regardless because.

1408
03:02:33.950 --> 03:02:36.350
Evan Thoms: Partly is to try to illustrate the.

1409
03:02:37.370 --> 03:02:46.700
Evan Thoms: The breath of God and in for people to be aware of geologic names that are being used in other parts of the country, and there may also be as we're going to see further down.

1410
03:02:48.740 --> 03:02:49.880
Evan Thoms: God will find.

1411
03:02:51.170 --> 03:03:01.670
Evan Thoms: usages that are similar to a map unit name but not exactly the same, and the author at that point may choose to change their map unit names to the usage being used in July.

1412
03:03:03.620 --> 03:03:14.270
Evan Thoms: So this is a case where it sort of looks like the author has intended for this to be a formal map unit name, and this is a point that will happy reconciled with the geologic names committee.

1413
03:03:17.630 --> 03:03:24.290
Evan Thoms: So here is a partial match in the map we've got vessel borough group.

1414
03:03:25.430 --> 03:03:31.010
Evan Thoms: And what's found in jira lex is the name facile borrow and found in maine.

1415
03:03:32.240 --> 03:03:33.200
Evan Thoms: And the age.

1416
03:03:34.220 --> 03:03:36.860
Evan Thoms: More or less the ages matchup but in July.

1417
03:03:37.940 --> 03:03:52.370
Evan Thoms: The units, known as vessel borough formation not gossip girl group so again, this is a situation where the author is going to have to reconcile this or justify their use of the term justify the use of the name, with the geologic names coming.

1418
03:03:56.990 --> 03:04:14.180
Evan Thoms: So if you've got a again if you've got a usage if you've used it a name if you use a map unit name that appears as a usage ngls and it's an exact match and the extent matches and the URL matches and you're good to go so.

1419
03:04:15.230 --> 03:04:18.530
Evan Thoms: The tool will do one check of the extent.

1420
03:04:19.910 --> 03:04:29.090
Evan Thoms: It simply is a match between the strings for the extent recording God that's in the extent provider dad at runtime if there's a match there.

1421
03:04:29.870 --> 03:04:44.720
Evan Thoms: The tool will report, yes usage has to be evaluated by a person that's where you look at these two terms and decide if they're equivalent and age also is like that to a person to review so again if those all three if all three answer yes.

1422
03:04:45.890 --> 03:04:50.570
Evan Thoms: Then you're good if if anyone these columns is no, then you move over to the next column.

1423
03:04:52.040 --> 03:05:00.560
Evan Thoms: And you write in some remarks about why either your the authors choice is the one that should be recorded and relax or.

1424
03:05:02.240 --> 03:05:04.250
Evan Thoms: make some remarks about why.

1425
03:05:05.330 --> 03:05:12.950
Evan Thoms: or make make make him a rock let's make a remark, for instance, that you decided to change the mapping that name to that appeal legs or age or the extent.

1426
03:05:14.390 --> 03:05:18.290
Evan Thoms: And references prefer to publish citations where you can.

1427
03:05:20.390 --> 03:05:22.700
Evan Thoms: publish name for other attributes.

1428
03:05:26.600 --> 03:05:40.010
Evan Thoms: And that's all I have to say about running the tool, I have a couple other comments to make about that finalized database phase, but i'll take a couple questions about this now if there aren't.

1429
03:05:43.070 --> 03:05:45.440
Robert Marvinney, DACF: Sure, any any questions from anybody.

1430
03:05:48.980 --> 03:05:54.260
Robert Marvinney, DACF: see any in the chat if you've got a question just unmute and ask your question.

1431
03:05:57.890 --> 03:06:02.960
Tyler Petty: every kind of format he question just with the hierarchy key.

1432
03:06:03.470 --> 03:06:13.610
Tyler Petty: yeah who is like, for the first part you there's no groups or anything like that, so you don't have that extra little indentation column once you get down to the.

1433
03:06:14.210 --> 03:06:33.110
Tyler Petty: hierarchy that starts with to you have the groups, you have to add in the extra column of digits why wouldn't you, for the first group or the for the hierarchy, starting with one why wouldn't you just want to like skip one digit and so, for example, the Granite.

1434
03:06:34.130 --> 03:06:42.200
Tyler Petty: Why wouldn't you want to move that over to make that three digits long and so that it matches up with the.

1435
03:06:44.150 --> 03:06:46.460
Tyler Petty: The hierarchy of to.

1436
03:06:48.980 --> 03:06:51.680
Evan Thoms: Well, actually, I think, to explain that Ralph do you have that.

1437
03:06:53.090 --> 03:06:58.310
Evan Thoms: handy we're showing the printed CMU and the.

1438
03:06:59.540 --> 03:07:03.110
Evan Thoms: hierarchies that you deduce from indentation.

1439
03:07:04.340 --> 03:07:09.800
Ralph Haugerud: um I don't have the spreadsheet did the spreadsheet or the graphic handy.

1440
03:07:10.310 --> 03:07:10.910
Evan Thoms: I think it's.

1441
03:07:11.720 --> 03:07:27.110
Ralph Haugerud: But basically, the the position, whether your first, second, third or fourth position is not about what rank you are whether your group or formation remember rough terrain it's about how many parents, you have grandparents and so on, and.

1442
03:07:31.190 --> 03:07:33.680
Ralph Haugerud: that's just if you were to leave.

1443
03:07:35.360 --> 03:07:39.680
Ralph Haugerud: insisted that always the group is recorded in the third position.

1444
03:07:41.720 --> 03:07:56.990
Ralph Haugerud: Both astronomy harder to parse when you're looking for parents and children and you're going to run problems in some maps that don't have groups or that have super groups and our nomenclature is is flexible enough and it's form that I think trying to.

1445
03:07:58.010 --> 03:08:01.760
Ralph Haugerud: Use of hierarchy, that is, strictly placed colored is probably a mistake.

1446
03:08:02.210 --> 03:08:08.480
David Soller: yeah I agree with route that the the the key term is flexible in a bit.

1447
03:08:10.010 --> 03:08:20.090
David Soller: It seems like every DM you is is unique it's customized to the authors preferences in how they organize it into either Platonic and.

1448
03:08:20.420 --> 03:08:34.700
David Soller: stratified rocks or or region to region, and so it really is, it can be a challenge to you know to concoct a hierarchy key that that that makes sense, so we're not driving towards.

1449
03:08:35.990 --> 03:08:44.450
David Soller: You know, rules on as Ralph noted about you know groups formations Members being a certain indentation in the hierarchy.

1450
03:08:47.360 --> 03:08:59.060
Evan Thoms: And I guess, I should also say that the hierarchy key examples that we've been seeing are just examples there's no specification for the form of that.

1451
03:09:00.080 --> 03:09:13.040
Evan Thoms: He in gems itself, these are just but we're using here what are sometimes called materialized paths that encode a particular branch of a parent child hierarchy tree.

1452
03:09:13.970 --> 03:09:28.130
Evan Thoms: You don't have to use that method of of hierarchy, it could just be a single you can just use anger incremental digits if you really want to just needs to be something that sorts roughly in the same order.

1453
03:09:29.180 --> 03:09:39.560
Evan Thoms: Or that would sort of the same wonders what's being shown on a DM you but you don't have to necessarily encode that parent child relationship in each value we think it's useful but it's not required.

1454
03:09:41.660 --> 03:09:46.100
David Soller: Evan could you put up the spreadsheet again I want to make a comment on that.

1455
03:09:46.400 --> 03:09:47.630
Evan Thoms: yeah thanks.

1456
03:09:47.960 --> 03:10:06.350
David Soller: So this was I you know this was a very gnarly problem, and you know Evan did a an excellent job and trying to parse out the thoughts from the geologic names committee on on how this might result in something that would be useful, and so.

1457
03:10:07.670 --> 03:10:14.870
David Soller: This really is the first systematic opportunity to identify names usage, especially in the States.

1458
03:10:15.530 --> 03:10:27.530
David Soller: and acquire from them apres the right documentation needed to add or modify the name in jail likes to likes will never be complete, I mean you can tell here that their their names that aren't in jail lacks.

1459
03:10:27.980 --> 03:10:39.230
David Soller: And that's really not the point, the point is to work towards establishing what is the current usage by the States geological surveys and usgs.

1460
03:10:39.950 --> 03:10:59.930
David Soller: it's a long process i'm rather excited that this gives us a systematic opportunity to identify it and again to to get the references a few remarks, perhaps a correction on the ages that sort of thing that that will make it possible to systematically update GL next.

1461
03:11:03.800 --> 03:11:08.930
Tyler Petty: thing I think you are, that makes definitely makes more sense of what I was thinking of so.

1462
03:11:09.590 --> 03:11:14.840
David Soller: yeah it's just a it's a think of this as a as an iterative process to build.

1463
03:11:16.520 --> 03:11:28.040
David Soller: So the lexicon isn't a isn't a word list it's not a list of of names that are used it's it's um it's restricted mostly.

1464
03:11:29.060 --> 03:11:30.170
David Soller: To formal names.

1465
03:11:32.540 --> 03:11:40.520
David Soller: And it's it's I think it's the most challenging science part of the NGO db project and.

1466
03:11:41.570 --> 03:11:45.920
David Soller: And so, this is, this is really an opportunity for us to.

1467
03:11:47.120 --> 03:11:50.300
David Soller: To get directly from the states from the map producers.

1468
03:11:51.440 --> 03:11:55.850
David Soller: The corrections in the right format, so that we can consider them and make them.

1469
03:12:04.010 --> 03:12:12.590
Evan Thoms: there's a question there from Julia i'm not too familiar with G let's first official geology but how does the names check work with superficial map databases.

1470
03:12:13.310 --> 03:12:23.630
Evan Thoms: As you can see if if it doesn't if the tool doesn't find a lexicon name in a map unit name it's just left blank it's only going to apply to.

1471
03:12:25.460 --> 03:12:28.790
Evan Thoms: map unit names were there is a less con name found in the string.

1472
03:12:30.020 --> 03:12:49.280
David Soller: So historically so much of God has content came from the geologic names you that that disbanded in the early 1990s, and at that time there weren't a lot of sacrificial formal names.

1473
03:12:51.080 --> 03:12:54.140
David Soller: We are making you know the our best effort to include.

1474
03:12:55.400 --> 03:13:03.890
David Soller: Formal strata graphic names that are glacial and other sufficient deposits, but but you've identified one of the areas of jail lacks that.

1475
03:13:05.090 --> 03:13:05.480
David Soller: That.

1476
03:13:06.980 --> 03:13:09.020
David Soller: Probably needs the most updating.

1477
03:13:10.760 --> 03:13:11.900
Ralph Haugerud: And I had to that.

1478
03:13:13.610 --> 03:13:30.110
Ralph Haugerud: If you stick in wetteland or none of them as a unit name nothing much comes back from July, where I work, the last playstation main bash on drift and I stick bash on into GL X and I get two units and seven usages.

1479
03:13:32.720 --> 03:13:33.170
David Soller: Right.

1480
03:13:35.090 --> 03:13:40.220
David Soller: yeah This is very much a a very challenging work in progress that.

1481
03:13:41.570 --> 03:13:41.960
David Soller: That.

1482
03:13:44.330 --> 03:13:49.700
David Soller: That needs the you know the it needs to be kind of a Community discussion.

1483
03:13:51.110 --> 03:14:01.430
David Soller: The the information comes into us and then, according to the geologic names committee staff and the and the strat code that that Evan mentioned.

1484
03:14:02.600 --> 03:14:05.360
David Soller: If it's possible to enter modified.

1485
03:14:06.590 --> 03:14:08.090
David Soller: that's that's what we'll do.

1486
03:14:16.340 --> 03:14:16.670
Robert Marvinney, DACF: Good.

1487
03:14:17.210 --> 03:14:17.600
Thanks.

1488
03:14:19.520 --> 03:14:20.960
Robert Marvinney, DACF: Margaret you have a question go.

1489
03:14:21.020 --> 03:14:22.490
Margaret Thomas: yeah Thank you i'm.

1490
03:14:22.820 --> 03:14:32.930
Margaret Thomas: Probably a question for Dave do you have any idea sort of what the update frequency is or is planned for July next we noticed that.

1491
03:14:33.590 --> 03:14:52.730
Margaret Thomas: It does a pretty good job with strata graphic names, especially historic ones, because I think that's how it was built on the strata graphic names, but you know for intrusive rocks for igneous rocks for a lot of you know, a newly identified metamorphic units.

1492
03:14:54.170 --> 03:15:11.960
Margaret Thomas: They they're not present, so what we've been doing is just putting in a comment about our usage why we've used it and you know what papers have come out about it but i'm just wondering when or how frequently you think chillax will be refreshed.

1493
03:15:12.680 --> 03:15:23.300
David Soller: yeah I think it'll be refreshed more often as more of these content suggestions come in, in terms of igneous rocks.

1494
03:15:24.980 --> 03:15:30.530
David Soller: You know well you know better than I, but, but a lot of these are our informal units.

1495
03:15:31.760 --> 03:15:45.680
David Soller: You know, a particular granted or the you know the basalt of dodge that sort of thing, and some of those were carried along into relax as informal names, but.

1496
03:15:46.760 --> 03:15:58.970
David Soller: Given the importance of documenting formal names we're not we're not placing an emphasis on including NGO lacks informal names, for example, for a particular Pluto on.

1497
03:16:02.360 --> 03:16:04.700
David Soller: i'm not sure if that really addressed your question or not.

1498
03:16:06.830 --> 03:16:08.120
David Soller: I tend to ramble sometimes.

1499
03:16:09.500 --> 03:16:21.770
Margaret Thomas: I think it does, but it's really I guess it's more of an approach as this this tool is fantastic it saves us a lot of time.

1500
03:16:23.060 --> 03:16:36.020
Margaret Thomas: But it it's not really prohibiting us from using a name if you know if the mapper you know, has has a reason to to identify the map unit that way.

1501
03:16:36.980 --> 03:16:39.290
David Soller: Absolutely not thank you for making that point.

1502
03:16:39.320 --> 03:16:49.760
David Soller: This is a recording of sick of significant publications of names that are that are in usage if a name comes out in a journal let's say.

1503
03:16:50.480 --> 03:17:07.190
David Soller: It doesn't and it's not included in jail legs it's entirely possible that we're waiting to see if it's generally accepted if it, you know passes the test of time if the state geological survey picks up on it and uses it.

1504
03:17:10.220 --> 03:17:27.680
David Soller: So no you're absolutely you're encouraged to you know to to do things as you have in the past, but when you find through this tool that there is a there is a discrepancy between your usage of a name and GL axes or the the age.

1505
03:17:29.600 --> 03:17:50.930
David Soller: Or perhaps it was used in new Hampshire but is now recognized in maine that's something we can update the aerial extent of so we're here to record what you know what the state geological surveys and usgs and others widely recognized as the as the SS strategic thing.

1506
03:17:52.640 --> 03:17:57.980
Margaret Thomas: I think this is really helpful and so i'm delighted to have it Thank you so much.

1507
03:17:59.600 --> 03:18:09.050
David Soller: And you know we intend to have some you know some tutorial some video sessions, with the state surveys to go over these these nuances.

1508
03:18:10.610 --> 03:18:16.700
David Soller: You know just to answer questions like that in a more focused setting of just particular service.

1509
03:18:19.460 --> 03:18:22.820
Evan Thoms: Day, yes Dave I have a question actually.

1510
03:18:24.500 --> 03:18:29.270
Evan Thoms: nomenclature all that well, but so am I am I right in understanding that.

1511
03:18:30.290 --> 03:18:34.520
Evan Thoms: If if an author wants to use an informal name.

1512
03:18:35.720 --> 03:18:38.660
Evan Thoms: If it's not in jira lex is.

1513
03:18:39.680 --> 03:18:44.090
Evan Thoms: it's just going to be suggested that they make sure that the form of the name.

1514
03:18:45.260 --> 03:18:49.490
Evan Thoms: Is looks makes it look like it is understood as an informal name.

1515
03:18:51.110 --> 03:18:52.580
David Soller: Yes, that's a very good point.

1516
03:18:52.610 --> 03:18:54.980
Evan Thoms: It wouldn't look like a formal name, whatever.

1517
03:18:55.190 --> 03:18:58.190
Evan Thoms: Those rules should happen to be, I guess, all I per capsule girl.

1518
03:18:58.850 --> 03:19:11.660
David Soller: Right, and you know the usgs doesn't want to be too prescriptive, but the the upcoming suggestions to authors of publications of the usgs the eighth edition has a very good chapter on.

1519
03:19:12.170 --> 03:19:27.140
David Soller: strider nomenclature use in genetic map descriptions and that Evans point is made there with with examples, so if you're interested in that we will be posting that link when the thing is published.

1520
03:19:28.580 --> 03:19:29.510
David Soller: At the side.

1521
03:19:30.950 --> 03:19:35.870
David Soller: But yeah it's it's important to there are nuances like years and years ago.

1522
03:19:37.100 --> 03:19:58.760
David Soller: The Dakota formation, the F was lower case until early to mid 20th century and then it became a formal it was uppercase def and so looking at an older publication that's lowercase F, does that mean it's formal or not formal so these rules are hard for you know for the.

1523
03:20:00.140 --> 03:20:03.140
David Soller: For non experts photographers to.

1524
03:20:04.280 --> 03:20:06.260
David Soller: You know, to internalize.

1525
03:20:09.110 --> 03:20:21.260
Robert Marvinney, DACF: Okay, you know that that's been a great discussion and we touched on a lot of things here, including sacrificial geology, which is a good segue to our next.

1526
03:20:21.740 --> 03:20:40.310
Robert Marvinney, DACF: short discussion will have a short discussion about bedrock versus an artificial maps and gems and then the remainder of the time will just be open for discussion or follow up questions that any of you might have knowing that we have about half an hour left to our session.

1527
03:20:41.540 --> 03:20:42.050
Robert Marvinney, DACF: So.

1528
03:20:43.280 --> 03:20:51.980
Robert Marvinney, DACF: I don't I don't have any illustrations here, I guess, some of, and you can stop sharing, but we can all see your smiling faces now.

1529
03:20:54.020 --> 03:20:55.250
Robert Marvinney, DACF: So we've seen.

1530
03:20:56.270 --> 03:21:07.820
Robert Marvinney, DACF: ralph's example of geologic map, which is in Pacific Northwest where he has both bedrock and sacrificial units on that same map.

1531
03:21:08.270 --> 03:21:18.920
Robert Marvinney, DACF: And, as he and I discussed, you know those official units are pretty much confined to the to the valleys and because of the pretty steep relief.

1532
03:21:19.370 --> 03:21:31.370
Robert Marvinney, DACF: In the Pacific North Northwest most of the mountains are our bedrock and so he you know he just treats them as geologic units that are exposed to the surface, which I think works great there.

1533
03:21:32.060 --> 03:21:42.740
Robert Marvinney, DACF: You saw our main example of Lisbon falls map that's a bedrock and we don't show this official materials on that and, although we do have a separate.

1534
03:21:43.220 --> 03:22:00.200
Robert Marvinney, DACF: Sufficient geology MAC and for us that works better, because those official units are they probably cover 95% of the state in in thicknesses enough to obscure most of the bedrock.

1535
03:22:01.340 --> 03:22:11.420
Robert Marvinney, DACF: And we found that just working with two separate maps works best for us makes the you know if we tried to combine them the superficial.

1536
03:22:12.320 --> 03:22:24.560
Robert Marvinney, DACF: material is at the surface and we would have to just dashed lines for for bedrock underneath that and I think pretty rapidly becomes unreadable so we.

1537
03:22:25.070 --> 03:22:37.640
Robert Marvinney, DACF: We maintain separate separate maps and I think that's the case with many new England states, there may be some exceptions in some areas where it's easy to to.

1538
03:22:38.150 --> 03:22:57.770
Robert Marvinney, DACF: combine the two but, for the most part we keep them separate never Ralph I know you told me that in gems you can have layers and and I take it to mean that you can turn a layer on or off as you choose to represent on a particular map.

1539
03:23:01.460 --> 03:23:04.040
Ralph Haugerud: I will take that as a licensed to say a little bit.

1540
03:23:06.320 --> 03:23:08.060
Robert Marvinney, DACF: I was hoping you bail me out Ralph.

1541
03:23:08.360 --> 03:23:15.680
Ralph Haugerud: there's a lot of interest in making multiplayer maps or 3D maps and gems and the bottom line is that um.

1542
03:23:16.550 --> 03:23:29.480
Ralph Haugerud: My impression dave's impression Evans impression, those of us working on the schema issues feel this Community doesn't have enough experience, so the right answer is, we need to keep working so gems is very much not prescriptive about how to do that.

1543
03:23:31.070 --> 03:23:33.440
Ralph Haugerud: behind that judgment, there are some other issues.

1544
03:23:34.640 --> 03:23:45.620
Ralph Haugerud: Art doesn't have very good 3D capabilities, when the Ark allows you to describe 3D geology a 3D map but God forbid, you try to make that an Arc the editing is new is not there.

1545
03:23:48.440 --> 03:23:57.440
Ralph Haugerud: There are several interesting experiments, or even successes and making layered maps there the stack unit maps with the Illinois survey has made.

1546
03:23:58.850 --> 03:24:00.410
Ralph Haugerud: They can be put into gems.

1547
03:24:01.460 --> 03:24:04.460
Ralph Haugerud: With only mildly breaking the gems format schema.

1548
03:24:05.690 --> 03:24:16.880
Ralph Haugerud: You can easily make a multiplayer map, where each layer is its own feature data set so you might have a sort of a geologic map feature data set you might have a.

1549
03:24:17.930 --> 03:24:26.360
Ralph Haugerud: superficial geology data set and then the bedrock would be called geologic map and if you do it like that you don't break the schema at all.

1550
03:24:28.790 --> 03:24:33.110
Ralph Haugerud: The Alaska state survey is experimenting with making multi layer maps and then another.

1551
03:24:34.190 --> 03:24:43.910
Ralph Haugerud: Protocol for doing it there's a I think my relative i'm biased a pretty good discussion about these questions in the faqs in the Appendix two gems.

1552
03:24:45.050 --> 03:24:49.190
Ralph Haugerud: So please go ahead and do it, try and find what works and teach us all.

1553
03:24:52.070 --> 03:25:05.720
Robert Marvinney, DACF: Okay, great I don't know if others want to weigh in on any of their experience, either in gems or or outside with with this question of bedrock official maps.

1554
03:25:06.860 --> 03:25:09.590
Robert Marvinney, DACF: or 3D maps or layers.

1555
03:25:12.080 --> 03:25:14.120
Christian Halsted: Well, Bob, I just wanted to offer that.

1556
03:25:15.200 --> 03:25:28.700
Christian Halsted: just maybe to reinforce the point that it is okay in gems to submit to completely different gems database for the same quadrangle one being bedrock one beings official.

1557
03:25:29.930 --> 03:25:36.650
Christian Halsted: For better or worse, be straight now that's I think the attack that we're trying to take me to comply with jim's.

1558
03:25:38.540 --> 03:25:47.060
Robert Marvinney, DACF: Right good I think that's an important clarification, so there there's there's actually a pretty simple solution if you want to have separate maps.

1559
03:25:51.740 --> 03:26:00.500
Ralph Haugerud: And i'd like to say that i'm intrigued by this discussion and how regional the differences of where we put concerns us and we were going are.

1560
03:26:01.760 --> 03:26:11.060
Ralph Haugerud: As a bedrock answer official mapper and cujo Lola and I am really grateful for that thick which one recovered that just allows me to not draw the bedrock contacts underrated.

1561
03:26:11.240 --> 03:26:13.580
Ralph Haugerud: I have no idea where they are I don't know how I would learn.

1562
03:26:13.730 --> 03:26:17.540
Robert Marvinney, DACF: yeah it can resolve a lot of bedrock problems under their catch it.

1563
03:26:17.750 --> 03:26:20.870
Ralph Haugerud: yeah and if I had to make a separate bedrock map i'd be in trouble.

1564
03:26:23.750 --> 03:26:32.000
Robert Marvinney, DACF: I don't know if any you know Steve or Margaret if you want to say anything about how your approach or if you've contemplated.

1565
03:26:33.080 --> 03:26:35.660
Robert Marvinney, DACF: Combined bedrock and sacrificial at all.

1566
03:26:39.170 --> 03:26:40.610
Stephen Mabee - MA: Bob Steve here.

1567
03:26:41.360 --> 03:26:43.910
Stephen Mabee - MA: I will say that some of our older.

1568
03:26:45.710 --> 03:26:56.990
Stephen Mabee - MA: gq series maps can in the mountainous parts in the berkshires did combine bedrock with sufficient because he just had que Al and The Valleys and you had.

1569
03:26:57.050 --> 03:27:06.890
Stephen Mabee - MA: us little pockets of of glacial flavio materials, you know, on the size of the valleys, but it was mostly bedrock of course in the newer.

1570
03:27:08.120 --> 03:27:18.050
Stephen Mabee - MA: map that Janet stone just published in 2019 for Massachusetts now we have a separate sufficient materials map for each of those claws.

1571
03:27:19.490 --> 03:27:27.890
Stephen Mabee - MA: One of the things that you know, maybe Dave can answer this more because I didn't married Giacomo Cohen, was the one who did the.

1572
03:27:28.460 --> 03:27:36.050
Stephen Mabee - MA: statewide to database from Massachusetts and one of the things we have is you know we have.

1573
03:27:36.470 --> 03:27:45.020
Stephen Mabee - MA: lake bottom sediments and then you have delta's programming out over those lake bottom settlements, and we have separated, you know fine grained.

1574
03:27:46.010 --> 03:28:09.530
Stephen Mabee - MA: lake bottom materials from our core stratified deposits, then you have post glacial materials windblown deposits and swamp deposits and louisville fans that then are on top of, and when I talked to Dave I think Dave I guess We broke some of the rules when we made those maps but.

1575
03:28:12.050 --> 03:28:20.510
Stephen Mabee - MA: Maybe you can explain further, but these are the things we would like to be able to have it more of a stack map type of approach, because when a driller goes out.

1576
03:28:22.040 --> 03:28:27.530
Stephen Mabee - MA: We want to know well we're going to run through 70 feet of sand and gravel in this delta and then we're going to hit.

1577
03:28:28.040 --> 03:28:43.310
Stephen Mabee - MA: 100 feet of lucasian deposits or you know 50 feet of the questions and then we're going to hit till before we hit to you know the sugar low far coast So these are things that we're interested in, so how that all fits together it'd be.

1578
03:28:43.520 --> 03:28:51.650
David Soller: helpful yeah so Steve when when y'all made that that map, you know gems wasn't really formalized and.

1579
03:28:54.410 --> 03:28:57.740
David Soller: So I, of course, have no argument with how with how.

1580
03:28:58.850 --> 03:29:14.420
David Soller: Mary get it at all that Ralph mentioned the the stack unit approach that Illinois takes and if those who aren't familiar with that approach, I it's merely a an intersection of all the materials.

1581
03:29:15.740 --> 03:29:18.800
David Soller: You know if each if each map unit.

1582
03:29:19.850 --> 03:29:30.350
David Soller: In three dimensions was its own layer you might say, and then you intersect all those layers you end up with this composite where every intersecting Polygon has a unique.

1583
03:29:32.990 --> 03:29:51.050
David Soller: unique vertical section and it's very elegant you know just just having a code that describes vertical section to those intersected polygons is Steve is that the approach that you are, you were.

1584
03:29:52.130 --> 03:29:54.800
David Soller: know or or something else, perhaps.

1585
03:29:55.190 --> 03:29:59.930
Stephen Mabee - MA: No, I think I don't think we're going to be doing stack map, we will be doing.

1586
03:30:00.650 --> 03:30:13.820
Stephen Mabee - MA: You know, we assume we have a ubiquitous layer till and then we have the glacial deposits, and that is a separate unit, and then we have post glacial deposit sometimes we separate those into early post glacial.

1587
03:30:14.210 --> 03:30:20.690
Stephen Mabee - MA: And then late post glacial deposits and their stack those are stacked on top of one another.

1588
03:30:20.900 --> 03:30:28.760
David Soller: Okay, so as rough noted, you know the city is still grappling with us and and depending upon the region, I think you know.

1589
03:30:29.930 --> 03:30:36.560
David Soller: depending upon the geologic setting there's going to be a different answer and different preferences, so we just don't have a.

1590
03:30:38.180 --> 03:30:52.040
David Soller: We don't have a strong suggestion for how to proceed, yet there is a companion project to NGA imdb that under that phase three funding is looking at and standards for three dimensional mapping.

1591
03:30:53.660 --> 03:31:02.420
David Soller: Led by done sweet kind and so perhaps under that effort some rules or some guidance will come out on.

1592
03:31:03.860 --> 03:31:05.420
David Soller: You know standard ways of.

1593
03:31:06.830 --> 03:31:10.850
David Soller: Making 3D gems complainant maps, what would just have to see.

1594
03:31:12.350 --> 03:31:13.700
Stephen Mabee - MA: Thanks yep.

1595
03:31:17.090 --> 03:31:21.110
Robert Marvinney, DACF: Okay, any other comments or discussion on this topic.

1596
03:31:26.840 --> 03:31:27.380
Robert Marvinney, DACF: All right.

1597
03:31:28.730 --> 03:31:36.470
Robert Marvinney, DACF: At this point we just really have open discussion, I mean that's all we have remaining we got about 20 minutes left in our session.

1598
03:31:37.760 --> 03:31:52.040
Robert Marvinney, DACF: If there's anything that yeah a lot to absorb, particularly if you're someone like me who hasn't really been terribly exposed to two gems this was a lot of material we're glad that the usgs will make the.

1599
03:31:53.540 --> 03:32:06.980
Robert Marvinney, DACF: Those recordings of those videos available on the the gems website and, of course, will be a recording of this session, as well, but you you'll be welcome to.

1600
03:32:07.670 --> 03:32:21.290
Robert Marvinney, DACF: review those videos at any time, and that can be pretty helpful once you haven't kept the context of this session, but any anybody want to bring up any any points or any observations from this.

1601
03:32:27.020 --> 03:32:28.040
Christian Halsted: I just wanted to.

1602
03:32:28.220 --> 03:32:28.700
Ask.

1603
03:32:29.810 --> 03:32:30.350
Christian Halsted: Evan.

1604
03:32:31.490 --> 03:32:36.080
Christian Halsted: you'd made a comment about some guidance around I think some of the final submissions.

1605
03:32:37.970 --> 03:32:43.130
Christian Halsted: If you were going to mention that and I don't know if we cut you off or moved on to quickly, did you have anything on that.

1606
03:32:43.730 --> 03:32:47.240
Evan Thoms: yeah yeah Let me take back the screen.

1607
03:32:48.980 --> 03:32:49.760
Evan Thoms: want to.

1608
03:32:52.610 --> 03:32:52.910
See.

1609
03:32:55.760 --> 03:32:59.930
Evan Thoms: yeah I was just going to point out that that the.

1610
03:33:02.180 --> 03:33:07.430
Evan Thoms: gems resources repository let's go to the main page.

1611
03:33:09.470 --> 03:33:12.470
Evan Thoms: That as you're starting to collect.

1612
03:33:13.670 --> 03:33:27.260
Evan Thoms: These materials together the geo database reports from the validate database tool, the report from the yogic names check tool that we've built in a checklist it's a PDF form oh i'm sorry that one open up.

1613
03:33:28.970 --> 03:33:30.410
Christian Halsted: A Evan sorry to interrupt.

1614
03:33:30.800 --> 03:33:32.540
Christian Halsted: yeah I think that might be on your other screen.

1615
03:33:33.080 --> 03:33:33.710
Okay.

1616
03:33:41.750 --> 03:33:43.580
Evan Thoms: yeah Oh, maybe this.

1617
03:33:45.470 --> 03:33:47.090
Evan Thoms: Is that sure that the spreadsheet.

1618
03:33:47.870 --> 03:33:49.190
Christian Halsted: yep yes.

1619
03:33:50.000 --> 03:33:50.690
Evan Thoms: And then.

1620
03:33:52.100 --> 03:34:01.670
Evan Thoms: At the gems resources repository there is this checklist PDF that you can use as you start to collect everything together and keep it organized before submitting.

1621
03:34:06.260 --> 03:34:07.820
Evan Thoms: And I just wanted to point that out.

1622
03:34:09.230 --> 03:34:12.530
Evan Thoms: And another thing I should mention is is that.

1623
03:34:13.700 --> 03:34:15.620
Evan Thoms: If you have trouble with any of the tools.

1624
03:34:16.940 --> 03:34:28.730
Evan Thoms: First of all, let me go back to the tool repository over the map one if if you have trouble with any of the tools, please go to this issues part of the github repository.

1625
03:34:28.850 --> 03:34:31.820
Ralph Haugerud: Of and we're still seeing the names check.

1626
03:34:32.300 --> 03:34:32.840
Okay.

1627
03:34:39.680 --> 03:34:45.470
Evan Thoms: i'm sorry i'm not seeing it on my gallery all right is that the repository.

1628
03:34:46.730 --> 03:34:49.430
David Soller: Yes, such tools Arc map.

1629
03:34:50.450 --> 03:34:55.250
Evan Thoms: Okay, so open an issue at the appropriate repository either Arc map or archos pro.

1630
03:34:56.510 --> 03:34:59.810
Evan Thoms: And let me hop back to gems resources.

1631
03:35:03.320 --> 03:35:04.970
Evan Thoms: and point out that we have.

1632
03:35:06.560 --> 03:35:09.860
Evan Thoms: The checklist PDF is here at this link under delivery.

1633
03:35:15.080 --> 03:35:30.290
David Soller: Evan that that thing lame that threat name transmittal letter is also guidance for especially state map state map data pres earth MRI recipients.

1634
03:35:32.240 --> 03:35:43.640
David Soller: And there'll be more I think more guidance coming from nc G and P on state map deliverables in the coming months on, you know, on how to proceed with submission.

1635
03:35:54.770 --> 03:35:55.400
Robert Marvinney, DACF: All right.

1636
03:35:56.960 --> 03:35:59.720
Robert Marvinney, DACF: Any other any other discussion from anyone.

1637
03:36:01.850 --> 03:36:03.530
Robert Marvinney, DACF: Here Julia see your hand up.

1638
03:36:04.580 --> 03:36:15.350
Julia Boyles: Yes, I just had a question about compilation map so in Vermont our current state map where we're working on sacrificial compilations, and that is what.

1639
03:36:16.040 --> 03:36:30.950
Julia Boyles: we're doing for our gems database and i'm just wondering if you have any advice for like adding in you know each sort of quadrangle to a compilation and how that works with gems.

1640
03:36:36.320 --> 03:36:37.610
Julia Boyles: If anybody has advice.

1641
03:36:39.350 --> 03:36:42.410
Robert Marvinney, DACF: i'm leaving it to one of the gems experts to respond.

1642
03:36:44.900 --> 03:36:51.770
Ralph Haugerud: Julia I will say the gems is designed to do single maps it's it's missing some important pieces to do multimap databases.

1643
03:36:53.660 --> 03:36:58.190
Ralph Haugerud: You could look at the portland map Sim 3443 for an example of a.

1644
03:36:59.240 --> 03:37:08.390
Ralph Haugerud: A map that was pasted together from oh something like two dozen different sources it's got 51 quads and not each one's a different author.

1645
03:37:09.050 --> 03:37:18.890
Ralph Haugerud: And not each one's a different report, but then pasted together with a fair bit of editing at the boundaries and one quadrangle almost invented from scratch.

1646
03:37:20.000 --> 03:37:25.310
Ralph Haugerud: And it would give you an example of how we chose to track data lineage say what came from where.

1647
03:37:27.080 --> 03:37:27.680
Ralph Haugerud: To look at that.

1648
03:37:28.310 --> 03:37:29.720
Julia Boyles: Thank you so much that will be helpful.

1649
03:37:29.780 --> 03:37:33.320
Ralph Haugerud: And if you want to talk more about this offline it's a subject that's near and dear to my heart.

1650
03:37:34.550 --> 03:37:35.000
David Soller: These.

1651
03:37:35.600 --> 03:37:43.010
David Soller: Funded compilations I think it's going to take a year or two, for you know for clarity on on.

1652
03:37:44.510 --> 03:37:56.660
David Soller: You know how those might might be done more systematically but you know it strikes me that if if it's a compilation it's a single database with lots of data sources.

1653
03:37:58.670 --> 03:38:01.070
Julia Boyles: Right that's sort of the direction we're headed in Vermont.

1654
03:38:01.100 --> 03:38:02.900
David Soller: yeah just viewing it simplistically.

1655
03:38:08.930 --> 03:38:14.960
Robert Marvinney, DACF: Okay, other other questions further discussion points people want to bring up.

1656
03:38:21.020 --> 03:38:22.280
Robert Marvinney, DACF: Alright well.

1657
03:38:23.810 --> 03:38:32.780
Robert Marvinney, DACF: Thanks everybody for participating in this short course I hope you got what you wanted out of it, I certainly learned a lot about.

1658
03:38:33.950 --> 03:38:53.990
Robert Marvinney, DACF: gems and digital mapping and translation between different systems and, thanks to our presenters Ralph I think those those videos you recorded were great and i'm glad they're going to be a resource going forward and.

1659
03:38:55.130 --> 03:38:57.920
Robert Marvinney, DACF: Thanks Dave for your overarching.

1660
03:38:59.120 --> 03:39:24.950
Robert Marvinney, DACF: Discussions and Evan for your your work on the the yield X and validation I think that's all really helpful and thanks Chris halston for contributing our our map to see to try to try to stump the pros here and in gems conversion glad to see that there's a route forward for us because.

1661
03:39:26.150 --> 03:39:42.500
Robert Marvinney, DACF: You know, in our funding environment it's going to be really important for us, and the other surveys to be able to put out information in this gems format so thanks a lot everybody Ralph Dave any you're having any closing remarks.

1662
03:39:44.330 --> 03:39:44.720
She.

1663
03:39:45.830 --> 03:39:52.250
David Soller: Would we be able to send to the participants, just a few a few links and such.

1664
03:39:53.360 --> 03:39:57.530
Robert Marvinney, DACF: yeah absolutely i'm sure through GSA somehow we can.

1665
03:39:59.300 --> 03:40:01.790
Robert Marvinney, DACF: I got all the emails and in a in a.

1666
03:40:04.400 --> 03:40:06.800
Robert Marvinney, DACF: In a spreadsheet so yeah we certainly can.

1667
03:40:07.370 --> 03:40:25.100
David Soller: yeah cuz we have a gems that usps.gov email alias it goes to Evan Ralph and me, so you know that's where particular questions can be can be hosted great and Bob, thank you for for for organizing this.

1668
03:40:25.880 --> 03:40:27.110
Robert Marvinney, DACF: Absolutely was.

1669
03:40:27.860 --> 03:40:28.640
Robert Marvinney, DACF: Very good session.

1670
03:40:32.090 --> 03:40:45.440
Robert Marvinney, DACF: Okay well with that I think we're done we'll give you a few minutes back to your day and thanks a lot, and we hope to see a number of you and other northeast GSA sessions coming up this.

1671
03:40:46.550 --> 03:40:47.480
Robert Marvinney, DACF: Sunday and Monday.

1672
03:40:49.430 --> 03:40:50.750
Robert Marvinney, DACF: Good take care, everybody.

1673
03:40:53.930 --> 03:40:52.000
Margaret Thomas: Great course.