Closed daxkellie closed 1 year ago
galah_geolocate
hasn't had much attention, but could probably use some. A few potentially worthwhile improvements might include:
galah_filter
via fields such as decimalLatitude
and decimallLongitude
galah
at presentDiscussion 2022-02-08 led to following proposal:
galah_polygon()
to replace current galah_geolocate
functionality, supporting wkt
strings. Add complexity limit (11 vertices?)galah_radius()
to specify a circle as per 'explore your area' toolgalah_bbox()
to extract a bounding box from an sf
object or shapefile, and pass that to galah_polygon
One final option (not discussed) is to retain galah_geolocate
as a wrapper function to the above arguments. Unclear whether this would be more or less confusing for users.
It would also be good to have a post on ALA labs site (forthcoming) to explain sensible workflows to users
completed with galah_bbox
and galah_polygon
It might not be clear to users how to use a shapefile with
galah_geolocate
or how to edit that shape file using thesf
package to make it work withgalah_geolocate
. For example, often shape files are too complex forgalah_geolocate
, and so it would be worth explaning how to deal with this error with information like: