BLOG
|
I have been incorporating this technique into Pro and it seems things have changed a bit. I find that I have to have the msgStub in the pre-main part of my program at block level 0 for it to work without 'Python syntax errors' inside AG Pro. It runs fine via command line and Python Window, just not via Toolbox if the msgStub class definition is in '__name__ == __main__'.
... View more
05-26-2023
02:17 PM
|
1
|
0
|
138
|
BLOG
|
This was a great idea for me - one modification I added was using subprocess to actually run an existing Python script directly from the command line (with arguments) inside the Python toolbox instead of putting the code in the Python toolbox file.
... View more
07-20-2022
02:18 PM
|
0
|
0
|
239
|
POST
|
I, and my RS class of 20 students, haven't had any issues in AG 2.9, might you be able to upgrade? Another option may be to store your data in File GDB rasters.
... View more
04-26-2022
08:52 AM
|
0
|
1
|
1650
|
POST
|
Thanks for the information. My work required me to revisit this workflow yesterday and it's still an issue. I guess I'll have to submit it to Support and see what's going on here.
... View more
04-15-2021
12:03 PM
|
0
|
0
|
1312
|
POST
|
I'm seeing this issue as well in 2.7.1. Have you submitted this to ESRI support? Or gotten any other advice?
... View more
03-11-2021
07:03 AM
|
0
|
0
|
1380
|
POST
|
I've got exactly the same issues (and would have the same screenshot), running 2.7.1. My system meets or exceeds all the requirements. The image I'm trying to profile is the 'Multispectral' raster product of Landsat 8, scene ID: LC08_L1TP_026031_20200710_20200912_02_T1. I've got some training samples and have already run some classifications with them but now I'd like to see what the spectral profiles look like so I can introduce the students in my class to the process of profiling. Should I not be profiling a raster product? Thanks!
... View more
02-18-2021
06:17 PM
|
0
|
1
|
2102
|
IDEA
|
The default color scheme for discretely symbolized data is currently a blue continuous ramp color scheme in ArcGIS Pro (see attached; current_default). This default option does not work well for most of the times when one wants to visualize data discretely as zones with similar values have very similar colors. A better default option would be one of the random color schemes (see attached; proposed_default) or an even better choice would be to allow one to specify the default color scheme used for discrete symbology. We can do that for stretched, why not discrete?
... View more
06-29-2020
11:12 AM
|
1
|
2
|
1575
|
POST
|
I received this error another time and it was due to a snap raster that did not exist. I fixed that and no more Error 000867
... View more
10-10-2019
12:44 PM
|
2
|
1
|
2420
|
POST
|
I was receiving the same error using arcpy. Once I took a deep enough look I realized my workspace was mistakenly trying to create a scratchGDB inside a feature class inside a File Geodatabase. It was trying to create a raster than ended in .afr inside the default workspace for the user. Once I fixed that insanity it worked correctly.
... View more
04-12-2019
10:49 PM
|
0
|
0
|
2420
|
POST
|
Did you ever find an answer to this? I am experiencing the same behavior with the Combine tool, and I see the same result in 10.3.1 and 10.6.1. All inputs are TIFFs. If you set the output to GRID my combine runs in 4 seconds. If you set it to TIFF it takes 120 seconds (with Windows Defender on it takes 1095 seconds!). I was wondering why my scripts were running so much slower in the newer versions and they seemed to switch to TIFFs as the default raster format in 10.5.1. You can still use .save() as a GRID but it's always creating an intermediate TIFF first.
... View more
07-26-2018
12:48 PM
|
0
|
0
|
574
|
IDEA
|
I'm not sure, I think the bug was brought in with the Multicore processing stuff, but ESRI doesn't tell you much on why these things happen. I couldn't use 10.4.X or 10.5.0 due to BUG-000095793, which corrupts Zonal Statistics Maximum calculations. I also found a few other things goofed up in 10.5.1, like Int and Abs calculations when used inside other SA tools. So, for me, it's 10.3.1 or 10.6.1 (fingers crossed) or Pro.
... View more
06-04-2018
10:20 AM
|
1
|
1
|
1091
|
IDEA
|
That bug was a pretty fun one! I discovered it and lost a few weeks, some data, and had to rebuild a couple computers. And it's not just data on the C drive that's at risk, it's whatever drives have workspaces you're accessing. I've been stuck on 10.3.1 due to a bug in 10.4.0 that didn't get fixed until 10.5.1 and was hoping I could finally upgrade and discovered this while checking things out. It looks like I'll have to go straight to ArcGIS Pro or stick with 10.3.1 with the tool I'm working on. I understand the 'wait until the .1 release' logic, but if everyone does that these bugs don't get discovered until the .1 release. Someone's got to test it (but it should be ESRI...)
... View more
05-29-2018
11:46 AM
|
2
|
0
|
1091
|
Title | Kudos | Posted |
---|---|---|
1 | 05-26-2023 02:17 PM | |
2 | 10-10-2019 12:44 PM | |
1 | 06-29-2020 11:12 AM | |
2 | 05-29-2018 11:46 AM | |
1 | 06-04-2018 10:20 AM |
Online Status |
Offline
|
Date Last Visited |
02-05-2024
01:14 AM
|