On Tue, 20 Sep 2016, Rich Shepard wrote:
Now that is really interesting. Running 'gdalinfo --formats' produces a
list that does not include MrSid, which explains why grass did not want to
import the .sid file. Time to recompile gdal.
I had an old version of gdal installed and just upgraded t
On Tue, 20 Sep 2016, Daniel Victoria wrote:
From what I read, you should point to the .sid file. But check if your
gdal is compiled with MrSID support. A gdalinfo on the file should inform
you if your gdal install can handle such files
Daniel,
Now that is really interesting. Running 'gdalin
>From what I read, you should point to the .sid file. But check if your gdal
is compiled with MrSID support. A gdalinfo on the file should inform you if
your gdal install can handle such files
On Tue, Sep 20, 2016 at 4:07 PM, Rich Shepard
wrote:
> On Tue, 20 Sep 2016, Rich Shepard wrote:
>
> Ne
On Tue, 20 Sep 2016, Rich Shepard wrote:
Never mind. I looked up the EPSG code and entered that directly.
However, I'm not finding the correct file at which to point grass.
r.in.gdal fails because it cannot find any bands. My web searches on how to
import a MrSID file all point me to the r
On Tue, 20 Sep 2016, Rich Shepard wrote:
Which file should I use to inform the grass GIS of the MrSID projection?
Never mind. I looked up the EPSG code and entered that directly.
Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
http://
A DRG file is in MrSID format with these files available: drg_s_or071.aux,
drg_s_or071.sid, drg_s_or071.sid.xml, drg_s_or071.sdw, and
drg_s_or071.sid.html.
The accompanying .txt file tells me the projection is UTM Zone 10. To
create a new location for this map I need to specify the file holdi
