ogrinfo -al -so on the .gdb produces this output:
Layer name: WSDACrop_2016
Geometry: Multi Polygon
Feature Count: 198132
Extent: (194040.798600, 26290.144100) - (776078.287500, 411036.825500)
Layer SRS WKT:
PROJCRS["NAD83(HARN) / Washington South",
BASEGEOGCRS["NAD83(HARN)",
Environment: grass7.9.dev updated 17 August on Slackware-14.2/x86_64.
I have a land use shapefile and created a new location for it based on the
.prj file. Importing via v.in.ogr grass suggested re-importing with a snap
distance. I did this 7 times, each using the gradually incrasing snap
On Mon, 17 Aug 2020, Markus Neteler wrote:
Maybe here?
https://grasswiki.osgeo.org/wiki/PostGIS#Direct_access_to_PostGIS_data_.28GRASS_7_only.29
Direct access to PostGIS data (GRASS 7 only)
Markus,
Perhaps. I don't recall.
Thanks,
Rich
___
On Sat, Aug 15, 2020 at 2:50 PM Rich Shepard wrote:
>
> On Sat, 15 Aug 2020, Micha Silver wrote:
>
> > But again, don't confuse - this is NOT PostGIS, and GRASS does not
> > need/use PostGIS for geometry. GRASS geometry is always independent of any
> > external geospatial format.
>
> Micha,
>
>
On Mon, 17 Aug 2020, Rich Shepard wrote:
Please educate me what I've done incorrectly here.
grass79 -c EPSG:2927 /data/grassdata/Washington/cities/
That's the ultimate destination; the correct new location is
/data/grassdata/wa_cities. This resolves the issue.
Rich
On Sun, 16 Aug 2020, Jeff McKenna wrote:
This is EPSG:2927 see: http://epsg.io/2927
Jeff, et al.:
Please educate me what I've done incorrectly here.
Using the above EPSG (with /data/grassdata/ as the pwd) I entered:
grass79 -c EPSG:2927 /data/grassdata/Washington/cities/
which is the
