Standardize options about spocc HOT 6 CLOSED

Good idea. We may be able to do this for some kinds of options, but not all.

Another option is that I currently have a parameter for each of the source data pkgs, gbifopts, 'rinatopts', etc. in which you can specify the arguments for searching each data source, e.g. https://github.com/ropensci/occdat/blob/master/R/occ.r#L27

Does that work?

from spocc.

Why not just pass the extras with ... for now? It would be good to just keep track of a list for now, build everything and standardize once they are working.

from spocc.

I was thinking there are some pretty standard types of options we'll want to pass. So the dates example it makes sense to just let users pass dates as one format and then we can parse it for each package. Maybe we should have a table of all the different options of each API and see which we want to include, and which we could standardize.

from spocc.

I am more or less doing ..., but I didn't know of a way to do multiple ...'s in a single function, so I pass by default empty lists to a do.call call - and user can populate each list if they want to specify parameters.

from spocc.

@emhart yeah, good idea to start thinking about standardizing

from spocc.

Possible options to bring into the main occ function as standardized across sources:

I'm not sure many others are possible to make available across sources. Will keep looking.

For these params to use across sources, should just force apply to all applicable sources. And tell user to just pass args to individual sources if they want different settings for different sources

1: This will take some converting of bounds from inat into a WKT - geometry for gbif and aoi for bison already accept WKT

from spocc.