Jeff McKenna

@rob-metalinkage this is the first I have heard of limitations of @type and @id in JSON-LD for spatial - are you referring to `"@type": "Dataset"` with `spatialCoverage`? ('challenges' to relay...

@pbuttigieg @fils the above is a great question submitted by the ICAN team. You can see that this primary key, the ODISCat ID, should be used for all of our...

thanks @bbest. Please also add to your tasklist: "create an ODISCat entry" (and point to the sitemap there) See steps at https://book.odis.org/gettingStarted.html We'll be driving the connection through that entry...

thanks @bbest & team, I have updated the ODIS Book to include a spatialCoverage with a box example (such as at https://book.odis.org/thematics/dataset/index.html ). (related to recent updates through https://github.com/CalCOFI/workflows/issues/24 )

@bbest can you make a minor change to your [ODISCat entry](https://catalogue.odis.org/view/3318)? The `Datasource URL` should point to your catalogue home, not to the sitemap.

I've regenerated all SWIG/Python bindings in GDAL, correct, with SWIG-master and Python 3.10.0 I can trigger the warning message with just `gdal2tiles --help` so I don't think this has to...

The results from the byte.tif test: ``` Generating Base Tiles: 0...10...20...30...40...50...60...70...80...90...100 Generating Overview Tiles: 0...10...20...30...40...50...60...70...80...90...100 swig/python detected a memory leak of type 'OSRSpatialReferenceShadow *', no destructor found. swig/python detected a...

@rouault I've confirmed this fix/workaround with `master` and SWIG 4.1.1 on Windows. thanks!

No issues bringing into Solr (unless I have the wrong file). Here is the indexed record in Solr (note that the Location/Place/LargeMarineEcosystem isn't yet handled by our regions/indexer code): ```...

@arojas1 thanks for all of this, it is excellent. A minor/general comment is that I try to limit all text lines (the paragraphs near the top of each of the...