[GRASS-user] Unusual [Open|ESRI]FileGDB: how to import

[Markus Metz]

On Thu, Oct 26, 2017 at 11:47 PM, Rich Shepard <rshepard at appl-ecosys.com>
wrote:
>
> On Thu, 26 Oct 2017, Even Rouault wrote:
>
>> You forgot +lon_0, and a bit counter-intuitively , proj.4 requires x_0 to
>> be expressed in meters (*)
>
>
> Even,
>
>   OK. Thanks.

Instead of manually creating a proj.4 definition, you can use
v.in.ogr in=BullTrout_201201_v931.gdb location=bulltrout_location -i

to create a location from that gdb. If you don't use the -i flag, the data
will also be imported into the new location.

With GRASS 7.3, v.in.ogr will report back if there are any problems with
the included SRS, or if no SRS is available for the selected layer.

Markus M

>
>> So try instead
>
>
>> +proj=lcc +lat_1=42.33333333333334 +lat_2=48.66666666666666 +lat_0=41
>> +lon_0=-117 +x_0=914401.8287999999 +y_0=0 +datum=NAD83 +units=us-ft
>> +no_defs
>
>
>> (hint: was given by "gdalsrsinfo the.gdb")
>
>
>   This is a new one for me.
>
>   Is it common for *FileGDB formats to not have EPSG codes?
>
> Regards,
>
>
> Rich
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20171027/7c28eae2/attachment.html>