Yes, I have used QGIS, and it works perfectly. However, my requirement is
to create map services using ArcGIS Server, so unfortunately QGIS isn't an
option for this task.
Thanks,
Jason
On Thu, Apr 7, 2016 at 9:46 AM, Jerl Simpson wrote:
> Just out of curiosity, have you tried using QGIS?
> It
Just out of curiosity, have you tried using QGIS?
It might solve the issue for you...or might just be a goose chase.
Jerl Simpson
V.P. Systems Engineering
Weather Trends Internationalhttp://www.weathertrends360.com/
This communication is privileged and may contain confidential information.
It's i
Trent,
I am able to load the VRT in ArcMap, and while it does now recognize -128
as the NoData value, it is identifying the raster as unsigned byte despite
the section workaround given by Even, and thus does not properly
respect the NoData areas. This is strange since it recognizes the original
Thanks for the workaround and quick fix. The VRT addresses the issue on
the data end. Now it's only an ArcGIS problem :)
Jason
On Wed, Apr 6, 2016 at 3:10 PM, Even Rouault
wrote:
> Le mercredi 06 avril 2016 20:38:36, Jason Greenlaw - NOAA Affiliate a
> écrit :
> > Hello,
> >
> > I've run int
Le mercredi 06 avril 2016 20:38:36, Jason Greenlaw - NOAA Affiliate a écrit :
> Hello,
>
> I've run into a snag trying to assign a negative NoData value to a Signed
> Byte raster.
Jason,
I've just pushed a fix for that in trunk (signed byte is a bit of a second
class citizen as a data type in G
Hello,
I've run into a snag trying to assign a negative NoData value to a Signed
Byte raster.
Example:
gdal_translate -a_nodata -128 -ot Byte -co PIXELTYPE=SIGNEDBYTE
signed8test.tif signed8testnew.tif
produces this error:
for band 1, nodata value has been clamped to 0, the original value bei
