treat_results
routine and use of oa_lad21_lookup
custom lookupwithin_cd
and return_style = minimal
– a non-functional combination – was allowed through.returnGeometry
option previously added, as this was seemingly causing a problem with centroid retrieval? I don't think it was really needed anywaybounds_level
and within_level
are the same.within_cd
parameter actually work (I don't think I had tested this properly before).%3D
with plain =
. In attempt to simplify error-hunting. But worried that this may not work with all endpoints. Had to do some tweaking to get OA:WD lookup to work.extract_lookup
function as the previous pluck
call did not always work. New combination of pluck
and map_df
hopefully will work OK. But again, worried that this may break things that were previously working.build_api_query
as I noticed that some queries weren't working properly. Turned out that lookups with more than 2000 results were being truncated. The way to fix this (see examples six and seven) is to specify a resultType
of "standard"
which allows responses up to 32,000 long. jogger's spatial queries were already batched into batches of 25/50 so this didn't come up as an issue.within
parameter to geo_get()
. If you're passing in codes, set within_cd = TRUE
geo_get
geo_get()
to be the main function - copied params documentation over from create_custom_lookup()NEWS.md
file to track changes to the package.Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.