New answers tagged error
i found an solution. it was an encoding problem, i solvesd it with chcp 1252. http://postgis.net/docs/RT_FAQ.html#qa_raster_fails_encoding_conversion
One thing I would certainly recommend, is to index all fields referenced in Definition Queries of every feature class participating in your batch process. I have a mixed ModelBuilder / ArcPy tool that regularly churns out 400 feature classes in a single File Geodatabase, the biggest of which was an OpenStreetMap dataset for entire France that resulted in ...
The problem comes from the unit of measurement, as specified by the Coordinate Reference System: EPSG:4326 (WGS84 LatLon) uses "degree" as the unit of measurement and the coordinate value. So your length is then also presented in decimal degrees. When you switch to a metric coordinate system that has meters as units of measurement (as has EPSG:3857), your ...
Here's one way. I suggest a) you join on st_dwithin() (or otherwise use that function), because it will make use of spatial indexes and reduce the size of the computation, and b) do the intensive query first, then worry about joining the pdetails table. Also, I assume your geometries are in some sort of projected units (otherwise your distances will be in ...
Possible answer here. Worked for me. https://gisnuts.com/terra/blog/2013/01/22/arcgis-geoprocessing-tools-scripting-error
Are you using Erdas Imagine 2015? I had the same problem as you when I was trying to run an unsupervised classification. I went to another computer that had Erdas Imagine 2011 installed. I then ran an unsupervised classification with the same exact parameters on the same image. No error message and the classification went smoothly. It wouldn't surprise me ...
I issued a bug and, in short, the response is: Qgis needs write access to that db, so the only solution is to change the permissions.
Thank you markusN for your interest! It worked. Because of the problem with the plugin, I did the viewshed analysis through command shell. First I saved my points in ascii with the command: v.out.ascii --overwrite input=points@vis type=point output=C:\coordinatess format=point separator=space precision=4 With this I created a .txt file with three columns ...
I have probably found the error and updated the command in the GRASS GIS Addons repository. Within 24 hours (i.e. tomorrow), the updated module will be online available: g.extension r.viewshed.cva
Top 50 recent answers are included