Pulling numbers from ASCII filename not working

[IamIan]

I searched the archives but couldn't find anyone else with this
problem. Basically I'm grabbing all ASCII files in a directory and
doing geoprocessing on them. I need to calculate a z-factor based on
the latitude of the ASCII file being worked on, which is in the
filename. If I type in the code manually it works and reads the
latitude value from the ASCII filename, but when run within ArcGIS it
crashes when it gets to int(LatString). Isnumber() returned false for
Latitude as well. Is there something different about reading values
from an ASCII filename?

import sys, os, win32com.client , string, gc

# Get a list of ASCII files in the workspace for ASCII To Raster
conversion
filenames = os.listdir(gp.w orkspace)
filenames = [filename.lower( )
for filename in filenames
if (filename[-4:].lower() == ".asc" and filename[0] != "-" )]
for filename in filenames:

# For each ASCII file, create Hillshade.
# account for latitude by computing Z units using radians
Latitude = filename[1:3]
LatString = str(Latitude)
LatInt = int(LatString)
radians = LatInt * 0.0174532925
zFactor = 1/(113200 * (cos(radians)))

[mrmakent]

First: http://www.catb.org/~esr/faqs/smart-questions.html

You say your program 'crashes' when it gets to 'int(LatString) '. I'm
guessing (and it's entirely a guess, since you don't tell us) that you
are getting an exception like 'ValueError: invalid literal for int():
whatever'. I'm guessing again that 'LatString' doesn't contain what
you think it does at this point. Have you tried inserting a print
statement to show you just what 'LatString' contains?

[Larry Bates]

At lest one of the filenames (or directories) being returned by
os.listdir doesn't have integer value where you are looking.
Remember that os.listdir returns subdirectories as well as files.
You may want to look at using glob.glob() instead and limit it
to *.asc.

Secondly,

filenames = [filename.lower( ) \
for filename in filenames \
if (filename[-4:].lower() == ".asc" and filename[0] != "-" )]

is better rewritten as (not tested):

import glob
filenames=glob. glob(os.path.jo in(gp.workspace , '*.asc'))
filenames = [f.lower() for f in filenames if not f.startswith('-')]

Larry Bates

IamIan wrote:

I searched the archives but couldn't find anyone else with this
problem. Basically I'm grabbing all ASCII files in a directory and
doing geoprocessing on them. I need to calculate a z-factor based on
the latitude of the ASCII file being worked on, which is in the
filename. If I type in the code manually it works and reads the
latitude value from the ASCII filename, but when run within ArcGIS it
crashes when it gets to int(LatString). Isnumber() returned false for
Latitude as well. Is there something different about reading values
from an ASCII filename?

import sys, os, win32com.client , string, gc

# Get a list of ASCII files in the workspace for ASCII To Raster
conversion
filenames = os.listdir(gp.w orkspace)
filenames = [filename.lower( )
for filename in filenames
if (filename[-4:].lower() == ".asc" and filename[0] != "-" )]
for filename in filenames:

# For each ASCII file, create Hillshade.
# account for latitude by computing Z units using radians
Latitude = filename[1:3]
LatString = str(Latitude)
LatInt = int(LatString)
radians = LatInt * 0.0174532925
zFactor = 1/(113200 * (cos(radians)))

[IamIan]

The exception I get is "TypeError: Cannot add value 'int' to string." I
have looked at LatString, and it is the string representation of
latitude ('17' etc.). What's odd is that the exception is raised not
when I include LatInt = int(LatString), but when I try to print
LatInt's value or multiply it by another number.

Filenames are along the lines of "N16W110.as c" - is there another way
to get LatString into a number for multiplication purposes?

[Fredrik Lundh]

"IamIan" <ia****@gmail.c om> wrote:

The exception I get is "TypeError: Cannot add value 'int' to string."

now that you've posted the exception, can you please post the code
you're using, and the *complete* traceback.

(the stuff you posted earlier contained syntax errors, and didn't con-
tain any additions. I suggest using copy/paste, rather than typing
things from memory).

</F>

[Bengt Richter]

On 24 Jan 2006 10:44:32 -0800, "IamIan" <ia****@gmail.c om> wrote:

I searched the archives but couldn't find anyone else with this
problem. Basically I'm grabbing all ASCII files in a directory and
doing geoprocessing on them. I need to calculate a z-factor based on
the latitude of the ASCII file being worked on, which is in the
filename. If I type in the code manually it works and reads the
latitude value from the ASCII filename, but when run within ArcGIS it
crashes when it gets to int(LatString). Isnumber() returned false for
Latitude as well. Is there something different about reading values
from an ASCII filename? Aren't you curious as to what the value of LatString was that failed?
Don't you know how to find out?

import sys, os, win32com.client , string, gc

# Get a list of ASCII files in the workspace for ASCII To Raster
conversion
filenames = os.listdir(gp.w orkspace)
filenames = [filename.lower( )
for filename in filenames
if (filename[-4:].lower() == ".asc" and filename[0] != "-" )] indentation of the above two lines would improve readability
for filename in filenames: I would try print repr(filename) here, to see what you are dealing with
# For each ASCII file, create Hillshade.
# account for latitude by computing Z units using radians
Latitude = filename[1:3]
LatString = str(Latitude) you probably won't need a print repr(LatString) here if you see the above print LatInt = int(LatString)
radians = LatInt * 0.0174532925
zFactor = 1/(113200 * (cos(radians)))

