Repository navigation
Geometry and date filters don't work in pyrasterframes STAC API #590
Description
Result of the same query using pystac-client:
stac = "https://earth-search.aws.element84.com/v0"
collection = "sentinel-s2-l2a-cogs"
shape = geopandas.read_file("zip:///shape.zip")
polygon = shapely.geometry.box(*shape.to_crs(epsg=4326).total_bounds)
SentinelSTAC = Client.open("https://earth-search.aws.element84.com/v0")
result = SentinelSTAC.search(
intersects=polygon,
collections=["sentinel-s2-l2a-cogs"],
datetime="2020-04-01/2020-04-10"
).matched()
print(result)
16
Using the pyrasterframes STAC API:
spark = create_rf_spark_session()
scenes = spark.read.stacapi(stac, {
'collections': [collection],
'intersects': polygon.__geo_interface__,
'datetime': '2020-04-01/2020-04-10'
}).limit(100)
print(scenes.count())
100
I set the limit to 100 on purpose because it takes a long time to complete the request. Also I noticed that pystac-client is much faster than pyrasterframes STAC API
Activity
pomadchin commentedon Sep 20, 2022
Hey @ngulyaev definitely looks like a bug.
I think that's been addressed in terms of stac-utils/stac4s#496 and stac-utils/stac4s#502 (see stac-utils/stac4s#495 for the bug description). If you're on develop, it may be enough to bump stac4s dep up to 0.8.1. I forgot to create a PR with deps upgrade.
ngulyaev commentedon Sep 20, 2022
@pomadchin Thanks a lot, I tried to override jars through the spark settings but unfortunately it didn't help :
Maybe I'm doing it in wrong way? It seems that these filter parameters are simply ignored, it don't fail even if I pass a string object instead of geometry to 'intersects'
pomadchin commentedon Sep 20, 2022
@ngulyaev yea I don't think it would work this way, it will still prefer the transitive dep over the extra I think. Publishing the local version based on the current dev is the only real way to check it.