Re: [postgis-users] Strange ST_Area problem

2012-03-25 Thread Mike Toews
On 25 March 2012 12:19, Eric Ladner wrote: > Would EPSG:32230 be appropriate?  (WGS 72, UTM > zone 30N)  I'm dealing with things roughly in the 30.0 to 31.0N range. EPSG:32630 is a better projected reference, since it shares the same spheroid, WGS 84, as EPSG:4326 (rather than mixing in the older

Re: [postgis-users] Strange ST_Area problem

2012-03-24 Thread Eric Ladner
On Sat, Mar 24, 2012 at 11:06 AM, Stephen Woodbridge wrote: > st_area returns in the same units as the input data. So data in 4326 is > degrees and you numbers are in degrees squared. If you want the number in > meters or feet then project then into an appropriate UTM or equal area > projection.

Re: [postgis-users] Strange ST_Area problem

2012-03-24 Thread Stephen Woodbridge
st_area returns in the same units as the input data. So data in 4326 is degrees and you numbers are in degrees squared. If you want the number in meters or feet then project then into an appropriate UTM or equal area projection. -Steve On 3/24/2012 11:48 AM, Eric Ladner wrote: I've got some

[postgis-users] Strange ST_Area problem

2012-03-24 Thread Eric Ladner
I've got some building outlines that I'm pretty sure I've worked with before. They are all srid 4326 (lat/lon), converted from a SHP file. ST_Area returns extremely small numbers for any of the buildings. It's almost like it's looking at the data like they are absolute numbers instead of lat/lon.