Git Product home page Git Product logo

arcsdm's People

Contributors

artolaiho avatar em-t avatar floodi avatar irvcaza avatar kkorhone avatar richardscottoz avatar tachyon-work avatar tomironkko avatar trotor avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

arcsdm's Issues

Calculate weights: automated naming of output tables

Automated naming of output tables feature in calculate weights tool is causing problems with Arc GRID format with limit of 13 characters in grid names. We should perhaps either

  1. disable this feature totally,
  2. let the user edit the given name or
  3. truncate the name within 13 character limit.

Current workaround is using other grid formats that allow long names.

Grid name length error using Calculate Response

Hi there. I'm getting ERROR 00878 when running the Calculate Response tool with rasters with names of near-13 characters length: "ERROR 000878: Output raster: The length of the grid base name in [...]\faults1km13_W0 is longer than 13". Which is true, it is 14 characters. But the last 3 characters, _W0, is added by the script to a temporary file. The problem does not occur in the old version of the SDM, which also makes the _W0 temporary rasters.

Cheers,
S

Issues encountered with the WoE Calculate Response tool

I am running the same model space in two ArcMap 10.2 sessions. One with the old SDM and one with the new version.

  1. weights tables within the ArcMap ToC cannot be dragged to the Input weights tables window, but have to be loaded from disc. In the old version, one can at least select tables loaded to the workspace in the dropdown menu. See attached image.
    calculateresponse_oldversion

  2. All output raster names are autoloaded as "[nameoffirstrasterloaded]_CalculateResponse.tif". In the old version, the names come up as %WORKSPACE%\W_pprb for post prob raster, W_Std for Std Dev raster, etc. The correct suffixes should be at least spelled out in the help file/tooltip.

2b) Output MD variance raster and Output Total Std Deviation Raster fields appear to expect .dbf endings, so dbf table outputs rather than rasters.

  1. Grid names need to be shorter than 13 characters. Not a new issue, and really a non-issue.

Calculate Response - issues with File Geodatabase

Tested the same setup as previously, but with file geodatabases as work space and temp storage. These were kept separate as the Calculate Response tool create a lot of temp files.

I'm not sure I am keen on use file geodatabases for spatial data modelling. They are good for sorting input data, although I couldn't get the rasters organised nicely as I appeared unable to pull individual rasters out of the raster catalogues with within the file geodatabase. And there are no ways to organise tables, whereas I would prefer to be able to separate final binary weights tables from early tests usually of the cumulative ascending or categorical kind. Rasters also need to be separated into input tables and final model output tables.

I ran four rasters and let the CW toolbox point to the "working" file geodatabase but otherwise let it pick its own names. It ran the weights tables with no issues, except as I mentioned that it is not possible to create subfolders for tables within a file geodatabase.

Running Calculate Response comes with a few issues. First of all, it is here also not possible to add wieghts tables directly from the workspace. Second, output rasters cannot be directly saved to a raster catalogue within the file geodatabase. Third, the script still hangs on line 400 since two of the output fields are set to DBF format and the script is looking for rasters to get standard deviations and such from. Finally, if the output fields are left as-is, the rasters (and dbf files) go to temp and won't work.

The tool manages to make a pprb raster, which looks sound. I will test outputs of the old and new toolbox tomorrow.

Cheers,
Simon
CalculateResponseCrash_FGDB.txt
calculateresponse_issues_fgdb

Cannot drag weights tables to Calculate response tool

weights tables within the ArcMap ToC cannot be dragged to the Input weights tables window, but have to be loaded from disc. In the old version, one can at least select tables loaded to the workspace in the dropdown menu.

Will see this issue also with ESRI support.

datatype="GPValueTable" and parameter columns = [['DETable', 'Weights table']] doesn't work.

But columns = [['GPRasterLayer', 'Evidence raster']] does work.

Calculate weights tool doesn't work on shape inputs

