Add GraphDB Support as a Provider for OGC API - Records

[gloriak9]

Description
I have a GraphDB catalog for geospatial metadata that uses RDF to represent relationships between data. I want to expose this catalog via OGC API records but I realise that I cannot use pygeoapi because of lack of GraphDB(or graph databases-) support. There is a lot of increased use of linked data and graph databases are more relevant now more than ever. It would be icredible to enhance pygeoapi to support them.

Proposed Implementation

1. Develop a new GraphDBCatalogue Provider class in pygeoapi/providers that extends the base provider architecture.
2. Implement SPARQL queries to fetch and transform GraphDB records into OGC API - Records JSON format.
3. Add configuration options in pygeoapi-config.yml for:

• GraphDB endpoint URL (e.g., http://localhost:7200/repositories/my_repo).
• Authentication credentials (if required).
• Custom` SPARQL query templates for record retrieval and filtering.

Suggestions.
On the other hand if anyone has a work around for using graph databases with pygeoapi please let me know.

[C-Loftus]

If you are interested in serving a graph database as ogc api features you can use a sparql provider plugin like the one my team has created here: https://github.com/cgs-earth/pygeoapi-plugins?tab=readme-ov-file#sparql

I am unsure if there is an implementation anywhere to serve ogc api records using a graph backend with sparql