NEWS

---

boundr 0.3.7

• Improves the behaviour of bounds() and points() by making it less likely that a lookup table will be created that does not match a geo data field
• Internally, shared code within bounds() and points() has been refactored out into a common function (not user-facing), making bounds() and points() more like wrapper functions.
• Several helper functions have been tidied up and some unnecessary duplication of functionality across helpers for lookup table creation and spatial data retrieval has been removed, making fewer and leaner helper functions and removing a chunk of code from the package.
• {cli} has been used to produce user-facing error messages, in place of {usethis}.
• The function that allows the user to supply their own lookup table and have {boundr} automatically add geo data to it to create an sfc object has now been improved and should be functional as intended.
• Linting has been added to the development process through the adoption of {lintr}.
• The convoluted process for handling MSOA-based lookups has now been obviated entirely - the ONS site now seems to support MSOA-based lookups much better.
• Internal copy of the schema data updated.

boundr 0.3.6

• Enables bounds() query to shortcut the lookup table step and just return all boundaries at that level (just call the function with a single lookup argument)
• Improved README with examples
• Added pkgdown site, thanks to Tom Smith (closes issue ## boundr v2)
• Improve some function param documentation
• Update schema data (10 Nov 2023)

boundr 0.3.5

• Some work to improve the handling of MSOA queries
• Create points() function to handle centroids queries more neatly
• Update package internal data (mirror of ONS API schema)

boundr 0.3.4

• Deleted all tests as they were useless. Will start again from scratch.
• Added add_bounds_to_table() function - for when you already have a lookup table and you just want to add geo data to it. It uses the lefthandmost column as the source for the geometry codes, so if they are not there it will just fail - that's for the user to sort out.
• This version adds centroid support and some fixes to the MSOA-LSOA-MSOA round trip hack
• The opengeo_schema internal data object has been refreshed
• I can't remember what happened to 0.3.3

boundr 0.3.2

• After a lot of intervals of not working on this very much, I have finally pushed a lot of further work on the new style. The package is now named boundr and the work has been done in the main branch.
• Functions are now better documented and the core workflow is quite nice now.
• Basic tests are written but further tests of core behaviours need to be written still.
• TODO: Make centroid queries eg MSOA centroids work

boundr 0.3.0

• Rebuilt whole program around a schema approach (git branch: schema)
• It's rough but it sort of works for now.
• TODO: Make MSOA queries work (not supported by ONS lookups)
• TODO: Function documentation
• TODO: Testing and undoubtedly more fixes

boundr 0.2.20

• Updates to API addresses, mostly relating to more area codes moving to 2021 codes
• used package doc file for %>% and other imports, and removed pipe.Rd etc
• Still some bugs that need fixing
• TODO I need to write more tests!
• TODO build local copy of whole API schema and work out a way of querying that rather than manually updating URLs and codes

boundr 0.2.16

• Simplifies treat_results routine and use of oa_lad21_lookup custom lookup

boundr 0.2.15

• Fixes internal data issue where datasets weren't being found
• Adds more internal datasets to internal package data
• Upgrades LAD boundaries query to 2021 boundaries
• Simplifies LSOA:MSOA lookup by using internal data for HoCL names CSV

boundr 0.2.13

• Fixes a bug where within_cd and return_style = minimal – a non-functional combination – was allowed through.
• Fixes an earlier mistake where I thought that all API URLs were "FeatureServer" now - but centroid queries still need "MapServer".

boundr 0.2.12

• Enables population-weighted centroid queries for OA and LSOA as well as MSOA now
• Fixes OA:LAD queries returning wards as intermediate levels instead of MSOAs

boundr 0.2.11

• Removes the returnGeometry option previously added, as this was seemingly causing a problem with centroid retrieval? I don't think it was really needed anyway

boundr 0.2.10

• adds the ability to retrieve lookups and geometries at a single level, i.e. where bounds_level and within_level are the same.

boundr 0.2.9.5

• tweaks to make the within_cd parameter actually work (I don't think I had tested this properly before).
• some tweaks to how the query URL string is built, replacing %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.
• changes to the 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.
• This is why we should have proper tests in place, and I should be using git branches to test things I'm not sure about...

boundr 0.2.9.4

• Added in result_type parameter to 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.

boundr 0.2.9.3

• Further build_api tweaks

boundr 0.2.9.2

• update and fix examples
• update and re-knit README.Rmd

boundr 0.2.9.1

• Bit of a refactor, remove duplications
• Move helper function get_serious to its own file
• Reorganised geo_get and geo_get_bounds, slimmed down & restructured

boundr 0.2.9

• Finally removed the code that was there for 2-stage lookups - not going to happen
• Added in a self-built lookup for UTLA:RGN and UTLA:CTRY as ONS doesn't have these
• Finally did documentation of the internal datasets

boundr 0.2.8

• Trying to fix lookup for MSOA centroids
• Reported issue relating to different return_styles

boundr 0.2.7

• Further query string updates, to incorp changes at OpenGeography
• (All query URLs are Feature Server now; no more Admin, as some were)
• Add returnDistinctValues=TRUE to standard query string (reduces d/loads?)
• Further tidying up of data in build_api_query.R

boundr 0.2.6

• just some minor fixes (out of date rgn19 and ctry19 in geo_get.R)

boundr 0.2.5

• Updated several URL details to latest on ONS OpenGeography

boundr 0.2.4

• Added OA:Ward lookup capability
• Fixed OA:Ward lookup capability that I thought I'd added
• Enabled passing in a vector of codes -- or names -- as the within parameter to geo_get(). If you're passing in codes, set within_cd = TRUE
• Enabled HoCL MSOA Names inclusion when doing an OA-level query
• First steps towards enabling 2-step lookups
• OA:LAD lookup now defaults to returning OA-Ward-LAD rather than OA-LSOA-MSOA-LAD

boundr 0.2.3

• Added (top secret!) capacity for Output Area queries
• By accident this also enabled (I think) LSOA/MSOA:RGN queries
• I discovered that the ONS query doesn't mind if you ask for duplicate field names in your query (as specifically requested return_fields) - it just gives you one of them. Very nicely behaved. (Why does this matter? Because there's no oa11nm and it would have been a real hassle to rejig my code to deal with e.g. three return fields instead of four - but instead I can just request oa11cd twice and it's fine.)
• In connection with the previous point, I also discovered that dplyr::select() is similarly well-behaved and doesn't mind if you pass it duplicate column names such as, I don't know, two lots of oa11cd for example. Presumably it just goes with the first one and ignores subsequent dupes
• Updated a few other query lookup URLs
• I still haven't written proper formal tests for many of the features
• Sprinkled a few TODO notes in the code for future work
• I also did a little bit more commenting. Need to do loads more.

boundr 0.2.2

• Enhance examples in geo_get to better match README
• Create geo_get_bounds as a separate function and move out of geo_get to sep file
• Remove distinct option from params
• Add a few more options for lookups (realised LTLA to UTLA could easily be added)

boundr 0.2.1

• Changed codes and boundary URLs to 2020 where possible
• Many tweaks required to build_api_query.R test!
• Fix to expand_lookup.R param docs!
• Add options for returning centroid and shape data fields with boundaries

boundr 0.2.0

• Added a centroids query option (MSOA only for now) as well as boundaries
• Added in option to specify spatial reference code eg ESPG 3857
• Lots of tidying up the code - eg removed return_style = "all" option as unnecessary; create_custom_lookup did not need a spatial_ref option etc
• Improved function parameter documentation
• Included new static HoCL MSOA Names URL and removed old version parameter
• Started writing README.Rmd and included examples
• Sorted out which functions to @export. Examples in create_custom_lookup.R are now \dontrun as the function is not exported (examples irrelevant now really)
• Sorted out a batch size issue that was preventing longer queries from succeeding
• Added GitHub Actions for CMD Check and Github Pages/pkgdown
• TODO: Write tests for geo_get

boundr 0.1.3

• Further improvements to documentation
• Wrote a few tests for build_api_query()
• Package builds OK
• Not all examples are working, not sure what the cause is
• Refactored and tidied up misc small parts of scripts

boundr 0.1.2

• Amended geo_get() to be the main function - copied params documentation over from create_custom_lookup()
• Fixed various build errors mostly to do with namespace
• Realised that utils::URLencode() isn't vectorised so rewrote build_api_query() process to account for that
• Removed examples where no longer accurate (params have shifted)
• TODOs from 0.1.1 remain

boundr 0.1.1

• Sorted out Imports in DESCRIPTION file
• check() package and build documentation
• TODO: document internal package data
• TODO: work on README
• TODO: examples

boundr 0.1.0

• Added a NEWS.md file to track changes to the package.
• Added parameter documentation to build_api_query.R
• Deleted superseded files (initial attempts)