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.
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.
Robert Marvinney, DACF: And we will have several.
Robert Marvinney, DACF: presenters.
Robert Marvinney, DACF: On our program this afternoon.
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.
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.
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.
Robert Marvinney, DACF: Please use the chat for questions there'll be opportunities as we go along to.
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.
Robert Marvinney, DACF: So, and there will be breaks in between some presentations to for questions and discussion.
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.
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.
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.
Robert Marvinney, DACF: Also, presenting today from the main geological survey is Chris homestead.
Robert Marvinney, DACF: he's been with us for almost a decade and.
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.
Robert Marvinney, DACF: Next Dave soller Dave are you there.
Robert Marvinney, DACF: turn on your camera Dave so we can all see you there's Dave.
David Soller: Yes, I am.
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.
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.
Robert Marvinney, DACF: brown Ralph haggard is also with the usgs in the civic Northwest good morning Ralph.
Ralph Haugerud: morning Bob yeah.
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.
Robert Marvinney, DACF: Conducting mapping projects in the Pacific Northwest and became an early advocate of.
Robert Marvinney, DACF: lidar and its application to the especially glacial mapping that he was doing in in that region of the country.
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.
Evan Thoms: yeah sure that's enough.
Robert Marvinney, DACF: Great well thanks.
Robert Marvinney, DACF: So we are all the presenters my role is going to be to.
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.
Robert Marvinney, DACF: In this short course.
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.
Robert Marvinney, DACF: And what what drew you to this short course today so starting at the top of the list is rosanna bear.
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.
Robert Marvinney, DACF: Great good you're in the right place.
Robert Marvinney, DACF: Next, Alan send them off.
Robert Marvinney, DACF: down here.
Robert Marvinney, DACF: Look at the list.
Robert Marvinney, DACF: Okay we'll move on Julia boils.
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.
Robert Marvinney, DACF: Very good, thanks john brooks.
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.
Robert Marvinney, DACF: Okay let's see uh john.
Robert Marvinney, DACF: vince CC my friend vince how our events.
Robert Marvinney, DACF: Since we can't hear you vince if you're trying to talk.
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.
Robert Marvinney, DACF: Right now you're muted vince maybe if you turn that off we'll hear you.
Robert Marvinney, DACF: Okay, well, I guess we'll move on to vince to Craig ebersole.
Craig Ebersole: hi everybody.
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.
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.
Craig Ebersole: get a crash course in this.
Robert Marvinney, DACF: Great okay well thanks Craig in enders.
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.
Robert Marvinney, DACF: Great okay thanks about Chelsea Hernandez.
Robert Marvinney, DACF: No okay.
Robert Marvinney, DACF: Karen eisenberg.
taryn isenburg: hi i'm tearing our.
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.
Robert Marvinney, DACF: Great okay zach clang.
Zach Klang: Hello everyone I work with taryn at the Connecticut geological survey I.
Zach Klang: Also, work on creating new maps and gems or digitizing maps making gems compliant digital maps.
Robert Marvinney, DACF: Okay, great.
Robert Marvinney, DACF: Steve maybe.
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.
Stephen Mabee - MA: Also, new mapping to be gems compliant.
Robert Marvinney, DACF: Okay, thanks Steve Jason you late.
Robert Marvinney, DACF: Jason are you here.
Robert Marvinney, DACF: Okay, moving on Tyler petty.
Tyler Petty: we're doing.
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.
Tyler Petty: Great.
Robert Marvinney, DACF: Okay, thanks and i'll apologize if I pronounce this incorrectly incorrectly blocking cf side.
Robert Marvinney, DACF: Now okay we'll move on as Elizabeth spielman.
Robert Marvinney, DACF: So Elizabeth here.
Robert Marvinney, DACF: Okay Roberts students oh.
Robert Stuetzle: yeah Robert students Lee I am.
Robert Stuetzle: hydrogeologist I work.
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.
Robert Marvinney, DACF: Great okay thanks thanks for joining us Margaret Thomas.
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.
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.
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.
Robert Marvinney, DACF: Okay, thanks Margaret Stephen psychosis.
stephen tzikas: Yes, hi i'm an environmental engineer, this is a continuing education class for me so it's all new material.
Robert Marvinney, DACF: All right, great.
Robert Marvinney, DACF: David Volterra.
Robert Marvinney, DACF: Stephen on.
Robert Marvinney, DACF: Okay we'll move on Lee whoo.
Lei Wu: Hello everyone i'm i'm i'm working with university in.
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.
Robert Marvinney, DACF: Very good, thank you so that's my list we have a pretty good cross section of.
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.
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.
Robert Marvinney, DACF: an overview of digitizing a map and then also translating and six existing digital map into the gems format.
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.
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.
Robert Marvinney, DACF: For discussion so i'm going to stop sharing my screen now.
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.
David Soller: Thank you, Bob.
David Soller: You can see the screen I hope.
David Soller: it's good.
David Soller: Okay, good so um as Bob mentioned, and we wanted to give an introduction to this this gem schema.
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.
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.
David Soller: In the mind of the.
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.
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.
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.
David Soller: But you know many of us who are around at the beginning of.
David Soller: Art with us today because they've retired.
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.
David Soller: In 96 the state surveys and nj mtb had a meeting in St Louis we set up a.
David Soller: Data model working group we published a design, known as version 4.3 in 1999.
David Soller: That then evolved into the North American data model Steering Committee and activity with the Canadian survey.
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.
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.
David Soller: The documents for any DM are still online.
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.
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.
David Soller: That design Evan TOMS Ralph haggard Steve Richard.
David Soller: We develop that design and presented it at DM team meetings, the last time was in 2009.
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.
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.
David Soller: insights into the process, the struggles to work together to develop a design that's going to work sufficiently for everyone.
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.
David Soller: So continuing.
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.
David Soller: conference calls advisory working groups discussions at TNT it went on for about three years.
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.
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.
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.
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.
David Soller: So here's some caveats.
David Soller: For those of you who aren't familiar with gems it's designed to content and topology of a single geologic map.
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.
David Soller: need to get started to implement Community.
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.
David Soller: The the gems design is will eventually incorporate the ability to manage multiple maps in a single database.
David Soller: But again.
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.
David Soller: So also gems is not necessarily recommended for capturing geologic data and observational information in the field.
David Soller: So point for me is the chief of the MGM db is is the next point.
David Soller: standardization of all types, is critical.
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.
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.
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.
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.
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.
David Soller: So final final comment, Bob mentioned Evan tom's is going to be discussing validating gems files prior to re positing them.
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.
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.
David Soller: Ralph is going to show us how to create the gems file database and how to migrate existing databases into gems.
David Soller: So thank you for your time.
Thanks, thank you.
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.
Robert Marvinney, DACF: Okay, I think we can move on, then Ralph are you ready to go.
Ralph Haugerud: I think i'm ready to go here um.
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.
Talk about getting started with gems, these are the topics I will cover.
Ralph Haugerud: Jim gems is a schema for encoding the contents of the geologic map and a GIs database.
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.
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.
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.
gems closely defines table structure and field names that are geologic map database, it has only three embedded vocabularies.
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.
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.
If they're using the database are defined in the glossary table and map the answer define the discussion mapping, there are resources online.
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.
The standard itself is usgs publication is whether dry reading, but I recommend the introduction to you, and some of the dependencies.
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.
look to see which feature classes belong intended feature data set what the fields are how they're defined.
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.
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.
tools.
And we're looking for the github site.
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.
So many advice on getting help.
A plea for collaboration.
And discussion in a few known issues.
We go back up at the top of the page.
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.
let's go back, we want to pick up the toolbox and, in general, you generally you want the latest release click the link.
grab the zip file.
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.
And it's done.
We can.
Open the containing folder.
grab a zip file.
I like to keep my code in a code directory so it's separate from my data, I mean I paste this here.
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.
extract all.
After a few seconds.
The toolbox.
A brief caution, this is the gym standard.
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.
A brief note on directory structure.
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.
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.
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.
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.
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.
don't want I do want snapping I do want standard I want tools and I want the apology available.
extensions are not critical.
For my GIs work I find it's very handy to have 3D analyst and spatial analyst available without thinking about it.
And then there's a sticky move tolerance and.
want to go to the editor and editing options.
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.
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.
And then you want to install the Ark toolbox and let's see, let me.
Open up the our toolbox window right click on empty spot in their ad toolbox.
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.
takes a few seconds.
But it should pop up.
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.
And that's it.
Robert Marvinney, DACF: Okay, thanks thanks Ralph.
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.
Robert Marvinney, DACF: had any experience with gems, are there any questions.
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.
Robert Marvinney, DACF: When you when you want to or need to.
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.
Robert Marvinney, DACF: is great yes.
David Soller: We can do that and, if possible, the recording as well yeah.
Robert Marvinney, DACF: I hope so okay.
Ralph Haugerud: And i'm discovering I can't see the chat but I videos playing i'm not sure what i've.
Robert Marvinney, DACF: lost but okay they're The only question was about recording so.
Ralph Haugerud: Okay.
Robert Marvinney, DACF: we're good we're good to move ahead.
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.
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.
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.
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.
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.
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.
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.
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.
We can see their contacts and, interestingly, none of them are dotted or concealed.
or dashed approximate they're all.
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.
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.
And there's some question as to how they can be treated.
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.
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.
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.
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.
they're defined in the damn us so they get stored in map unit lines in the gems database.
We also have striking didn't mission it's a fair number of them a lot of them quite hard to read.
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.
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.
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.
we're going to run the create new database script.
That we're going to add a map outline to it.
we're going to transfer the map outline into contacts and false fill out its attributes and get rid of the map outline.
Then we're going to add a pre packaged layer file that gives us digitizing templates.
and begin digitizing the line work we'll come back to this.
So here is.
The scan of the truck and for southeast quadrangle i've added some reference layers.
For example here scan usgs toes off of the.
base map collection and I happen to have lidar data for the area on my hard drive, so I had that also.
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.
turn the light on or off the.
scan I made partially transparent, if we look at the base map the scan total maps, we can see the scene in here.
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.
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.
scan a German snap on top of here and hooray that corner is roughly.
Where the corner, is in the base layer
We can also go look at the lidar and I have a fair bit of faith that the lidar is where.
it's supposed to be.
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.
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.
Go to the output workspace and it's.
to walk them for se we're gonna call this.
and
ordinarily I would say copy the reference framework from.
The input base map.
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.
ut and Canada let's use that.
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.
And orientation points we don't want to cross section we're not going to enable at a tracking.
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.
Like Okay, the runs multi very long, we can sit here and watch it.
it'll tell you what it's doing.
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.
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.
Of this output.
So we can see where the error occurred.
One minute and eight seconds later it's done.
And we can close this window and.
Close the toolbox for the moment, and we can add data to our map.
here's our database and we want to add the contacts and faults.
And makin outlines future classes to the map composition.
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.
We want to know.
We want to know where the the box is going to be.
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.
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.
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.
decimal degrees, and for that it's time for the calculator and 2.5 divided by 60 equals 0.04167.
and
We don't care about tix pasting the output is indeed.
nad 27 the output you database.
We can write this to the database we're building things in.
The output coordinate system.
We want to use.
You tm Ken.
And the scratch workspace we have an empty folder here we're going to use that, and this should run it's done.
You should be able to open the catalog.
and
here's our map outline you can add our map outline to the composition.
And there is a thin red line let's make it a little thicker.
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.
editable.
And selected copy.
paste.
paste it into contacts and faults.
We can turn this off and there it is in contacts and false let's give us some attributes.
So the type.
Is.
need line.
it's not concealed.
We calculated its location, so we know exactly where it is we're certain.
That it exists.
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.
Now we've got a box we've got something to digitize we're looking at.
let's make this easy we're going to add a a layer of templates that allow us to digitize features, without having to.
figure out too closely what other attributes are and we're going to go to add data.
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.
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.
and go back to our new database.
and select the contacts and faults layer
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.
and so on.
And the nice thing about this later also let's move in and zoom a little bit in here.
If we decide to.
Start digitizing.
let's see where editable okay.
We want.
Great features window.
We want to remove.
contacts and faults from here.
We want to remove map unit.
lines.
Stop editing yes.
So, if we look at one of these here.
it's got a name it's align.
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.
And it's.
references and hill type of contact 100 meters.
that's why i'm seeing here on this main.
So I can take this.
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.
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.
scan 24 K I think what this is showing is a measure of the distortion involved in making a map.
pretty good on paper string in the library and scanning it again.
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.
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.
And you hit our contact me to the next.
line.
And as you may notice i'm snapping is enabled.
This is the.
Ark map configuration, we set up in the.
First bit here earlier.
I know this is really exciting to watch I won't bore you too much more.
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.
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.
Open the table and change these values.
That 10.
And the handles are skinnier.
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.
We have.
The map boundary.
And this contact that makes a close Polygon and this contact me so close Polygon.
We can make polygons now, before we do that.
i'd like to see what we have selected here so let's.
zoom is like the features.
If we build polygons from this.
Well let's do it.
In pawleys oh.
We need to have Polygon features in here Polygon layer to make polly's into it so let's add mapping apologies.
Now we can build polly.
And this will build polly's inaccurate police.
And we do not want that Polygon.
That was sort of the the local universe, we can keep.
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.
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.
We can select a map boundary.
select contact.
build pawleys.
Okay, that Polygon look at its attributes, that is, like everything else in here map unit.
ti si es.
it's like this one.
looks like this one.
let's do.
One other map unit here one of the Polygon.
And again.
One of my my template 30 meters.
Now it's not going to snap.
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.
there's a closed Polygon.
and select that.
construct polygons.
That one.
Co.
We can now.
Double Click on this go to the assemblage of biology field symbolized by unique values of Matthew.
And let's pick some colors that makes sense to us that's a nice ese so i'm going to call it, green.
and
gold color.
orange.
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.
i'm gonna stop recording this and go digitize the rest of the map and we'll come back later.
Robert Marvinney, DACF: Thanks Ralph.
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.
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.
Robert Marvinney, DACF: Ralph one question in the chat is why not digitizing unit as polygons.
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.
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.
Robert Marvinney, DACF: Okay.
Robert Marvinney, DACF: Any any other questions folks Is this a good time to.
Robert Marvinney, DACF: If you've got any other questions to unmute yourself and just ask Ralph directly.
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.
Robert Marvinney, DACF: So Ralph are you continuing then.
Ralph Haugerud: Yes, let me share my screen again.
Okay.
Ralph Haugerud: and start the next one.
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.
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.
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.
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.
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.
need to add.
The orientation points feature class.
You said some civilization.
And here's a bunch of things and I want to use the F CDC civilization.
Oh, I forgot.
set it to rotate.
By the as the midfield say okay.
And let's see what else um let's try one here.
So you can zoom in.
let's.
Start editing.
We find him as a template we can grab.
digitize the point grab the edit tool.
Right click attributes, this has got a 45 degree dip.
And then we can grab the rotation tool.
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.
and set the reference scale to be 24,000.
And then we zoom in.
The symbols bigger.
And I think i'm going to make the symbol of bright color so I can see it.
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.
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.
Now we can go on.
To the next one.
And we grabbed the template.
The editor toolbar the attributes that has a.
I believe a 40 degree inclination.
And we can grab the rotate tool.
rotate until it lines up.
Back to create features rabbit template.
i'm using the scroll wheel, a change by zoom.
attributes that's got a 60 degree inclination.
grab the rotate tool.
Around till it lines up.
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.
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.
bedding.
And, as I didn't take very well let's try this again feel the calculator.
And they have double quotes on both sides.
yeah.
i'm i'm going to give you a break and go to the rest of these will come back in a minute.
i've digitized all the strikes and dips I think next step is to do map, you know lines.
So we need to add the magnetic lines feature class the map composition.
We can go over here and starting this little one here.
And I want to something stop editing.
Yes.
And this should bring up a template for nappy two minds, and I can go in here and digitize.
This short piece of.
piece of.
Tough bed T T.
And so the attributes map unit is T T.
it's not concealed.
it's a dashed line which makes me think that location conference meters at the scale of about 100 is appropriate.
That appears to be certainly there.
And certainly identified i'm gonna leave the other attributes blank for the time being.
and come to the West.
and
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.
next piece goes across the valley.
start a continuous piece.
And my guess is is continuous through this striking difference broken only so striking to put show.
You can see i'm i'm starting an ending ending and starting line wherever the line character changes from concealed to dash continuous.
Again i'm zooming.
Using the scroll wheel.
My mouse.
Now i've done a whole bunch of lines, and these are all tough bed.
T T.
See I believe let's open up the attribute table and collect all of these lines that are not labeled.
and say that these are map unit T T C.
and
Now it gets a little more interesting.
I want to select the ones that are concealed.
That REACH.
This reach this REACH.
This one.
and
This one and again.
back to the actual table and the field calculator.
knows all are.
concealed.
The remainder.
Of this easy way.
didn't get those.
Are his concealed.
was no.
Now, if we can see this, we had certain length.
That were continuous lines well located there's one.
Any shift and select again there's another one.
there's another one.
there's one there.
You can open up the attribute table.
And these are the ones that well located so their location conference leader should be fairly small.
And on this map I think well locators probably.
30.
remainder or not well located and i'm going to stick with a value.
Of 100.
And I hope in the discussion someone will ask me how I chose those values and how I defend them.
um.
let's see let's clear selection.
Everything has existence confidence is certain.
And everything has an identity confidence that certain.
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.
All skills that are larger than one 200,000.
So plot at scale is the denominator of the smallest scale of each can be plotted out.
thousand.
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.
problem is now in symbolizing these.
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.
So I am going to stick in a.
dummy value.
Which means I need to stop editing.
i'm going to add a field here.
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.
of text and let's see that 50.
So let's start here.
On is concealed.
Sorry.
And then sort by location competence meters.
And so.
So for those that have that are not concealed and have a well located we're going to call those.
The bed.
Continuous.
Are these here that are not concealed but or not well located.
In all those key bed.
dashed.
And for these that are concealed.
we're going to call them key bed.
garden.
And at this point.
We can symbolize these on those categories.
categories field is l type at all values.
And we can search for.
Key bed.
and
I think I want to use that one.
that's the dashed one.
And here's a dotted key bed.
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.
little bit clumsy in this case.
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.
selection.
We can turn on mapping a polly's and turn off this and this begins to look like a geologic map.
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.
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.
want to.
Take this line here.
Ah.
i'm going to extend that contact so it's got a dang.
And for that matter, it doesn't lie on top of the Polygon boundary there.
And i'm going to go back to the PowerPoint when you save my edits here.
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.
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.
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.
places where the contact misconceived continuation don't align places where they do align but the break isn't it the value or contact.
places or four units meet at one point which is geologically implausible.
faults, with no offset.
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.
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.
ology check also builds tables showing what map units are on what side of certain classes of contact and fault.
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.
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.
there's also a false nuts and sealed table.
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.
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.
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.
map.
and add this to the.
map composition open it and we're going to edit it so.
Start editing our map units from top to bottom, or que Al.
To oil.
tcs and.
we're going to leave all the other stuff like for the time being.
National turn the description field off want to see.
hierarchy and i'm going to say there's one dash.
one.
Special one one dash to.
dash.
three.
and two.
We can sort this in.
versus sending order and screw it up, let me start by hierarchy.
and get back the order, we want the strategy, what are the map, yes.
With this done, you can save our edits and stop editing.
and run the topology check tool.
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.
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.
We can run it.
And oh yeah every recently added to the tool kira a little bit of a.
really nice thing if you're connected to the Internet, when you run one of these tools it checks.
Back at the github repository and sees that there's a new newer version and tells you, which is nice to know.
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.
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.
Then we're looking at the directionality at the beginning and ending so you can figure out how the.
Line segments go around each node and doing a lot of fancy logic and.
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.
The topology check tool makes a new folder and puts a new database incited.
and
And those two.
I think that's all we need here.
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.
and put them underneath.
The lines of my my database, the good ones and most of these.
Are the.
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.
Where there's a problem.
That we knew we were going to have.
Where the Polygon boundary is no longer underneath the contacts remove the contact.
If we turn on our arrows bad nodes good to bad notes in here also looking to see what those are.
And one of them here.
let's see.
Sorry dangling contact and the other is a case where four lines.
meet at a point.
And that's geologically implausible if we fix the line work.
I need to edit this here.
And features start editing.
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.
Areas where well here let's look at this.
Where the boundary was covered by a line.
Ralph Haugerud: looks like that's the end of my video.
Robert Marvinney, DACF: Okay Ralph.
Robert Marvinney, DACF: One question in the chat at this point.
Robert Marvinney, DACF: Whether you have an opinion on using auto complete Polygon to digitize map uni pawleys.
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.
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.
Ralph Haugerud: Make the polygons from the lines.
Robert Marvinney, DACF: Okay anyone else have any questions right now for Ralph.
Christian Halsted: So this is Chris.
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.
Ralph Haugerud: Certainly.
Ralph Haugerud: So for line work, there are three confidence values we care about existence confidence identity confidence and location competence meters.
Ralph Haugerud: and on our maps traditionally if there's a question about the existence or identity alliance queried.
Ralph Haugerud: And so, if the lines not query dynamic check questionable on those they're always certain if the line is query.
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.
Ralph Haugerud: And the basic rule of thumb.
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.
Ralph Haugerud: But it's surprising how.
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.
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.
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.
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.
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.
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.
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.
Ralph Haugerud: And then, for this map I said the contacts were drawn as certain so usgs map it's in dry country.
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.
Ralph Haugerud: And so I went to 30.
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.
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.
Ralph Haugerud: I hope that's some a useful answer Chris.
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.
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.
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.
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.
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.
Next.
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.
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.
Ralph Haugerud: Because I find it simply wasn't reasonable to hypothesize how well located those lines were.
Robert Marvinney, DACF: Okay.
Robert Marvinney, DACF: there's a question in the chat for john brooks john you can just unmute and ask this question directly.
John Brooks: There we go i'm.
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.
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.
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.
John Brooks: The you know it seems like the setup processes fairly time consuming.
John Brooks: I didn't know if there be discontinuity of file locations, or something like that what.
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.
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.
Ralph Haugerud: And so, if you.
Ralph Haugerud: Take the database alone and put it someplace else it will know how to symbolize itself.
Ralph Haugerud: One of the templates anyway, if you put symbol values in and say use this style file that it does know how.
Ralph Haugerud: But, but the the mx D is where that layer information is stored.
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.
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.
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.
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.
Ralph Haugerud: and
Ralph Haugerud: You know those things are very recently handled with with feature templates those templates I would guess tend to be fairly idiosyncratic.
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
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.
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.
Thank you.
Ralph Haugerud: And Stephen maybe has a question about stacking map units.
Ralph Haugerud: That does not obey topology and.
Ralph Haugerud: This question is an advanced gems question and I don't dare go there.
Ralph Haugerud: it's been done, if you don't need to document well such a database in some ways, is unlikely to.
Ralph Haugerud: pass muster it's got some problems again because mostly topological.
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.
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.
Robert Marvinney, DACF: Right actually i'd like to ask a question Ralph.
Robert Marvinney, DACF: i'm probably asking this from ignorance, because i've really stepped away from all my GS GIs activities and know.
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.
Robert Marvinney, DACF: And I know that my staff and others when they're out in the field they're often collecting.
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.
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.
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.
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.
Robert Marvinney, DACF: Okay, so that might be a way for people who are oriented that way in the field to.
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.
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.
Robert Marvinney, DACF: All right, okay.
Christian Halsted: Oh i'll just jump in on that.
Christian Halsted: I guess I should spend a little bit more time with Bob field.
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.
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.
Christian Halsted: Data out of the schema that sitting in rgs online and puts it in our database schema so it's.
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.
Robert Marvinney, DACF: Good okay.
Robert Marvinney, DACF: Any other any other questions at this point.
Robert Marvinney, DACF: alright.
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.
Ralph Haugerud: Well, actually i'm just going to go through and build the non spatial tables for.
Robert Marvinney, DACF: This okay.
Robert Marvinney, DACF: yeah.
Ralph Haugerud: I think that's what's up here.
Ralph Haugerud: You some civilization let's see what happens here.
Okay.
Ralph Haugerud: and share that.
we've built an empty database digitize contacts made polygons we've digitized striking dips we digitize key beds, we checked topology.
The next step is to click non spatial tables in the map.
Ralph Haugerud: let's go look at our recipe here.
gems prescribes three non spatial tables other essentially internal metadata a data sources table that tells for data scribes were data comes from.
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.
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.
first thing to do is to add.
tables.
one.
Excuse me.
To the map and then let's go open.
Open one of them.
And the.
table is partly filled, because the gems schema.
uses some terms everywhere that need definition and they're they're built it's built into the database, the database, make it.
Smaller.
However, we know that we use some other sources for the data in this map in particular there's john wet and so far.
So we need to.
edit this.
And now we can.
Stick in.
The source, but typing into these fields is a pain.
Very difficult to do it accurately and well, and so what i've done is typed up.
Some data sources.
externally.
And I can take this.
I can copy it one of this field and paste in there it is.
For data sources, especially when we digitize.
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.
definition in the source data there my judgment, naturally recorded so let's.
copy that.
and put that in the notes field.
And there's a an optional field or an as needed field, the URL this report is available on the web.
So let's put that in here.
And we need something to call this, and one thing we could call it.
Is data source number one it's the primary data source that works.
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.
we're also going to stick in a few other sources.
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.
and
That we're going to describe here.
we're not going to use it as is, I chose to modify some of the definitions and so this is.
modified from glossary geology.
And I think i'm going to stop right there, we can.
Close this.
save our edits and move on to the glossary table.
And again, it comes pre populated with a couple of terms.
We want to add some more we know we have type contact in here.
That needs a definition when we have tight bedding.
And my first inclination is to go to the glossary geology and get definitions for these things so let's do that.
and
there's a picture I took on my cell phone yesterday my trusty glossary of geology I opened to the contact.
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.
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.
and
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.
And the source for that was I usgs.
si am 3443 which we're going to.
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.
and
I like the glossary of geology.
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.
And that's going to be G or g.
Fifth edition modified.
We now have a need for new data sources entries.
gog five m.
We need Sim 3443.
God fight and it's here already.
Sim 3443.
And a long title or long reference.
also has a URL.
yeah and we need the token that defines it.
Now.
I think we've actually got this fairly well under control.
We filled out on spatial tables.
we've got our spatial stuff done oh.
We left some fields unpopulated let's go through these here those open orientation points.
there's a bunch of points in here and.
None of them have a confidence values.
or a data source or additions data sources so let's step through here i'm.
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.
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.
So that's certain.
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.
we're we're, certainly including the answer here.
On.
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.
i'm gonna leave this will run a script later to calculate that.
station ID these things don't have stations map unit we're actually we could populate that right now, all of these are inside.
unit tcs.
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.
location source is from the map, we just digitized.
And the orientation source.
Is the same.
No notes on these.
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.
So we can say that's done.
We can go to map, you know lines.
And do some of the things data sources populated.
existence confidence.
we're good there.
contacts and faults.
Well, this locally, open up the contacts and bolts to attribute table.
everyone's got a type it's coming as concealed valued as an existence confidence value identity confidence location confidence meters.
We are good, except for the data source ID.
And i'm going to stop here, these three lines.
The neat line, we did not get out of john wooden's mouth so that's got to be something else.
rest of these.
All came.
From which welcome for southeast.
quad.
And we have gone through oh Matthew nepalis what's that very confidence, nothing was queried.
These are all certain.
Data source ID was again.
And again, p type as a convenience for translating from all a cart and we're not going to use it here.
At this point, the next step is to calculate the ID values for all these features.
Open the gyms tools go to set ID values.
We don't want to reset our data source ids we we like what they look like.
that's done.
We can see what happened by opening up say one of these here.
Over there.
This is populated.
And it will be that in all the tables in here.
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.
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.
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.
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.
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.
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.
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.
Okay.
let's close this.
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.
Since we have some problems not surprising.
Okay.
We have one term missing and glossary one missing data sources.
So we didn't stick in data source to that we need need line.
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.
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.
I prefer to use the fgc.
color set which is available online.
Each of these colors has.
An identifier, which was in this case, a text string which can be keyed into the DM you.
use other symbols values also.
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.
illustrator or something like that to or use the art style manager to read the rgb values and keep those in.
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.
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.
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.
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.
The mapping of type is concealed and the confidence values to symbol values is described in the file.
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.
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.
And this.
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.
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.
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.
When you've done this already your transition to presentation quality graphics and.
want to move to a new plot file.
So we want to save as two different xd.
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
step through each layers and set the symbolic.
And mostly use categories master symbols and style.
symbol field and match it to the FTC style.
We want to label the mapping apologies feature to us, we add a new.
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.
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.
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.
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.
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.
makes it in point and rights.
Rights the dip number on top of it.
And I think that's it.
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.
Robert Marvinney, DACF: Alright well thanks for that Ralph.
Robert Marvinney, DACF: Any questions from anybody.
Robert Marvinney, DACF: we're right right on schedule Ralph.
Ralph Haugerud: Is it time for a short break.
Robert Marvinney, DACF: yeah I think we ought to take a five minute break here and.
Robert Marvinney, DACF: Back at 3053 or six something like that folks.
Robert Marvinney, DACF: Okay.
Robert Marvinney, DACF: Okay, well, I guess, we could get underway again Ralph.
Robert Marvinney, DACF: Now this section is going to be.
Robert Marvinney, DACF: Ralph you and Chris working on.
Robert Marvinney, DACF: translating the existing digital map that correct.
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.
Christian Halsted: Sure, no problem so.
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.
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.
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.
Christian Halsted: He started working on it and then.
Ralph Haugerud: We just.
Christian Halsted: kind of went back and forth on.
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.
Ralph Haugerud: Thank you, Chris Let me share my screen here.
Ralph Haugerud: and start playing.
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.
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.
It corresponds to a published map has been falls South quadrangle.
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.
it's kind of Title block.
author, who did the cryptography who just he just was publication date.
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.
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.
woke me up a contact of uncertain origin, maybe it's right after contact reformed and interesting symbol.
And lots and lots of points symbols and I would note here that some of these are unrelated they're they're about outcrops.
Excuse me, some of them are about more about outcropping photo locations so on, and many are oriented.
And there's a very short geology table two samples two locations.
interpretive cross section.
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.
Ralph Haugerud: With the exception of the marginal notes, most of this other stuff doesn't have already home in Champs.
But the explanation of units explanation of symbols, the gop on table the Cross section all due.
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.
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.
We need a cross section feature data set.
With the mapping of policies and contacts and faults again standard gems features that the client access it shows in the cross section.
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.
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.
Chris very kindly pointed me at.
A web map service that the main GS runs that makes images of their published maps available.
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.
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.
And then rock units will start with their.
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.
Open up the toolbox.
Why is this so slow.
For a new database.
I want to put it in.
No it's not where I want to put it.
database is going to be.
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.
And we have some optional things we want to add, we need to cartographic lines, we need.
A miscellaneous map information.
We need orientation points.
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.
and proceed.
it's done.
Now, go to the catalog window.
To load the data into this newly main database and.
We have a geologic map.
let's look at the bedrock eunice layer before we begin here.
Sorry feature class.
It has, in it, Edit tracking information that we don't need.
Information about patterns that are on top of the polygons colors the polygons on the map unit.
Under unit.
and
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.
So let's right click on MAC nepalis load load data next.
Go look for.
Our data set we're going to go for bedrock units open add next.
Next, and mapping it wants to have unit put in it and synergy wants to have symbol, and that is yet.
It looks like everything is there let's load, the new.
feature class into Arc.
and open up the attribute table, and we have mapping that we have symbol and a bunch of other attributes.
Looking at the map, none of these mapping of polygons or query so conference for everything.
is certain.
Everything has come from the same data source, the main database we're going to call that data source one.
and
I don't think we need to do anything else here right now.
We can proceed to load contacts and false let's look at those first.
Now, here again, all the edit tracking you don't need comments the information here, I see is in two.
Two fields symbolic.
which has values of contact dash contact dotted.
Contact regular and non plotting.
And in the draw field.
Which is either yes.
or no.
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.
To just maybe they're mad boundaries.
So let's load.
stuff into contacts and faults.
Sorry.
Next next.
we're going to load symbolic into l type.
Because we're going to use them that value to figure out what the gems attributes of type and confidence and so on are.
On we're not going to put anything in there and i'm going to put.
draw in the notes field just relax.
tell me what to leave type empty.
Next next next.
When you should be able to add.
The.
contacts and faults here.
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.
We can say right now that all of this again is coming from data source one.
let's do that.
And I think we'll stop with that.
let's see what's the recipe say I do next okay.
um.
I want to go to the the non plotting lines in contacts and faults find out what they are.
Okay i'm back here to the contacts and faults.
So wrong button.
Open attribute table.
And we want to go to.
Contact certainly sending here the non plotting lines, the ones that aren't contacts.
With those and I want to zoom the selected features and sure enough there the map boundary.
And this line down the middle of the map which intrigues me.
So let's turn off.
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.
contacts and faults.
and find.
Just those two lines, I want.
No.
need to be editing to do this.
About one.
And I wanted to zoom see how much I got there's a little bit of that same line out here.
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.
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.
fault question mark.
And that better be inside double quotes or remote work.
And with these values from the main database somewhat modified.
I can now go to a gems toolbox script that uses the lt value to drive the setting of all these others.
So in the gems toolbox, and I want to go to attribute by key values.
And it might be worth looking at what this does.
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.
And we need to give it a database.
Which is the one we're working on.
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.
One of these in the.
Oh, I didn't pull it up here.
In the gems toolkit.
And the resources folder.
there's An example of this file.
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.
To.
My local working directory and renamed it.
And added stuff to it and modified it and so i've got the values.
Of.
became up the main database.
and the one that I invented.
That say that if.
l type.
Is a fault question mark then it's type.
Is a fault its location conference meters is 50 existence confidence is certain identity confidence is questionable and it's not concealed.
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.
We can take this file we've ever save X I made some changes and.
figured out.
and run the script.
It tells us what it's doing.
And it's not finding anything and orientation points because it's empty then it's done.
We can open.
contacts and faults and look you'll see them as populated distance conference and type is populated.
We don't need this anymore.
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.
To the map composition, we want lines, and we want units.
and
let's zoom glare and see where they are looks good.
If we look at the lines.
pretty much.
All the information appears to be in the symbologist field and that's basically the line type.
So we can open cross section, you can go to their load load data next select the input data.
And you don't want to put that there you don't want that we do want to put somebody.
In the light.
We should be able to take this now and put it in our map composition.
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.
sort of sending an anticlimax this which does not participate in.
The mapping topology that should be in a different feature class well.
And we need to select this by from.
Cross section, a context in the faults.
Line type equals get unique values.
On a selected, we should be able now to export this.
selected features.
And let's make sure we're in the same right place take three Lisbon Paul South cross section a.
lines.
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.
edit this start editing.
and delete it.
Now geologic lines future classes one line, and we also have.
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.
I want to label them something different, so I can.
Contact regular but maybe.
elevation tick.
Okay, say that it's stop editing.
select by attributes and we want to select one a clear this one.
i've selected these want to export those.
Data export data.
And again i'm.
hey there there if we turn off.
The geologic lines.
We still see it in here.
We can go back now to the contacts and faults.
feature class and.
The attribute table.
And we have these selected and delete them.
Rest the lines are still there.
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.
and participates in the map unit polygons and contacts and faults topology so i'm going to leave that in there.
we've got some cleanup to do let's go into here now and.
let's see, we have a fighting Gray line that's thin.
That is, I suspect the ground surface so let's.
call that.
Round surface for the type.
it's.
not concealed and we know where it is within a few feet this map has a 10 foot contra hon.
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.
On a clear the selection.
Every line on here is not concealed.
So we can say.
Most of these lines.
With the exception of the one who just labeled.
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.
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.
What location conference meter is meters here is and for numeric fields, a good no value is minus nine or minus 999.
We know where every one of these.
That it exists.
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.
line that may be lines that may be false or maybe contacts and so those.
Well, we can use this way here, those are questionable.
And those have an l type we're using dimension here that their.
main part of the map, we call them false question.
And everything on this map is from data source number one on this cross section.
What else can we say here.
We need some symbols.
And i'm here.
The dashed lines.
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.
These.
Are.
Continuous lines.
On the ground, surface we.
don't know what the surface, with the symbol is i'm going to call it, this for now.
These lines.
Summer dash some or not that's the below ground one it's solid.
I believe that's a 2.1 Point two.
And I think.
Say that it's.
let's see if we got this right.
let's go to properties.
Symbolic categories match the symbols in a style use the symbol field match to the FTC Jesse and.
Alice pretty good.
So we wanted to get.
And then, if we add.
cartographic lines geologic lines.
we're in good shape.
We also have the Cross section polly's to add.
And let's look at the source material.
We have.
unit missing biology.
So let's.
Go back to.
Cross section a nappy nepalis.
load load data next input data is cross section units open.
Next next.
Symbolic it's symbolic EG and map unit gets unit.
that's done.
We should do sorry I forgot to add that, to the composition.
Remove.
We can open this go to symbolic.
categories bashes symbols in the style use the symbol field let's match to the main.
GS.
And it works at least we get answers and it looks about right.
got a few things to clean up in here.
you'll in no queries in here everything appears to be certain as to what its identity is.
Everything came from data source number one.
and
I think.
that's it.
So we've loaded.
The future feature classes in.
The geologic map and the Cross section feature datasets, with the exception of her point Dale and we're going to stop right here.
Ralph Haugerud: i've got about 10 or 12 minutes more on point data.
Ralph Haugerud: And the non spatial tables, but if there are questions now we happy to address them.
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.
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.
Christian Halsted: You know geologists are pretty attached to colors especially better archaeologists.
So what we've.
Christian Halsted: What we've decided to do is.
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.
Christian Halsted: FTC matching color and some cases as an exact match some cases it's you know a little bit off.
Christian Halsted: We actually decided that we would put a custom field.
Christian Halsted: into the math unit polly's that would have.
Christian Halsted: The symbolic from our database and we would use the symbol field, we will populate that with the FTC value.
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.
Christian Halsted: Was that a good idea or somewhere along that spectrum.
Ralph Haugerud: I think you're doing fine my sympathies are completely with you.
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.
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.
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.
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.
Ralph Haugerud: I think carrying two sets of similar values is a very reasonable compromise.
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.
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.
Ralph Haugerud: should also notice, especially for the line and point markers symbols.
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.
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.
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.
well.
Ralph Haugerud: David you want to add to that.
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.
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.
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.
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.
Ralph Haugerud: let's see if I can.
Ralph Haugerud: let's talk about the Jews and non specialty.
Ralph Haugerud: Okay share my screen.
Ralph Haugerud: share.
Its.
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.
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.
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.
And in the database, the oriented features features litigation attitudes and not oriented features like pigmented outcrops observations.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
sentence map information data sources are pretty easy to do that away description a map units needs a little more discussion.
let's start with the published map which has an explanation of map units in the legend.
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.
A name.
A description descriptive text.
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.
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.
it's hard to enter a color fill the color salmon keyboard into the BAT Peter Paul a stable so symbolism work.
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.
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.
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.
The explanations are maps are typically strongly hierarchical this case we have stratified locks is the first order heading.
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.
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.
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.
hierarchy in this explanation is shown by font and by indentation and.
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.
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.
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.
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.
That we were to take our DNA new table and sorted, for example on name vassal bro group or on.
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.
In some dn us there are ambiguities about whether a row is meant to be treated.
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.
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.
And copy it and bring in a word, document and copy and paste that description text.
And we get this.
And, with a little bit of hand editing.
We can translate that into this, which is our map your description.
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.
And every bracket.
In the explanation of units.
The color values I read off of the bedrock units table in the map database Chris hall said Kenny supplied the main.
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.
That point.
I can copy the table.
Control see.
and go to.
excel control V there's a table with long text descriptions and I can file save as.
and
I don't want to save this glossary I want to save this as a.
DM you and actually already done this already was been doing you ut of eight and save.
I can place it okay.
And I want just the only stack that you don't that's fine.
clothes word close this.
And I can go back to map composition open catalog.
and open my database i've been building go to the CMU and load load data next navigate to.
find my csv file open add next next.
All the fields map appropriately next.
And if I open this up.
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.
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.
build feature classes for photo points and for geodon points, and when I did this, I didn't add glossary definitions for the.
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.
let's talk about points features and nonfiction tables.
Robert Marvinney, DACF: Okay, great thanks Ralph I don't know if anybody has any questions right now.
Robert Marvinney, DACF: Okay, not seeing any so Evan you're going to talk about validation is that right.
Evan Thoms: I think, because ralph's already shown it i'm not going to go into it.
Evan Thoms: In detail i'll talk about the geologic names check tool and and I also want to show.
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.
Robert Marvinney, DACF: Right.
Evan Thoms: Okay let's see how I can mention.
Evan Thoms: Alright, so.
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.
Evan Thoms: open a web browser and search for usgs gems.
Evan Thoms: It.
Evan Thoms: won't probably won't see the gems resources it near the top of the results least until people start searching.
Evan Thoms: But you can go to either of the repositories for the tools APP or curious pro repository.
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.
Evan Thoms: So this wiki is living at the gems resources repository.
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.
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.
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.
Evan Thoms: and
Evan Thoms: here's a link to the validate database documentation, with some of these rules that we've already seen.
Evan Thoms: So let's see to back up, there is also a page last step to finalize database phase.
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.
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.
Evan Thoms: So.
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.
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.
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.
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.
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.
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.
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.
Evan Thoms: And look them up in the US geological names lexicon, which is the big book.
Evan Thoms: of mapping of names in North America and starting in the US and US territories.
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.
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.
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.
Evan Thoms: and
Evan Thoms: it's going to look at the results at the top of this, page under here units unit names, starting with the.
Evan Thoms: want to point out that.
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.
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.
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.
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.
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.
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.
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.
Evan Thoms: Well, not finding any, but there are other.
Evan Thoms: Non letter characters described at the very bottom and scroll down.
Evan Thoms: It gives some attributes to the usage, so an asterisk, for instance, indicates that the usage is was published by usps authors.
Evan Thoms: Obsolete terms are also recorded in jira lex as denoted by no current usage, or you will see this little dagger symbol.
Evan Thoms: And slashes indicate, but a slash before name indicates, doesn't conform to to the nomenclature guidelines, so there are these.
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.
Evan Thoms: So let's go to our GIs pro and talk about.
Evan Thoms: The DM you and the structure of the DM you before you run it through the tool.
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.
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.
Evan Thoms: Now unit name.
Evan Thoms: full name and age, but no others.
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.
Evan Thoms: Most any kind of table actually.
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.
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.
Evan Thoms: To the god likes database.
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.
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.
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.
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.
Evan Thoms: cannot you.
Evan Thoms: So your name is chuck tool is.
Evan Thoms: In the toolbox, it has three parameters, you need a pass to.
Evan Thoms: DM you.
Evan Thoms: i'll put that in for the Lisbon falls South here database we've been looking at.
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.
Evan Thoms: And then there's a checkbox to whether you want the excel spreadsheet to be open.
Evan Thoms: And the tool to progress with the messages.
Evan Thoms: and
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.
Evan Thoms: spreadsheet is named after the database.
Evan Thoms: And is upended with the term underscore names check.
Evan Thoms: In an excel extension okay and ran so.
Evan Thoms: Okay, so this is a report that the author.
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.
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.
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.
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.
Evan Thoms: But let's go down to where we start to get some hits.
Evan Thoms: So here we've got Cox pinnacle granted.
Evan Thoms: And in the lexicon there is a name recorded Cox and there's one and there's one called pinnacle.
Evan Thoms: there's no less code name called clocks pinnacle and neither Cox nor pinnacle even.
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.
Evan Thoms: Partly is to try to illustrate the.
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.
Evan Thoms: God will find.
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.
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.
Evan Thoms: So here is a partial match in the map we've got vessel borough group.
Evan Thoms: And what's found in jira lex is the name facile borrow and found in maine.
Evan Thoms: And the age.
Evan Thoms: More or less the ages matchup but in July.
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.
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.
Evan Thoms: The tool will do one check of the extent.
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.
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.
Evan Thoms: Then you're good if if anyone these columns is no, then you move over to the next column.
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.
Evan Thoms: make some remarks about why.
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.
Evan Thoms: And references prefer to publish citations where you can.
Evan Thoms: publish name for other attributes.
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.
Robert Marvinney, DACF: Sure, any any questions from anybody.
Robert Marvinney, DACF: see any in the chat if you've got a question just unmute and ask your question.
Tyler Petty: every kind of format he question just with the hierarchy key.
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.
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.
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.
Tyler Petty: The hierarchy of to.
Evan Thoms: Well, actually, I think, to explain that Ralph do you have that.
Evan Thoms: handy we're showing the printed CMU and the.
Evan Thoms: hierarchies that you deduce from indentation.
Ralph Haugerud: um I don't have the spreadsheet did the spreadsheet or the graphic handy.
Evan Thoms: I think it's.
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.
Ralph Haugerud: that's just if you were to leave.
Ralph Haugerud: insisted that always the group is recorded in the third position.
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.
Ralph Haugerud: Use of hierarchy, that is, strictly placed colored is probably a mistake.
David Soller: yeah I agree with route that the the the key term is flexible in a bit.
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.
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.
David Soller: You know, rules on as Ralph noted about you know groups formations Members being a certain indentation in the hierarchy.
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.
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.
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.
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.
David Soller: Evan could you put up the spreadsheet again I want to make a comment on that.
Evan Thoms: yeah thanks.
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.
David Soller: This really is the first systematic opportunity to identify names usage, especially in the States.
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.
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.
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.
Tyler Petty: thing I think you are, that makes definitely makes more sense of what I was thinking of so.
David Soller: yeah it's just a it's a think of this as a as an iterative process to build.
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.
David Soller: To formal names.
David Soller: And it's it's I think it's the most challenging science part of the NGO db project and.
David Soller: And so, this is, this is really an opportunity for us to.
David Soller: To get directly from the states from the map producers.
David Soller: The corrections in the right format, so that we can consider them and make them.
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.
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.
Evan Thoms: map unit names were there is a less con name found in the string.
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.
David Soller: We are making you know the our best effort to include.
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.
David Soller: That.
David Soller: Probably needs the most updating.
Ralph Haugerud: And I had to that.
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.
David Soller: Right.
David Soller: yeah This is very much a a very challenging work in progress that.
David Soller: That.
David Soller: That needs the you know the it needs to be kind of a Community discussion.
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.
David Soller: If it's possible to enter modified.
David Soller: that's that's what we'll do.
Robert Marvinney, DACF: Good.
Thanks.
Robert Marvinney, DACF: Margaret you have a question go.
Margaret Thomas: yeah Thank you i'm.
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.
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.
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.
David Soller: yeah I think it'll be refreshed more often as more of these content suggestions come in, in terms of igneous rocks.
David Soller: You know well you know better than I, but, but a lot of these are our informal units.
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.
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.
David Soller: i'm not sure if that really addressed your question or not.
David Soller: I tend to ramble sometimes.
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.
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.
David Soller: Absolutely not thank you for making that point.
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.
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.
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.
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.
Margaret Thomas: I think this is really helpful and so i'm delighted to have it Thank you so much.
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.
David Soller: You know just to answer questions like that in a more focused setting of just particular service.
Evan Thoms: Day, yes Dave I have a question actually.
Evan Thoms: nomenclature all that well, but so am I am I right in understanding that.
Evan Thoms: If if an author wants to use an informal name.
Evan Thoms: If it's not in jira lex is.
Evan Thoms: it's just going to be suggested that they make sure that the form of the name.
Evan Thoms: Is looks makes it look like it is understood as an informal name.
David Soller: Yes, that's a very good point.
Evan Thoms: It wouldn't look like a formal name, whatever.
Evan Thoms: Those rules should happen to be, I guess, all I per capsule girl.
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.
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.
David Soller: At the side.
David Soller: But yeah it's it's important to there are nuances like years and years ago.
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.
David Soller: For non experts photographers to.
David Soller: You know, to internalize.
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.
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.
Robert Marvinney, DACF: So.
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.
Robert Marvinney, DACF: So we've seen.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Ralph Haugerud: I will take that as a licensed to say a little bit.
Robert Marvinney, DACF: I was hoping you bail me out Ralph.
Ralph Haugerud: there's a lot of interest in making multiplayer maps or 3D maps and gems and the bottom line is that um.
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.
Ralph Haugerud: behind that judgment, there are some other issues.
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.
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.
Ralph Haugerud: They can be put into gems.
Ralph Haugerud: With only mildly breaking the gems format schema.
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.
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.
Ralph Haugerud: The Alaska state survey is experimenting with making multi layer maps and then another.
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.
Ralph Haugerud: So please go ahead and do it, try and find what works and teach us all.
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.
Robert Marvinney, DACF: or 3D maps or layers.
Christian Halsted: Well, Bob, I just wanted to offer that.
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.
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.
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.
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.
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.
Ralph Haugerud: I have no idea where they are I don't know how I would learn.
Robert Marvinney, DACF: yeah it can resolve a lot of bedrock problems under their catch it.
Ralph Haugerud: yeah and if I had to make a separate bedrock map i'd be in trouble.
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.
Robert Marvinney, DACF: Combined bedrock and sacrificial at all.
Stephen Mabee - MA: Bob Steve here.
Stephen Mabee - MA: I will say that some of our older.
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.
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.
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.
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.
Stephen Mabee - MA: statewide to database from Massachusetts and one of the things we have is you know we have.
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.
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.
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.
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.
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.
David Soller: helpful yeah so Steve when when y'all made that that map, you know gems wasn't really formalized and.
David Soller: So I, of course, have no argument with how with how.
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.
David Soller: You know if each if each map unit.
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.
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.
David Soller: know or or something else, perhaps.
Stephen Mabee - MA: No, I think I don't think we're going to be doing stack map, we will be doing.
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.
Stephen Mabee - MA: And then late post glacial deposits and their stack those are stacked on top of one another.
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.
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.
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.
David Soller: Led by done sweet kind and so perhaps under that effort some rules or some guidance will come out on.
David Soller: You know standard ways of.
David Soller: Making 3D gems complainant maps, what would just have to see.
Stephen Mabee - MA: Thanks yep.
Robert Marvinney, DACF: Okay, any other comments or discussion on this topic.
Robert Marvinney, DACF: All right.
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.
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.
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.
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.
Christian Halsted: I just wanted to.
Ask.
Christian Halsted: Evan.
Christian Halsted: you'd made a comment about some guidance around I think some of the final submissions.
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.
Evan Thoms: yeah yeah Let me take back the screen.
Evan Thoms: want to.
See.
Evan Thoms: yeah I was just going to point out that that the.
Evan Thoms: gems resources repository let's go to the main page.
Evan Thoms: That as you're starting to collect.
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.
Christian Halsted: A Evan sorry to interrupt.
Christian Halsted: yeah I think that might be on your other screen.
Okay.
Evan Thoms: yeah Oh, maybe this.
Evan Thoms: Is that sure that the spreadsheet.
Christian Halsted: yep yes.
Evan Thoms: And then.
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.
Evan Thoms: And I just wanted to point that out.
Evan Thoms: And another thing I should mention is is that.
Evan Thoms: If you have trouble with any of the tools.
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.
Ralph Haugerud: Of and we're still seeing the names check.
Okay.
Evan Thoms: i'm sorry i'm not seeing it on my gallery all right is that the repository.
David Soller: Yes, such tools Arc map.
Evan Thoms: Okay, so open an issue at the appropriate repository either Arc map or archos pro.
Evan Thoms: And let me hop back to gems resources.
Evan Thoms: and point out that we have.
Evan Thoms: The checklist PDF is here at this link under delivery.
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.
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.
Robert Marvinney, DACF: All right.
Robert Marvinney, DACF: Any other any other discussion from anyone.
Robert Marvinney, DACF: Here Julia see your hand up.
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.
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.
Julia Boyles: If anybody has advice.
Robert Marvinney, DACF: i'm leaving it to one of the gems experts to respond.
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.
Ralph Haugerud: You could look at the portland map Sim 3443 for an example of a.
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.
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.
Ralph Haugerud: And it would give you an example of how we chose to track data lineage say what came from where.
Ralph Haugerud: To look at that.
Julia Boyles: Thank you so much that will be helpful.
Ralph Haugerud: And if you want to talk more about this offline it's a subject that's near and dear to my heart.
David Soller: These.
David Soller: Funded compilations I think it's going to take a year or two, for you know for clarity on on.
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.
Julia Boyles: Right that's sort of the direction we're headed in Vermont.
David Soller: yeah just viewing it simplistically.
Robert Marvinney, DACF: Okay, other other questions further discussion points people want to bring up.
Robert Marvinney, DACF: Alright well.
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.
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.
Robert Marvinney, DACF: Thanks Dave for your overarching.
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.
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.
She.
David Soller: Would we be able to send to the participants, just a few a few links and such.
Robert Marvinney, DACF: yeah absolutely i'm sure through GSA somehow we can.
Robert Marvinney, DACF: I got all the emails and in a in a.
Robert Marvinney, DACF: In a spreadsheet so yeah we certainly can.
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.
Robert Marvinney, DACF: Absolutely was.
Robert Marvinney, DACF: Very good session.
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.
Robert Marvinney, DACF: Sunday and Monday.
Robert Marvinney, DACF: Good take care, everybody.
Margaret Thomas: Great course.