Closed rdenham closed 1 year ago
I chose to add idsplit
directly rather than relying on passing it via ...
so the intention of ...
remained unchanged (ie in the help it says Additional arguments to pass to the ArcGIS REST POST request
). I didn't want to change this.
Thanks for addressing this issue @pfrater
Is it possible to now provide some documentation on the idsplits
argument ?
If it's of any use, my attempt was:
#' @param idsplit Positive integer. Limits the number of records returned in
#' each request. To get the full set of records, multiple requests will be made
#' in batches of no more than \code{idsplit} in size. These will then be merged.
#' Setting this to a smaller value can be useful when requesting
#' fewer, complicated features, which might otherwise silently return an empty
#' layer.
Thanks for writing this very handy package. I think though I run into a problem with retrieving spatial data due to queries becoming too large if all records are requested in one query.
Looking at the code, I see that features are retrieved in chunks:
I think that the default chunk size of 500 is too big for some of the things I'd like to retrieve. I tested it with smaller values, and it seemed to work. Note that you don't get any errors or warnings, just an empty result. I wouldn't be suprised if there were some server setting that limits the size of the returned query, but I'm not really familiar with the ArcGIS server.
Here is my test:
I added the argument
idsplit
inget_esri_features
which then gets carried through by your...
mechanism.Do you think this could be added to the code? Happy to make PR if you'd like.