Matt
@mabecabrera this was OTU filter, right? I think I now know how to make the query, so maybe we can integrate it directly. Note to self: leaves.
Here is where we need OTUs with valid names really, that's all.
Understood @mabecabrera, you are correct in terms of trying to get the result you want. We had a little more discussion on this with a couple more insights. Might be...
At the TWT discussion just now @dshorthouse hinted at possible extensions. This got me thinking that we could explore a metadata element that lets providers point specific fields/terms to a...
I have updated to * Use `-strip` in all derivatives (removes EXIF) * Use `auto_orient=true` in all derivatives * Added an option to regenerate derivatives (for sticky manual cases, just...
Closing as stale.
Sounds like you're at the point where you want to try more data? I think using the resultant geoJSON would be inefficient as we'd have to go to and from...
A migration will be need to handle the following requirements: ``` CREATE EXTENSION postgis_raster; SET postgis.gdal_enabled_drivers = 'ENABLE_ALL'; ``` Note that the latter works, but might be overkill.
Following above, this enabled for the server side: ``` ALTER SYSTEM SET postgis.gdal_enabled_drivers TO 'ENABLE_ALL'; SELECT pg_reload_conf(); ``` Does require further exploration.
> and we have apparently currently disregarded the TDWG distributions from the maps Untrue. They have shapes and are treated like any other.