Latest Contributions by SeanLyons

Allow the Analyze Datasets tool to update all branch-versioned related system tables Our organization manages a set of features classes in our enterprise geodatabase that totals over 30 million features, and we are actively updating or adding thousands of new features every single day. Due to this large size, database optimization is a high priority for us, and we have created automated procedures to update indexes and statistics on all our layers and associated tables on a nightly basis to ensure that we are getting the best performance possible. We are relying on the Analyze Datasets geoprocessing tool to update the statistics for all the tables in our enterprise geodatabase, however, while reviewing the results in the database, we noticed that a number of the branch-versioned related system tables (including the sde_branch_tables_modified and sde_branches) are not updated by the Analyze Datasets tool. These tables are updated frequently, so not having them analyzed means that the optimizer doesn't have the information required to fully optimize queries, which then could cause the optimizer to make the wrong decision resulting in performance issues. We are requesting that the Analyze Datasets tool be updated to include all tables related to branch versioning to ensure that the statistics on these tables can be updated using the same mechanism as the rest of the tables in the enterprise geodatabase. This would allow us to ensure that all the necessary tables are being analyzed at the same time through the same tool and avoid manually or scripted back-end updates to the geodatabase that are currently required to update the handful of tables that are being missed by the Analyze Datasets tool. ... View more

Our organization receives plans in with radial bearings defining the direction of the curve. Once entered, the parcel fabric in ArcGIS Pro stores this information in chord bearing. We have no issue with the fact that this is stored in chord bearing, but once stored, there doesn't appear to be an easy way to identify the radial bearing of a curve anymore. We would like a tool (perhaps something on the Parcel Utilities Add-In?) that, when we click on a curve, provides all the curve parameters. Or, similar to the Traverse window, where you can specify curve parameters, can this be an enhancement to the Attribute Window for once the curve has been entered?  Our use case for this is: we had a parcel with a high misclosure and we couldn't figure out why. It turned out to be due to a bad curve bearing, but this was very hard to identify, since the plan displayed radial bearings and the lines in the fabric displayed chord bearings. In ArcMap, we would have opened the parcel, which would have showed us the radial bearing since those would have been the properties stored on the plan. Then we could easily compare what was entered to the plan. We would find it helpful to have something that allowed us to do this in ArcGIS Pro.  that radial line in shown in desktop needs to be this according to plan but you only get the chord in ArcGIS pro so I have no way to enter a new radial ... View more

We understand the Align Parcels tool was designed with parcels in mind. For that reason, if you are trying to complete an alignment and there are no adjacent parcels to the parcels that are selected to participate in the alignment, then the alignment will fail. Essentially, the tool is expecting to see other parcel polygons within the alignment buffer area:  We would like to request that the Align Parcels tool be enhanced so that it is possible to align a scenario like the one pictured above without receiving an error. For now, we can either create a dummy parcel adjacent to the selected parcels or drop one of the parcels from the alignment.  In our organization, we model posting plans as connection lines in the parcel fabric. In other jurisdictions, these types of plans may be called Monument plans, or Boundaries Act plans - they are survey plans with no parcels, only lines. In the scenario pictured above, we are attempting to align a block of parcels to a new posting plan - this is why we are selecting all parcels in that block to participate in the alignment and why all our alignment links go between the selected parcels and the connection lines representing the posting plan.  For us, this is a very common scenario and it would be ideal not to have to use a workaround.  ... View more

The generate alignment links within tolerance option is an efficient way to automatically generate parcel alignment links; however, it would be beneficial to have an optional checkbox that would allow you to specify to generate links only within the map extent. This option would allow you to have more control over where links are automatically generated. Say there is an area you are aligning where the links to create are quite obvious, but there is another area where you would be better off manually creating links. This option would allow that to be a smooth process.  ... View more

