The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]dogado.de.
bcdc_search_facets(),
bcdc_list_group_records() and
bcdc_list_organization_records() were not returning all
records after the upgrade to CKAN 2.9 (#353). Includes adding tests and
bcdata-specific options for these queries, see
bcdc_options().%like% and
%in% in bcdc_query_geodata() (#356, thanks
@bevingtona).!! or
local() for local functions more restrictive; updated tests
and examples (#341).bcdata.single_download_limit option, as
it was mostly redundant with bcdata.chunk_limit, and should
always be set by the server. Please set the page size limit for
paginated requests via the bcdata.chunk_limit option
(#332).jsonlite::read_json() as a file read method, so
users can now download & read json resources in B.C.
Data Catalogue recordsdownload_audience default from
Public to NULL in bcdc_search()
(#315)bcdc_search()
need to be quoted to generate a valid API query (#315)bcdc_list_organizations and
bcdc_list_organization_records as helper functions for
finding records #322bcdc_query_geodata(),
function calls in filter() that need to be evaluated
locally are no-longer auto-detected. They now need to be wrapped in
local() to force local evaluation before the
CQL query is constructed and sent to the WFS server. Please
see vignette("local-filter") for more information. This
aligns with recommended usage patterns in other dbplyr
backends (#304, PR #305).dbplyr edition 2, bumped dependency to
2.0.0 (#300)bcdc_get_citation to generate bibliographic
entries (via utils::bibentry) for individuals records.
#273bcdc_search() (objects of class
"bcdc_recordlist") now print 50 records by default, instead
of 10. In addition, there is a new [ method for
"bcdc_recordlist" objects, allowing you to subset these
lists and still have a nice printout (#288).bcdc_get_data() fails informatively when a
given resource doesn’t exist in a record (#290)dbplyr 2.2.0 (#297,
82b9defa376ab)bcdata package, most of which are internal
only (#283). These should be mostly invisible to the user, except for
the removal of the type search facet in
bcdc_search() and bcdc_search_facets(). If you
use an API key (authorized catalogue editors only), you will need to
login to the new catalogue and get your updated key and set the value
your BCDC_KEY environment variable to the new key.names method for bcdc.promise objects.
You can now call names on an object produced by
bcdc_query_geodata. This is handy when trying to figure out
exact column spelling etc. #278bcdc_describe_feature (#279).onLoad() that sent a request to the wfs
getCapabilities endpoint could cause the package to fail to load. This
was moved into an internal function bcdc_get_capabilities()
that makes the request the first time it’s required, and stores the
result for the remainder of the session (#271)bcdata.single_download_limit limit
dynamically from the getCapabilities endpoint. #256bcdc_describe_feature now joins an object description
column to the returned object to provide more information about a field
directly in R. #241, #259bcdata.max_geom_pred_size option. #243, #258bcdc_check_geom_size so users can
check prior to submitting a WFS request with filter to see
if the request will require a bounding box conversion. #243, #258bcdc_query_geodata(). #240,
#264bcdc_query_geodata(). #265, #267bcdc_list_groups and
bcdc_list_group_records to provide the ability to query on
the group endpoint of the catalogue API. #234bcdata.single_download_limit to enable
setting the maximum number of records an object can be before forcing a
paginated download (#252)collect.bcdc_promise where the wrong
parameter name in crul::Paginator$new() resulted in an
error in paginated wfs requests (#250, thanks @meztez)bcdata.chunk_limit option
had a typo, so that it was not actually used properly (#252)as. functions (e.g.,
as.Date(), as.character(),
as.numeric()) in a filter statement would fail. (#218,
#219)DBI S4 generics
(DBI::dbQuoteIdentifier() is now used instead of
dbplyr::sql_escape_ident() and
DBI::dbQuoteString() instead of
dbplyr::sql_escape_string()), to comply with upcoming
dbplyr 2.0 release (#225, #225;
https://github.com/tidyverse/dbplyr/issues/385)try()
to avoid spurious check failures (#229).selectable column from
bcdc_describe_feature to sticky and modify
corresponding docs and tests (#180).head and tail methods for
bcdc.promise objects. Thanks to @hgriesbauer for the suggestion! (#182,
#186)as_tibble as an alias for collect
in line with dbplyr behaviour (#166)bbox object as well
as an sf* object (#176)bcdc_get_data now outputs
a messages indicating the presence and names of any sheets (#190)bcdc_get_data() & bcdc_query_geodata()
will now work with full B.C. data catalogue url including resource
(#125, #196)bcdc_sf objects now have an
time_downloaded attributeBCDC_KEY environment variable with
their catalogue API token
(https://github.com/bcgov/bcdata#bcdc-authentication; #208).select, filter and mutate
roxygen so that bcdata specific documentation to these methods is
availablebcdc_tidy_resources for retrieving a data frame
containing the metadata for all resources from a single B.C. Data
Catalogue record (PR#149, #147)bcdc_query_geodata() (#129, #138, #139)mutate method for bcdc_promise that only fails and
suggest an alternative approach. (PR#134)tidyselect so that
select.bcdc_promise behaviour is typical of
dplyr::select ($140, #138)BEYOND() and RELATE() geometry
predicates as they are currently not fully supported by geoserverNOTE: Namespace in Imports field not imported from: ‘methods’
error on CRAN (#145)DWITHIN wasn’t working because
units needed to be unquoted (#154)BBOX() used in a
filter() statement combined with
bcdc_query_geodata() did not work (#135, #137, #131)bcdc_query_geodata() (#126, #127)show_querybcdc_get_record to enable
suppressing console writingThese binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.