Updates for the 1.1.0 release

[cholmes]

This branch prepares everything for release, in the hopes of being able to discuss the final issues in the next meeting and finalize the release. The remaining issues to discuss and potentially merge includes:

#227 - schema version for projjson
#198 - antimeridian crossing - @jorisvandenbossche had some potential ideas.
#123 - Test data - not sure if Joris had a couple more he wanted to get in.
#229 - version compatibility suggestion that just landed, but seems pretty good.

[tschaub]

It looks like there is another version number in the example_metadata.json file that needs to be manually updated as part of the release process (alternatively, maybe the scripts/generate_example.py script could be updated to generate this file so we have fewer places to update version numbers).

geoparquet/examples/example_metadata.json

Line 138 in a684d7a

"version": "1.1.0-dev"

[cholmes]

It looks like there is another version number in the example_metadata.json file that needs to be manually updated as part of the release process (alternatively, maybe the scripts/generate_example.py script could be updated to generate this file so we have fewer places to update version numbers).

Good catch, thanks. Will fix it (and at least mention something in the release wiki).

[cholmes]

@tschaub - I think this is right on this branch. Your link in the comment looks like it goes to the PR for the projjson schema fix - a684d7a. I see it right on the 1.1 release branch.

Let me know if I'm missing anything.

[tschaub]

My bad. Looks right in this change.

[cholmes]

No prob! Thanks for checking. A +1 on the release is appreciated :)

[cholmes]

Ok, I think this is all ready to go. Approvals are now open! Our conclusions on the call were as follows:

#227 - (projjson schema version update) datemerged
#198 - (antimeridian crossing) - we don't feel like we have a great solution all ready, so moving to 1.2 and retaining the official guidance of just saying 'don't do that'.
#123 - Test data - Joris may try to get something in, but there's lots more test data, we're just missing some for 1.0, which we didn't have for 1.0 anyways, so we decided not to block on this (but he may try to get it in soon).
#229 - (version compatibility) merged - with a bit of back and forth on 'forward compatibility'.

And I couldn't find where @tschaub pointed out that the version was off. If reviewers could make sure that there are no 1.1.0-dev versions anywhere on this branch then that'd be much appreciated.

I'm aiming for at least 4 +1's before releasing. When we've got that I'll tag the release and push it out. Thanks all!

[tschaub]

Looks like it is the example_metadata_point.json file that has the wrong version number:

geoparquet/examples/example_metadata_point.json

Line 12 in 3048e5f

"version": "1.1.0-dev"

We could:

1. manually update the version number in this file as well and update the release process so that others do the same in the future
2. remove this file (not clear to me that it is used)
3. update things so that this file is generated from a corresponding example_point.parquet file (that would be generated from the generate_example.py script and would mean fewer version numbers to maintain)

Any preferences?

[cholmes]

Good catch.

I think for now I lean towards #2, as I'm not clear what it's for, and then at some point get better test data.

[cholmes]

Oh wait, I see, it's meant to be an example of the geoarrow encoding. So probably shouldn't just remove it. Ideally we'd have an example that is actually in the geoarrow encoding in parquet, not just the metadata.

[tschaub]

I updated the version in example_metadata_point.json and opened #232 to suggest consolidating the example/test data.