Executing (Calculate Weights (7)): CalculateWeightsTool rc_till_au # orogenic_gold_thin Descending C:\ArcSDM_New\Test_VMN\wofe1\rc_till_au_WD 2 1 -99
Start Time: Tue Jan 03 10:23:14 2017
Running script CalculateWeightsTool...
Reloaded arcsdm modules

========== arcsdm values ==========
ArcSdm 5.00 for ArcGis (Pro and Desktop)

Workspace: C:\ArcSDM_New\Test_VMN\wofe1
Scratch workspace: C:\ArcSDM_New\Test_VMN\wofe1\tmp
Mask: "study_area.shp" and it is FeatureLayer
Mask size: 98856.9549994
Cell Size: 500.0

Training Sites: 40

Unit Cell Area: 1.0km^2, Cells in area: 98856.9549994
Prior Probability: 0.000405
Training Set: C:\ArcSDM_New\Data\shp\orogenic_gold_thin.shp
Study Area Raster: C:\ArcSDM_New\Data\shp\study_area.shp
Study Area Area: 98856.9549994km^2
Map Units: meter

========== Calculate weights ==========
Creating table: %WORKSPACE%\rc_till_au_WD (Descending)

Calculate weights caught arcpy.ExecuteError:
ERROR 999999: Error executing function.
The name of the Field is invalid: valid names may contain letters, numbers or underscores.
Failed to execute (AddField).

-------------- END EXECUTION ---------------
ERROR 999999: Error executing function.
The name of the Field is invalid: valid names may contain letters, numbers or underscores.
Failed to execute (AddField).

Completed script CalculateWeightsTool...
Failed to execute (Calculate Weights (7)).
Failed at Tue Jan 03 10:23:15 2017 (Elapsed Time: 1,94 seconds)

Toolbox not working in ArcGis pro - Calculate Weights

Parsing error:
Traceback (most recent call last):
File "", line 6, in
File "C:\ArcSDM\Toolbox\arcsdm\calculateweights.py", line 367
if wtsrow.GetValue('class') <> MissingDataValue:
^
SyntaxError: invalid syntax

Calculate Weights auto file names

The automatic naming of files seems to be working for the Calculate Weights tool. Only Categorical is still misnamed by the Autonamer: It should be _CT (not _CC).

Thanks for all your work.

Cheers,
Simon

calculate response and "missing data"

I have one layer with missing data (with pixel value of -99). Calclulate weights run well but something breaks when running calculate response. Here the messages:

Executing (Calculate response): CalculateResponse rcam4kres;rcaemres;rc_apv_hg4 C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_WA;C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_WA;C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg4_WD training_07_c # -99 0.5 C:\ArcSDM_New\Test_VMN\wofe2.gdb\W_pprb C:\ArcSDM_New\Test_VMN\wofe2.gdb\W_std C:\ArcSDM_New\Test_VMN\wofe2.gdb\W_MDvar C:\ArcSDM_New\Test_VMN\wofe2.gdb\W_Tstd C:\ArcSDM_New\Test_VMN\wofe2.gdb\W_conf
Start Time: Wed Feb 15 13:15:36 2017
Running script CalculateResponse...
Reloaded arcsdm modules

========== arcsdm values ==========
ArcSdm 5.00.05 for ArcGis (Pro and Desktop)

Workspace: C:\ArcSDM_New\Test_VMN\wofe2.gdb (LocalDatabase)
Scratch workspace: C:\ArcSDM_New\Test_VMN\wofe2.gdb (LocalDatabase)
Mask: "study_area2" and it is RasterLayer
Mask size: 18642.0375
Cell Size: 50.0

Training Sites: 33

Unit Cell Area: 0.5km^2, Cells in area: 37284.075
Prior Probability: 0.000885
Training Set: C:\arcsdm\klappi\data\training_07_c.shp
Study Area Raster: C:\arcsdm\klappi\data\study_area2
Study Area Area: 18642.0375km^2
Map Units: meter

========================================= Starting calculate response =========================================
Study Area: 37284.075

training points: 33

