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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: Ldp [Added to the original trac issue at 9.04pm, Wednesday, 14th July 2010]
I'd prefer if way_area was consistently correct, independent of the projection. If we start making more rendering decisions based on polygon size, it needs to make the same decisions for both 900913 and 4326.
Author: TobWen [Added to the original trac issue at 9.14pm, Wednesday, 14th July 2010]
I've done some calculations directly using spheroid geometry (geodetic on WGS84). It's valid all over the globe, even on very big polygons. The problem is the area is built up by GEOS when the coordinates are projected already. So I never can grab the original coordinates calculate the geodetic area ;-(
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Reporter: TobWen
[Submitted to the original trac issue database at 2.49pm, Wednesday, 14th July 2010]
When using projection 4326 on osm2pgsql import, way_area might get zero if it's too small. This can mess up sorting.
Possible solutions:
Remarks:
The text was updated successfully, but these errors were encountered: