The safedata system uses an underlying gazetteer data source, which is a GeoJSON file defining the known sampling locations and any other arbitrary properties of each Feature in the file. This is widely used - the website provides the gazetteer map and then the safedata R package uses it to convert locations in data tables into full sf spatial data frames.
However at the moment, sdv uses a really cut down abstraction of that data, basically just location names and bounding boxes and a list of aliases. Logically though, this whole dataset should be managed locally as a GIS resource and then be uploaded to the safedata_server, from where it goes on to be downloaded by the safedata R package.
So, we need to update locations to use the gazetteer GeoJSON source (and describe it!) and aliases file. Then sdv will be in charge of loading those files to the metadata server via the update_gazetteer function, and hence on to users of safedata.
The
safedatasystem uses an underlying gazetteer data source, which is a GeoJSON file defining the known sampling locations and any other arbitrary properties of each Feature in the file. This is widely used - the website provides the gazetteer map and then thesafedataR package uses it to convert locations in data tables into fullsfspatial data frames.However at the moment,
sdvuses a really cut down abstraction of that data, basically just location names and bounding boxes and a list of aliases. Logically though, this whole dataset should be managed locally as a GIS resource and then be uploaded to thesafedata_server, from where it goes on to be downloaded by thesafedataR package.So, we need to update locations to use the gazetteer GeoJSON source (and describe it!) and aliases file. Then
sdvwill be in charge of loading those files to the metadata server via theupdate_gazetteerfunction, and hence on to users ofsafedata.🎁 🎅 🎁 📦