Prior_prob: 0.000885096384985
Input rasters: [u'rcam4kres', u'rcaemres', u'rc_apv_hg4']
Input rasters: [u'rcam4kres', u'rcaemres', u'rc_apv_hg4']

Creating weight rasters

Processing rcam4kres
Temp_Raster=C:\ArcSDM_New\Test_VMN\wofe2.gdb\temp_raster54
Wts_Table=C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_WA
Output_Raster: C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_W4

Processing rcaemres
Temp_Raster=C:\ArcSDM_New\Test_VMN\wofe2.gdb\temp_raster55
Wts_Table=C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_WA
Output_Raster: C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_W4

Processing rc_apv_hg4
Temp_Raster=C:\ArcSDM_New\Test_VMN\wofe2.gdb\temp_raster56
Wts_Table=C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg4_WD
Output_Raster: C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg4_W3

Getting Post Logit raster...

Input_data_str: "C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_W4" + "C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_W4" + "C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg4_W3"
InexpressionPlog: -7.02892852099 + ("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_W4" + "C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_W4" + "C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg4_W3")

Creating Post Probability Raster...

InExpression 1 ====> Exp(-7.02892852099 + ("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_W4" + "C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_W4" + "C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg4_W3")) / (1.0 + Exp(-7.02892852099 + ("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_W4" + "C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_W4" + "C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg4_W3")))
Postprob: C:\ArcSDM_New\Test_VMN\wofe2.gdb\W_pprb

Executing: RasterCalculator "Exp(-7.02892852099 + ("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_W4" + "C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_W4" + "C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg4_W3")) / (1.0 + Exp(-7.02892852099 + ("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_W4" + "C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_W4" + "C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg4_W3")))" C:\ArcSDM_New\Test_VMN\wofe2.gdb\W_pprb
Start Time: Wed Feb 15 13:16:14 2017
Exp(-7.02892852099 + (Raster(r"C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_W4") + Raster(r"C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_W4") + Raster(r"C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg4_W3"))) / (1.0 + Exp(-7.02892852099 + (Raster(r"C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_W4") + Raster(r"C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_W4") + Raster(r"C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg4_W3"))))
Succeeded at Wed Feb 15 13:16:20 2017 (Elapsed Time: 5,88 seconds)

Creating STD rasters...

Processing rcam4kres
OutputRaster:C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_S4 exists: 0
RasterLayer=OutRas_lyr2
Temp_Raster=C:\ArcSDM_New\Test_VMN\wofe2.gdb\temp_raster57
C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_S4
Processing rcaemres
OutputRaster:C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_S4 exists: 0
RasterLayer=OutRas_lyr2
Temp_Raster=C:\ArcSDM_New\Test_VMN\wofe2.gdb\temp_raster58
C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_S4
Processing rc_apv_hg4
OutputRaster:C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg_S3 exists: 0
RasterLayer=OutRas_lyr2
Temp_Raster=C:\ArcSDM_New\Test_VMN\wofe2.gdb\temp_raster59
C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg_S3

Creating Post Probability STD Raster...

Sum_args: Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_S4") + Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_S4") + Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg_S3")

InExpression = SquareRoot(Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\W_pprb") * (0.030303030303 +(Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_S4") + Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_S4") + Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg_S3"))))
InExpression 2 ====> SquareRoot(Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\W_pprb") * (0.030303030303 +(Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_S4") + Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_S4") + Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg_S3"))))

Executing: RasterCalculator SquareRoot(Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\W_pprb") * (0.030303030303 +(Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_S4") + Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_S4") + Square("C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg_S3")))) C:\ArcSDM_New\Test_VMN\wofe2.gdb\W_std
Start Time: Wed Feb 15 13:16:58 2017
SquareRoot(Square(Raster(r"C:\ArcSDM_New\Test_VMN\wofe2.gdb\W_pprb")) * (0.030303030303 +(Square(Raster(r"C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcam4kres_S4")) + Square(Raster(r"C:\ArcSDM_New\Test_VMN\wofe2.gdb\rcaemres_S4")) + Square(Raster(r"C:\ArcSDM_New\Test_VMN\wofe2.gdb\rc_apv_hg_S3")))))
Succeeded at Wed Feb 15 13:17:03 2017 (Elapsed Time: 5,04 seconds)
**GP ERRORS:

