Opened 8 years ago
Closed 3 years ago
#27550 closed New feature (fixed)
add version of GEOSGeometry.normalize() that returns new geometry
| Reported by: | Sergey Fedoseev | Owned by: | Marcelo Galigniana |
|---|---|---|---|
| Component: | GIS | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
GEOSGeometry.normalize() normalizes geometry in-place. In some cases it would be more convenient to have a cloned normalized geometry for the code conciseness.
We could add clone kwarg to this method similarly to GEOSGeometry.transform() or we could add the normalized property.
Change History (11)
comment:1 by , 8 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 8 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 8 years ago
comment:4 by , 8 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
Accepting the problem, even if the solution is undecided.
comment:5 by , 3 years ago
| Owner: | removed |
|---|---|
| Status: | assigned → new |
comment:6 by , 3 years ago
Could I go for the "add clone kwarg to this method similarly to GEOSGeometry.transform()" approach?"
Or should I post in the developer email group to define the best solution?
Version 0, edited 3 years ago by (next)
comment:8 by , 3 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:9 by , 3 years ago
| Has patch: | set |
|---|
comment:10 by , 3 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
Note:
See TracTickets
for help on using tickets.
I'm not sure. Could you audit other methods and tell us if the use case could be applied to other methods? Then we might better recommend using the
clone()method before normalizing the geometry.