Latest Contributions by RichardDaniels

well, Lidar derived elevations are originally referenced to a Geoid elevation or NAVD88. Those elevations are in reference to a fixed geoid model, while MLW and MLLW are not. Translation to tidal datums should be done based on the published survey data for a specific tidal station (s). See tidal.gif (880×680) for reference. ... View more

If it is 'back' for ArcGIS Pro I would check the shortcut again since a ArcGIS Pro upgrade (3.4. to 3.5) or a Service Pack install could have replaced the shortcut itself. In Task manager you can see if Pro is running in Efficiency mode (it will show the green leaf if it is).   ... View more

There is option to SET the output cell sizes vs. letting it default. Notice 1 row and column was added, most likely the projection being used has rotation causing these to be added. ... View more

ArcGIS Pro 3.4 change the default driver from DirectX 11 to DirectX 12. Ways to resolve are to (1) ensure you have the newest DirectX 12 graphics driver, (2) change default back to DirectX 11, or (3) change default to OpenGL. Graphic card options can be set in Pro's options->display tab. ... View more

A good option would be Microsoft SQL Server Express or Microsoft SQL Server Local DB. Both support standard T-SQL and one or more databases (on Express) with no licensing costs.  It has some limitations, such as a maximum database size of 10 GB and support for only 1 GB of memory and 1 physical processor.  Use Microsoft SQL Server Manager to manage your database.   Links: Download Microsoft® SQL Server® 2022 Express from Official Microsoft Download Center ... View more

just and FYI, adobe remembers your last settings. So if you use a Adobe driver 'outside of ArcGIS Pro' for printing those settings may carry over into ArcGIS Pro (or ArcMap).  ... View more

probably defaulting to 97 dpi, try to set the output parameters with print to pdf vs. export/save to pdf. ... View more

key here being, .NET Desktop Runtime version 8.0.19 or higher within the v8 family. Each .Net major version change is a breaking change for ArcGIS Pro. ... View more

Most users should not have Admin permissions on their computers.  We enforce install as allusers=true to prevent this -otherwise different users can install ArcGIS Pro with different versions on the same machine. Allowing individual installs makes it near impossible to do managed deployments. Just me, but since I have IT support with Software Center and Intune Company Portal available, I never would enable or use ESRI's or AGOLs software auto-download/update function for ArcGIS Pro.  ... View more

This ability is already available in the ArcGIS Pro installation within the command line during install or as a registry setting found with in the MSI install package. If you are doing managed deployments, you should set the 'do not check for updates' option.   Command line: msiexec /i ArcGISPro.msi ALLUSERS=1 ESRI_LICENSE_HOST=my_license_server  SOFTWARE_CLASS=Viewer LOCK_AUTH_SETTING=False AUTHORIZATION_TYPE=CONCURRENT_USE CHECKFORUPDATESATSTARTUP=0 ACCEPTEULA=YES Install Editor (Orca.exe) Find the Property table within your MSI and set the CHECKFORUPDATESATSTARTUP setting, set to 0. Of note, most command line parameters can be set in this table as well. ... View more

You should load Service Pack 6 for ArcGIS Pro 3.3 and solve this problem. ... View more

or you can just create the .prj file manually. They are just text files with a .prj (projection) extension, if your shapefile is named mydata.shp then the prj would be named mydata.prj.  Example contents of the file at ESRI PRJ File (https://vsp.pnnl.gov/help/vsample/ESRI_PRJ_File.htm) ... View more

you need to use DEFINE projection tool ... View more

The ability to define a coordinate system is a fundamental 1st step in creating any dataset. I discussed this issue with the ESRI Coordinates team at the User Conference, that being stated this is what happens when you higher programmers who can't spell 'GIS' and given them veto authority over the GeoScientists in the room. Breaking a tool that has existed since ArcInfo 9.0 without appropriate error messaging shows they were not doing regression testing.  A user should not have to come 'HERE' to see why the DEFINE command failed. ... View more