PYTHON ERRORS:
Traceback Info:
File "C:\ArcSDM_New\Toolbox\arcsdm\calculateresponse.py", line 400, in Execute
import MissingDataVar_Func

Error Info:
<type 'exceptions.ImportError'>: No module named MissingDataVar_Func

Unhandled exception caught
Traceback (most recent call last):
File "C:\ArcSDM_New\Toolbox\arcsdm\common.py", line 45, in execute_tool
func(self, parameters, messages)
File "C:\ArcSDM_New\Toolbox\arcsdm\calculateresponse.py", line 400, in Execute
import MissingDataVar_Func
ImportError: No module named MissingDataVar_Func**

Completed script CalculateResponse...
Failed to execute (Calculate response).
Failed at Wed Feb 15 13:17:03 2017 (Elapsed Time: 1 minutes 27 seconds)

ROC tool crashes

Executing: ROCTool OrogenicAu # GammaOGD C:\arcsdm\LapinKaiku\OrogenicAu_ROCTool1.dbf
Start Time: Wed May 24 09:56:59 2017
Running script ROCTool...

Traceback (most recent call last):
File "", line 267, in execute
File "C:\ArcSDM_New\Toolbox\arcsdm\roctool.py", line 30, in execute
_roc_curve, _roc_ints, _auc_value, _auc_confints = CalculateCurveForModel(messages, raster_descr, negatives_descr, positives_x, positives_y)
File "C:\ArcSDM_New\Toolbox\arcsdm\roctool.py", line 94, in CalculateCurveForModel
messages.addMessage("Performing Monte Carlo simulation (%d realizations)." % self.NUM_REALIZATIONS)
NameError: global name 'self' is not defined

Failed to execute (ROCTool).
Failed at Wed May 24 09:57:12 2017 (Elapsed Time: 13.26 seconds)

Ajamme molemmat tätä ArcGIS 10.4.1 versiolla.

Demodata from Finland

Create new demodataset and maintain it as virgin data inside project. Filegeodatabase preferably?

Calculate response Demo crashes

Steps:

  1. Download ArcSDM and ArcSDM_DemoData.

  2. Unzip ArcSDM-Master.zip, this creates ArcSDM-master folder.

  3. Unzip ArcSDM_DemoData.zip inside ArcSDM-master folder, this creates Data folder.

  4. Execute file InitWorkDir.bat inside ArcSDM-master, this creates work folder.

  5. Open ArcMAP 10.5 and open ArcSDM_Desktop_work.mxd inside work folder

  6. Create folder connection for ArcSDM-master folder.

  7. In Arc Toolbox, select add toolbox and select ArcSDM-master/Toolbox/ ArcSDM.pyt

  8. In CalculateResponse demo.tbx, Step 1 and Step 2 appear with a red x. As well as LogisticRegressionDemotbx

  9. In Step 1, select edit and appears the model where calculate weights appears with a red x.

  10. Selected Calculate weights directly with
    a. Evidence raster layer : lithoname200k, rc_dnsstru, rc_magn_res4k, rc_till_cu, rc_em_real
    b. Training points orogenic gold thin
    c. Changed Output to end in WD
    d. Everting else as default

  11. Run calculate response with the obtained tables, orogenic_gold_thin and defaults

  12. ArcMAP closes. Output obtained before crash:

