From bf6b4c355467b726a7c36a5ab44e5c6b6e54f74a Mon Sep 17 00:00:00 2001 From: justinkadi Date: Fri, 7 Mar 2025 18:59:06 +0000 Subject: [PATCH 1/2] Adding chapter on spatialVector data --- workflows/misc_file_types/spatialVector.Rmd | 165 ++++++++++++++++++++ 1 file changed, 165 insertions(+) create mode 100644 workflows/misc_file_types/spatialVector.Rmd diff --git a/workflows/misc_file_types/spatialVector.Rmd b/workflows/misc_file_types/spatialVector.Rmd new file mode 100644 index 00000000..b32f97d3 --- /dev/null +++ b/workflows/misc_file_types/spatialVector.Rmd @@ -0,0 +1,165 @@ +## Spatial vector data + +### About + +Spatial vector files are geospatial files that represent geographic features using points, lines, and polygons. Spatial vector files can include GeoJSON (.json), ESRI shapefiles (.shp), GeoPackage (.gpkg), GeoParquet (.parquet), Google Keyhole Markup Language (.kml, .kmz), etc. + +### Processing `spatialVector` entities + +In addition to the usual metadata information we'll need (description, attributes, physical), we'll need some additional metadata to create a `spatialVector` entity. In particular, we'll need to know the *geometry* and *coordinate reference system* of the file. + +To do this, we can either get this information from the submitter directly or upload the vector file into QGIS (or another GIS software) to explore its metadata. Otherwise, it will take some extra sleuthing and file processing in R from our end. Here we'll go over some techniques to gather this information from vector files. Then, we'll show how to create a `spatialVector` entity within an EML doc. + +We'll start by setting our node, reading in the data package, and gathering the PID of our geospatial file: + +```{r, eval=FALSE} +library(sf) +library(dataone) +library(datapack) +library(uuid) +library(arcticdatautils) +library(EML) + +### Set up node and gather data package +d1c <- dataone::D1Client("...", "urn:node:...") # Setting the Member Node +resourceMapId <- "..." # Get data package PID (resource map ID) +dp <- getDataPackage(d1c, identifier = resourceMapId, lazyLoad = TRUE, quiet = FALSE) # Gather data package + +### Load in Metadata EML +metadataId <- selectMember(dp, name="sysmeta@formatId", value="https://eml.ecoinformatics.org/eml-2.2.0") # Get metadata PID +doc <- read_eml(getObject(d1c@mn, metadataId)) # Read in metadata EML file + +### Read in spatial vector file +spatial_vector_pid <- selectMember(dp, "sysmeta@fileName", "exampleFile.zip") +``` + +#### Reading in the vector file + +We'll first need to read in the vector file to extract the necessary metadata. + +##### ESRI shapefiles + +To find information from ESRI shapefiles, we can first use a function `arcticdatautils::read_zip_shapefile()`. + +```{r, eval=FALSE} +shapefile <- arcticdatautils::read_zip_shapefile(d1c@mn, shp_pid) +``` + +##### GeoJSON, GeoPackage, and Parquet files + +For GeoJSON, GeoPackage, and Parquet files, we don't have an arcticdatautils function to read the file from the node, so you'll need to download the file locally. We can use the `sf` library to read in these vector files instead. + +```{r, eval=FALSE} +geojson_file <- sf::st_read("~/path/to/vectorFile.json") +geopackage_file <- sf::st_read("~/path/to/vectorFile.gpkg") +geoparquet_file <- sf::st_read("~/path/to/vectorFile.parquet") +``` + +#### Exploring vector file for metadata + +To find information from ESRI shapefiles, GeoJSONs, GeoPackages, and Parquet files, we can use the `sf` library again to find the *coordinate reference system* and *geometry*. + +```{r, eval=FALSE} +### Get coordinate reference system +sf::st_crs(file) + +### Find the geometry +sf::st_geometry(file) +``` + +To reference the names of the coordinate reference systems, we can use `arcticdatautils::get_coord_list()`. + +##### Additional files + +For `.kml` and `.kmz` files, or other vector files not mentioned, there may be other libraries in R that can be used to explore their metadata. Uploading the file into QGIS or another GIS software is another quick way to retrieve this metadata information. + +#### Edit format ID + +Next, we'll want to check the format ID and, if necessary, change the format ID to reflect the correct file type. If it needs to be changed to an ESRI shapefile, we'll do the following: + +```{r, eval=FALSE} +spatial_vector_pid <- selectMember(dp, "sysmeta@fileName", "exampleFile.zip") +sysmeta <- dataone::getSystemMetadata(d1c@mn, spatial_vector_pid) +sysmeta@formatId <- "application/vnd.shp+zip" + +dataone::updateSystemMetadata(d1c@mn, spatial_vector_pid, sysmeta) +``` + +You can check for format IDs in this [documentation](https://cn.dataone.org/cn/v2/formats). + +#### Creating `spatialVector` entity + +Next, we'll be creating our `spatialVector` entity. We can use an `arcticdatautils` function to do this. Then, we'll add it to the EML doc. + +One thing we'll need for this entity is an attribute list. If one was already created from the web editor, you can copy that over. Otherwise, you can use R to create and add one for this file. The example code below will assume that we're copying the attribute list over from the `otherEntity` of an ESRI shapefile. + +```{r, eval=FALSE} +spatialVector <- arcticdatautils::pid_to_eml_entity(d1c@mn, + spatial_vector_pid, + entity_type = "spatialVector", + entityName = "exampleFile.zip", + entityDescription = "spatial vector description", + attributeList = doc$dataset$otherEntity[[i]]$attributeList, + geometry = "Polygon", + spatialReference = "list(horizCoordSysName = GCS_North_American_1983")) + +doc$dataset$spatialVector[[1]] <- spatialVector + +doc$dataset$otherEntity[[i]] <- NULL # removing the previous otherEntity of the file +``` + +Finally, we'll run `eml_validate(doc)` to make sure everything is fine. + +### Example script + +Here is an example script combining everything when processing an ESRI shapefile: + +```{r, eval=FALSE} +### Set up node and gather data package +d1c <- dataone::D1Client("PROD", "urn:node:ARCTIC") # Setting the Member Node +resourceMapId <- "..." # Get data package PID (resource map ID) +dp <- getDataPackage(d1c, identifier = resourceMapId, lazyLoad = TRUE, quiet = FALSE) # Gather data package + +### Load in Metadata EML +metadataId <- selectMember(dp, name="sysmeta@formatId", value="https://eml.ecoinformatics.org/eml-2.2.0") # Get metadata PID +doc <- read_eml(getObject(d1c@mn, metadataId)) # Read in metadata EML file + +### Creating Spatial Vector + +# read in shapefile +shp_pid <- selectMember(dp, "sysmeta@fileName", "PeatTess.zip") +shapefile <- arcticdatautils::read_zip_shapefile(d1c@mn, shp_pid) + +# get coordinate system +sf::st_crs(shapefile) # -> GCS_North_American_1927 + +# find geometry of shapefile +sf::st_geometry(shapefile) # -> polygon + +### Edit formatId + +# Format ID +vector_pid <- selectMember(dp, "sysmeta@fileName", "PeatTess.zip") +sysmeta <- getSystemMetadata(d1c@mn, vector_pid) +sysmeta@formatId <- "application/vnd.shp+zip" + +updateSystemMetadata(d1c@mn, vector_pid, sysmeta) + +### Create spatial vector entity +spatialVector <- pid_to_eml_entity(d1c@mn, + shp_pid, + entity_type = "spatialVector", + entityName = "PeatTess.zip", + entityDescription = "1km tessellation of the Alaska peatland map", + attributeList = doc$dataset$otherEntity$attributeList, + geometry = "Polygon", + spatialReference = list(horizCoordSysName = "GCS_North_American_1927")) + +# add spatial vector to doc +doc$dataset$spatialVector[[1]] <- spatialVector + +# NULL the corresponding otherEntity +doc$dataset$otherEntity <- NULL + +eml_validate(doc) +``` From 46a44a5c2ae0b1b1feb27cf42ef0fc00730f6eb7 Mon Sep 17 00:00:00 2001 From: justinkadi Date: Thu, 11 Sep 2025 17:38:50 +0000 Subject: [PATCH 2/2] Adding spatial raster reference material --- workflows/misc_file_types/spatialRaster.Rmd | 165 ++++++++++++++++++++ 1 file changed, 165 insertions(+) create mode 100644 workflows/misc_file_types/spatialRaster.Rmd diff --git a/workflows/misc_file_types/spatialRaster.Rmd b/workflows/misc_file_types/spatialRaster.Rmd new file mode 100644 index 00000000..c39b717a --- /dev/null +++ b/workflows/misc_file_types/spatialRaster.Rmd @@ -0,0 +1,165 @@ +## Spatial raster data + +### About + +The spatial raster files that we typically work with are `.tif` files. + +### Processing `spatialRaster` entities + +This reference tutorial will assume that the `otherEntity` of the `.tif` file already has an attribute list. If it exists, you can copy it. Otherwise, you can add one through the web editor before beginning this process, or create one through R to add. + +In addition to the usual metadata information we'll need (description, attributes, physical), we'll need some additional metadata to create a `spatialRaster` entity. In particular, we'll need to know the *coordinate reference system* of the file, *number of bands*, *cell size*, and other information that we can gather from exploring the TIF files. + +```{r, eval=FALSE} +library(sf) +library(dataone) +library(datapack) +library(uuid) +library(arcticdatautils) +library(EML) + +### Set up node and gather data package +d1c <- dataone::D1Client("...", "urn:node:...") # Setting the Member Node +resourceMapId <- "..." # Get data package PID (resource map ID) +dp <- getDataPackage(d1c, identifier = resourceMapId, lazyLoad = TRUE, quiet = FALSE) # Gather data package + +### Load in Metadata EML +metadataId <- selectMember(dp, name="sysmeta@formatId", value="https://eml.ecoinformatics.org/eml-2.2.0") # Get metadata PID +doc <- read_eml(getObject(d1c@mn, metadataId)) # Read in metadata EML file +``` + +#### Downloading the files + +We will first download the files into our `datateam` server. We can do this using the `download.file()` function. +```{r, eval=FALSE} +download.file(url1, destination1) +``` + +#### Changing the format IDs + +We will then change the format IDs within the `sysmeta` and in the entity itself. The following example code assumes that you only have geoTIFF files. + +```{r, eval=FALSE} +pids <- selectMember(dp, "sysmeta@fileName", ".tif") + +for(i in 1:length(pids)){ + sysmeta <- getSystemMetadata(d1c@mn, pids[i]) + + sysmeta@formatId <- "image/geotiff" + + updateSystemMetadata(d1c@mn, pids[i], sysmeta) +} + +for(i in 1:length(doc$dataset$otherEntity)){ + doc$dataset$otherEntity[[i]]$entityType <- "image/geotiff" +} +``` + +#### Getting raster metadata + +We have defined this function that we haven't added into `arcticdatautils` yet, but we will share below. + +```{r, eval=FALSE} +get_raster_metadata <- function(path, coord_name = NULL, attributeList){ + + # define a raste object + raster_obj <- raster::raster(path) + #message(paste("Reading raster object with proj4string of ", raster::crs(raster_obj)@projargs)) + + # determine coordinates of raster + if (is.null(coord_name)){ + coord_name <- raster::crs(raster_obj)@projargs + } + + raster_info <- list(entityName = basename(path), + attributeList = attributeList, + spatialReference = list(horizCoordSysName = coord_name), + horizontalAccuracy = list(accuracyReport = "unknown"), + verticalAccuracy = list(accuracyReport = "unknown"), + cellSizeXDirection = raster::res(raster_obj)[1], + cellSizeYDirection = raster::res(raster_obj)[2], + numberOfBands = raster::nbands(raster_obj), + rasterOrigin = "Upper Left", + rows = dim(raster_obj)[1], + columns = dim(raster_obj)[2], + verticals = dim(raster_obj)[3], + cellGeometry = "pixel") + return(raster_info) +} +``` + +This function takes in a path to the geotiff file and creates a `spatialRaster` object to be added into the EML. + +To use this function, we will need to know the coordinate reference system as well to add as an argument. We can do this using the `raster` library in R. + +```{r, eval=FALSE} +# Create object with path to folder containing all the tif files +raster_folder <- "path/to/your/rasters" + +# Create list of the file names with full file paths +raster_names <- list.files(raster_folder, full.names = TRUE) + +# Find datum of a TIF file +raster::raster(raster_names[[1]]) +raster::crs(raster::raster(raster_names[[1]]))@projargs + +# Loop through all of the files +for(i in 1:length(raster_names)){ + print(raster::crs(raster::raster(raster_names[[i]]))@projargs) +} + +# An example output of this section can look like + # datum WGS84 + # projection UTM + # zone = 22 + # units = m +``` + + +We can use `arcticdatautils::get_coord_list()` to see a table of coordinate reference systems that we can use in our EML document. We can look through this table by looking for `WGS_1984_UTM_Zone_22` in the `horizCoordSysDef` column. Then, we can look for the corresponding `geogCoordSys` and see our coordinate system is `GCS_WGS_1984`. + +#### Creating the `spatialRaster` object + +We will first create an empty list for spatial raster entities to live. Then, we'll use the function to populate this list. + +```{r, eval=FALSE} +spatialRaster <- vector("list", length(raster_names)) + +for (i in 1:length(raster_names)) { + spatialRaster[[i]] <- get_raster_metadata(raster_names[i], + coord_name = "GCS_WGS_1984", + attributeList = doc$dataset$otherEntity[[i]]$attributeList) +} +``` + +Note that this code assumes that the `otherEntity` and `raster_names` have the TIF files in the same order when assigning the attribute list. If this is different, we will need to find a way to assign the correct attribute list. + +#### Adding `spatialRaster` entity + +Before we're able to validate the EML doc, we'll need to assign the `spatialRaster` entities and remove the corresponding `otherEntities`. + +```{r, eval=FALSE} +doc$dataset$spatialRaster <- spatialRaster + +doc$dataset$otherEntity <- NULL + +eml_validate(doc) +``` + +Note that if there are other files in the data package's `otherEntity` section that are not TIFs, we don't want to set them all to `NULL`. In that case, we would only `NULL` the corresponding files. + +Then, remember to set the physicals for the `spatialRaster` section. + +```{r, eval=FALSE} +for (i in seq_along(doc$dataset$spatialRaster)) { + raster_name <- doc$dataset$spatialRaster[[i]]$entityName + + raster_pid <- selectMember(dp, "sysmeta@fileName", raster_name) + physical <- arcticdatautils::pid_to_eml_physical(d1c@mn, raster_pid) + + doc$dataset$spatialRaster[[i]]$physical <- physical +} + +eml_validate(doc) +``` +