[MUSIC] Hello, everyone and welcome back. In this lesson, I'm going to show you personal geo databases. They're really similar to file geo databases in many ways but they have a few key differences. So, we're going to walk-through them. Once again I'll show you how you can send personal geo databases Also show you a bit about making and saving queries in personal geo databases and a bit about the different limits in personal geo databases. Okay, let's get started. So, just as a refresher, personal geodatabases and file geodatabases look the same. They have the same icon in arc map but they're actually very different storage formats under the hood. File geodatabases are fully and as restored format and personal geodatabases use an old access format. Microsoft Access which is a database system. They use an old MDB geodatabase format. And what that is is it's a Access 2003 database. And Esri ArcMap adds in a bunch of information that enables it as a spatial database. So it's still a valid Access database, but it is also a geodatabase. And I'll show that to you in just a second. So, when we expand them we see very similar things to what we see in file geo databases. We have feature classes we can also store, rosters, and feature data sets and tables just like we can in file geo databases. As I said in the last Lecture. You might not want to store rasters. Because they'll fill up your 2GB file size limit in your personal geodatabase very quickly though. A common work flow I'll need or I'll use when I need a personal geodatabase is I'll store all of the data that I want. To be relational, so that all the feature information and all the tables in a personal geodatabase. And then I'll store my rasters in a file geodatabase next to it. So I'll end up with a two-database system, but it works, and I get the personal and geodatabase advantages for the feature classes and I'll show you what those are in just a second. So just like last time, let's take a look at what it takes to send a personal geo database. So in Windows we see instead of the Windows file folder that we see for file geo databases, we see a Microsoft access database. File and then we also see a lock file since I have it open in ArcMap. It locks the records in the geo data base. But we can still open it and the nice thing is that this is the only file that's necessary if I want to send this to somebody. I can just Share this whole file with them. If I have Dropbox, or Google Drive, or something, I can just share this file, and they have all of the information they need to have the whole geo-database, whereas with the file geo-database, remember, we had to zip or compress the whole folder in order to send it to somebody. So I can double-click it to open it up, because Microsoft Access is registered as the File handler for this, so it means that when I double click it Microsoft Acess intervenes and opens it up. As I said it's a standard Microsoft access file just with some spacial extensions that ArcMap adds in. And when it opens up I see those special objects. So I see these tables. It organizes them for me into tables and my feature classes show up as just tables and. Microsoft Access, so I see all these geodatabase specific items then it has some, some tables for selections as well. And then I see my protected areas 2015 data set. So let's view that side by side with ArcMap here. And so we see these two items are the same thing. And I can view it in ArcMap. But I can also open up the data table in Microsoft Access here and view it all and just like in ArcMap, the shape field stores all of the feature information. And then I can see all of the rest of the record information as well by just scrolling over to the right. Now, one thing I should point out is that I couldn't have just created a database within Access and then open it in ArcMap as a spatial geodatabase. If I create a Microsoft Access database and try to open it in ArcMap, it will see tables in it potentially, but it will not be able to use it as a personal geo database. I have to create personal geodatabases from within the catalog window here. Only then can I open them in Access and see them as an Access database as well. So why am I showing you Microsoft Access here when we can already view all this data in ArcMap and we can view the feature information? Well, I think Microsoft Access is a great viewing and editing environment for a lot of your data. So if I wanted to change this data here, I could, and it writes the changes immediately for me so I can say that maybe. This was an error and this one was also. This field here was actually the same here. So I can edit it and that data updates for me, so I can edit really quickly, my attribute tables in Access and I just restore that value. But I can also create queries and relationships here. I can create relationship diagrams between my tables to view how they all relate to each other and I can also create reports. So, it has a reports wizards. It can automate reports for me so I can create all sorts of Advanced little application out of my personal geodatabases. So that they are both a data storage mechanism but also a little bit of an application. And if you're familiar with Microsoft Access already, that's a great little feature to have. And I can also create permanent queries in here. So I can go to the query design view and select the protected areas 2015 table and Close. And I'm going to just switch it over to the SQL view. You can use this query design editor if you like, but I'm going to switch over to the SQL view. And we're going to say where, let's see, that was, We want the owner name is 0720. And I'll confirm that field name here. Equals 0720. And now, I can run this query. Can run this query, and I get only where that criteria is met. So when I have this query, I can then switch back to the SQL view and make more edits to it and refine it and then I can save this query. So I can run it repeatedly and view the data this way. So it's almost, in a way, it's like saving a selection where I view the data table but I can come back to it later, this exact selection all the time. And if things change, I can View it in Access that way. So, I'll view it as a datasheet which is the same as running it. So then, I'll save this query and I'll say owner 0720 is the query. And, over here, on the left side, I get a query section where I have owner 0720 so I can close this out and I can be browsing the I can be browsing my data table but then if I want to go just subset it immediately to that query that I wrote that's of interest to me. I can double click it and run that query immediately against the live data. Microsoft Access is a subject all on its own, so I'm not going to go deeper than that right now, but just know that there's a lot of power in having a geo database that is also an Access database. So I'm going to close out of Access here. And we'll come back in and I just want to point out one other thing, which is that in select by attributes, we get different operators when we are looking at data from a personal geo database versus a file geo database. So notice these brackets around the field names here. Let's close this out. And bring in the California counties layer again, pin that. And if I go to select by attributes on, so this is protected areas 2015 and if I go to California counties I don't need field delimiters around them. So, if I double click them it doesn't have that. But, for personal geo databases, I need to surround my fields in brackets. And it's just one of those things where each has different data storage back end engines. And to satisfy those query engines in the personal geo databases versus the file geo databases, we have to format our queries slightly differently. And I just want to point out that that's something to get used to. But that's also why I encourage you to use the double click query builder here because then you never are wondering if you got your fields right, because I like to type in queries myself but I probably would have typed in Own_Name here rather than putting in the brackets around it. And double clicking saves me from making those mistakes. Okay. That's all I have to show you about personal geo databases right now. They support many of the same things that file gio databases do, including feature datasets but they have a few caveats and a few advantages. Namely that they have that two gigabyte file size limit, but they are also a fully fledged Access database to use for all your queries and any sorts of little mini applications you want to create in your Access database through reporting and forms and things like that. It's also really nice to be able to send a single file to somebody if you want to share it. I think that they are really great for small projects where you have a lot of data tables or future classes that you want to relate to each other. They're a great central storage piece to those kinds of projects which you can expand with other file geo databases as you need. One thing to note is that these are going away. So, Esri has stated that they're not really going to be supporting these in the long run, and you can't create them right now with an ArcGIS Pro. You can use them, but you can't create them in ArcGIS Pro. So, they're sort of becoming a legacy item, but they're being replaced with other options in the long run. They're still useful for now and worth you knowing about though. Okay, in the next lecture, we're going to learn a little bit about shape files so I'll see you there.
