Latest Contributions by curtvprice

Two notes about inline variable substitution to generate output names: If you need to get more fancy, for example, change special characters, add a filename extension, or specify a full path to put the output in a specific location, the way to do this is using Python string expressions in the Calculate Value tool. If it really gets complicated you can write a python function in that tool.  If you do this in a loop, it's good practice to use precondition, connecting the Calculate Value tool to the tool that writes output using the calculated path -- to ensure the pathnames get calculated before you use them within the process chain. Example Calculate Value Python expression, with a fix in case the Name has an embedded space, and a .dbf extension for writing in dbase format to a folder. r"%Out Folder%\%Name%.dbf".replace(" ","_")   ... View more

This has been logged! ENH-000163033: Provide the capability to support Z values in the Polyline to Raster tool in ArcGIS Pro ... View more

Hi Ken - your method worked pretty darn fast and did the interpolation without the step of densifying the lines or doing the processing of creating points for every vertex. A little detail: to run the Near 3D the input must have Z values so when I ran Raster To Point I had to enable Zs and assign a default value using the environment settings for the tool run. ... View more

Thanks for the excellent thoughts, fine sirs! For the record I have an incident logged: Esri Case #03484588 - Conversion of Z enabled Polyline to Raster ... View more

Note this would be possible using current tools (Pro 3.2's profile tool) if this idea was implemented: Polyline To Raster support for Z values ... View more

Just a little comment, I strongly suggest you mention right at the get go (under the heading "Data Migration Tools) that ArcMap is required so those of us that have lost access to ArcMap know that OLE is our only path in to be able to extract (only tabular) data from personal gdbs. Thanks again for a really great blog series. ... View more

Elaine, thank you and you collaborators for a very useful set of articles. My Federal agency is losing ArcMap in February and these workarounds could save some data that would have been lost, so thank you!  Note, we can still read coverages in Pro from Python and I wrote a Pro python script to convert them to gdb, and even one that can upgrade file naming in pre-7.0 coverages so Pro's geoprocessing tools can read them. Read access to old formats is so important! ... View more

Either that or replace it with an underscore "%Path_Name%". My experiences is that spaces in variable names for rasters broke raster calculator parameter validation (checking) before substitution in the ArcMap raster calculator as well. ... View more

I think you are almost there, just use the Stop tool (in the utility dropdown in the ribbon) with the variable labeled True at right as the precondition. ... View more

The issue is not with the software but with the shapefile format - which has not changed. Shapefiles do not contain an x,y tolerance as do geodatabase feature classes.  x,y tolerance is the minimum distance between coordinates before they are considered equal. This x,y tolerance is used when evaluating relationships between features within the same feature class or between several feature classes. It is also used extensively when editing features. When using any operation that involves the comparison of features, such as tools in the Overlay toolset, the Clip tool, the Select Layer By Location tool, or any tool that takes two or more feature classes as input, use geodatabase feature classes (which have an x,y tolerance) rather than shapefiles. I would add that if you do overlay shapefiles, it is a good idea to set the XY Tolerance environment to avoid unnecessary issues. I believe shapefile coordinate precision is only 32 bits, and since they are floating point (not integer like geodatabases), these are approximations so the "fuzzy creep" your translated quote alludes to can be a real issue over multiple overlay operations. Your post title is talking about something else, which is also an important thing to know, about shapefile table (.dbf format) fields: Unlike other formats, shapefiles store numeric attributes in character format rather than binary format. For real numbers (that is, numbers containing decimal places), this may lead to rounding errors. This limitation does not apply to shape coordinates, only attributes.  ArcGIS Pro Help: Geoprocessing considerations for shapefile output   ... View more

Have you considered passing the whole SQL Server  table, or a point dataset from the whole table to the Split By Attributes tool? That may be easier, even if you need to do some renaming/copying of the results. ... View more

Maybe use the Copy Features tool instead of Export Features? ... View more