Since I haven't run this yet, I'm still wrapping my head around it. Is this refactor an alternative way to run the demo? I understand it isn't completely fleshed out yet.

Sorry that was really half-baked PR without enough explanation - moving the line of updated test code from the module out to the corresponding test file now. The idea here is that this new get.run_get() function would work across all the retrieval (e.g., get.run_get("library", aoi_gdf) instead of cultural.get_library(aoi_gdf)). That should simplify the package structure and how a user uses it but the tradeoff is this stored data structure (centralizes the information but has to be versatile, not too verbose and maintainable).

Any ideas on a better name for the module/function?

Relevant tests (note new code isn't implemented throughout, working in some not in others)
CHAPPIE/tests/test_cultural_assets.py::test_get_historic FAILED
CHAPPIE/tests/test_cultural_assets.py::test_get_library FAILED
CHAPPIE/tests/test_cultural_assets.py::test_get_museums PASSED
CHAPPIE/tests/test_cultural_assets.py::test_get_worship PASSED
CHAPPIE/tests/test_cultural_assets.py::test_get_recAreas PASSED