Latest Contributions by MaribethPrice

Sun, Rasters only store ONE field attribute directly and it is contained in the “Value” field. Any other fields may have been added by users or copied during a polygon-to-raster conversion process. Most raster tools use the Value field by default, and not many of them allow you to select an alternate. If you have a soil raster, then I surmise that the Value field contains a unique number code for each soil unit, and the slope field you indicate was merely copied from a polygon soils data set when it was converted to the raster. Presumably this field already contains the average slope of the field, so if you trust this value, then you don’t need to run zonal stats at all. To use zonal stats, you need a slope raster containing slope values in the Value field (not a soils raster containing a soil code). If you have a digital elevation model already, you can calculate slope from the DEM quite easily with the Slope tool and use that in zonal stats. You might want to review the Help files on how rasters are stored and analyzed; it sounds like you have might some misunderstandings about how they function. Maribeth ... View more

If you want world boundaries, then exporting a raster is NOT the way to get them.  You should be able to find a shapefile or feature class (with the borders as lines or polygons) in a variety of places, including ArcGIS Online, Esri Data and Maps, etc., the ArcGIS Pro tutorial data, etc. ... View more

You might also try the Zonal Statistics as Table tool, with your polygons as the zone data set and the crop raster as the values data set.  It will provide a table with a Count field for all the pixels in each polygon. You would need to reclasify (Reclassify tool)  the raster so that you would have only corn or only soybeans in each raster. Give each a value of 1 and a nodata everywhere else. The output is a table that you would join back to the polygons.  You will need a unique identifer for each field; the ObjectID should work if you don't have anything else. You will need a Spatial Analyst extension license to run these tools. Maribeth ... View more

I submitted this to tech support and it was confirmed as two different bugs.  These were attached to Esri Case #01849644 if you want to follow up further. For those needing to get work done, it works more reliably if you try to create the new domain from the Domains box in the Fields tab. After you create the new field and assign the data type, save the field update (optional but seems to help), then click in the domains box in the field row to create either the coded or ranged domain.  The field type and domain type get copied into new domain. ... View more

I am systematically working my way through Pro for my book update and there are a few things I do like: Multiple maps and layouts. I wrote a paper last summer and had to create a different map doc for every figure, even though it was all the same data being used.  I'd update some annotation in one figure and then have to do it again in another.  I'd zoom into the map in data view to fix something and then have to re-scale it for the figure.  I like that Pro creates a geodatabase for the project. With ArcMap, my students were forever saving things in the default geodatabase on the C drive and never finding them again. I used to create "junk" databases to hold intermediate stuff from Spatial Analyst workflows.  Now I just let them save in the project geodatabase Love being able to enter an attribute in an edit template and then create features with that attribute value. Love that I can keep a tool open and edit it after it finishes, instead of having to reopen and fill the whole thing out again.  Created 4 feature datasets in a geodatabase in under 20 seconds yesterday. Neat that the map display units can be set to UTM and automatically adjust for the zone you are in. Query builder panel is more intuitive for beginners, although more tedious to operate.  Thank goodness for the SQL view. My dislike list is still pretty long, mind you, but I expect I will get used to most of them in time.  Except the symbols.  Is it just me or are the default styles ugly, with the ugliest and least useful symbols at the top, so you have to scroll down to find reasonable ones every time?  It was heaven to find you can import the old ArcMap styles.  First thing I do with every new project. ... View more

I checked the references, but they all say how to move vertices--just click and drag--but not nodes.  I'm starting to think that the functionality to move shared nodes simply doesn't exist in Pro. You can sort of get the right behavior if you select the street edge with the Move tool and move/ rotate it until the node is centered in the intersection, but this only works for perfectly straight streets, and it may make the node on the other end worse. In other situations I guess you just have to re-digitize the feature with Replace Geometry, or edit and snap vertices individually for the features sharing the node. Another sad face for Pro.  ... View more

Trace is different.  Stream digitizing isn't that useful unless you have a digital pen and do a lot of curvy polygons like geology and soil units.  Then it is a godsend.  Guess I'll have to use ArcMap for it, at least for a while. Yes, I found that list of tools that aren't available, but lots of stuff wasn't a tool in AM. Good to have it, though. On the bright side, my book's Pro edition is gonna be a lot shorter than the AM edition!  ... View more

That would work.  Maybe I'll give it a try! ... View more

Have you tried using a reference scale? If you set the label sizes appropriately for one map, they will then be scaled proportionally when you view the other map. Just set up your labels for one map, then right-click the map and choose Set Reference Scale.   Map reference scales—Properties of maps | ArcGIS for Desktop  ... View more

I've been playing with this for several hours. You workaround of exporting the table (so the fields are there but it is no longer a joined table) does work. However, the scary thing is that the attempt to do SbA or MFL on a joined table appears to corrupt the data and make it unjoinable in the future, even after removing/re-adding the data to a new project (the joined fields are null). That is why the second attempt fails; the join is no longer valid.  I had to replace the data from another source to get the join to work again.  After another run through SbA or MFL on the new data (it works once), the join went bad again.  This is a nasty one.  I put in a tech support request on it. ... View more

Oh, and I did also try saving as a .xlsx file (office 2013).  That didn't work either. ... View more