Luís de Sousa

Hi again Hugh, yes, the test case is in the issue report at GitHub. Regards. -- Luís ------- Original Message ------- On Thursday, May 12th, 2022 at 9:50 PM, HughWilliams...

@sgillies Uncompressed this dataset is "only" 15 GB (including no data cells), which in this 32 GB RAM system should not be a problem. Beyond the issue of trying to...

The GirdOffsets can contain 2 or 4 elements. This is detailed in the WCS 1.1.1 document: page 46, note g.

This is a considerably different use case to that I proposed with #615. In this formulation only some of the properties values are transformed into RDF objects with URIs. In...

@dblodgett-usgs @ksonda I believe that what I coded last year matches you requirements. Check the proposed config file [here](https://github.com/geopython/pygeoapi/pull/615/files#diff-c6c4b36562d4918ed8b6b6839d0caff62a21eea31d2731ee38e0c489e35184bc).

It is work in progress as I still want to introduce more features. But what is in this pull request is functional. I would suggest a merge into development so...

Travis is trying to run the tests, but there is no Virtuoso instance set up in the environment. Should something be done about the tests? Or can the PR be...

@pvgenuchten The GeoSPARQL provider is independent of the back-end. Whether it is a true triple store or something else, as long as it can reply to GeoSPARQL queries it will...

Hi folks, any news on this PR?

> This suggests that item-level JSON-LD response for feature collections might have an option for GeoJSON-LD (default) and some kind of GeoSPARQL representation. Since #676 the optional JSON-LD using schema:geo...