|
POST
|
@DrewDowling @jcarlson When you add a parcel fabric to a new map we set the correct default behavior = geodatabase topology. If you close and open the map it does remember this setting. If you know the steps that make the map 'forget' the setting we would love to know (and fix).
... View more
07-17-2023
09:42 PM
|
1
|
5
|
4189
|
|
POST
|
@FrankOuyang There is nothing special about the default feature layers that come with the parcel fabric, but this is a good opportunity to consider 3D default layers or improvement of the existing layers. You can use the geoprocessing tool 'Apply Symbology' and apply your green layer to your grey layer. As a rule of thumb, to improve performance, try to have fewer layers in the 3D and move layers that can be 'rasterized' on the surface to the 2D group. If there are layers that are not needed remove them altogether. You only need the parcel fabric controller layer in the map if you plan to perform parcel editing in that map. Please let us know how this works. You are a pioneer, so we can all learn from your experience and improve.
... View more
07-10-2023
06:53 AM
|
4
|
0
|
1561
|
|
IDEA
|
How to add other linear units such as Chains? Project -> Options >- Units -> Distance Units -> Then click on select unit code and add your favorite Chain flavor. You can also get rid of units that are not applicable Open the traverse pane and you will see the units Notes: The measurements are always stored in the unit of the spatial reference. Why? this is very useful when you have to project the data or need to compare it to the geometry. You can modify the label expression to show the dimensions in your favorite unit. For example: PLSS features layers show dimensions in chains while other parcel types shows dimensions in feet.
... View more
07-07-2023
12:19 AM
|
0
|
0
|
2347
|
|
POST
|
Yes - option one is the same as not triggering the rule on 'Insert', only on 'update'. If you can trigger an update after feature creation you'll get the same result. Task verification can be executed on all features that were created during the task execution and prevent the user from proceeding to the next step if any of verifications fail.
... View more
07-05-2023
11:57 PM
|
1
|
0
|
3810
|
|
POST
|
@ChaimSchwartzIroads As you have found out, Attribute Rules constraints do precisely what their name suggests 🙂 Here are a few options to explore: 1. If you use editor tracking, you can use the creation time to skip checking the feature if it has been created in the last few seconds. Here is a code sample you might adjust for a similar case: //Setting: If your data was migrated on June 18th 2019, you should add 2 days (June 20th) to avoid time rounding issue.
var MigrationDate = Date(2019,05,20); //Note: the month count starts at zero. year 2019, month of JUNE, 20th day.
var CreationDate = Date($feature.Create_Date);
if (DateDiff(CreationDate, MigrationDate, 'days') > 0){
return !IsEmpty($feature.CreatedByRecord);
}
return true; 2. You can set the default value of the field to a value and use the Arcade logic to ignore that value. That is not that good though, as there's no difference between this value and 'NULL' 3. Switch the rule to Validation Rule instead of the constraint rule. In many editing workflows features exist in an interim state, before they get planarized, merged etc. So it is easy to catch errors upon validation versus creation. 4. Use Task verification. It is not stored in the information model. The caveat is that the user must use the task. Any edits outside of a task will not be captured.
... View more
07-05-2023
03:07 AM
|
1
|
0
|
3834
|
|
IDEA
|
@MichaelVolz It has been implemented partially but is not yet exposed on the UI. We cannot provide a timeline when this will be implemented 😞
... View more
06-26-2023
02:26 AM
|
0
|
0
|
2392
|
|
POST
|
If you want to keep them in order to be able to understand how the parcels got created (clipped and merged), you can wither create a separate parcel type for them as @anna_garrett suggests. Just keep in mind that having too many parcel types has a performance hit (opening database cursors....), so you can also consider have a parcel category for those - just add a field with a domain to manage them, symbolize them in the layer, update the editing feature templates etc. If you want these parcels to be in a separate layer, you can use definition queries. The Parcel Transfer tool also be considered for this type of workflows.
... View more
06-21-2023
03:32 AM
|
0
|
0
|
1423
|
|
POST
|
Do you need your deleted parcels to be copied to an external feature class for further research when they get deleted? Some organizations do not have the time to research each case and would rather copy them out, for others this might be an early symptom of 'parcel hoarding' 🙂 In any case, the attribute rule is triggered when the parcel is deleted. At that event, it is copied to an external feature class. you can download the attached project package to review it. If you like it just export the attribute rule, import it and make the needed modifications (table names, attributes...)
... View more
06-21-2023
03:05 AM
|
4
|
1
|
1785
|
|
POST
|
Use Attribute Rules to calculate the next parcel number in a given book and page. In this video I walk you through the process of writing such a rule, starting with popups. You can use the attached project package to review and apply the expression/attribute rule to your data. Please let me know if you find this helpful, or have any ideas on how this can be improved, please leave a comment. Amir
... View more
06-15-2023
02:59 AM
|
2
|
0
|
1148
|
|
POST
|
@DrewDowling Yes - you can modify any of the Attribute Rules that are shipped with the system. You can even delete them if they are not applicable for you. The current expression for the rule MUST HAVE A RECORD is: return !IsEmpty($feature.CreatedByRecord); You can modify it to: //Setting: If your data was migrated on June 18th 2019, you should add 2 days (June 20th) to avoid time rounding issue.
var MigrationDate = Date(2019,05,20); //Note: the month count starts at zero. year 2019, month of JUNE, 20th day.
var CreationDate = Date($feature.Create_Date);
if (DateDiff(CreationDate, MigrationDate, 'days') > 0){
return !IsEmpty($feature.CreatedByRecord);
}
return true;
... View more
06-14-2023
05:01 AM
|
1
|
0
|
3594
|
|
POST
|
@RobertChaney Great to see that you are improving efficiency by moving away from annotation to labels. From looking around you can use the arcpy method ' queryPointAndDistance' It is documented here: https://pro.arcgis.com/en/pro-app/latest/arcpy/classes/polyline.htm You can also view this code sample copy - pasted from here: pnt = [x[0] for x in arcpy.da.SearchCursor("point",["SHAPE@"])][0]
line = [x[0] for x in arcpy.da.SearchCursor("line",["SHAPE@"])][0]
line.queryPointAndDistance(pnt)
#output
(<PointGeometry object at 0x27b71d30[0x27b71860]>, 212.1234, 23.1234, False) Another place to look at is this community post which concludes the use of the same method. Once you have it working it might be good to share with others that run into the same issue and want to leverage the LabelPostion field.
... View more
06-12-2023
01:26 AM
|
1
|
0
|
3414
|
|
IDEA
|
@SusanLMoore Thanks for your comment on the other idea. Can you please change the title of this idea to say something like "Highlight Gaps and Overlaps in multiple parcel layers simultaneously? When a gap or overlap is identified, would it be challenging to know which layer it belongs to? Should the layers be visible when it runs? We are looking to introduce multiple enhancements to the Highlight tool, so it's great timing to collect the business requirements and design them all at once. Thank you!
... View more
06-09-2023
01:08 AM
|
0
|
0
|
5218
|
|
POST
|
@DianeBaker Since Attribute Rules work on a table, and since the historic parcels are in the same table as the current parcels, the expression (once written) will find the next available number within a 'book and page' regardless if the parcels are current or historic. I'll probably get to it next week.
... View more
06-09-2023
12:58 AM
|
0
|
0
|
3173
|
|
IDEA
|
@SusanLMoore This looks like a duplicate idea of https://community.esri.com/t5/arcgis-parcel-fabric-ideas/update-the-highlight-tool-to-allow-for-multiple/idi-p/1294930.
... View more
06-08-2023
03:47 AM
|
0
|
0
|
2278
|
|
POST
|
@DianeBaker @AdamHart1 This Arcade expression below can be used in a popup to find the next value in a 'Book' and 'Page'. (right click on the layer, configure popup, add an expression...) // Expression uses the 'Book' and 'Page' fields to find the maximal parcel name in the given 'Book' and 'Page'
// then returns the value + increment
var ParcelsFS = FeatureSetByName($map, 'Parcels_CREST', ["Name", "Book", "Page"], true);
var book = $feature.Book;
var page = $feature.Page;
var MaxParcelNumber;
// Find the maximal parcel number in a given book and page
if ((!IsEmpty(book))|| (!IsEmpty(page))) {
var sql = "BOOK = '" + text(book) + "' AND PAGE = '" + text(page) + "'";
var FilteredParcels = Filter(ParcelsFS, sql);
MaxParcelNumber = Max(FilteredParcels,"Name");
//Increment
var increment = 1; // change to your increment size
If (!IsEmpty(MaxParcelNumber)){
MaxParcelNumber = text(number(MaxParcelNumber) + increment);
return MaxParcelNumber;
}
} It assumes you have a 'Book' and 'Page' fields on the parcels layer. I was about to turn this into an Attribute Rule when I realized that if you create a new parcel, you are unlikely to have the Book and Page fields populated... so when creating a new parcel, the expression will need to intersect with another layer to get the Book and Page values. Before creating the Attribute Rule: Do you have a feature class for the Book and Page? Is this a valid path forward?
... View more
06-05-2023
09:02 AM
|
1
|
1
|
3192
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 4 weeks ago | |
| 1 | a month ago | |
| 3 | a month ago | |
| 2 | a month ago | |
| 1 | 06-12-2023 01:26 AM |
| Online Status |
Offline
|
| Date Last Visited |
Monday
|