[MUSIC] Hello everyone, and welcome back. In this lesson we're going to through some of the core features of geodatabases in general so that you know how you can organize your data and ensure its integrity. Specifically I'll show you how to use featured data sets to both organize your data but also ensure high integrity of the data. How to use relationship classes to make relates more permanent. How to add attachments to your features so you could store images in your database. And then also how to compact your database to get some space back if you've deleted information. Okay so let's start out with the featured data set. Think of featured data sets as folders that aren't primarily for organizational purposes, but have a side benefit of it and are really there to enforce projection and coordinate system constraints On your data to make sure that your data keeps the same integrity across a project. So if I create a new feature data set in my geodatabase by right-clicking on it and going to that, I can give it a name. So I'll call it Streams Data or Streams. And it's going to ask me for the coordinate system of my streams data. Now, or of the feature data set in particular. And anything that I'm going to put into this folder, this feature data set in the future, needs to be in that coordinate system and it needs to match, or else it won't be allowed to be in that feature data set so I'll leave that there for the x y coordinate system. It's asking me for the z coordinate system, I'm not going to select one. The data that I have won't have a z coordinate system. Then it's asking me for x y tolerance, z tolerance, m tolerance, I'm going to leave all of these as the defaults for now. I'll click finish and I get this little new icon named streams here with an expansion item here and Nothing expands because there's nothing in it. This is a feature data set and let's try to put something in it, so that the HD flow line data that I have that streams information I have for California is in that same coordinate system, it's in the 1983 coordinate system that I just used. And it also doesn't have a z coordinate system but if I try to drag and drop it in here, it tells me the spatial references don't match And it seems like they should, right, but according to it, they don't. So I'm going to instead right click on it and go to import, feature class and I will drag the NHD Flowline over to the input features and it's putting the output location as my streams feature data set and I'll call it NHD Flowline Now in 1983, just to indicated that it's enforced to that coordinate system in there. If I try to name it HD flow line, it would probably conflict with what I have here already. The names need to be unique still. So if I click okay It's going to start running, and it's importing that data, it's converting that data across to a compatible format in that streams feature data set. So when they use the import tool there, or the feature class, the feature class geo-processing tool, which is what that was, it automatically handles any translations the data needs in order to be compatible with the feature data set, which is really nice. So what it's done is like most geo processing tools, it starts adding it to my map for me and I can see that I have it in here. So that's pretty cool. They're useful structures for using integer databases to make sure that your data is using the same coordinate system in particular. The side benefit, as I said, is that you can use them as a sort of folders to classify your data. I could create multiple feature data sets that have different names, but even the same coordinate system, so that they're both a constraint, but also a way to classify my data. If I wanted to, I could also add the nav streams layer into that now, but we'll skip that. You just saw the process for it. But, I want to point out that can store multiple items. In enterprising geo databases, where you're using a geo database server instead, feature data sets are also useful for managing permissions. So, you can set permissions for who can access items for any given feature data set. And then they're also useful for data sharing. That's one of the usages that esray lists for them. One final thing I want to note about them before we move on is that if I right click on them and click on New, note that, I don't get the same options that I do if I right click on the whole geodatabase and go to new. I have many more options specifically for rasters and for toolboxes. That's because again, it's a feature data set, it only handles feature data, it does not handle raster data. So I can't import my raster data into a feature data set. Okay the next thing I want to point out is relationship classes so let's remove this for now, and a relationship class is like making a relate in the map document where do kind of that many to many join or that one to many join Except that it makes it permanent in the geo database so if I right click and created a new relationship class, I can give it a name of NHD_Attribures. And I'm going to do some of the same things just with different terminology than before. And with a little more power than we do when we do standard relate in arch map document. So our origin data is the data we're trying to join to the feature class. So I have NHD plus attributes that I want to join in Data table of information I want to attach to my feature class. And then, let's just use that string that we just had. So, I'll choose NHDFlowline, and I'll click next. So, this is what we would do, even in ArcMap. We choose the data that we're joining from, and the data that we're joining to. And we'll go next, and we have some options here, basically it's saying are the data independent of each other? If I delete attributes and then HD Plus attributes should I also delete the corresponding records in the feature class? In this case we're going to say no they're independent of each other and we'll use the simple relationship. I'm going to breeze through this a little bit because there are so many options here. And mostly they're important in different situations. But know that relationship classes can make permanent relates, and that you should take a look at these options if you go to make a relationship class for yourself. So we'll leave the labels it creates as the defaults. You'll see those when you go to switch between the tables in the arc map document. I'll point that out in a moment. And then we won't propagate messages, We'll skip that for now. And in this case it's a one to one relationship. So we could have actually done this with a straight join in ARC map but we're going to do it through a relationship class for now. And so it's a one to one relationship. We have one record in HD plus attributes for every record in HD flow line. And we're not going to add any additional attributes using the relationship class, so I'll leave it as no. And then, here's where we select the fields that are common to the data sets. So these two use a field called component ID or COM ID. Then they both use that field. So I'm selecting that. And that's the field that is going to do the join on. And then I'll click Next again. It gives me a summary, and I'll click Finish to create the relationship class. It thinks for a bit, and then it adds this item here, which is relationship class, these arrows pointing between features here. Now, if I add the NHD flow line to my map document again, and I open up the attribute table, I will see the properties that we usually get through a relate. So if I select those there and then go up here to the related tables, I can see those names that I was talking about earlier, where we could choose the directions of the names. And if I click that, it highlights the related fields for me here. So, I can switch back and forth between the two tables this way. And note that I didn't have to go to Join and Relates and then Relate and that I also can't remove the Relate because it's not existing in the map document, it's existing in the geo database. It's permanent. So, what's really great is if I send this geo database to anybody, it's already It already has the relate inside of it, so that's a permanent relate. If I decide I don't want it anymore though I could right click on it and go to delete. Okay, now I want to show you geodata Database attachments. So we'll use our California counties layer for that instead. I'm going to select Butte County because I have an attachment for it. An attachment is a way for us to store other data that's not geographic data in our geodatabases attached to our features. So that we can view them when we're working with the feature. So, we could add images or we could add other information that just doesn't fit in the data tables for whatever reason. So, to add attachments, I need to right-click on the layer and go to Manage And then create attachments and we sit it adds a couple new things for so that's the data table with an attached suffix, and then it adds a relationship cause which we just learn about that relates this two tables together. But that relationship class is going to do work in the background. We don't need to be too concerned about it. And then, to work with attachments, I need to be editing the data, so I'll go to editor and then start editing, which we should be getting familiar with now. It's going to warn me that the spatial reference doesn't match the data frame. That's okay. I'm not working with actual feature data here. And then I'm going to collapse that and I need to bring up the attribute window that we have used before. And when I have a feature selected, now I get this attachments section at the top of the attributes up here. So if I make that stay here. And I'm going to collapse the catalog window for now. I can now click this down arrow, and go to, open attachment manager. And I can now add and organize my attachments on this particular feature. So as I said, it's Butte County in California. And I have a picture that I want to add that's representative Butte County to me. For whatever work I'm doing. So I'm going to navigate to the folder and pasting it in the bottom and hitting enter, it takes me to the folder. And then I have this butte_county.JPG here. And so when I click okay, it's going to load that image into the database as an attachment to this feature. And so I'll click save edits. And it's all loaded in now. And now, in attachments, I can see there's a dropdown here. What else is really cool is that, we just glossed over the HTML pop-up in the past, but if I want to use an HTML pop-up to see the attributes on these features, on another feature it just shows the datatable, but on one that has attachments, it Shows us the attachments where it can, so this makes it a really great tool to explore and manage our data. And it also let's us keep all of our data for a project in one spot, it makes our geodatabase a true database where we store our data for a project. Also, now that our attachments are saved, I don't have to go back into the editing environment just to see the attachments. If I click on the layer in the attribute table, I can load the attachments from the right-click menu on the layer. So select the layer there, right-click on the edge, and go to open attachment manager and I can see those attachments there. And for items that get opened up in external programs, I can just click on them here and click Open. So anything that gets opened in a program on my computer, I can open it straight from there. So I don't just see it in the HTML pop-up. Okay, let's close out of this and let's remove this from our map, and stop editing, and bring up the catalog video again. The last thing I want to show you is compacting a geodatabase. Compacting takes all the space that's been freed up in a geodatabase and actually clears it so it saves space on your Hard drive and most geo databases have this concept, but it works a little differently in each one. But know that if I was to delete something in my geo database or shorten an actual table significantly. It just marks those spots as free but the space isn't necessarily freed on your hard drive. So if I right click on geo database and go to administration. I can compact the database. And it runs a geoprocessing tool that handles this. I'll click OK and down at the bottom it's running it, and it's freeing up the space on my hard drive and compacting the geodatabase into a single unit for me. Okay, that's it for this lesson. In this lesson, I showed you some core concepts of geo-databases that transcend different geo-database types. So we talked about feature data sets, which you can use to ensure integrity of your data and specifically coordinate systems. I showed you about relationship classes, which you can use to make relates on your data Permanent. I showed you attaching information to your data to make your geodatabases a true central spot for your data, and then I showed you how to compact your geodatabases in order to free up extra space. In the next lesson, I'll show you specifically about file geodatabases and then we'll proceed from there to different storage environments. See you then.
