The builder currently uses specific releases from [LimnoTech's fork of pygeoapi](https://github.com/LimnoTech/pygeoapi) to incorporate bug fixes and new features. Here are some of the main blockers for making the switch: - [x] Upstream to switch back to Pydantic 2.0 (see further discussion in #25 on timeline) - [x] PR [1641](https://github.com/geopython/pygeoapi/pull/1641) addressing [1578](https://github.com/geopython/pygeoapi/issues/1578) (discussed in #23) - UPDATE: Geopython's PR [#1641 CRS handling in xarray provider properties ](https://github.com/geopython/pygeoapi/pull/1641) was merged September 2024 and released with [0.18.0](https://github.com/geopython/pygeoapi/releases/tag/0.18.0) Considerations when we make the change - [ ] We can address #24 - [x] Update gdptools from `0.1.post2` to a more recent release. Pygeoapi has upgraded to Shapely 2.0, so should now be compatible with newer versions. - UPDATE: completed with MR !117 @ptomasula_limno.com, are there any other pending PRs or work from your end that we should add to this list related to the hateoas provider?