update examples page, add download buttons & css

* added css for download buttons, and added the buttons in to download datasets on the examples page
* updated several incorrect vocab links
* changed how figures are displayed to use an R function

.github/workflows/deploy.yml

@@ -16,7 +16,7 @@ jobs:
       - uses: r-lib/actions/setup-r@v2
       - uses: r-lib/actions/setup-pandoc@v2
       - name: Install R packages
-        run: Rscript -e 'install.packages(c("rmarkdown", "bookdown","fontawesome","webshot","rsvg","tinytex"))'
+        run: Rscript -e 'install.packages(c("rmarkdown", "bookdown","fontawesome","webshot","rsvg","tinytex","downloadthis"))'
       - name: Install phamtomJS for webshot
         run: Rscript -e 'webshot::install_phantomjs()'
       - name: Render Book

checklist.md

@@ -13,7 +13,21 @@ Note that when you publish your dataset on the IPT, if you use a term not listed
 - Terms marked with 1 indicate that the specified term is accepted in the Event or Occurrence table, but preference is that they be recorded in the eMoF table in the measurementType column so they can be linked with controlled vocabulary
 - For the Occurrence table, distinction is made if the term could be used in the core or the extension table
 
-`r fontawesome::fa(name="download", fill="green", height="2em")` <a href="docs/OBIS-termchecklist.csv" download>**Click here to download the checklist.**</a>
+```{r, echo=F}
+library(downloadthis)
+download_file(
+    path = "docs/OBIS-termchecklist.csv",
+    output_name = "OBISchecklist",
+    output_extension = ".csv",
+    button_label = "Download checklist as csv",
+    button_type = "default",
+    has_icon = TRUE,
+    icon = "fa fa-save",
+    class = "hvr-sweep-to-left",
+    style = "background-color: #1e74ac; color: white; border: none; padding: 10px 20px; font-size: 16px; border-radius: 5px;
+            margin-top: 5px; margin-bottom: 20px;"
+  )
+```
 
 | Term | OBIS Required | Term's DarwinCore Class | Event core | Occurrence core | Occurrence extension | eMoF Table | DNA Table |
 |:---------|:-----------|:---------|:----------|:--------|:----------|:----------|:--------|

common_qc.md

@@ -31,7 +31,7 @@ Sometimes locality information can be difficult to interpret, especially if reco
   `r fontawesome::fa("flag", fill="darkblue", prefer_type="solid")` Always be sure to fill in the `georeferenceSources` field to indicate the source(s) you used to obtain locality information when appropriate
 </div>
 
-- If you have a set of points, a line, or a polygon (perhaps from the Map tool), you can find the centroid of the features using either [obistools::calculate_centroid](https://github.com/iobis/obistools#calculate-centroid-and-radius-for-wkt-geometries) or [PostGIS](https://postgis.net/docs/ST_PointOnSurface.html), and then enter this coordinate into the `decimalLatitude` and `decimalLongitude` fields. This PostGIS guideline will help you select a centroid that is guaranteed to fall within your designated area.
+- If you have a set of points, lines, or polygons (perhaps from the Map tool), you can find the centroid of the features using either [obistools::calculate_centroid](https://github.com/iobis/obistools#calculate-centroid-and-radius-for-wkt-geometries) or [PostGIS](https://postgis.net/docs/ST_PointOnSurface.html), and then enter this coordinate into the `decimalLatitude` and `decimalLongitude` fields. This PostGIS guideline will help you select a centroid that is guaranteed to fall within your designated area.
 - Estimate `coordinateUncertaintyinMeters` that is wide enough to cover the area
   - If the location is provided as an array or WKT format, you can use R package [obistools::calculate_centroid](https://github.com/iobis/obistools#calculate-centroid-and-radius-for-wkt-geometries) to obtain coordinate uncertainty.
   - Use the [OBIS maptool](https://obis.org/maptool/) to obtain from the “radius” column. This is only applicable for lines or polygons, not point features.