On Thu, Oct 28, 2010 at 6:56 PM, German Ocampo wrote:
> The issue is that using PIL I get pixel values in the greyscale of 127
> or rgb(0,0,0), where really I could see in Gimp that these pixels have
> a different value. Looks like PIL can decode part of the picture and
> another part of the pict
Check the inverse of the numbers, there are a ton of inconsistencies
of x,y and matrix representation. Basically an image's x axis
progresses left to right, whereas a matrix's x is top to bottom (x,y
versus row,column). So check 2,3 and 3,2 on GIMP, etc.
On Thu, Oct 28, 2010 at 12:56 PM, German
Chris
Many thanks for your email.I want to read values from images in
grayscale or rgb, because the product that is coming from Arcmap could
be either.
The issue is that using PIL I get pixel values in the greyscale of 127
or rgb(0,0,0), where really I could see in Gimp that these pixels have
a d
Why would the image go between greyscale and rgb? In anycase, perhaps
the easiest solution is use np.resize on temp instead of the for
loops. Then if you have tuples of rgb versus ints you can use
np.where()
On Thu, Oct 28, 2010 at 4:36 AM, German Ocampo wrote:
> Good morning
>
> Im reading an
Good morning
Im reading an 8bit image generated by ArcMap using PIL in windows, the
image load well without error messages but, when I try to extract the
values to a numpy array I got some lines of the image with value of
pixel 127 (greyscale) or rgb(0,0,0). When I open the image using GIMP
or arc
