Tag Info

New answers tagged

0

Since I could not get any fix for this issue, I wrote an ArcGIS extension for searching for tools. I may extend it to enable searching for other things besides tools in future. It is available for download from Tool Finder v1.0-beta.


0

Another alternative to skipping errors would be to instead pre-test for issues that would lead to errors. So, in your example above, after you iterate to the next raster, you could write a small Python script that could pre-test the raster and either pass or fail the raster, at which point your model could read the results (True/False?) either pass the ...


2

There is an Esri technical article on this subject. This condition is often (unknowingly) created when someone opens a shapefile .dbf file in Excel and makes alterations. Essentially, the article recommends using a Shapefile Repair Tool. Keep in mind that this solution will alter the shapefile, so create a backup.


2

Geoprocessing tools (with the exception of Spatial Analyst tools) return a Result object, which is what arcpy.ApplySymbologyFromLayer_management returns here. It doesn't have a save method. You may be getting this mixed up with a MapDocument or Layer object.


1

I have had similar problems when interpolating data of a scanned image which I imported in a WGS84 projection using its pixel-coordinates (for practical reasons). The points I used for the interpolation were about 0.010 units apart. I retried after multiplying all coordinates by a factor 10^6, and the problem was gone. If this also works for you, it is ...


0

There is not any issue in the data. However, it is very important the metada file in: http://pubs.usgs.gov/of/2000/of00-444/of00-444.met. There, you can observe the projection (EPSG: 4326) of the shapefiles (one is sf-qpys.shp; polygon type) and all classes (58) in, for example, PTYPE field. With this code in the field calculator of QGIS: CASE WHEN ...


1

Eventually, found a way to solve the problem, but I'm not 100% sure if this is it or not. After installing the PyQt4-devel, the next step would be to source the file (you can watch a nice tutorial done by Tim Sutton). If you still have problems with the make file, try to run the "compile strings" file just like in the video. Else if it doesn't work, ...


0

I was able to fix this in the end, though I still don't know for sure why I had this problem. I completely uninstalled QGIS, including the deletion of my user data and the registry key. I then went with the standalone 32-bit QGIS installer, and did a basic install. This did the trick! Again, I don't know why I had the issue as I have a 64 bit operating ...


0

You have to remeber that the arcpy module is really just a wrapper around a huge COM library. Most of the time it usually works but every once in a while you run into something like this. My guess is that the problem is in the underlying COM library, in which case this could be difficult to deal with. One thing you can try, although this is a long shot, ...


2

i don't trust the gc module as much as I do spawning a separate process. The separate process will do the work and will then be killed after the join(). Try adding: from multiprocessing import process to the top of your script then replace: exportAISMap(mxd_path, pdf_path) with p = Process(target = exportAISMap, args = (mxd_path, pdf_path)) ...


1

As per my comment in that question, it's to do with the spTransform. Simply remove the offending line: world <- spTransform(world, CRS("+proj=robin"))


0

I'm not sure, but this might be caused by the version conflict of the linked C runtime dlls between gdal111.dll and python bindings. Dependency Walker shows that gdal111.dll is linked to msvcr100.dll, but _gdal.pyd is linked to msvcr90.dll. Opening a ticket in OSGeo4W bug tracker is a good idea.


0

I had a similar problem running anaconda/spyder on a windows machine and it turned out to be an issue with a Microsoft patch that was not installed which is required by gdal. I was not able to import gdal and fiona until I downloaded the correct patch (I am on a 64-bit windows 7 system and the x84 version would not work for me. It was downloaded by my ...


1

I know I'm coming a bit late, but a quicker way to do this (provided that you're using Windows), is by using the OSGeo4W Shell. Make command will work from there. Source and I've also tested it QGIS version 2.8.1 if that adds any more relevance. Best regards,


0

nmperterson is correct with the naming rules. Names must begin with a letter, not a number or special character such as an asterisk (*) or percent sign (%). However, this was not the full solution to the problem. What was done to carry over the Name 20130101 to the output file in my case was utilizing the Parse Path Function and outputting a new Variable ...


1

Geodatabase feature class (and raster, etc.) naming rules: Names must begin with a letter, not a number or special character such as an asterisk (*) or percent sign (%). Names should not contain spaces. If you have a two-part name for your table or feature class, connect the words with an underscore (_), for example, garbage_routes. Names should not ...



Top 50 recent answers are included