cligj
cligj copied to clipboard
Click-based argument and option decorators for Python GIS command line programs
This constraint, forces all downstream poetry users to also pin the upper python version which depending on the use case might not be desirable. This PR removes the constraint. Fixes...
Could you, please consider removing python < 4 constraint? It forces all downstream poetry users to add it :(
Remove Python 3.7 Due to compatibility issues that are not caused by the project we skip 3.7 ref : https://github.com/TheKevJames/coveralls-python/pull/337
line 18. mess up the codespell check.
The following incorrectly formatted geojson source will result in an internal server error: ``` {"type": "MultiPoint", "geometry": [[134.519974,34.084171],[134.546188,34.081322],[134.546219,34.078766],[134.542374,34.081287]]} {"type": "MultiPoint", "geometry": [[130.405380,33.571598],[130.383682,33.567059],[130.486740,33.652233],[130.455490,33.597004],[130.437195,33.601784],[130.447998,33.654606],[130.409592,33.606941]]} ``` This PR adds an `else` case to...
Since we have removed the upper limit on supported versions of click (see #37).
If we followed https://numpy.org/neps/nep-0029-deprecation_policy.html we might support only 3.7+ for a release in early 2021.
New features.
Resolves #19 TODO: obviously this changes the output of some programs like rio-shapes. I'm going to do a survey for those.
Current default is feature collections. Would be a major breaking change, but it seems to me that feature sequences are more flexible than collections are and scale better. What say...