#16 closed defect (fixed)
Area measurement values too large
Reported by: | bfraser | Owned by: | |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | GeoMOOSE/JS | Version: | 2.6 |
Keywords: | Cc: |
Description
Area measurement values too large by a couple of orders of magnitude (an area of about 1 square mile is reported as 1546.85 somethings)
Change History (3)
comment:1 by , 13 years ago
Priority: | major → critical |
---|
comment:2 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 12 years ago
Here's my test:
- I zoomed to a relatively square parcel, PIN = 130250001050 and measured it. Total sq meters: 659637. I did a *very* rough measurement.
- I used ogrinfo to look up the parcel:
ogrinfo -sql "select * from parcels where PIN = '130250001050'" parcels.shp
- I used the WKT from OGR to import it into python and measure the area:
python from osgeo import ogr g = ogr.CreateGeometryFromWkt('POLYGON ((485913.017479933565482 4934701.067506796680391,486013.56988882512087 4934700.510960625484586,486193.935001186735462 4934699.512649787589908,486315.824376355740242 4934698.837991303764284,486718.631217579299118 4934696.60840945225209,486718.695145161706023 4934686.55355294700712,486723.768515298201237 4933888.604368083178997,485918.672129619633779 4933895.632465255446732,485913.088064994546585 4934691.013341022655368,485913.017479933565482 4934701.067506796680391))'); g.GetArea()
g.GetArea() returned 649664.68. That's close enough for me with the precision level I was at.
I then tested converting that value to square miles, acres, and square yards. Both in the application and in Google Calculator. They all came out correct.
Note:
See TracTickets
for help on using tickets.
I think I fixed the goofy measurments. refs: [618]