Prerequisites:
Postgres/PostGIS:
For customers to use Hub they are required to have a PostGIS (PG) instance, running at a minimum of version 16. If a customer is hosting the PG instance themselves then Geoxphere will require additional admin rights to access source tables and to create the necessary schema, tables, functions and user for Hub to function.
Data:
To utilise the Hub APIs and Channels the customer will require the necessary source data/tables for the API to be available within the same PG instance.
UPRN: Waste:Collection and Elections:Polling Place Hub APIs require the data to contain a UPRN. If your UPRNs contain a leading zero then this will need to be removed. Geoxphere will be able to provide the SQL to do this.
Geometry: Other than the Waste:Collection and Elections:Polling Place Hub APIs, all other APIs require the source data to contain a geometry column and geometry values. The source project is irrelevant as this will be reprojected to 27700 in the Hub View.
Recommendations:
Software:
We would recommend having access to either Dbeabver or PG-admin so that you can update, copy, modify or create your own Hub APIs.
SQL:
While it is not necessary to be proficient in PG SQL it is an advantage. Geoxphere will provide SQL snippets and examples of Hub APIs, as well as provide full support and training.