You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not correct to detect the UTM zone by the first coordinate.
For example, the first point can be in one zone, and all geometry in another.
It is more correct to determine the geometry center of mass, and it is better to return all UTM zones in which the geometry is located, sorted by intersection area.
The text was updated successfully, but these errors were encountered:
While I agree that the first point might seem simplistic and opens up for a lot of problems, I think if you have a geometry that spans more than one zone, you are going to end up with problems even if you you centroid/center of mass: parts of the geometry will still be outside the returned zone.
That is, if your geometry spans more than one zone, there simply is no well-defined answer to the question which zone it is in. Yes, we could traverse all coords and return all possible zones, but it would also be pretty easy to call the library like that if that's what you need. Another solution would maybe be throwing an error. That would however be a bad solution for our actual use case for this module, so it's not a change I'm keen on implementing.
It is not correct to detect the UTM zone by the first coordinate.
For example, the first point can be in one zone, and all geometry in another.
It is more correct to determine the geometry center of mass, and it is better to return all UTM zones in which the geometry is located, sorted by intersection area.
The text was updated successfully, but these errors were encountered: