Errors in v.proj, m.get.stp, & m.setproj

[Ronald Thomas]

GRASSusers,

I reported an error to the bugs.list, and want to share it with the general
users.

When using m.set.stp or m.setproj to set up a state plane projection in a
mapset, beware of errors. Here in northern Colorado, these programs select
the central Colorado state plane zone (502)  for Larimer County, when in
fact, the county is in the northern zone (501).  If you use v.proj to
transform data, be aware that it uses m.setproj to create projection
reference files in the new state plane mapset, and its output should be
checked for errors.

Now that I have data transformed from my UTM mapset to a state plane
mapset, I'm having trouble setting/changing the region within the state
plane mapset.  Am I correct in assumming that in order to make full use
of the state plane data, I must copy the state plane mapset from the UTM 
location into a separate State Plane location?  

Thank you to all that answered my r.mapcalc/floating point question last
week, and I'm glad to see it started such a vigorous discussion on
the subject!!

^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
   Ronald Thomas                         ^  ront at meeker.cfnr.colostate.edu
    Natural Resources Spec. (GIS)        ^  
     Resources Management Division       ^   Phone: 303-586-3565  x285
      Rocky Mountain National Park       ^          700-323-7285  (FTS)
       Estes Park, CO  80517             ^ 
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^