Latest Contributions by DarylHochhalter

‎10-30-2019

Hi KKramer-esristaff I was trying it yesterday (ArGIS Pro 2.4), but didn't see a check box for selected records only and it seemed to take awhile to run so thought it recalculated all of them. The other thing has to do with Planar or Geodesic area calculations. I believe only the Geodesic property was available because my data is in GCS, but think it should calculate geometry in the projected coordinate system you choose and the properties that are available to select should be based on that selection, not the coordinate system of the underlying data?

‎10-30-2019

KKramer-esristaff had already done that 2 years ago, guess I was hoping the original author might come back and select a new correct answer. Had I not already known that, might not have looked past the correct answer.

‎10-29-2019

arcgis-pro-2.4‌ We need the ability to calculate the selected records and the ability to choose the geometry property based on the selected projection, not the coordinate system of the underlying data. Update: Per post by Kory Kramer, geoprocessing tools do selected records by default so scratch that part, already does it.

‎10-29-2019

Along with fixing the ability to select the planar property regardless of what the data coordinate system is, we need the ability to calculate the selected records!

‎10-29-2019

That is not the correct answer, calculate and add do two different things.

‎10-29-2019

I certainly hope they get it fixed soon, really no reason to select a coordinate system for the calculation, if the properties are restricted by the coordinate system of the data. I believe projection on the fly is a wonderful thing, no need to have multiple copies of the same data in order to run various types of analysis.

‎10-28-2019

https://community.esri.com/docs/DOC-13641-arcgis-pro-roadmap-july-2019

‎10-28-2019

I would just like to second Mathew Boyle's comment, even though it seems we are already set to get the utilities we need. There is no good reason for ESRI to limit the users ability to use replication which is really all they would be doing by following the course they seem to have chosen. Basically, it would only be available through online services and now called sync. From my perspective, we need the ability to replicate outside the feature service workflow. We are using the same workflow Mathew Boyle mentioned. We have some data we make available to the public and some data we collect from the public, the data requires different permissions and is exposed in different ways to the public. it is an extra layer of security to publish the services from replicas of our enterprise database. In fact it works quite well to publish services from replica FGDB's for webmaps that will only be viewed by users having no need or ability to edit.

‎10-28-2019

There is no good reason for ESRI to limit the users ability to use replication which is really all they would be doing by following the course they seem to have chosen. Basically, it would only be available through online services and now called sync. From my perspective, the concept makes no sense. However, since we now need to provide reasons to keep functionality some of us have used for many years, that works quite well, I will provide this scenario/workflow. We have some data we make available to the public and some data we collect from the public, the data requires different permissions and is exposed in different ways to the public. it is an extra layer of security to publish the services from replicas of our enterprise database. In fact it works quite well to publish services from replica FGDB's for maps that will only be viewed by user.

‎09-25-2019

The way curves are stored has changed since 10.4, as I stated above was looking for a way to test before performing an upgrade on the original EGDB. That is my reason, but also wondering what happens should I decide to import some data after the upgrade. I'm curious about how ArcGIS Pro determines the version when using it to create a file or Enterprise GDB, by the portal you login through or the version of desktop installed on the local computer, if there is one. It is difficult to test this, I haven't figured out how to view the actual release version, since properties in ArcCatalog simply state it matches the client version, and GDB properties don't seem to be available in the context menu of Pro.

‎09-25-2019

Thanks for the reply, I'm aware of the upgrade procedure for a geodatabase, but was just curious if it was effectively the same thing to copy data from an older version to a newer version. I would sort of like to test the curve data especially since I know there was an issue with curves upgrading from 10.4 to 10.5 but I believe that may have been corrected in later upgrades.

‎09-24-2019

I'm just wondering if copying or importing data from a version 10.4 database to a version 10.7 database will work? Is it the functional equivalent of upgrading the database? Is it even possible?

‎08-23-2018

Twice in the last couple weeks I've been editing as usual and the copy & paste attribute feature seems to develop a mind of it's own. Instead of pasting the attributes to the selected feature, it pastes an entirely new feature. Usually directly under the feature I copied attributes for, but in some cases randomly somewhere close by, and perhaps a partial shape. Any Ideas on what might cause this kind of strange behavior? It seems to clear up again if I shutdown my computer for awhile. It may only be occurring after I have used the attribute transfer tool in the same edit session. Maybe need to just file a bug on this? ArcGIS Desktop 10.4 Advanced on Windows 10, editing an enterprise database. Ok, so I was wrong on the computer restart. The issue seems to be in the MXD file. I restarted the computer and had the same issue, so copied the layers to a new MXD and copy paste attributes seems to function as expected again. Not sure what is causing this strange behavior in the first place. Was editing with the original MXD for months now, suddenly an issue and pretty sure I've used the Attribute transfer tool before this morning.

‎06-01-2018

I am currently having the very same issue using model builder and ArcGIS 10.4 advanced.

‎05-31-2018

That is indeed the issue, using False for the validate parameter is a must, if you don't the resulting mxd still references the the original datasource in some way. I just ran it both ways twice and got the same results. import arcpy CurFldr = r'\\Gis Server Data\Replicas\test' + '\\' OldGDB = arcpy.GetParameterAsText(0) NewGDB = arcpy.GetParameterAsText(1) mxd = arcpy.mapping.MapDocument(r'\\Gis Server Data\Replicas\test\test.mxd') mxd.findAndReplaceWorkspacePaths(CurFldr + OldGDB, CurFldr + NewGDB, False) mxd.saveACopy(r'\\Gis Server Data\Replicas\test\Copy_of_test.mxd') del mxd

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by DarylHochhalter

Re: ArcGIS Pro Calculate Geometry Fixes

Re: ArcGIS Pro Calculate Geometry

ArcGIS Pro Calculate Geometry Fixes

calculate geometry

Re: ArcGIS Pro Calculate Geometry

Re: Planar vs Geodesic Area/Length?

Re: Working with distributed data using ArcGIS Enterprise and ArcGIS Pro

Re: Working with distributed data using ArcGIS Enterprise and ArcGIS Pro

Re: Replication Tools in Pro

Re: Can you copy or import data from a database that has an older version?

Re: Can you copy or import data from a database that has an older version?

Can you copy or import data from a database that has an older version?

Copy & Paste Attributes

Re: Create Replica using arcpy

Re: Using arcpy.mapping to change the datasource for .mxd?

Searching for maps in Field Maps app

Re: Configure pop-ups gone from Map Viewer?

Re: New User Types

Re: New User Types

Map Viewer Mapservice tables