BTW, capitalizing the first letter of python variable names is counter to usual convention.

Regards,
Bengt Richter

[IamIan]

Thank you for the replies, I'm new to Python and appreciate your
patience. I'm using Python 2.1.

To reiterate, the ASCII files in the workspace are being read correctly
and their latitude values (coming from the filenames) are successfully
being converted to string. Even doing LatInt = int(LatString) works,
however the second I try to print LatInt's value or use it in
mathematical operations, the code chokes in ArcGIS.

My full code:

# Import system modules
import sys, os, win32com.client

# Create the geoprocessor object
gp = win32com.client .Dispatch("esri Geoprocessing.G pDispatch.1")
print gp.usage("Hills hade_sa")
print gp.usage("Raste rToOtherFormat_ conversion")
print gp.usage("Defin eProjection_man agement")

# Check license availability
gp.AddMessage ("ArcInfo license is " + str(gp.CheckPro duct("ArcInfo") ))
gp.SetProduct(" ArcInfo")
gp.CheckOutExte nsion("Spatial" )

# Set workspace
workspace = "E:\\GISTes t"
gp.workspace = workspace
gp.AddMessage(" Workspace = " + gp.workspace)

filenames = os.listdir(gp.w orkspace)
filenames = [filename.lower( )
for filename in filenames
if (filename[-4:].lower() == ".asc" and filename[0] != "-" )]
for filename in filenames:

# For each ASCII file, create Hillshade.
# account for latitude by computing Z units using radians
Latitude = filename[1:3]
LatString = str(Latitude)
LatInt = int(LatString)
gp.AddMessage(" LatInt is " + LatInt)
radians = LatInt * 0.0174532925
zFactor = 1/(113200 * (cos(radians)))

The complete traceback:

Traceback (most recent call last):
File "e:\python21\py thonwin\pywin\f ramework\script utils.py", line
310, in RunScript
exec codeObject in __main__.__dict __
File "E:\Documen ts and
Settings\Admini strator\Desktop \Ian\GIS\Python \zOnly.py", line 32, in ?
gp.AddMessage(" LatInt is " + LatInt)
TypeError: cannot add type "int" to string
I tried print repr(filename) and it returned the actual filename:
'n16w099.asc' , 'n17w062.asc' , etc.

[Steven D'Aprano]

On Wed, 25 Jan 2006 12:42:20 -0800, IamIan wrote:

Thank you for the replies, I'm new to Python and appreciate your
patience. I'm using Python 2.1.

To reiterate, the ASCII files in the workspace are being read correctly
and their latitude values (coming from the filenames) are successfully
being converted to string. Even doing LatInt = int(LatString) works,
however the second I try to print LatInt's value or use it in
mathematical operations, the code chokes in ArcGIS.
[snip]
LatString = str(Latitude)
LatInt = int(LatString)
gp.AddMessage(" LatInt is " + LatInt)
Dude. You're trying to add a string to an int. What did you think would
happen?
The complete traceback:

Traceback (most recent call last):
File "e:\python21\py thonwin\pywin\f ramework\script utils.py", line
310, in RunScript
exec codeObject in __main__.__dict __
File "E:\Documen ts and
Settings\Admini strator\Desktop \Ian\GIS\Python \zOnly.py", line 32, in ?
gp.AddMessage(" LatInt is " + LatInt)
TypeError: cannot add type "int" to string

The traceback tells you exactly what is wrong, and where it is going
wrong: you are trying to add a string to an int.

What you probably want is either gp.AddMessage(" LatInt is " + LatString)
or gp.AddMessage(" LatInt is %d" % LatInt).
--
Steven.

[IamIan]

>Dude. You're trying to add a string to an int. What did you think would

happen?

Dude. I thought it would concatenate the value for LatInt with the rest
of the sentence; I wasn't literally trying to add them. Apparently you
can only concatenate strings like this in Python.

[Steven D'Aprano]

On Wed, 25 Jan 2006 16:57:47 -0800, IamIan wrote:

Dude. You're trying to add a string to an int. What did you think would
happen?

Dude. I thought it would concatenate the value for LatInt with the rest
of the sentence; I wasn't literally trying to add them. Apparently you
can only concatenate strings like this in Python.

No. An interactive session is your friend. You can concatenate all sorts
of things, not just strings:

[2, 3, 4] + [5] [2, 3, 4, 5] (2, 3, 4,) + (5,)

(2, 3, 4, 5)

What should 4 + "5" give you? 9 or "45"?

Your description of the problem was *utterly* wrong. You said you get an
error when you try to print LatInt; but that's not true, is it? print
LatInt works fine, I bet. If you had actually posted the traceback, rather
than trying to describe it in your own words, your problem would have been
solved after one post. In other words, you sent us all on a wild goose
chase.

But the main thing is, the traceback was telling you exactly what was
wrong. Listen to it, it knows.

--
Steven.