Marcin
Marcin
This is practically the same situation. Okay, now I fully understand the process of selecting images for rendering. You work around the lack of implementation of this functionality by using...
Yes I agree thank you for the clarification. The query I should aim for should contain information on two parameters: start and stop. This would select the rasters acquired in...
@geographika Is there any possibility of implementing the LIMIT class in the near future?
> For comparison, Geoserver has an option named ExcessGranuleRemoval for avoiding unnecessary rendering. I found documentation from https://docs.geoserver.geo-solutions.it/edu/en/raster_data/mosaic_pyramid.html. The system filters out images (granules in Geoserver language) based on their...
> maybe that's a [pgstac](https://github.com/stac-utils/pgstac) issue > > cc @bitner Yes, that was my first thought, but then I checked that everything is fine from the side of loading and...
@vincentsarago unfortunately response remains the same: ``` { "type": "FeatureCollection", "context": { "limit": 10, "returned": 0 }, "features": [], "links": [ { "rel": "collection", "type": "application/json", "href": "http://***/collections/sentinel-2-l1c" }, {...
Hey @vincentsarago I checked. I see the same error as you, but after running the load command, the data appears in the database. In fact, all the pgstac tables appear....
Hey @bitner :) as you suggested I tried: `ALTER ROLE SET search_path to pgstac, public;` and it helped in terms of inserting the data into / editing data in pgstac....
@bitner @vincentsarago I also tested other versions of stac-fastAPI (2.4.11), and the problem occurs there as well. I guess it's only a pgstac problem.