Does r.poly support lat/lon?

We suspect r.poly may not work properly for lat/long projections.
Overlaying the resulting vector data over the original raster data
shows the edge lines to be fractionally offset, both N to S, and E to W.

Can anyone verify that lat/long support is implemented for r.poly?
IF so, have we encountered a bug, or a user error?

greg

******************************************************************************
Greg Koerper Internet: greg@heart.cor.epa.gov
ManTech Environmental Technology, Inc. UUCP: hplabs!hp-pcd!orstcs!koerper
200 SW 35th St., JSB
Corvallis, OR 97333 "The 90s will make the 60s look like the 50s.
(503) 754-4490 Just ask your kids."
fax: (503) 754-4338
******************************************************************************

In info.grass.user you write:
r.poly was NOT included in the lat/lon work. In general, the lat/lon
is far from finished, and the vector side of grass is particular
ignorant of lat/lon (which the few exception of d.vect and v.to.rast).

We suspect r.poly may not work properly for lat/long projections.
Overlaying the resulting vector data over the original raster data
shows the edge lines to be fractionally offset, both N to S, and E to W.

Can anyone verify that lat/long support is implemented for r.poly?
IF so, have we encountered a bug, or a user error?

greg

******************************************************************************
Greg Koerper Internet: greg@heart.cor.epa.gov
ManTech Environmental Technology, Inc. UUCP: hplabs!hp-pcd!orstcs!koerper
200 SW 35th St., JSB
Corvallis, OR 97333 "The 90s will make the 60s look like the 50s.
(503) 754-4490 Just ask your kids."
fax: (503) 754-4338
******************************************************************************

--

Michael Shapiro U.S. Army CERL
Environmental Division
P.O. Box 9005
Champaign, Ill. 61826-9005

email: shapiro@zorro.cecer.army.mil
phone: (217) 352-6511 ext 526
fax: (217) 373-7222