POST
|
I have figured out a simple work around. You can get the active record globalid for the record from one of the layers that participates in the fabric if you click the "Show Only Active". This sets up the definition query which you can get the ActiveRecordNumber from. In the following bit of code the Taxlot_Lines is a feature layer that is part of the fabric. RecordNumber is the final variable that contains the globalid of the active record. aprx = arcpy.mp.ArcGISProject("CURRENT") Map = aprx.activeMap mapTaxlotLineLyr = Map.listLayers("Taxlot_Lines")[0] TaxlotLineLayerWhereClause = mapTaxlotLineLyr.definitionQuery RecordNumber = TaxlotLineLayerWhereClause.split('{')[1] RecordNumber = RecordNumber.split('}')[0]
... View more
11-16-2021
10:48 AM
|
1
|
0
|
893
|
POST
|
That is it! Have not used CIM before so this is a great introduction to it. Thanks
... View more
11-09-2021
05:54 AM
|
0
|
0
|
963
|
POST
|
Parcel fabric has default definition queries Taxlot_lines - (RetiredByRecord Is NULL). I have successfully added additional definition queries to support other business needs and can manually change between them. Is there any way to change which definition query to use with Python. Also I create a new definition query with the layer property but would rather not delete and create them all the time. Especially when parcel fabric comes with some already.
... View more
11-08-2021
11:21 AM
|
0
|
2
|
1028
|
IDEA
|
Have not been able to find this. Any idea what release this is planned for?
... View more
11-01-2021
03:56 PM
|
0
|
0
|
2306
|
IDEA
|
Sorry for my absence. Took a short vacation and then was slammed with some non-gis deadlines. Very much appreciate the comments Amir and Frank. 1. The relationship classes and filters do work. But it requires me to set this all up and manage. (Yes I know I am lazy.) From a gis support persons perspective it would be great to have a tool/command that did this and then honored it through some basic operations as folllows: -- When an record is active these features would automatically be assigned to the active record (the same way a line that participates in the parceltype would be. -- When features are selected for the active record these features would be selected -- When Show only Active record is clicked you would see these feature as well. At this time all of these capabilities need to be managed within the task environment and with scripts. 2. Retire Records - Sorry about terminology - when a number of functions impact a record and the features associated with record are assigned "Retired By Record" I want this to also be done to the related feature classes. To Be Clear - I am referring to a point, line and annotation feature classes that are used for cartographic purposes to assist in replicating a record. The following diagram illustrates some of these features (highlighted in red). I our redesign to Pro/Fabric and review of business practices these features remain as annotation and lines (I hope this helps describe what I am talking about).
... View more
10-07-2021
06:23 AM
|
0
|
0
|
1359
|
IDEA
|
Amir - here are response... Should the cartographic features be associated to a parcel instead? No - My thought is that they should be associated with the record. As you stated if with the parcel it can get confusing. In addition, some cartographic features that may be put on the map (some reference lines) may not be directly associated with a single parcel. In our business process the cartographic features are associated with the record. For your current workaround Attribute Rules could be used to populate the fields in the cartographic features when a parcel (polygon / line) is updated. I did not use attribute rules for this. As attribute rules are always on or off (with enterprise) and there are business cases where the cartographic features may be updated without a record. So I use tasks (user selects record to get the record id and then does work, as part of the task the feature is update with the record id). Sorry this explanation may not be overly clear. Order of operations might also play a role - do the cartographic features always get created after the parcel is created? In our business process it seems so, but there may be exceptions that I have not thought of. It also seems this can also cover 'cadastral reference features' that often appear on cadastral maps like: walls, structures, trees, wells, ... Yes these are also types of features that are part of the record. I have also be discussing this with Frank Conkling (He has been helping me clarify my request).
... View more
09-23-2021
06:42 AM
|
0
|
0
|
1443
|
IDEA
|
Problem: Many users have cartographic feature classes (lines and annotation) that are managed in support of the parcel feature classes/types in the record. These feature classes are used to clarify and assist record editors and the public in understanding the parcel record features (polygons and lines). They are currently not viewable as being part of the record and are not retained the way historical polygons and line parcel fabric feature classes are. Request: Develop a means where cartographic features classes (lines and annotation) can be associated/tied to the record types in the parcel fabric. By having this association when a parcel is marked as historic, the annotation and cartographic lines can also be marked as historic (not deleted but still available.) Conversely, as a parcel is created, all annotation and cartographic elements created are also associated with the record and would be visible, edited and managed as part of the record. Current WorkAround: I have added the "created by record", and a field called "current" to my cartographic feature classes. (In hindsight I probably should have included the "retired by record" field instead of the "current" field). I have prototyped tasks with embedded scripts to manage how cartographic feature classes are added, retired and viewed as part of a record. This works but is not a great solution and does not provide the user with much flexibility.
... View more
09-21-2021
09:47 AM
|
1
|
10
|
1474
|
POST
|
Thanks for looking at this. Your second statement is correct, I do not know that active record's name. The $map.ActiveRecord would be great to use. Does this exist? If so I am not sure how. Currently I have created a task that the first step is to select the active record and from that task, I pick up the recordname and globalid as attributes for the selected record to use later in the task workflow. This seems to work OK but ties me to a task process and that maybe ok. Once this is done I am working on automatically filtering the related feature classes for just that record (based on filter of globalid - which I have as an attribute in each feature class). I then will have a palate of tools that when used will automatically calculate the globalid for each feature as it is added. Re-reading this it may not be too clear (sorry). So backing up, being able to use the $map.ActiveRecord would be great.
... View more
08-16-2021
08:21 AM
|
0
|
1
|
1058
|
POST
|
Is there an arcade or some other function/process that will allow me to get/save the GlobalID of the current ActiveRecord. It appears that the active record (when you create a new record) is not selected and is only selected when you use the "select record" or "attribute rule showing selected record" in the record menu. For example, if I have a record named "TEST1" and use the "select record" the selection set is "TEST1". However, when I go to manage records and select another recent record "TEST2" and set it the active record the selection set in the records table is still "TEST1" until I use the "Select Records" or "attribute rule showing selected record" in the records menu. I have other feature classes that I want to associate with the current active record (cartographic lines, annotation classes, etc). Ultimately I would like to create an attribute rule that does this but not having that I think I could do it with a workflow task.
... View more
08-11-2021
07:54 AM
|
0
|
5
|
1083
|
POST
|
We looked at Parcel Type Admin Boundaries in 2.6 and had some issues. Now that 2.8 is out I am looking at this again. Business Case: Our administrative boundaries are managed by our cartographers (along with taxlots). Our admin boundaries are managed as taxcode areas. Taxcodes have a many-to-many relationship with a variety of taxing districts (fire, school, city, transit, etc.). Over 95% of the time these boundaries are coincident with taxlot boundaries. Changing of taxcode boundaries (annexations of any district) are initiated by a "legal" record of some kind. Every spring our cartographers process these annexations so that they are included in the next tax season valuation (Very simple overview) Pros/Cons: The advantage of the admin only parcel type is the built-in nature of the record. I have built three different sets of custom business flows over the years to track and manage taxcode/district annexations. The parcel fabric record does all that for me (no coding - nice!). I have done a few simple business flow tests and it looks good. Question: Who has implemented (or are their more detailed ESRI examples of) the Parcel Type as an Administrative Boundary? Unfortunately, I have not found a lot of documentation or examples where folks have implemented this (impacts on editing, topology rules, etc). I would like to get some links/contacts to help in my review and testing. I hope it is in some video that I just missed or that some user has some thoughts on this. I will continue to test.
... View more
07-27-2021
08:33 AM
|
3
|
1
|
513
|
POST
|
We are learning how to use traverse within the parcel fabric environment and really like that you can measure and use traverse both working at the same time. Unfortunately, measure always has a default units of imperial when we open a project. . We followed the documented method to set the default units in options/units/distance units to set the default units to feet As follows: Unfortunately, the units are still imperial. Are we doing something wrong? It appears that this was a issue some time ago and was fixed but I was not able to find it as a current bug. I have tested this in both 2.8 and 2.6 so feel I must be doing something incorrectly.
... View more
06-17-2021
12:09 PM
|
0
|
2
|
1117
|
POST
|
This problem appears to be back in 2.6 and 2.8 ArcPro. The default is ALWAYS imperial. The options--> Units-->Distance Units dos not change the default. I have it set to Feet as the option and the following happens... Am I missing something??
... View more
06-14-2021
09:48 AM
|
0
|
0
|
2024
|
POST
|
It appears I am using the Maplex Label Engine (Option selected below)
... View more
02-22-2021
09:03 AM
|
0
|
0
|
895
|
POST
|
We manage our dimensions for bearing/distance as annotation. Labels are a great way preview these features and they are easily converted to annotation using the ConvertLabelsToAnnotation tool. I have built a simple script in our edit environment to manage this process and it is working great. However, when we display bearing/distance an option my cartographers often use is to place bearing on top and distance below. I am doing this with Label Class - Position (Regular placement / Allow stacked labels / Centered Straight). My labels are stacked with this Python Code (I assume it would be the similar with Arcade). def FindLabel ( [Direction],[Distance] 😞 beardir = [Direction] + "\n" + [Distance) ] return beardir My issue is, I need to Offset the Direction Above and Distance Below to be farther then the default allows me. The only ways I found to do this is to create two separate label classes and position one above and one below or to insert a second line feed "\n". I like the annotation stacked as the tools in ArcPro to edit stacked annotation work very well and the second line feed creates an offset that is too large. I am hoping that there is a simple option to offset stacked labels above/below the line and I have missed it.
... View more
02-22-2021
06:01 AM
|
0
|
3
|
948
|
POST
|
I am much more familiar with Python so that is good with me.
... View more
02-04-2021
10:05 AM
|
0
|
0
|
1185
|
Title | Kudos | Posted |
---|---|---|
1 | 06-10-2024 10:15 AM | |
1 | 06-10-2024 05:19 AM | |
1 | 06-05-2024 11:55 AM | |
1 | 11-14-2022 05:13 AM | |
1 | 02-14-2024 08:17 AM |
Online Status |
Offline
|
Date Last Visited |
06-19-2024
03:50 PM
|