-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Geometry and date filters don't work in pyrasterframes STAC API #590
Comments
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. |
@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' |
@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. |
Result of the same query using pystac-client:
Using the pyrasterframes STAC API:
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
The text was updated successfully, but these errors were encountered: