New answers tagged error
After removing the '.prj' files from the directory with my shapefiles, my batch file ran without a hitch. Solution discovered here.
It looks like you are telling Arc that you are trying to input a z-factor in the slope tool, but not actually defining the variable. Removing the extra comma from that line of code should help, unless of course you do want to specify the variable in which case you need to put something in there after the comma: out_slope = Slope(input_raster, ...
I solved this issue finally. The problem was I was accessing the DEM on a mounted UNIX-type data partition which was formatted ext4. Copying the whole DEM to a Windows-type partition (NTFS formatted) allowed me to open the DEM in both ArcMAP and ArcSCENE.
The wildcard to use with LIKE depends on the data source. You are using square brackets as field name delimiters. So I suppose you are using a Personal Geodatabase. The wildcards you have to use to query a personal geodatabases are asterisk (*) for any number of characters and question mark (?) for one character. If you use SDE or file based geodatabase ...
As Zach suggested I put my own comment as an answer, eventhough I'm not fully satisfied with it. "Just to update that I have overcame this obstacle; unfortunatly by using ArcCatalog. With it I was able to drop the fields that I didn't want, and one of them caused the problem." Maybe it will be better to tell that the whole process of working with roads ...
I've explored this question recently. I think people want to know what spherical radius should I use? what is the resulting error? A reasonable metric for the quality of the approximation is the maximum absolute relative error in the great-circle distance err = |s_sphere - s_ellipsoid| / s_ellipsoid with the maximum evaluated over all possible pairs ...
I'm going to say that you can't access fieldA by index like that in Field Calculator. Might be wrong. Anyway, you could try it in VB: fieldB = Left([fieldA], 5), for example. Or, try !fieldA[index1:index2]!
Solution: needed to copy the r.roughness.window.area script from the src folder into /usr/local/grass-6.4.3svn/scripts r.roughness.window.vector was there, but r.roughness.window.area was not.
I'm a bit late to this conversation, but a general comment on the non-arcpy python structure is that you instantiate cenvar and varexp each time you iterate w/in your for cfname, prefieldname loop, which is wasteful. Do it once prior to the loop if it’s not going to change. Also, use itertools.izip instead of zip in general. Your lists aren’t killer long, ...
There are addons for GRASS 6.x (addons) and there are others for GRASS 7 (addons) Since the future version 7 (still being developed with several versions per month, which do you use ?) marks a major break with the 6.x versions (new vector API, etc.) it is doubtful that all GRASS 6.x addons works without problems (there is no r.roughness in GRASS 7 raster ...
More Google searching came up with an answer. Unlike ARCMAP, you can't drag all the files, just the shape files. Thanks for the leads and suggestions. Alyre
Try using the ESRI wkt or the ESRI .prj file at EPSG:2953 or fix the projection in QGIS after importing the file (without the prj file, if necessary)
Make sure your project references the ESRI.ArcGIS.Client.Toolkit.dll assembly.
Okay, Problem solved, it was an ESRI Error, after talking with ESRI Support they said that installing service pack one should fix it and it did. They only had 4 records of this happening and they weren't quite sure what was causing it. But any how Service Pack 1 does the trick. – ACrain 1 min ago edit
Seems like this is a "feature"...http://hub.qgis.org/issues/777 When the provider loops through the features, python stores the geometry, but as soon as the loop continues to the next iteration, the feature gets destroyed, and with it the geometry gets destroyed--passing invalid memory when trying to combine the geometries. So to save the geometries to ...
Top 50 recent answers are included