On Thu, 15 Sep 2016, Markus Neteler wrote:
Seems we are back on track? Please update and let us know.
Markus, Yes, we're back on the tracks. My project's location report: GRASS 7.3.svn ~/projects/oregon/<proj_name>/data/features > g.proj -pt -PROJ_INFO------------------------------------------------- name : NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601_Feet_Intl datum : nad83harn ellps : grs80 proj : lcc lat_1 : 44.33333333333334 lat_2 : 46 lat_0 : 43.66666666666666 lon_0 : -120.5 x_0 : 2500000 y_0 : 0 no_defs : defined -PROJ_UNITS------------------------------------------------ unit : Foot units : Feet meters : 0.3048 The OpenFileGDB roads location report: GRASS 7.3.svn (ODOT2014):~/data/grassdata/ODOT2014 > g.proj -pt -PROJ_INFO------------------------------------------------- name : NAD83 / Oregon Lambert (ft) datum : nad83 ellps : grs80 proj : lcc lat_1 : 43 lat_2 : 45.5 lat_0 : 41.75 lon_0 : -120.5 x_0 : 399999.9999984 y_0 : 0 no_defs : defined -PROJ_EPSG------------------------------------------------- epsg : 2992 -PROJ_UNITS------------------------------------------------ unit : foot units : feet meters : 0.3048 And v.proj run from the project location has no complaints about transforming projection data from the source location. The state is supposed to have a single projection so it's interesting to learn that map sets from two different state agencies have slightly different parameters. I don't mind testing in the corners of the development (trunk) branch. Thanks to Even, Martin, and you for taking the time to patch things, Rich _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user