On Fri, 9 Sep 2016, Micha Silver wrote:
Maybe I'm not following your workflow exactly, but...
Micha,
My workflow may well be the cause of the problem. That's what I want to
determine.
Did you first run v.in.ascii in a Long/lat location?
Yes.
... so I moved the source to a new mapset in the Oregon long/lat NAD83
location (which is the target projection and coordinate system (unless the
HARM adjustment changed things).
Once you have the vector map in a long/lat location, then switch to your
Oregon HARN 1983 Location and then do v.proj.
That's what I did.
Importing the source .txt file into the Oregon-ll83 location's project
mapset with v.in.ascii gave me a vector file in x-y coordinates.
Restarting grass in the target location/mapset I ran 'v.proj
location=Oregon-ll83 mapset=4247.01 input=proj_bnd' (all on one command
line).
Thanks,
Rich
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
