Latest Contributions by ScottMcGee3

Well, it seems that I have it working properly now.   I originally started this project in ArcMap. I started doing the graduated symbols symbology in ArcMap, and then decided I’d switch over to ArcGIS Pro. So I saved an MXD, then started a new Pro project and imported the MXD into it.   It was in Pro where I started having the problem with my graduated symbology (using the Manual method) not being retained after saving the Pro project and re-opening it. So, as a test, I opened the Pro project, removed the feature class that I was symbolizing, saved the Pro project and closed it.   I then opened the Pro project again and added the feature class back into it. I then re-did the graduated symbology (using the Manual method), set my desired Intervals and symbol colors, saved the project, and closed it.   Upon re-opening the project, all of my graduated symbology, intervals, and colors were exactly as I had saved them – everything was fine, no problems. So maybe the original problem I had might have had something to do with importing the MXD into the Pro project, but that’s just a wild guess on my part.   Also, I was able to successfully save to a layer file and then apply the symbology from the saved layer file to a new feature class in my Pro project. That worked just fine – no problems.   At any rate, all’s well now. ... View more

Dan, thanks for the tips. I used the Manual Interval method and defined my desired Upper Value ranges, then saved as a layer file. No problem with that. Here's what my graduated colors and ranges looked like: I then saved my ArcGIS Pro project and closed it, as I had other stuff to do. Later, when I re-opened my Pro project again to continue working on it, my carefully defined Upper Values had somehow changed, as shown below. I didn't do anything other than just re-open the project. I expected that everything would be exactly as shown in the first screenshot above. I have no idea why some of my Upper Values were changed and why others were not. Strange. But it seems to me this should not happen. Then, as a test, I copied my Height Change (2000 to 2016) layer and pasted the copy into the Contents pane, and switched the Field from 00 to 16 to 00 to 15, and then applied (imported) the symbology from my saved layer file. The result was the same as the screenshot directly above - with the incorrect Upper Value values. So I don't know what's going on. It seems that, in theory, this should all work. But I can't get it to keep the Upper Values that I manually enter. ... View more

Yes, I was aware that I could manually change the ranges and set the colors using graduated colors symbology. But even that won't do what I want to do. I'll try to explain what I want to accomplish. Every year, I measure how much the surface elevations of glaciers either increases or decreases (are they getting thicker or thinner, and where?). Each year, the elevation changes are different. For example, let's say that in 2010 the range of change was from +2 to -5. Then in 2011, the change was +0.7 to -3.5. And in 2012 it was +4 to -10. I need to be able to represent each year using the only one set of graduated colors and ranges. So I need to set my colors and ranges such that they encompass a range greater than the range of elevation change that I see in any one year. In other words, I need a master graduated color scale that does not change, and that I can apply to elevation changes from year to year. Then, once I have a master graduated color scale and defined ranges, I need to be able to save it in some way so that I can re-use it. It's critical that once I define the ranges and colors, that they don't change, even when the master color scale is used to symbolize a feature class in which the minimum and maximum elevation change values are less than the range of the master color scale. Does that make any sense? I know what I want to accomplish, but trying to explain it is difficult. ... View more

This is a follow up on my previous post above. I upgraded our SQL Server-hosted geodatabase to ArcGIS 10.5. So now everything we have is at version 10.5 (ArcGIS Desktop, ArcGIS Enterprise, SQL-hosted GDB). We're also using ArcGIS Pro 1.4. Here's a recap of the problem I'm having: 1) I started a brand new, empty Pro 1.4 project. In that project, I added a database connection to our SQL-hosted GDB and added a feature class (PLSS Sections) to the map. 2) Using ArcCatalog, I exported the PLSS Sections from the SQL-hosted GDB into a new, empty file geodatabase. I did this so I could test using the same feature class (PLSS Sections) from two different sources (SQL-hosted GDB and file GDB). 3) I added the PLSS Sections from the file GDB into the map. 4) Calculating the date field in the file GDB PLSS Sections feature class worked fine. I could see the newly-calculated value in the date field of the attribute table. 5) Calculating the date field in the SQL-hosted GDB PLSS Sections feature class sort of worked.The calc operation completed without any errors, but the date field in the attribute table did not show the newly-calculated value. However, when I saved the project, closed it, and opened it up again, the newly-calculated value was shown in the date field of the attribute table. 6) The problem described in #5 above occurs with all fields of all feature classes of all of our SQL-hosted GDBs. So... 1) Pro 1.4 and a file GDB: calculating a field value works as it should. No problems. 2) Pro 1.4 and a SQL-hosted GDB: calculating a field value works, but the only way to confirm that it worked is to close the ArcGIS Pro project and then re-open it. Upon re-opening the project, I can see newly-calculated field values. I took a wild guess that the problem might be due to using DirectX vs. OpenGL. So I tried both settings in Pro 1.4. It didn't make any difference. I also downloaded and installed the latest driver for my graphics card. That made no difference either. Obviously, it's not reasonable to close my Pro 1.4 project(s) and re-open them every time I calculate a field value in our SQL-hosted GDBs. So this pretty much makes Pro 1.4 unusable for me (even though I'm really trying to like it!). Has anyone else experienced this problem? ... View more

"Is the data versioned or not?" Yes, it is versioned. "Does it happen with all data types in Pro or just dates?" Yes, it happens with all data types in all of our SQL-hosted geodatabases.and feature classes. I think I've narrowed down the problem to being specific to ArcGIS Pro 1.4 and our version 10.4.0 SQL-hosted geodatabases. The problem does not occur when using Pro 1.4 to edit file geodatabases or shapefiles. So I suspect I need to upgrade our SQL-hosted GDBs from version 10.4.0 to version 10.5. Just to give a bit of additional info, I did some testing and found that when using Pro 1.4 to calculate field values in any of our SQL-hosted feature classes, that the calculation did actually insert the new value into the field. However, the attribute table still showed the old value, as if the attribute table was not being refreshed. The only way to see the newly-calculated field value was to close the ArcGIS Pro project and open it again. Then the calculated value was shown in the attribute table. ... View more

DateSerial doesn't work. I get a message saying "module datetime has no attribute dateserial" ... View more