In the ArcMap Join dialog box, one of the ways in which you can manually create a link is by drawing a box around 2 points - the software will automatically create a link between the two points you drew a box around. Can something similar be provided in ArcGIS Pro? Currently, the only way to manually create a link is to click once on the starting point and then again on the ending point. It would be faster to just be able to draw a box.  Our organization typically prefers to create links manually as opposed to auto generating them, just so we can be sure the links are all correct. In a plan like the one pictured below, having a box tool would save a significant amount of time:    ... View more

 Within the parcel fabric our organization maintains, we store control points for the entire province. Keeping these control points up to date requires regularly ingesting a control feature class containing 10s of thousands of control points and only updating the changed points in our parcel fabric. Previously in ArcMap, this workflow was accomplished using the ‘Load control points’ tool. Our organization is now in the process of migrating to ArcGIS Pro. The ‘Import Parcel Fabric Points’ tool in ArcGIS Pro is missing some key functionality for it to be used as a replacement in our workflow. In its current state, the ‘Import parcel fabric points’ tool is better suited to importing small numbers of points in a single plan, rather than a large number of control points throughout a whole province. There are several important enhancements that would help make the ‘Import Parcel Fabric Points’ tool more suitable for importing a large number of control points: Additional Matching Methods: Proximity Match based on XYZ Attributes: Allow the matching of existing control points based on the XYZ attributes rather than shape geometry. This will make it easier to update points that have been moved without having to manually match them. Match based on Attribute Only: Allow the ability to match points based on a field only (such as the Name field), not proximity. This would make it easier to update a large number of existing points quickly using a known unique attribute without the need for computationally expensive proximity calculations. Additional Optional Parameters: Update Attributes Only: Allow the ability to update only the attributes of the points, including the XYZ attributes, without updating the geometry. This will reduce the risk of unintended changes to the parcel fabric Detailed Logging: Provide more detailed logging options that include information about what points have changed and how they have changed. This will make it easier to identify any issues that may arise. With the ArcMap ‘Load Control Points’ tool it was possible to output a Log Results file, this functionality would be beneficial in ArcGIS Pro as well. By incorporating these enhancements into the ‘Import Parcel Fabric Points’ tool, our organization will be able to more efficiently update our parcel fabric control and reduce the risk of errors or unintended changes. ... View more

As an organization, we accept many types of plans from Surveyors. This includes posting plans, which contain parcel boundary linework but no related parcels. We use a digital submission process that creates simple feature class that represent survey plan information. The resulting line feature class that is created from the digital submission process is brought into the parcel fabric using the ‘Copy Lines To’ tool. This is the most efficient way to bring in the geometry and attributes of the lines into the parcel fabric; however, the ‘Copy Lines To’ tool automatically creates seeds for each closed loop. In the case of the posting plans we work with, we do not need parcel seeds built for each closed loop of lines. This means that once the lines are copied into the parcel fabric and the seeds are created, the seeds need to be selected and deleted. This can be a tedious process. We would like to be able to have the option to decide whether the ‘Copy Lines To’ tool creates seeds or not. This could look like a radio button that you can enable if you would like to create seeds when the tool is executed or disabled if you do not need to create seeds for the linework you are bringing in. This would streamline our workflow and save us time in the long run. Example of a posting plan is attached, note there is no parcels created with this plan only lines. ... View more

Our organization relies on a digital submission process to efficiently bring in parcel data received from Surveyors. Our digital submission process produces simple feature classes that contain the geometry and attribution we need in order to create features in the parcel fabric without having to manually create each feature. The output line layer created from our digital submission process consists of the parcel boundary lines as well as any relevant connection lines that are depicted on the survey plan. Currently, we use the ‘Copy Lines To’ tool to bring in the line work from our digital submission process. This works very well for lines that represent parcel boundaries; however, we are unable to use this tool to create Connection Lines in parcel fabric, as Connection lines are not associated with any parcel type. Since we can’t use the ‘Copy Lines To’ tool for Connection Lines, we have to use a ‘Copy> Paste Special’ workflow to bring them in. Although this process does work, it is less reliable (sometimes the ‘Paste Special’ option is greyed out) and it is not consistent with how we bring in the other lines. The Paste Special is also difficult to use in our case because the vast majority of the time, it is more convenient to select features in a way that is not compliant with selecting features for editing. We mainly either use select by attribute (which sometimes works with the Paste Special) or select all (which does not work with the Paste Special). The desired functionality would be to have the ability to use the ‘Copy Lines To’ tool to copy lines into the parcel fabric Connection Line layer. This would greatly improve the flow of our workflows and ensure consistency with how lines are being brought into the parcel fabric regardless of what layer the lines are being brought into. It would also allow us to avoid common mistakes when using the Copy and Paste Special. Thank You! ... View more