Re: [GRASS-user] Importing data in .atx/.gdb format [RESOLVED ... REALLY!]

2016-09-15 Thread Helmut Kudrnovsky
> In the ODOT2014 location I created an empty mapset called 'hwy_2015.gdb'. >Exited grass. Moved the contents of the downloaded source file (also called >'hwy_2015.gdb') into the new mapset. Then restarted grass. AFAIK it's not recommended to move/copy any foreign stuff not created by GRASS

Re: [GRASS-user] Importing data in .atx/.gdb format [RESOLVED ... REALLY!]

2016-09-15 Thread Rich Shepard
On Thu, 15 Sep 2016, Rich Shepard wrote: Ah, shoot! I thought I put the extension on the subdirectory name. Did so the first time but not when I moved it elsewhere. Renamed the subdirectory and, of course, that resolved the issue. Again, my apologies, Rich

Re: [GRASS-user] Importing data in .atx/.gdb format [RESOLVED ... REALLY!]

2016-09-15 Thread Rich Shepard
On Thu, 15 Sep 2016, Even Rouault wrote: Same here: it doesn't end with .gdb Ah, shoot! I thought I put the extension on the subdirectory name. Did so the first time but not when I moved it elsewhere. Mea culpa! Rich ___ grass-user mailing

Re: [GRASS-user] Importing data in .atx/.gdb format [RESOLVED ... REALLY!]

2016-09-15 Thread Rich Shepard
On Thu, 15 Sep 2016, Helmut Kudrnovsky wrote: what do you mean by "let grass create a new mapset, moved the source files there"? Helmut, In the ODOT2014 location I created an empty mapset called 'hwy_2015.gdb'. Exited grass. Moved the contents of the downloaded source file (also called

Re: [GRASS-user] Importing data in .atx/.gdb format [RESOLVED ... REALLY!]

2016-09-15 Thread Even Rouault
Le jeudi 15 septembre 2016 20:22:01, Rich Shepard a écrit : > On Thu, 15 Sep 2016, Even Rouault wrote: > > What do you exactly mean by "fail" ? Does it report something like > > > > FAILURE: > > Unable to open datasource `foo.gdb' with the following drivers. > > > > -> PCIDSK > > -> netCDF > >

Re: [GRASS-user] Importing data in .atx/.gdb format [RESOLVED ... REALLY!]

2016-09-15 Thread Rich Shepard
On Thu, 15 Sep 2016, Even Rouault wrote: What do you exactly mean by "fail" ? Does it report something like FAILURE: Unable to open datasource `foo.gdb' with the following drivers. -> PCIDSK -> netCDF -> JP2KAK Even, Yep. ogrinfo reported it could not open the data source with any

Re: [GRASS-user] Importing data in .atx/.gdb format [RESOLVED ... REALLY!]

2016-09-15 Thread Helmut Kudrnovsky
>The location is the same as the previous map so I let grass >create a new mapset, moved the source files there, restarted grass, and was >told there was no layers selected. what do you mean by "let grass create a new mapset, moved the source files there"? moving the filegdb directory to a

Re: [GRASS-user] Importing data in .atx/.gdb format [RESOLVED ... REALLY!]

2016-09-15 Thread Even Rouault
>I just tried to import a different transportation map in OpenFileGDB > without success. The location is the same as the previous map so I let > grass create a new mapset, moved the source files there, restarted grass, > and was told there was no layers selected. That's because none were >

Re: [GRASS-user] Importing data in .atx/.gdb format [RESOLVED ... REALLY!]

2016-09-15 Thread Rich Shepard
On Thu, 15 Sep 2016, Even Rouault wrote: You can use ogrinfo -al -so (-so means Summary Only) to avoid listing the features and get only projection info, feature count and field definitions. Will save you a few gigabytes. I just tried to import a different transportation map in OpenFileGDB

Re: [GRASS-user] Importing data in .atx/.gdb format [RESOLVED ... REALLY!]

2016-09-15 Thread Rich Shepard
On Thu, 15 Sep 2016, Even Rouault wrote: I've just added support in the OGR FileGDB & OpenFileGDB drivers for '.' as a valid dataset name (the resolved directory of '.' must still end up with .gdb) Even, Thank you. For some of us ... me, at least ... using '.' to represent the pwd is

Re: [GRASS-user] Importing data in .atx/.gdb format [RESOLVED ... REALLY!]

2016-09-15 Thread Even Rouault
Le mercredi 14 septembre 2016 23:47:57, Rich Shepard a écrit : > On Wed, 14 Sep 2016, Helmut Kudrnovsky wrote: > > "." is this really your directory which holds the filegdb data? > > Helmut, > >Bash recognizes this as cwd (current working directory). However, ... I've just added support in

Re: [GRASS-user] Importing data in .atx/.gdb format [RESOLVED ... REALLY!]

2016-09-14 Thread Rich Shepard
On Wed, 14 Sep 2016, Helmut Kudrnovsky wrote: "." is this really your directory which holds the filegdb data? Helmut, Bash recognizes this as cwd (current working directory). However, ... Here's a summary of what I did so that others can gain from my learning and import a OFGDB data