|
IDEA
|
In ArcGIS Pro you can calculate fields on any parcel features. Parcel features in Pro are simple feature classes and layers. You can use the Calculate Field as well as the Calculate Geometry.
... View more
11-27-2020
06:25 AM
|
0
|
0
|
2118
|
|
POST
|
Hi Marius, A new tool to Merge Parcel Fabric Points is coming out with Pro 2.7. Please post any Pro Parcel Fabric related question/idea in the new parcel fabric place: https://community.esri.com/t5/arcgis-parcel-fabric/ct-p/arcgis-parcel-fabric Amir
... View more
11-19-2020
02:04 AM
|
0
|
5
|
3956
|
|
POST
|
Hello Anna, With ArcGIS Pro 2.7 any points that move will also move any feature that is connected to it including connection lines. We will probably show it in the next meetup event: https://www.meetup.com/Esri-Parcel-Fabric-Meet-Up/events/273744780/ Amir
... View more
11-18-2020
02:26 AM
|
1
|
0
|
3776
|
|
POST
|
Hello Kara (?!) Yes - you can have an attribute rule that recalculates the geometry of polygons in a different feature class when the source feature is updated. You will have to think what you do for Insert (new), Update and Delete events. You might want to read this blog: https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/advanced-gdb-attribute-rules-editing-external-features-with-attribute-rules/ Here is an example I wrote to update a 'Section' PLSS feature class when another PLSS aliquote is updated: var twpNo = $feature.TWNSHPNO var twpDir = $feature.TWNSHPDIR var rangeNo = $feature.RANGENO var rangeDir = $feature.RANGEDIR var sectionNo =$feature.FRSTDIVNO //The attribute rule is added to the Intersected polygon class on the FRSTDIVNO field on update //select all other intersected polygons that belong to the same section //construct a sql query for intersected and sections var sql = "TWNSHPNO = '" + twpNo + "' And TWNSHPDIR = '" + twpDir + "' And RANGENO = '" + rangeNo + "' And RANGEDIR = '" + rangeDir + "' And FRSTDIVNO = '" + sectionNo + "'"; //dissolve all intersected polygons in the section to get a polygon geometry var fields = ['TWNSHPNO','TWNSHPDIR','RANGENO','RANGEDIR','FRSTDIVNO', 'GlobalID']; var intersected = FeatureSetbyName($datastore, "Intersected",fields, true); var fsIntersected = Filter(intersected,sql); var SectionGeometry = Geometry($feature); for (var interPoly in fsIntersected){ SectionGeometry = Union(SectionGeometry, Geometry(interPoly)); } //find the corresponding section geometry feature var sections = FeatureSetbyName($datastore, "Sections",fields, true); var fsSections = Filter(sections,sql); //get the section row (we should only have one ) var sectionToUpdate = first(fsSections); var sectionGlobalID = sectionToUpdate.GlobalID; return { //we want to just return the value of field `FRSTDIVNO` no change require "result": $feature.Field, //this keyword indicates an edit that need to happen, its an array since we can make many edits "edit": [ { //the other class we want to edit "className" : "Sections", //the type of edit, in this case we want to update so we say `updates`, its an array since we can make many updates "updates" : [ { //what feature we need to update? we can either find it by the globalid or the objectId "globalID" : sectionToUpdate.GlobalID, //what do we want to update (we can optionally add attributes property and update properties there) "geometry": sectionGeometry } ] } ] }
... View more
11-16-2020
03:10 AM
|
2
|
1
|
3104
|
|
POST
|
Hello Mahinda, Did you already install 2.6.3? If yes - would you mind repeating the process and reporting? Thanks, Amir
... View more
11-16-2020
02:08 AM
|
0
|
0
|
2800
|
|
POST
|
Hi Wiley, I recommend that you submit a technical support case. It is always a good practice to run the geoprocessing "Check Geometry" and/or "Repair Geometry". Amir
... View more
11-16-2020
02:04 AM
|
0
|
0
|
1603
|
|
POST
|
Hi Dave, Not yet... can you please expand the use case you want to use it for? Is this for: 1. Calculating a field? 2. Verification action? 3. Other? Thanks, Amir
... View more
11-13-2020
04:16 AM
|
0
|
0
|
1267
|
|
POST
|
Some commands require the correct context to be set up. If you want to open the properties of a layer or a table it has to be the only one selected in your table of content. Make sure you have the correct map view as active and then set the table of interest as selected. the same step can call the Properties command. Using the action recorder is the easier and safest way to make sure you are using the right command.
... View more
11-13-2020
04:10 AM
|
1
|
0
|
1133
|
|
POST
|
Apologies Menno. There is no way to recover it - it is gone. This is a bug we have been chasing for a long time and cannot reproduce. If you have a backup of your project (APRX) or a backup of your task item as a task file you could use it. Amir
... View more
11-13-2020
03:56 AM
|
1
|
1
|
8230
|
|
POST
|
Hi Jay, I think I have an easier way for you to accomplish your workflow: use Attribute Rules (calculation). You can update fields in the 'affected area' polygon by using the Arcade Intersect method: https://developers.arcgis.com/arcade/function-reference/geometry_functions/#intersects If needed you can use a task step to trigger an update event on the 'Affected Area' feature. Here is an example of a parcel polygon using the method to find a field value in another layer. In your case you can use the Count method. You might need to combine a SQL query to only select valve that are closed.
... View more
11-13-2020
03:52 AM
|
0
|
0
|
1313
|
|
POST
|
Hi Julia, Currently, there is no way in Tasks to change a definition query. Current options: 1. Use a task to select the layer properties, then instruct the user on how to modify the definition query. 2. Write a python script tool that modifies the definition query, then use a task step to call that script Future: This capability is in Tasks Roadmap.
... View more
11-13-2020
03:36 AM
|
0
|
1
|
3356
|
|
IDEA
|
Hi Mike, We plan to implement the option to choose between parcel type (and subtype) and the feature template for a few tools including the Duplicate Parcels tool.
... View more
11-13-2020
03:06 AM
|
0
|
0
|
1789
|
|
POST
|
Hi Mike, There are 2 issues I see: 1. You are trying to copy a parcel fabric from a feature dataset to the SAME feature dataset. We only allow one parcel fabric per feature dataset. 2. The name of the input parcel fabric is the same as the output in the SAME geodatabase. Recommendation: The geoprocessing Copy Parcels is best used as an exchange mechanism and replaces the old cadastral XML format. So you can create a new File GDB and export the (selected) parcels into it without having to rename it.
... View more
11-13-2020
03:03 AM
|
0
|
0
|
1299
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 3 | 2 weeks ago | |
| 2 | 2 weeks ago | |
| 1 | 06-12-2023 01:26 AM |
| Online Status |
Offline
|
| Date Last Visited |
a week ago
|