On Thu, 21 Jun 2018, Markus Metz wrote:
you need to patch together all bare earth coverages from all years in
order to get a more complete coverage
Markus,
I missed this point when I read the descriptive data. It certainly
explains why there's 2009_OLC_Hood-to-Coast, 2013_OLC_Clackamol,
On Thu, 21 Jun 2018, Daniel Victoria wrote:
Daniel,
What I've seen is that most of you data has values -3.4028e+38 which
appears to be the NODATA value. So, are you sure this part of the data is
not a corner of the mapped area? Because there is valid data for the upper
and left borders. Also,
On Thu, 21 Jun 2018, Markus Metz wrote:
No, they should not. They cover a part of that rectangle. You need to
patch coverages from different years together in order to get a more
complete coverage.
Markus,
Ah, I didn't realize this. That explains the why there are three files
with
Trying to help those trying to help Rich:
the tiling scheme is available in a web viewer here:
https://gis.dogami.oregon.gov/maps/lidarviewer/
the archive containing the data in question is available here:
http://www.oregongeology.org/pubs/ldq/LDQ-45122C3.zip (1.8 GB)
you need to patch
Rich,
I was able to open your GRID in QGis. And if it works in QGis, it should
work in GRASS too.
What I've seen is that most of you data has values -3.4028e+38 which
appears to be the NODATA value. So, are you sure this part of the data is
not a corner of the mapped area? Because there is valid
On Thu, Jun 21, 2018 at 7:24 PM, Rich Shepard
wrote:
>
> My problems are that pointing r.in.gdal to the hdr.adf files display
only
> the strange wedge/rectangle I attached to messages earlier in this thread.
> They should be retangles for a full 1 degree x 1 degree topographic quad
map
> with
On Thu, 21 Jun 2018, Rich Shepard wrote:
to replacing this ancient 32-bit system with a more capable 74-bit system.
Er, ... that should be 64-bit system.
Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
On Thu, 21 Jun 2018, Daniel Victoria wrote:
I tried to download the data you placed on file dropper (other email
tread). But both links you sent gave me corrupt files.
Daniel,
There was something funky going on with file dropper. But, I just
successfully uploaded bare_earth.tar.xz there:
OK.
I tried to download the data you placed on file dropper (other email
tread). But both links you sent gave me corrupt files.
If you can manage to place the files in some shared folder or point to the
original data source, I can take a look.
Have you tried opening in some other software, like
On Thu, 21 Jun 2018, Daniel Victoria wrote:
ESRI ArcINFO used two formats that spreded files into a directory with the
layer name and another directory called INFO. In the directory with the
layer name, the files had the .ADF extension you mentioned in the first
email. But their content is
Hi Rich,
Looks like I confused things a bit.
ESRI ArcINFO used two formats that spreded files into a directory with the
layer name and another directory called INFO. In the directory with the
layer name, the files had the .ADF extension you mentioned in the first
email. But their content is
Hi Rich,
You are correct about GRID being a raster format in ESRI world. But from
your description, I believe what you have is a coverage, which is ESRI
vector format for ArcINFO (shapefile beeing another vector format).
LiDAR data is obtained as XYZ point cloud. That's why you probably have
On Mon, 18 Jun 2018, Daniel Victoria wrote:
Actually, your ADF file is part of a vector format from ESRI named
Coverage, that includes some files in a folder with the name of your data
and some other data in a folder called INFO. Here is some more info on the
Coverage format [1]
Daniel,
I
Hi Rich,
Actually, your ADF file is part of a vector format from ESRI named
Coverage, that includes some files in a folder with the name of your data
and some other data in a folder called INFO. Here is some more info on the
Coverage format [1]
GDAL OGR can handle both shape and coverage formats
On Wed, 30 May 2018, Helmut Kudrnovsky wrote:
So you have to look by ogrinfo/gdalinfo --formats; you can get further
information on the GDAL Website.
I have LiDAR files in two ESRI formats and don't know which would be the
better one to use: .shp and .adf.
My research taught me that .adf
Rich Shepard wrote
> On Wed, 30 May 2018, Helmut Kudrnovsky wrote:
>
>> So you have to look by ogrinfo/gdalinfo --formats; you can get further
>> information on the GDAL Website.
>
> Helmut,
>
>Thank you for the reminder; I forgot about these tools. Here, all three
> formats are supported
On Wed, 30 May 2018, Helmut Kudrnovsky wrote:
So you have to look by ogrinfo/gdalinfo --formats; you can get further
information on the GDAL Website.
Helmut,
Thank you for the reminder; I forgot about these tools. Here, all three
formats are supported for vector files.
Best regards,
Rich
Rich Shepard wrote
> I see that gdal supports GeoPackage as well as ESRI's Shapefile and
> FileGDB. I want to write a script to convert all my existing data files
> and
> have not found a GRASS web page that tells me if grass7 supports this
> exchange format. I assume it does but haven't found
I see that gdal supports GeoPackage as well as ESRI's Shapefile and
FileGDB. I want to write a script to convert all my existing data files and
have not found a GRASS web page that tells me if grass7 supports this
exchange format. I assume it does but haven't found confirmation. Please
point me
19 matches
Mail list logo
