Re: [GRASS-user] Estimating import time for large data file

On Sun, 31 May 2020, Helmut Kudrnovsky wrote: thus I suggest, as already before, to use another projection appropriate for your working area. Helmut, I haven't clearly communicated. I don't care about the projection of the source file as long as I can import it into GRASS. Once imported I

Re: [GRASS-user] Estimating import time for large data file

Rich Shepard wrote > On Sun, 31 May 2020, Helmut Kudrnovsky wrote: > >> it seems the projection of your data (+proj=merc) doesn't correpond to >> the >> Enterprise Office's projections you mentioned (+proj=lcc, +proj=lcc, >> +proj=longlat) > > Helmut, > > That's true. So I created a new

Re: [GRASS-user] Estimating import time for large data file

On Sun, 31 May 2020, Helmut Kudrnovsky wrote: it seems the projection of your data (+proj=merc) doesn't correpond to the Enterprise Office's projections you mentioned (+proj=lcc, +proj=lcc, +proj=longlat) Helmut, That's true. So I created a new location for this huge shapefile. The issue has

Re: [GRASS-user] Estimating import time for large data file

Rich Shepard wrote > On Sun, 31 May 2020, Helmut Kudrnovsky wrote: > >> is it >> EPSG:3857 [1] [2] >> ? > > Helmut, > > I've no idea. This dataset was downloaded from the Oregon Geospatial > Enterprise Office (clever name, eh?). The introductory page is here: >

Re: [GRASS-user] Estimating import time for large data file

On Sun, 31 May 2020, Helmut Kudrnovsky wrote: is it EPSG:3857 [1] [2] ? Helmut, I've no idea. This dataset was downloaded from the Oregon Geospatial Enterprise Office (clever name, eh?). The introductory page is here: . Oregon provides data

Re: [GRASS-user] Estimating import time for large data file

Rich Shepard wrote > On Sun, 31 May 2020, Markus Neteler wrote: > >> I didn't confirm at all :-) It was just an information or warning. > > Markus, > > Using ogr2ogr was what Moritz suggested. > >> I'd stick to submeter but I don't know what data you are working with >> nor what their

Re: [GRASS-user] Estimating import time for large data file

On Sun, 31 May 2020, Markus Neteler wrote: I didn't confirm at all :-) It was just an information or warning. Markus, Using ogr2ogr was what Moritz suggested. I'd stick to submeter but I don't know what data you are working with nor what their resolution/scale is... This is what the

Re: [GRASS-user] Estimating import time for large data file

Rich, On Sun, May 31, 2020 at 6:31 PM Rich Shepard wrote: > > On Sun, 31 May 2020, Markus Neteler wrote: > > > ogr2ogr > > -simplify > >Distance tolerance for simplification. Note: the algorithm used > > preserves topology per feature, in particular for polygon geometries, but > > not for

Re: [GRASS-user] Estimating import time for large data file

On Sun, 31 May 2020, Markus Neteler wrote: ogr2ogr -simplify Distance tolerance for simplification. Note: the algorithm used preserves topology per feature, in particular for polygon geometries, but not for a whole layer. Markus, Thanks for confirming this approach. ... keep in mind

Re: [GRASS-user] Estimating import time for large data file

On Fri, May 29, 2020 at 2:52 PM Moritz Lennert wrote: > On 29/05/20 14:37, Rich Shepard wrote: > > On Fri, 29 May 2020, Moritz Lennert wrote: ... > Another, untested, path for possibly speeding up import: use ogr2ogr > with the -simplify option to first simplify the geometry, if that is >

Re: [GRASS-user] Estimating import time for large data file

On Fri, 29 May 2020, Moritz Lennert wrote: grass --help is your friend ;-) Moritz, Good to know; I never tried this. grass -c epsg:4326 GISDBASE/LOCATION replace GISDBASE and LOCATION with the respective names -c can also be used with a file: -c /path/to/georeferenced/file Thanks

Re: [GRASS-user] Estimating import time for large data file

On 29/05/20 14:37, Rich Shepard wrote: On Fri, 29 May 2020, Moritz Lennert wrote: Importing such a large file can take a lot of time because of the cleaning in order to get it into GRASS GIS' topological format. Moritz, I assumed it would taka a while, but it seemed to be stuck. Perhaps

Re: [GRASS-user] Estimating import time for large data file

On Fri, 29 May 2020, Moritz Lennert wrote: Importing such a large file can take a lot of time because of the cleaning in order to get it into GRASS GIS' topological format. Moritz, I assumed it would taka a while, but it seemed to be stuck. Perhaps because that polygon was large, complex,

Re: [GRASS-user] Estimating import time for large data file

On 28/05/20 17:25, Rich Shepard wrote: I'm trying to import (using v.in.ogr) a rather large file (1.22G *.shp and 4.5M *.dbf). I see a lot of system disk reads, low cpu usage, but after a half-hour it appears to have stopped processing. Importing such a large file can take a lot of time