Comments (11)
As you may guess, the release process is not entirely ironed out. I find the wiki easier to edit than creating pull requests for each tweak. But contributions adding a release.md
that points to the wiki are welcome. And when everything is solid, we can get rid of the wiki page in favor of a release.md
file if people want.
Update: #181 adds a RELEASE.md
doc.
from geoparquet.
Yeah, I was just starting to address this.
I wrote up these steps for creating a release: https://github.com/opengeospatial/geoparquet/wiki/Release-Process
These steps include updating the version numbers scattered throughout the repo before creating the release tag.
At this point, I think it would be fine to delete the rc.1 tag and start over with the steps on the above wiki page.
I would do this, except I am wrestling with the python dependencies required by the scripts
that update the example data and example metadata. If anybody can update the instructions to get set up to run the python in the scripts
directory, please do so.
from geoparquet.
Failure to install pyarrow. It looks like I had a brew installed version of poetry. Trying again using the poetry installer.
from geoparquet.
No problem, @cholmes. @m-mohr was right that the release doc on the wiki page was not easy to find - I even forgot having written it. It was good to tidy up a few things as a result of this. I think #180 is one thing that warrants further discussion before 1.0.
from geoparquet.
The geoparquet.md also says "1.0.0-dev": https://github.com/opengeospatial/geoparquet/releases/download/v1.0.0-rc.1/geoparquet.md
I assume there could be more instances where the replacement doesn't work. Or you forgot to just update the references in #176, but as there was no response to my comment I assumed there would be some kind of replacement magic happen in the release process.
The archives, e.g. https://github.com/opengeospatial/geoparquet/archive/refs/tags/v1.0.0-rc.1.zip, are similarly broken.
from geoparquet.
I would do this, except I am wrestling with the python dependencies required by the
scripts
that update the example data and example metadata. If anybody can update the instructions to get set up to run the python in thescripts
directory, please do so.
What's the issue you're hitting here?
from geoparquet.
Great, thanks.
I wrote up these steps for creating a release: https://github.com/opengeospatial/geoparquet/wiki/Release-Process
Maybe put them in a release.md in the main repo? That's much more common, I never even expect someone using/filling the Wiki...
from geoparquet.
Oh I just tried to install it on my M1 Mac and it failed because it's still using pygeos and that is trying to compile from source for some reason.
Is anyone still using write_nz_building_outline.py
or can/should we delete it? @cholmes was the only one I knew who was using it I think.
from geoparquet.
I created #178 with some additional detail on the failure I'm hitting with a "fresh" poetry install. Not entirely sure how to start over (perhaps I have stale/conflicting/outdated/bad things installed), but I'll keep trying.
from geoparquet.
https://github.com/opengeospatial/geoparquet/blob/v1.0.0-rc.1/format-specs/schema.json now has the correct version number (updated in 6a9c43e).
from geoparquet.
Hey all, thanks for the help on this - I appreciate it, and sorry for messing it up. Thanks for fixing up my mess.
from geoparquet.
Related Issues (20)
- Declare `Z` in the geometry type? HOT 5
- Geometry types HOT 1
- Add tests on JSON schema, to ensure that updates to the schema are valid / good
- Publish schemas on geoparquet.org HOT 1
- Consistent case HOT 1
- Propose and document release process HOT 2
- Cut new release HOT 2
- make website to share info about geoparquet HOT 2
- Default value of the crs field is too vague
- Restrictions on column names? HOT 1
- value not present vs null HOT 2
- Clarify support for zero geometry columns HOT 2
- PROJJSON for CRS, WKT for CRS and ISO19111 HOT 6
- WKT support for 3/4D using Z and/or M HOT 10
- Simplify or remove script dependencies HOT 3
- PROJJSON schema version HOT 4
- Metadata encoding options for GeoArrow-encoded columns in GeoParquet metadata HOT 2
- Is it possible to define a transform alongside a CRS, similar to geotiff? HOT 3
- Recommendation on the Arrow specific type for the WKB geometry column ? HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from geoparquet.