getSentinel_query never returns more than 200 results about getspatialdata HOT 2 CLOSED

Thank you for using and testing getSpatialData and for investigating and pointing out the paging mistake. I fixed it according to your solution (will be referenced in NEWS). An additional parameter for defining the maximum number of query results is a good idea – will implement it with one of the next commits.

from getspatialdata.

Works great, thanks for the quick fix.
I also looked for a way to add extra filters to the called URL, since my target is to get all Sentinel-1 data over intersection of a very small bounding box (1km x 1km) for the months of January and December in the past 5 years. Filtering data.frame AFTER getSentinel_query would imply downloading a very large amount of data (about 500 Sentinel-1 images per year). It took my PC 2 minutes to get the answer from ESA's servers for a one year range over the 1km2 bounds. Increasing time range and/or zooming out esponentially increases the amount of results and the time-of-retreival, making my app a bit impractical.
Filtering directly in the URL would be a solution, but ESA SciHub has two different APIs - Open Data Protocol (OData) and Open Search (Solr) and it is not possible, to my knowledge, to use a single API to filter for area intersection AND month. If I find a solution for implementing server-side filtering I will propose it. Thanks.

from getspatialdata.