Running script CalculateResponse...
Reloaded ArcSDM modules
========== arcsdm values  ==========
ArcSdm 5.00.12 for ArcGis (Pro and Desktop)
Workspace:           C:\Users\irca\Downloads\ArcSDM-master\work\database.gdb (LocalDatabase)
Scratch workspace:   C:\Users\irca\Downloads\ArcSDM-master\work\scratch.gdb (LocalDatabase)
Mask:                "study_area" and it is FeatureClass
Mask size:           98856.95500162625
Cell Size:           500.0
# Training Sites:    40
Unit Cell Area:      1.0km^2, Cells in area: 98856.95500162625
Prior Probability:   0.000405
Training Set:        C:\Users\irca\Downloads\ArcSDM-master\work\database.gdb\Study\orogenic_gold_thin
Study Area Raster:   C:\Users\irca\Downloads\ArcSDM-master\work\database.gdb\study_area
Study Area Area:     98856.95500162625km^2
Map Units:           meter
========================================= Starting calculate response =========================================
Study Area:          98856.95500162625
# training points:   40
Prior_prob:          0.00040462504635452285
Input rasters: ['lithoname200k', "'Reclassified rasters\\rc_dnsstru'", "'Reclassified rasters\\rc_em_real'", "'Reclassified rasters\\rc_magn_res4k'", "'Reclassified rasters\\rc_till_cu'"]
Input rasters: ['lithoname200k', 'rc_dnsstru', 'rc_em_real', 'rc_magn_res4k', 'rc_till_cu']
Creating weight rasters
=========================================
Processing lithoname200k
 


"Mask" environment variable type in Training sites reduction

The Mask variable is not allowed to be of a raster type in Training sites reduction tool. Polygon Mask works fine.

Error message, if raster:

Failed to execute. Parameters are not valid.
ERROR 000840: The value is not a Feature Layer.
Failed to execute (MakeFeatureLayer).
-------------- END EXECUTION ---------------
Unhandled exception caught
Traceback (most recent call last):
File "C:\ArcSDM\ArcSDM-master\Toolbox\arcsdm\sitereduction.py", line 49, in ReduceSites
arcpy.MakeFeatureLayer_management(maskpolygon, maskname)
File "c:\program files\arcgis\pro\Resources\arcpy\arcpy\management.py", line 5726, in MakeFeatureLayer
raise e
File "c:\program files\arcgis\pro\Resources\arcpy\arcpy\management.py", line 5723, in MakeFeatureLayer
retval = convertArcObjectToPythonObject(gp.MakeFeatureLayer_management(*gp_fixargs((in_features, out_layer, where_clause, workspace, field_info), True)))
File "c:\program files\arcgis\pro\Resources\arcpy\arcpy\geoprocessing_base.py", line 506, in
return lambda *args: val(*gp_fixargs(args, True))
arcgisscripting.ExecuteError: Failed to execute. Parameters are not valid.
ERROR 000840: The value is not a Feature Layer.
Failed to execute (MakeFeatureLayer).

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\ArcSDM\ArcSDM-master\Toolbox\arcsdm\common.py", line 45, in execute_tool
func(self, parameters, messages)
File "C:\ArcSDM\ArcSDM-master\Toolbox\arcsdm\sitereduction.py", line 342, in ReduceSites
raise arcpy.ExecuteError;
arcgisscripting.ExecuteError
Completed script SiteReductionTool...
Failed to execute (SiteReductionTool).
Failed at 29. toukokuuta 2017 13:01:59 (Elapsed Time: 11,49 seconds)

Version system (visible to user)

Somekind of versionsystem for the toolbox that would be shown in the beginning of each tool when run. Suggestion: sdmvalues.py reads something.

CalculateWeightsTool fails with Carlin demo data

Here an error found by Gary. He is running the tools using ArcGIS 10.3 and using the Carlin data sets from the original ArcSDM package.

Vesa
I put my data in a personal geodatabase and ran calculate weights, which failed. The error message is below.

Executing: CalculateWeightsTool sbintgb # TrainGB Descending C:\SDM10.0\CarlinPGDB.mdb\sbint_WD 2 1 -99
Start Time: Thu Feb 16 16:33:22 2017
Running script CalculateWeightsTool...
Reloaded arcsdm modules

========== arcsdm values ==========
ArcSdm 5.00.02 for ArcGis (Pro and Desktop)

Workspace: C:\SDM10.0\CarlinPGDB.mdb
Scratch workspace: C:\TEMP
Mask: "stdyarea250" and it is RasterLayer
Mask size: 56799.0625
Cell Size: 250.0

Training Sites: 32

Unit Cell Area: 1.0km^2, Cells in area: 56799.0625
Prior Probability: 0.000563
Training Set: C:\SDM10.0\CarlinPGDB.mdb\TrainGP
Study Area Raster: C:\SDM10.0\CarlinPGDB.mdb\stdyarea250
Study Area Area: 56799.0625km^2
Map Units: meter
========== Calculate weights ==========
Creating table: %WORKSPACE%\sbint_WD (Descending)
ERROR 999999: Error executing function.
GPMEs: 0
CW - PYTHON ERRORS:
Traceback Info:
File "C:\ArcSDM-master\Toolbox\arcsdm\calculateweights.py", line 258, in Calculate
wtsrow.Count = row.Count

Error Info:
<function format_exc at 0x121B20B0>

Unexcpected exception caught
Traceback
File "C:\ArcSDM-master\Toolbox\arcsdm\common.py", line 45, in execute_tool
func(self, parameters, messages)

Error Info:
ERROR 999999: Error executing function.
ArcPy ERRORS:

Completed script CalculateWeightsTool...
Failed to execute (CalculateWeightsTool).
Failed at Thu Feb 16 16:33:38 2017 (Elapsed Time: 15.90 seconds)

Gary

Calculate Weights tool still not working with filesystem workspace

Downloaded and tested the 5.00.5 version. Still getting the same issue: The CW tool creates its own name for the output file in \Temp\ called "[filename]_CalculateWeightsT.dbf". If an attempt is made at changing the directory and file name, it reverts to "%WORKSPACE%[filename]_WD": http://i.imgur.com/CbZgWJx.png.

If the tool is run straight up as shown, an error still occurs: (http://i.imgur.com/tcUDO8b.png) suggesting that the file "%WORKSPACE%[filename]_WC" already exists. However, the file doesn't seem to exist anywhere - I'm not sure where it was written to. It seems to not be where Environments is pointing.

pprb raster creating and missing data

Hi there. Looks like the new toolbox still cannot deal with missing data. Here is a table of four rasters run with the old and new SDM tool, identical model spaces overall.

The one weights table that differs between the models is the aubicu_rc one, which in the new model gets weighted very strongly. The only difference between it and the other weights tables is the presence of a NoData (-99) property.

As calculated, this means that not only does the layer seem to get a very high constrast/stud c, but also a very high rank, more than half the total weights of the model - so undue high influence on the final pprb output.
TestModels_Outcome.xlsx

Wrong endings for Calculate Weights

Quote: The autorenamer is fine, although the name suggested is "[rastername]_CalculateWeightsT1.dbf" when the Evidence Raster Layer is at first dropped into the tool window. When clicking the folder icon to change the save location and returning to the tool window, save location changes to %WORKSPACE% and name to "[rastername]_WD for Cumulative Descending tests, for example.

The specs you got from your science advisors on the naming is different from what it used to be, and from what the tooltip still says for the Calculate Weights tool: It used to be _CA for cumulative ascending, _CD for cumulative descending, _CT for categorical, and _U for ungeneralised (unique) weights. Changing them to _WA, _WD etc. is fine if the Calculate Response tool is also updated to work with these endings, and the tooltips will need updating as well. I personally would prefer to stick with the old suffixes, so I don't have to rename hundreds of files when I rerun old models.

Does SDM work for ArcMap 10.4?

I'm getting an error that says <type.'exceptions.AttributeError'>: 'NoneType object has no attribute 'lower.'

All of my rasters are in the same projection and in meters and my evidential theme and study grid area are the same size. Do you know why this error is happening?

Demodata faults

GBFaults3 has already bearings in demodata folder - initialize demodata.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.