[go: up one dir, main page]

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

Example data to test implementations #123

Open
cholmes opened this issue Oct 24, 2022 · 2 comments
Open

Example data to test implementations #123

cholmes opened this issue Oct 24, 2022 · 2 comments
Assignees
Milestone

Comments

@cholmes
Copy link
Member
cholmes commented Oct 24, 2022

One idea that @jorisvandenbossche suggested is that we should have a set of data that shows the range of the specification, that implementors can use to make sure they're handling right, and which could be the basis of 'integration' testing.

This would include geoparquet files that have a variety of projections, geometry types (including multiple geometry types as in #119), plus things like multiple geometry columns, different edges values, etc. It could also be good to have a set of 'bad' files that can also be tested against.

@cholmes
Copy link
Member Author
cholmes commented May 29, 2024

There was also work on this in #204 for the new geometry encodings. We should figure out if we want to try to do more for 1.1

@jorisvandenbossche
Copy link
Collaborator

If I can finish #134, then I think we can close this issue with that PR

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

No branches or pull requests

2 participants