|
POST
|
Thanks - this will get me started. Was looking at SDK but was hoping I could make it happen with Python. Will see how it goes. Thanks again
... View more
09-02-2022
09:45 AM
|
1
|
2
|
4574
|
|
POST
|
I am looking for some advice. I am currently using ArcPro 2.9+ with a branched versioning and am setting up a new workflow. As a first step in our workflow process I need to create a version with a record. I prefer to do this all in one step so that I can programmatically control/manage both version and record info with one user interface. Once a version is created I have found that I can programmatically create a record using the following code which creates a record in the Parcel Fabric records feature class (with no spatial component). Obviously, I will be adding more attributes but am using this as a basic test. ------------- thisProject = arcpy.mp.ArcGISProject("CURRENT") Map = thisProject.activeMap TargetFabric = Map.listLayers("TaxlotsPF")[0] TargetRecord = Map.listLayers("Records")[0] cursor = arcpy.da.InsertCursor(TargetRecord, ["Name"]) cursor.insertRow(["DeanTest111"]) ---------------- I also found I can create a version using the "CreateVersion" tool. Again, using the tool from a script is important as we want to manage both the version name and the record name following a set of rules and also ensure that improper characters are not used to name a version or a record. I just took the following example from the user documentation but have used the tool successfully in a test environment. arcpy.CreateVersion_management(inWorkspace, parentVersion, versionName, "PUBLIC") ----- The "Change Version" tool only seems to apply to specific layers. It does seem to work that I can assign my new record change to a specific version (yay). Can this tool apply to "ALL" layers in my current project? (I will be trying this next - It should be pretty simple to loop through all layers in my current active map ) My question is: Is this a good way to do this or are there better ways? I have been testing a variety of tools, scripts, tasks etc. in a branched version environment for awhile. Again Our Goal - One user interface that helps the user create both a new version with a new record and changes the version and makes the new record active.
... View more
09-02-2022
06:28 AM
|
0
|
15
|
6494
|
|
POST
|
Amir Thanks for the response and I apologize for my slow response (as usual). I get it that the tool changes the schema. What I would like is a tool that does NOT to change the schema but lets me replicate what I can currently do interactively from within the CreateFeatures / Active Template tab. Using the tab I can open the active template and change set the default for the features I am about to create. This default is assigned for the features I am going to add. When that is done the "default" gets reset back to schema. Having this capability to programmatically set the default would be nice. I hope this clarifies what I am trying to do. Thanks
... View more
08-22-2022
10:59 AM
|
0
|
0
|
827
|
|
POST
|
We are in the process of testing branched versioning with Parcel Fabric. I preparation we have using parcel fabric in a standard Geodatabase. The AssignDefaultToField tool appears to work fine in ParcelFabric editing of a feature in a geodatabase. However, it does not appear to work in when using branched versioning. Using standard processes I can go in and change a default value (see below) However, when I go to use the tool it give the following error message. From the documentation it does not appear that this should be a problem. Is this an error or did I miss something regarding the limitation of features stored in a branched version?
... View more
06-26-2022
05:59 AM
|
0
|
2
|
926
|
|
POST
|
I got that, symbols that have a -1 are not using the symbolid. Unfortunately, I want them to have the symbolid when I am adding. In the annotation symbology properties I have it set to "No Substitutions" which I thought would force only reference to the symbolid. My problem is when the template has the symbol set(in my case 9) and I do not allow substitutions, when annotation text is added it should not assign the symbolid to be -1. The symbol that has been added should have a symbolid of 9 as contained in the template.
... View more
05-31-2022
02:36 PM
|
0
|
0
|
1605
|
|
POST
|
Sorry --- This happens in both Arcpro 2.8 and 2.9 with a standard geodatabase.
... View more
05-31-2022
02:10 PM
|
0
|
0
|
1617
|
|
POST
|
I have a lot of annotation. As I understand it, annotation is referred to by its AnnotationClassID and SymbolID (similar to ArcMap). My AnnotationClassID for bearing/distances have an id "34-Bearing/Distance" with a symbolid of "9" (made sure of this when converting from ArcMap). In the following example I have the symbolid in the template set to 9. But when I add an annotation string the symbolid is assigned a -1. Is there a way for the symbolid that is in the template to be assigned the correct value "9" ??
... View more
05-31-2022
02:09 PM
|
0
|
4
|
1621
|
|
POST
|
Thanks! That is so funny. I had not set up the templates for the parcel line feature class. Its working fine now.
... View more
05-03-2022
11:02 AM
|
1
|
0
|
1692
|
|
POST
|
Currently the traverse command appears to use the Default feature template. I have not found a way to easily change this. Does one exist? As a work around within the task environment, I have added a step before the traverse command and imbedded the "Assign Default to Field" tool. Unfortunately, this tool does not recognize coded domains and only lets you select a value (see below). The values below of 8,14,32 represent parcel boundaries, road right-of-ways, and railroad right-of-ways. Please let me know if there is a better way to deal with this issue. Thanks
... View more
05-03-2022
10:24 AM
|
0
|
2
|
1745
|
|
POST
|
Sorry found some code elsewhere. The following will remove all definition queries from a layer. In this case the layer is called "Anno0200Scale" as follows: import arcpy aprx = arcpy.mp.ArcGISProject("CURRENT") Map = aprx.activeMap Lyr = Map.listLayers("Anno0200Scale")[0] Lyr_cim = Lyr.getDefinition('V2') fTab = Lyr_cim.featureTable fTab.definitionFilterChoices = None Lyr.setDefinition(Lyr_cim) I am not sure if this is the best way to do it but it does it. Please let me know if there are better ways. Thanks
... View more
04-05-2022
10:17 AM
|
1
|
0
|
1609
|
|
POST
|
Been using 2.8 for a bit and have had no problem clearing definition queries with the following code. If TurnQueryOn is true it sets the definition query. If it is false it sets definition query to None. if TurnQueryOn: RecordWhereClause = "CreatedByRecord = " + "'" + RecordNumber + "'" for FilterLayer in FilterLayers: mapFilterLyr = Map.listLayers(FilterLayer)[0] if mapFilterLyr.isFeatureLayer: mapFilterLyr.definitionQuery = RecordWhereClause else: for FilterLayer in FilterLayers: mapFilterLyr = Map.listLayers(FilterLayer)[0] if mapFilterLyr.isFeatureLayer: mapFilterLyr.definitionQuery = None I just upgraded to 2.9 (I still have a machine 2.83 so was able to double check). But the definition queries are no longer being deleted but just turns them to "inactive". Is there something I am doing wrong? (I have seen other posts for this in the past and they appear to operate the same as mine does in 2.83.)
... View more
04-05-2022
09:24 AM
|
0
|
2
|
1625
|
|
POST
|
Final Test - Created a new geodatabase, Created a new line feature class, ran Enable CoGo tool. Entered a four sided box (1000,1000,1000,999). Closed it. All looks good. Divided the north line (1000 foot) as follows: Exhibits same behavior as before. Second COGO line has no distance as follows: When I use the percentage option, or equal parts option in works fine (of course). I continue to be confused.
... View more
02-14-2022
03:01 PM
|
0
|
1
|
2709
|
|
POST
|
Doing more checking. My COGO lines appear to be OK. When I do a line intersection and do not "Recalculate COGO Attributes" the tool calculates the cogo attributes correctly from the parent. In the following attribute list the intersecting line is non-cogo. It is intersecting with a COGO line that has a distance of 199 ft. The two distances total to 199 feet after the intersection (as a further test this was a closed line with a one foot error. It all operated as expected.
... View more
02-14-2022
02:37 PM
|
0
|
2
|
2709
|
|
POST
|
First - thanks so much for help on the duplicate domain issue. That fixed the problem. On my second issue. I was concerned about the line so I created a NEW line with the traverse tool (just a simple 200 foot long straight line as illustrated above). Attribute for cogo enabled was "entered" so not sure what is going on. Glad it works as expected for you. At least that means I understand how it is supposed to work. Now just have to figure out what is wrong. I am not sure what a "true COGO-Enabled Line" is. I have replicated my problem using my converted taxlotline COGO data from ArcMap (non-fabric) and also from newly created lines. We have been testing and using other commands such as Traverse on this dataset for months and it has been operating correctly (as expected). I have also replicated my problem on a non-fabric COGO feature class that has had the "Enable COGO tool" run. I assume this makes a COGO line? So I think I am using COGO enabled lines. I there some setting I missed?
... View more
02-14-2022
01:33 PM
|
0
|
3
|
2710
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | yesterday | |
| 1 | 07-09-2025 10:30 AM | |
| 1 | 02-05-2025 06:39 AM | |
| 1 | 06-10-2024 10:15 AM | |
| 1 | 06-10-2024 05:19 AM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|