Cut 0.2.0 release sooner (without spatial index)? #44
cholmes
started this conversation in
Specification
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Seeing a handful of issues that might be nice to get fixed sooner rather than later:
#41 - Have a type field to give clients a hint of what geometry type to expect
#18 - Looks like everyone is leaning towards ISO WKB, so could just get that set
We could also tackle #35, though that perhaps needs more discussion, and I'm thinking of just trying to get out a 0.2.0 in the next few days.
There's also #42: we could change version to schema-version. And even if we don't it seems cleaner to have a 0.2.0 release that is consistent, since right now most all 0.1.0 files won't have the version, but if we update the tools then we'll still have all old existing files as 0.1.0 but not quite following the spec. If we release 0.2.0 then all data will be consistent with the tools.
Then 0.3.0 would be the target for the spatial index.
Beta Was this translation helpful? Give feedback.
All reactions