get_padus() layers do not match PAD-US national geopackage layers

[kevinwolz]

I am trying to create a version of get_padus() that reads local data from the geopackage and arrives at the same end result as get_padus() with remote data.

get_padus() allows selection of one or more "layers" to download. However, the PAD-US national geopackage downloaded from HERE has a totally different set of "layers":

sf::st_layers("PADUS3_0Geopackage.gpkg")

Driver: GPKG 
Available layers:
                                                     layer_name geometry_type features fields                                            crs_name
1                                                   PADUS3_0Fee Multi Polygon   247507     41 USA_Contiguous_Albers_Equal_Area_Conic_USGS_version
2                                           PADUS3_0Designation Multi Polygon    18736     41 USA_Contiguous_Albers_Equal_Area_Conic_USGS_version
3                                              PADUS3_0Easement Multi Polygon   170267     52 USA_Contiguous_Albers_Equal_Area_Conic_USGS_version
4                                          PADUS3_0Proclamation Multi Polygon     3360     41 USA_Contiguous_Albers_Equal_Area_Conic_USGS_version
5 PADUS3_0Combined_Proclamation_Marine_Fee_Designation_Easement Multi Polygon     3360     43 USA_Contiguous_Albers_Equal_Area_Conic_USGS_version
6                                                PADUS3_0Marine Multi Polygon     3360     55 USA_Contiguous_Albers_Equal_Area_Conic_USGS_version
7            PADUS3_0Combined_DOD_TRIB_Fee_Designation_Easement Multi Polygon   438113     43 USA_Contiguous_Albers_Equal_Area_Conic_USGS_version
> 

I am very confused with how the layers in the remote data line up with the data in the local data. It seems like many of the "layers" described by get_padus() (e.g. Manager_Name, Manager_Type) are actually "fields" in many of the "layers" within the geopackage.

Any insight on this generally would be much appreciated. In addition, I would suggest adding some explanation around this to the documentation of get_padus().

[bocinsky]

Hi @kevinwolz. Thanks for your note, and for identifying the apparent discrepancies between the PAD-US downloadable data and the PAD-US web services. I don't have any insights into why these discrepancies exist. Happy to clarify (int he documentation) that the data from the various sources are structured differently.

[kevinwolz]

@bocinsky I think THIS on the web services page suggests that the web services layers for Manager_Type, Manager_Name, and Federal_Management_Agencies all come from the "combined" layer in the core database, which I think would correspond to the PADUS3_0Combined_DOD_TRIB_Fee_Designation_Easement layer in the downloadable data.