Skip to content
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

collections/{collection_id}/items and collections/{collection_id}/items/{item_id} return incorrect results #345

Closed
davidraleigh opened this issue Feb 15, 2022 · 4 comments · Fixed by #346
Assignees
Labels

Comments

@davidraleigh
Copy link
Contributor

davidraleigh commented Feb 15, 2022

Summary

Seeing incorrect results for collections/{collection_id}/items and collections/{collection_id}/items/{item_id}. Maybe this is a pgstac error?

To Reproduce

add lines to create empty-collection at end of ingest_joplin_data function (right below line 44):

    collection["id"] = "empty-collection"
    post_or_put(urljoin(app_host, "/collections"), collection)

run pgstac app

git checkout 2.3.0
docker-compose build
docker-compose -d app-pgstac
python scripts/ingest_joplin.py http://localhost:8082

Expected

Actual results

@vincentsarago
Copy link
Member

@bitner
Copy link
Collaborator

bitner commented Feb 15, 2022

PR bumping pgstac version that should fix this incoming.....

@bitner bitner self-assigned this Feb 15, 2022
@bitner bitner added the pgstac label Feb 15, 2022
@bitner bitner mentioned this issue Feb 15, 2022
4 tasks
@davidraleigh
Copy link
Contributor Author

Thank you for the heads up on 0.4.5.

It solves my issue for these two routes

But this route is still returning results for joplin when empty-collection is empty

@davidraleigh
Copy link
Contributor Author

let me know if you want me to close this issue, change this issue to address the lack of a 404 returned for an empty collection with a joplin stac id, or open a new issue for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants