WEBVTT Kind: captions Language: en-US 00:00:05.069 --> 00:00:06.069 [Drew Decker] Hi. 00:00:06.069 --> 00:00:09.340 I am Drew Decker with U.S. Geological Survey. 00:00:09.340 --> 00:00:14.310 And welcome to today's Hydro Community Call. 00:00:14.310 --> 00:00:18.710 So today what we're going to be doing, having a very nice presentation by Annalisa Stasey 00:00:18.710 --> 00:00:19.710 with the USGS. 00:00:19.710 --> 00:00:21.330 She's the NHD Partner Support. 00:00:21.330 --> 00:00:25.609 Her topic will be on the new GeoPackage format. 00:00:25.609 --> 00:00:28.109 And Annalisa if you're ready. 00:00:28.109 --> 00:00:29.859 [Annalisa Stasey] Good morning, everybody. 00:00:29.859 --> 00:00:34.430 Welcome to the January 2022 hydrography community. 00:00:34.430 --> 00:00:40.340 Call my name is Analisa Stacy and I am a cartographer with the Hydrography Partners Support Section 00:00:40.340 --> 00:00:43.750 at the National Geospatial Technical Operations Center. 00:00:43.750 --> 00:00:49.920 In today's presentation, we will discuss the new GeoPackage format data we will be offering 00:00:49.920 --> 00:00:52.600 with our hydrography downloadable products. 00:00:52.600 --> 00:00:57.080 Greg Cocks will be serving as a co-presenter for today's presentation. 00:00:57.080 --> 00:01:02.670 Greg is the senior NHD Applied Researcher in the Topographic Applied Research Section 00:01:02.670 --> 00:01:03.670 (TARS). 00:01:03.670 --> 00:01:06.250 [Greg Cocks] Greg, please take it away. 00:01:06.250 --> 00:01:09.060 So GeoPackages is an OGC Standard. 00:01:09.060 --> 00:01:16.659 It's built on an SQLite database, and it has a particular schema with a spatial focus. 00:01:16.659 --> 00:01:21.229 You can read as well as I can, but just some quick background on it. 00:01:21.229 --> 00:01:29.009 It handles vector and raster datasets, and it has various extensions that allow it to 00:01:29.009 --> 00:01:33.400 handle things like tiling of both vector and raster datasets. 00:01:33.400 --> 00:01:38.400 Metadata in a particular way is a OGC format, as mentioned. 00:01:38.400 --> 00:01:44.050 And so people who would like to generate their own extensions are able to and they might 00:01:44.050 --> 00:01:45.729 then become part of the regular 00:01:45.729 --> 00:01:51.189 distribution of that dataset if it's considered worthwhile. 00:01:51.189 --> 00:01:54.320 One of the beauties of the GeoPackage, it's 140 terabytes. 00:01:54.320 --> 00:01:59.450 As far as I'm aware, nobody has hit that limit yet, but let's see. 00:01:59.450 --> 00:02:06.570 And it's also very useful in terms of cross-portability through open source and also ESRI and other 00:02:06.570 --> 00:02:10.460 proprietary software packages. 00:02:10.460 --> 00:02:15.770 Because it is a database container, it supports direct use that as you download one data package, 00:02:15.770 --> 00:02:19.320 there's no extract, transform load functionality necessary. 00:02:19.320 --> 00:02:22.580 There's no need to agglomerate various datasets into one. 00:02:22.580 --> 00:02:27.169 Once things of that nature that some things, like shapefile, often have to have. 00:02:27.169 --> 00:02:28.169 The USGS, 00:02:28.169 --> 00:02:37.370 in fact, the Department of Interior since 1953 - circular A16 - has been in place, last 00:02:37.370 --> 00:02:39.500 update, was 2016. 00:02:39.500 --> 00:02:44.530 And then there's a mandate executive order to basically provide our data to the public 00:02:44.530 --> 00:02:47.610 in the best accessible format. 00:02:47.610 --> 00:02:53.600 The GDA codified this through Congress, so now it's becoming even more prevalent. 00:02:53.600 --> 00:02:59.199 The main thing directing the use of GeoPackage or similar things is the Open Data Act. 00:02:59.199 --> 00:03:04.669 This was signed into law 2019, and the idea is that every dataset has to be available 00:03:04.669 --> 00:03:09.479 in a format that is accessible to everybody and especially formats 00:03:09.479 --> 00:03:12.200 that are not proprietary. 00:03:12.200 --> 00:03:16.500 The overriding intent, as it states here, is to foster greater public and private sector 00:03:16.500 --> 00:03:20.169 use of federal data to encourage innovative and data driven process. 00:03:20.169 --> 00:03:26.229 In a sense, it allows people like researchers, smaller companies that don't have access or 00:03:26.229 --> 00:03:32.330 the budgeting for proprietary software packages, things of that nature to proceed and still 00:03:32.330 --> 00:03:36.519 use the data and make it accessible. 00:03:36.519 --> 00:03:42.510 USGS has been investigating the GeoPackage in various forms, and it's being used across 00:03:42.510 --> 00:03:44.479 the agency. 00:03:44.479 --> 00:03:50.310 My efforts a couple of years back were directed to look into seeing using GeoPackage that 00:03:50.310 --> 00:03:57.090 -step one back - to look into a nonproprietary format and GeoPackage was decided as the most 00:03:57.090 --> 00:03:58.170 suitable format, 00:03:58.170 --> 00:04:04.100 rather than, say, Postgres and PostGIS and things of that nature. 00:04:04.100 --> 00:04:05.340 And now we're back to Annalisa. 00:04:05.340 --> 00:04:06.340 Great. 00:04:06.340 --> 00:04:07.630 Thank you so much, Greg. 00:04:07.630 --> 00:04:10.790 Thank you for the background on why we're using GeoPackage. 00:04:10.790 --> 00:04:16.729 And now we're going to discuss what changes users will notice with the new GeoPackage 00:04:16.729 --> 00:04:17.729 format. 00:04:17.729 --> 00:04:21.100 [Annalisa Stasey] We will offer GeoPackage format data for all 00:04:21.100 --> 00:04:27.160 hydrography, products including NHD, WBD and NHDPlus HR. 00:04:27.160 --> 00:04:33.450 GeoPackage is an additional product offering, so geodatabase and shapefile format products 00:04:33.450 --> 00:04:36.480 will still be available for download. 00:04:36.480 --> 00:04:40.810 If you are more comfortable using geodatabase data, then please continue to download your 00:04:40.810 --> 00:04:43.430 data in that format. 00:04:43.430 --> 00:04:48.590 The geopackage is a nonproprietary format, meaning it is not tied to a single software 00:04:48.590 --> 00:04:49.720 package. 00:04:49.720 --> 00:04:55.900 In contrast, geodatabases function best in ESRI software. 00:04:55.900 --> 00:05:02.000 GeoPackage is compatible with many software packages, including QGIS, which is free. 00:05:02.000 --> 00:05:03.460 Users who manipulate hydrography 00:05:03.460 --> 00:05:09.360 data using programming tools such as R and Python will find some benefits to utilizing 00:05:09.360 --> 00:05:14.030 the GeoPackage over geodatabases and shapefiles. 00:05:14.030 --> 00:05:20.790 The GeoPackage is better at handling large table operations and does not have lock files. 00:05:20.790 --> 00:05:26.790 Most users are familiar with ArcPro and ArcMap, so we're going to illustrate the differences 00:05:26.790 --> 00:05:30.780 you will see when utilizing GeoPackage data in ArcMap. 00:05:30.780 --> 00:05:35.210 Here is a comparison chart displaying the differences between Geodatabase and GeoPackage 00:05:35.210 --> 00:05:37.420 format products. 00:05:37.420 --> 00:05:42.440 Feature classes and tables are supported in the GeoPackage format. 00:05:42.440 --> 00:05:47.310 Feature datasets are not supported in the GeoPackage format. 00:05:47.310 --> 00:05:52.460 Relationship classes are not supported in the GeoPackage format, but users then can 00:05:52.460 --> 00:05:55.930 create these manually if they wish. 00:05:55.930 --> 00:06:01.770 All attributes with coded value domains will have a new attribute added. 00:06:01.770 --> 00:06:07.550 The new attribute will be the name of the attribute plus underscored description. 00:06:07.550 --> 00:06:12.400 The existing attribute will contain the integer value, and the new attribute will contain 00:06:12.400 --> 00:06:16.410 the domain description text from the coded value domain. 00:06:16.410 --> 00:06:25.680 Lastly, geometric networks are not supported for NHD and NHDPlus HR, HU4, HU8 level GeoPackage 00:06:25.680 --> 00:06:28.280 format products. 00:06:28.280 --> 00:06:32.440 Feature classes and table names will look different. 00:06:32.440 --> 00:06:36.690 Now we will discuss some of the differences you'll see with the new GeoPackage format 00:06:36.690 --> 00:06:38.840 hydrography data. 00:06:38.840 --> 00:06:44.750 Once you extract the data and loaded into ArcMap, it will look similar to a geodatabase. 00:06:44.750 --> 00:06:48.050 The overall structure for the data will be the same. 00:06:48.050 --> 00:06:51.840 The number of feature classes and tables will be identical. 00:06:51.840 --> 00:06:58.460 The number of features in the feature classes and tables will be identical between formats. 00:06:58.460 --> 00:07:02.500 GeoPackaged feature classes and tables will have the word 'main' appended onto them when 00:07:02.500 --> 00:07:05.380 loaded into ArcMap and ArcPro. 00:07:05.380 --> 00:07:07.960 This is an ESRI construct and cannot be removed. 00:07:07.960 --> 00:07:10.280 It will not affect the product in any way. 00:07:10.280 --> 00:07:16.130 It is simply a naming convention used by ESRI for GeoPackaged products. 00:07:16.130 --> 00:07:23.130 Linked here is an ESRI document on how to use OGC GeoPackages in ArcGIS Pro. 00:07:23.130 --> 00:07:28.530 The graphic on the left displays the GeoPackage product when loaded into ArcCatalog. 00:07:28.530 --> 00:07:34.470 As you can see, the word 'main' is appended onto all feature classes and table names. 00:07:34.470 --> 00:07:37.320 This will not affect the functionality of the product. 00:07:37.320 --> 00:07:43.590 In QGIS, the GeoPackage product displays as expected with no additional characters appended 00:07:43.590 --> 00:07:47.780 onto the feature class or table name. 00:07:47.780 --> 00:07:51.090 GeoPackage extents must be calculated in ArcMap. 00:07:51.090 --> 00:07:54.230 The extent is the display boundary of the data. 00:07:54.230 --> 00:07:58.620 When GeoPackage data is loaded into ArcMap, users will be prompted to select whether they 00:07:58.620 --> 00:08:05.500 want to calculate the extent using the input extent or the spatial references domain extent. 00:08:05.500 --> 00:08:10.150 If you do nothing and wait, it will calculate the extent on its own. 00:08:10.150 --> 00:08:14.830 We suggest that users do not take any action at this point in. 00:08:14.830 --> 00:08:19.010 In ArcPro the software will calculate the extent on its own. 00:08:19.010 --> 00:08:23.120 Users are not prompted to select an extent in ArcPro. 00:08:23.120 --> 00:08:29.260 Here is a video demonstration of what this process will look like. 00:08:29.260 --> 00:08:34.519 In this video, we will load in an NHD flow line feature class from the GeoPackage format 00:08:34.519 --> 00:08:37.550 NHD data into the map document. 00:08:37.550 --> 00:08:42.200 As you can see, it takes a few seconds for ArcMap to determine the layers extent. 00:08:42.200 --> 00:08:45.820 Once the extent is calculated, the data loads into the map document. 00:08:45.820 --> 00:08:53.240 GeoPackage uses lowercase attribute names and attribute casing within attribute tables 00:08:53.240 --> 00:08:58.020 is different between the Geodatabase and GeoPackage products. 00:08:58.020 --> 00:09:02.550 In the top graphic see the difference between the alias and the name of the field in the 00:09:02.550 --> 00:09:06.700 attribute table for the Geodatabase format product. 00:09:06.700 --> 00:09:11.190 The Geodatabase field names are in lowercase, but will display in camel case as seen in 00:09:11.190 --> 00:09:13.230 the alias field. 00:09:13.230 --> 00:09:17.820 Camel Case is a naming convention where the first letter of a word is capitalized and 00:09:17.820 --> 00:09:20.490 allows for mixed casing. 00:09:20.490 --> 00:09:24.830 This change occurred as part of the database migration. 00:09:24.830 --> 00:09:29.670 The GeoPackage product will contain only lowercase attribute names. 00:09:29.670 --> 00:09:35.000 The lower graphic displays no difference between the alias and name of the fields for GeoPackage 00:09:35.000 --> 00:09:36.000 format products. 00:09:36.000 --> 00:09:37.630 They will be lowercase. 00:09:37.630 --> 00:09:43.120 We talked about this on the October 2021 Hydrography Community Call. 00:09:43.120 --> 00:09:47.000 [Annalisa Stasey] This change was necessary as part of a database 00:09:47.000 --> 00:09:52.480 migration that occurred in conjunction with the new data model release. 00:09:52.480 --> 00:09:56.930 You can review this presentation on the USGS YouTube channel. 00:09:56.930 --> 00:10:01.370 Unique identifiers must be selected in ArcMap for GeoPackage. 00:10:01.370 --> 00:10:05.020 When GeoPackage table data is loaded into ArcMap, 00:10:05.020 --> 00:10:10.320 users will be prompted to select the unique identifier field for the data, select Object 00:10:10.320 --> 00:10:12.690 I.D. and click Finish. 00:10:12.690 --> 00:10:16.010 Please note that users will not need to take this action in ArcPro. 00:10:16.010 --> 00:10:20.830 Next, we will see a video demonstration of what this looks like. 00:10:20.830 --> 00:10:26.120 We will load the NHD, reachcode maintenance table into an ArcMap document. 00:10:26.120 --> 00:10:31.491 When you drop the table into the map document, it prompts the user to select the unique identifier 00:10:31.491 --> 00:10:33.310 field for the data. 00:10:33.310 --> 00:10:34.350 Click 'Finish'. 00:10:34.350 --> 00:10:37.200 The table then loads successfully. 00:10:37.200 --> 00:10:38.200 In ArcPro 00:10:38.200 --> 00:10:42.940 the software will calculate the unique identifier field on its own. 00:10:42.940 --> 00:10:47.700 Users are not prompted to select a unique identifier field when utilizing GeoPackage 00:10:47.700 --> 00:10:49.700 data in ArcPro. 00:10:49.700 --> 00:10:55.450 Coded domain values are not supported in GeoPackage. 00:10:55.450 --> 00:10:56.450 Attribute 00:10:56.450 --> 00:11:02.050 fields containing coded value domains will contain the coded value in integer form. 00:11:02.050 --> 00:11:08.800 A new description field that contains descriptive text of the coded value domain is added to 00:11:08.800 --> 00:11:11.240 the attribute table. 00:11:11.240 --> 00:11:14.900 The description fields are the text description of the coded value that was listed 00:11:14.900 --> 00:11:16.300 in the domain. 00:11:16.300 --> 00:11:20.440 For the entire list of coded value domains, please see the model poster for the product 00:11:20.440 --> 00:11:22.000 of interest. 00:11:22.000 --> 00:11:25.850 These can be found on the National Hydrography web page. 00:11:25.850 --> 00:11:30.300 The number of records in the files are the same, but the number of attributes in feature 00:11:30.300 --> 00:11:36.190 classes with coded value domains will increase to include the description fields. 00:11:36.190 --> 00:11:43.190 As we can see here, the Fcode field contains the numerical value of the Fcode and the 'Fcode 00:11:43.190 --> 00:11:49.220 underscored description' field contains the text description of that value. 00:11:49.220 --> 00:11:56.100 The NHD Flow Line feature class contains several description fields for the coded value domain. 00:11:56.100 --> 00:12:03.040 In this demonstration, we will load the NHD Flow Line Feature class into an ArcMap document 00:12:03.040 --> 00:12:05.220 and view the attribute table. 00:12:05.220 --> 00:12:10.580 ArcMap will prompt the user to select an extent. 00:12:10.580 --> 00:12:14.529 If you wait, it will automatically load the data. 00:12:14.529 --> 00:12:22.300 Once the data loads, it will function like a normal feature class in a geodatabase. 00:12:22.300 --> 00:12:27.250 You can open the attribute table by right-clicking the feature class. 00:12:27.250 --> 00:12:31.890 Here we open the feature class and view the attribute table where you will notice the 00:12:31.890 --> 00:12:33.800 differences. 00:12:33.800 --> 00:12:35.970 The field names are all lowercase. 00:12:35.970 --> 00:12:39.310 You will notice the new underscore description fields. 00:12:39.310 --> 00:12:43.600 Users may choose to move the description fields next to the original coded value domain fields, 00:12:43.600 --> 00:12:47.490 so it is easier to crosswalk the value with the description text fields. 00:12:47.490 --> 00:12:53.790 Coded value domains are listed on the NHD model version 2.3 poster and are broken into 00:12:53.790 --> 00:12:59.140 two categories feature code domains and non feature code domains. 00:12:59.140 --> 00:13:02.870 The download link to this poster is found on the slide. 00:13:02.870 --> 00:13:06.830 Coded value domains listed on the NHDPlus HR model 00:13:06.830 --> 00:13:14.200 version 2.0 poster include many of the ones listed on the NHD model poster. 00:13:14.200 --> 00:13:19.030 Additional coded value domains specific to NHDPlus HR are listed here. 00:13:19.030 --> 00:13:26.870 Coded value domains are listed on the WBD model version 2.3 poster. 00:13:26.870 --> 00:13:30.080 GeoPackage does not support relationship classes. 00:13:30.080 --> 00:13:38.850 Relationship classes are contained within the NHD, WBD, and NHDPlus HR geodatabase products. 00:13:38.850 --> 00:13:44.040 Here's a screenshot of the relationship classes from the NHD model poster. 00:13:44.040 --> 00:13:49.560 The relationship classes are used to navigate the various metadata tables within the NHD 00:13:49.560 --> 00:13:50.560 data. 00:13:50.560 --> 00:13:55.769 Relationship classes are not supported in GeoPackage, but can easily be created by the 00:13:55.769 --> 00:13:57.672 user using relates in ArcMap or ArcPro. 00:13:57.672 --> 00:14:06.019 For example, users can build freely from the NHD Flow Line feature class to the NHD metadata 00:14:06.019 --> 00:14:11.510 table using 'permid' and 'metaprocessID'. 00:14:11.510 --> 00:14:14.380 GeoPackage does not support feature datasets. 00:14:14.380 --> 00:14:20.300 Geodatabase products contain feature datasets, which are an ESRI construct. 00:14:20.300 --> 00:14:23.220 GeoPackage does not support feature datasets. 00:14:23.220 --> 00:14:28.930 The picture below shows the catalog view for the NHD geodatabase. 00:14:28.930 --> 00:14:35.360 Hydrography and WBD feature datasets exist in the NHD geodatabase data. 00:14:35.360 --> 00:14:39.200 These will not be present in the GeoPackaged data. 00:14:39.200 --> 00:14:42.590 GeoPackage does not support geometric networks. 00:14:42.590 --> 00:14:50.589 Geometric networks are found in NHD and NHDPlus HR HU4, HU8 geodatabase data and can be used 00:14:50.589 --> 00:14:52.230 in ArcMap. 00:14:52.230 --> 00:14:58.230 The geometric network is an ESRI construct and will not exist in GeoPackaged data. 00:14:58.230 --> 00:15:01.950 ArcPro utilizes the Trace Network. 00:15:01.950 --> 00:15:08.980 We've talked a lot about what GeoPackage does not support. 00:15:08.980 --> 00:15:13.510 The GeoPackage will have a populated flow table. 00:15:13.510 --> 00:15:19.399 The NHD flow table is populated in GeoPackage products at the HU4 and HU8 level for NHD 00:15:19.399 --> 00:15:23.019 products, that will contain an added description field, 00:15:23.019 --> 00:15:25.710 but will function similarly to the geodatabase products. 00:15:25.710 --> 00:15:31.880 Keep in mind that the NHD flow table is not populated at the state level. 00:15:31.880 --> 00:15:38.910 To reiterate, the NHD flow table will only be populated at the HU4 and HU8 levels. 00:15:38.910 --> 00:15:46.230 The NHDPlus flow table will be populated for the HU4 and HU8 level GeoPackaged products 00:15:46.230 --> 00:15:48.560 in the NHDPlus HR. 00:15:48.560 --> 00:15:53.760 The populated flow table will allow you to perform network analyzes and network trace 00:15:53.760 --> 00:15:55.610 independently of ArcMap. 00:15:55.610 --> 00:16:01.790 All GeoPackaged products will be larger than their geodatabase counterpart. 00:16:01.790 --> 00:16:06.410 This is due to the additional description fields contained in the data. 00:16:06.410 --> 00:16:11.170 The shapefile format will be the largest of the three. 00:16:11.170 --> 00:16:15.940 GeoPackage format products will be available from the downloadable products directory, 00:16:15.940 --> 00:16:19.760 ScienceBase and The National Map. 00:16:19.760 --> 00:16:22.899 During the October Hydrography Community Call, 00:16:22.899 --> 00:16:28.730 we discussed changes to the hydrography downloadable products folder structure. 00:16:28.730 --> 00:16:34.310 During that call, we also mentioned the Geopackage format that will soon be released. 00:16:34.310 --> 00:16:39.470 Let's quickly review the downloadable products folder structure changes. 00:16:39.470 --> 00:16:43.860 The Red X's indicate folders that are being removed. 00:16:43.860 --> 00:16:48.970 The green hatched folders indicate new folders that are being added. 00:16:48.970 --> 00:16:50.500 For NHD we will 00:16:50.500 --> 00:16:56.490 remove the high-resolution folders and add Geopackage folders as this data is produced. 00:16:56.490 --> 00:16:59.920 This will make downloading NHD data less confusing. 00:16:59.920 --> 00:17:03.020 For NHDPlus HR. 00:17:03.020 --> 00:17:07.699 we will remove the beta folder and replace it with a VPU folder containing current and 00:17:07.699 --> 00:17:10.079 archive folders. 00:17:10.079 --> 00:17:16.730 Existing data will be placed in the current folder and moved to archive as it is refreshed. 00:17:16.730 --> 00:17:21.989 We will also populate the GeoPackage folder as this data is produced. 00:17:21.989 --> 00:17:25.909 Raster data will be contained in a separate folder. 00:17:25.909 --> 00:17:29.519 These changes will benefit our users in several ways. 00:17:29.519 --> 00:17:36.990 First, there will be less confusion between the downloads of the NHD and NHDPlus HR products. 00:17:36.990 --> 00:17:43.489 Second, by removing the high-resolution folder, it will be easier to access NHD data. 00:17:43.489 --> 00:17:53.429 Third, NHD, WBD and NHDPlus HR will be released in the GeoPackage format over the coming months. 00:17:53.429 --> 00:17:58.529 Future Geopackage products will be written to a new Geopackage folder as they are published. 00:17:58.529 --> 00:18:04.400 And lastly, these changes are needed to support new product versions for an NHDPlus HR which 00:18:04.400 --> 00:18:06.470 will soon be released. 00:18:06.470 --> 00:18:09.879 In the first phase of implementation 00:18:09.879 --> 00:18:14.269 we will re-baseline the entire system and update the folder structure. 00:18:14.269 --> 00:18:20.889 We will generate all NHD downloadable hydrography products into the new folder directory and 00:18:20.889 --> 00:18:26.700 generate the new Geopackage products in addition to our typical product offerings of geodatabase 00:18:26.700 --> 00:18:28.360 and shapefile. 00:18:28.360 --> 00:18:30.049 During the first phase of implementation, 00:18:30.049 --> 00:18:43.090 we will update the WBD HU2, NHD HU4, NHD HU8 and NHD state products to include the new 00:18:43.090 --> 00:18:44.730 Geopackage format. 00:18:44.730 --> 00:18:48.869 We hope to have this phase complete by the end of January 2022. 00:18:48.869 --> 00:18:51.659 During the second phase of implementation, 00:18:51.659 --> 00:19:03.019 We will update the WBD National, NHD National, NHDPlus HR HU4, NHDPlus HR HU8, NHDPlus HR 00:19:03.019 --> 00:19:06.610 national products to include the new GeoPackage format. 00:19:06.610 --> 00:19:10.540 You will see these changes come live over the next few months. 00:19:10.540 --> 00:19:18.779 Here is a summary of differences and changes to expect with the new Geopackage format release. 00:19:18.779 --> 00:19:25.679 We will release Geopackage format data for all hydrography products including NHD, WBD, 00:19:25.679 --> 00:19:27.980 and NHDPlus HR. 00:19:27.980 --> 00:19:31.389 Coded domain values are not supported in Geopackage. 00:19:31.389 --> 00:19:36.700 Attribute fields containing coded value domains will contain the coded value in integer form. 00:19:36.700 --> 00:19:41.260 The new description field that contains descriptive text of the coded value domain will be added 00:19:41.260 --> 00:19:43.309 to the attribute table. 00:19:43.309 --> 00:19:47.679 All attribute names will be lowercase. 00:19:47.679 --> 00:19:53.289 Geometric networks are not supported in Geopackage and will not exist on any Geopackage products. 00:19:53.289 --> 00:19:58.239 Relationship classes are not supported in Geopackage and will not be included with the 00:19:58.239 --> 00:19:59.239 data. 00:19:59.239 --> 00:20:02.509 Users can create these on their own. 00:20:02.509 --> 00:20:03.509 Feature 00:20:03.509 --> 00:20:08.190 datasets are not supported in Geopackage and will no longer exist. 00:20:08.190 --> 00:20:15.179 The product will now contain a singular list of feature classes and tables in the Geopackage 00:20:15.179 --> 00:20:16.830 container. 00:20:16.830 --> 00:20:21.739 These products will function like geodatabases in ArcMap and ArcPro. 00:20:21.739 --> 00:20:22.739 Thank you. 00:20:22.739 --> 00:20:24.889 [Drew Decker] Thank you Annalisa, thank you Greg. 00:20:24.889 --> 00:20:30.350 A few questions that are starting to pop-up in the chat and we can cover those now. 00:20:30.350 --> 00:20:31.419 OK. 00:20:31.419 --> 00:20:38.190 [Greg Cocks] There were two questions in the chat for Annalisa. 00:20:38.190 --> 00:20:41.769 One: Will the tutorial video be created for 00:20:41.769 --> 00:20:45.049 how to use GeoPackage? 00:20:45.049 --> 00:20:48.909 [Annalisa Stasey] That is a good question. 00:20:48.909 --> 00:20:57.070 As I have not planned on creating a tutorial video, but rather pointing out further information 00:20:57.070 --> 00:20:59.399 on our National Hydrography web page. 00:20:59.399 --> 00:21:06.749 Maybe a tutorial might be something that is more relevant to put on the webpage. 00:21:06.749 --> 00:21:09.519 So thank you for that idea. 00:21:09.519 --> 00:21:15.190 And yes, more information about the GeoPackage will be coming out on the National Hydrography 00:21:15.190 --> 00:21:17.159 web page here in the next few weeks. 00:21:17.159 --> 00:21:20.929 [Greg Cocks] The second question was are the relationships 00:21:20.929 --> 00:21:22.820 set up as foreign keys in the GeoPackage 00:21:22.820 --> 00:21:24.049 SQLite database? 00:21:24.049 --> 00:21:28.669 [Annalisa Stasey] We don't have any relationships start up in 00:21:28.669 --> 00:21:32.059 the geo package products at this time. 00:21:32.059 --> 00:21:36.570 Users can create those just as you would with a relate. 00:21:36.570 --> 00:21:41.690 However, Greg, I'm not as familiar with the additional functionality of GeoPackage. 00:21:41.690 --> 00:21:44.269 Do you know any more about that? 00:21:44.269 --> 00:21:47.960 [Greg Cocks] I think what Fred is asking is in RDBMs, you 00:21:47.960 --> 00:21:51.710 can have a primary key like a unique identifier. 00:21:51.710 --> 00:21:58.070 So there are going to be some unique identifiers and Annalissa is still working on these efforts 00:21:58.070 --> 00:22:01.999 to look into how to code those unique identifiers. 00:22:01.999 --> 00:22:03.710 There's not a question here. 00:22:03.710 --> 00:22:04.950 I can help with this one to Annalisa. 00:22:04.950 --> 00:22:09.059 It says, Are GeoPackages larger than file geodatbases? 00:22:09.059 --> 00:22:11.710 In my experience not really. 00:22:11.710 --> 00:22:16.869 But I think the normalizing by adding in the descriptions for all of the coded domain use 00:22:16.869 --> 00:22:19.000 is blowing it out a little bit. 00:22:19.000 --> 00:22:21.830 Annalisa and I were chatting about this this morning. 00:22:21.830 --> 00:22:28.570 The developers are going to be using vacuum or typically deflate to bring those down somewhat. 00:22:28.570 --> 00:22:30.639 Geopackages is an efficient format. 00:22:30.639 --> 00:22:32.489 So even if it is larger, it's not going to... 00:22:32.489 --> 00:22:37.409 I don't think there will be any speed impacted because they are attribute data, not vector 00:22:37.409 --> 00:22:38.409 data. 00:22:38.409 --> 00:22:40.320 Do you have anything to add there, Annalisa? 00:22:40.320 --> 00:22:43.299 [Annalisa Stasey] Nope, we're still doing a little bit of final 00:22:43.299 --> 00:22:47.240 tweaking on the way that we're compressing the data. 00:22:47.240 --> 00:22:53.309 As Greg said, we're looking at using deflate instead of vacuum to do that. 00:22:53.309 --> 00:22:59.509 We're currently seeing the GeoPackage product be quite a bit bigger than the Geodatabase, 00:22:59.509 --> 00:23:05.299 so we're hoping to bring down that size differential a little bit. 00:23:05.299 --> 00:23:09.489 [Greg Cocks] And with all of these processes, the first 00:23:09.489 --> 00:23:15.460 couple of versions at the gate need to be tweaked and refined as Annalisa procedes the 00:23:15.460 --> 00:23:18.720 breaking developments. 00:23:18.720 --> 00:23:20.590 There was another question here, Annalisa. 00:23:20.590 --> 00:23:25.909 Given that GeoPackage format is not cloud optimized will the USGS develop software that 00:23:25.909 --> 00:23:34.009 allows users to subset data sets on the fly. 00:23:34.009 --> 00:23:37.850 My particular approach to that was trying to do that would be to maybe use the national 00:23:37.850 --> 00:23:44.799 dataset and to use the web services, maybe approach it in that direction. 00:23:44.799 --> 00:23:52.269 The data sets themselves are - GeoPackage is very efficient if you're using the software 00:23:52.269 --> 00:23:55.649 so that subsetting, you might be able to do that within the software 00:23:55.649 --> 00:23:56.649 itself. 00:23:56.649 --> 00:24:00.009 My understanding is there is no plans currently to do that. 00:24:00.009 --> 00:24:05.249 All right, note that in Alasks they are not HU4s s they are HU8s because of the aerial 00:24:05.249 --> 00:24:07.849 extent of the Alaskan HUCs. 00:24:07.849 --> 00:24:14.289 So the dataset size will be a different HUC level, but it'll be kind of a similar 00:24:14.289 --> 00:24:15.590 dataset size. 00:24:15.590 --> 00:24:18.489 If that makes sense. 00:24:18.489 --> 00:24:21.240 I think that's all the questions Drew. 00:24:21.240 --> 00:24:25.669 [Drew Decker] Any other questions feel free to speak up 00:24:25.669 --> 00:24:31.019 right up to the chat and will cover them here. 00:24:31.019 --> 00:24:32.179 We don't have any. 00:24:32.179 --> 00:24:33.349 You could. 00:24:33.349 --> 00:24:36.190 We'll go ahead and oh, here we go. 00:24:36.190 --> 00:24:37.320 Here's another word. 00:24:37.320 --> 00:24:42.940 You mentioned that the state extracts would be available in GeoPackage this month, will 00:24:42.940 --> 00:24:46.989 state extracts in geodatabase also be available? 00:24:46.989 --> 00:24:50.890 [Annalisa Stasey] Yes, we're very excited about that. 00:24:50.890 --> 00:24:55.659 It's been over a year and we will finally be regenerating the state extracts. 00:24:55.659 --> 00:25:01.309 So I'm really hoping we can have that all out by the end of end of the month and every 00:25:01.309 --> 00:25:04.080 all of the formats will generate concurrently. 00:25:04.080 --> 00:25:10.960 So if we're going to regenerate GeoPackage, of course, the Geodatabase and shapefile extracts 00:25:10.960 --> 00:25:11.960 will be regenerated. 00:25:11.960 --> 00:25:13.239 as well. 00:25:13.239 --> 00:25:16.019 [Drew Decker] Another question. 00:25:16.019 --> 00:25:19.960 Will state geodatabases have geometric networks? 00:25:19.960 --> 00:25:24.769 [Annalisa Stasey] No state geodatabases will not have geometric 00:25:24.769 --> 00:25:25.769 networks. 00:25:25.769 --> 00:25:26.769 No they will not. 00:25:26.769 --> 00:25:29.599 You can generate it on your own, though, using the utilities. 00:25:29.599 --> 00:25:36.369 [Drew Decker] OK, well, Annalisa and Greg thank you guys 00:25:36.369 --> 00:25:40.409 very much for the for the presentation and helping answer the questions 00:25:40.409 --> 00:25:41.409 , really. 00:25:41.409 --> 00:25:43.629 What I would like to do for the moment. 00:25:43.629 --> 00:25:47.389 Switch gears to some announcements. 00:25:47.389 --> 00:25:53.609 For today, I would like to begin with Kevin McNinch, who has an announcement he wants 00:25:53.609 --> 00:25:55.419 to share with everybody. 00:25:55.419 --> 00:25:56.919 [Kevin McNinch] Yeah, thanks. 00:25:56.919 --> 00:25:57.919 Thanks, Drew. 00:25:57.919 --> 00:26:02.830 Yeah, we just wanted to make an announcement for an upcoming change to some of the map 00:26:02.830 --> 00:26:05.440 services. 00:26:05.440 --> 00:26:15.460 So we do host ArcGIS server, dynamic map services for hydrography for the NHD, WBD, and NHDPlus 00:26:15.460 --> 00:26:16.460 HR. 00:26:16.460 --> 00:26:19.499 So, if you're not aware of these, this is a public service. 00:26:19.499 --> 00:26:24.399 These are available and you're more than welcome to use these, and they do have some good utility, 00:26:24.399 --> 00:26:26.989 especially for quickly finding some some data without having 00:26:26.989 --> 00:26:27.989 to download. 00:26:27.989 --> 00:26:32.879 But we do have this NHDPlus HR service that I'm just going to open the description up 00:26:32.879 --> 00:26:34.179 real quick. 00:26:34.179 --> 00:26:37.980 And we are going to do some changes to this, probably in February. 00:26:37.980 --> 00:26:42.509 Just wanted to kind of let everyone know ahead of time that we're going to be changing this 00:26:42.509 --> 00:26:43.509 map service. 00:26:43.509 --> 00:26:46.989 We're going to be adding some more data and updating the data in it as well and making 00:26:46.989 --> 00:26:49.200 it much more up to date. 00:26:49.200 --> 00:26:52.119 But there could be an impact through the layers that we have here. 00:26:52.119 --> 00:26:57.250 So the real announcement is just be aware if you're using this map service in code or 00:26:57.250 --> 00:26:59.849 in a geoprocessing service or something. 00:26:59.849 --> 00:27:03.349 We're trying to minimize the impact, but we're going to add some more layers and it may change 00:27:03.349 --> 00:27:04.489 the index order of these. 00:27:04.489 --> 00:27:12.029 So if you access this service using the index order of these layers, you may have a change 00:27:12.029 --> 00:27:13.029 to deal with. 00:27:13.029 --> 00:27:14.029 Just as an FYI. 00:27:14.029 --> 00:27:16.529 We will be publishing a news article. 00:27:16.529 --> 00:27:21.981 So if you're not aware of the news site on the USGS.gov National Hydrography page, we 00:27:21.981 --> 00:27:26.169 have news articles that we published that get summarized in a newsletter that can set 00:27:26.169 --> 00:27:31.059 out, but we will be publishing the full details here as we finalize them, probably 00:27:31.059 --> 00:27:32.059 within the next month. 00:27:32.059 --> 00:27:34.070 And that's all I had. 00:27:34.070 --> 00:27:35.309 So thanks, Drew. 00:27:35.309 --> 00:27:36.559 [Drew Decker] OK. 00:27:36.559 --> 00:27:40.039 Any other announcements, that anyone has? 00:27:40.039 --> 00:27:44.990 Think we've got everything covered, those no, no announcements. 00:27:44.990 --> 00:27:48.809 Again, thank you very much, and Annalisa and Greg. 00:27:48.809 --> 00:27:50.989 Great presentation. 00:27:50.989 --> 00:27:51.989 So thanks. 00:27:51.989 --> 00:27:52.509 Have a great day.