|
POST
|
@AngelaP- the second problem that you mention with saving the traverse file is a bug that is fixed with the latest patch, IE ArcGIS Pro 3.0.2. It sounds like you may need to update to that. For the first problem, that is not as easy to discern. Do you have a definition query set on the layer? If it's what @JeffWard mentioned, you could also try to turn off the scale dependency on the connection lines layer, by setting the "Out beyond" to <None>:
... View more
10-28-2022
01:49 PM
|
0
|
2
|
4570
|
|
POST
|
@MahindaAbeykoon- what you describe regarding the Merge Parcel Points tool is not the same problem as outlined in the original description of this post. The good news is that there is also a solution for your case. We have, by default, allowed the merging of multiple points that have their Is Fixed attribute set to "Yes". This allows an editor to accommodate workflows where they need to merge what are sometimes referred to as "porcupine corners" where there are multiple "Fixed" points at a single corner, and they need to be merged. To solve your case, where you'd like to protect from an accidental deletion when merging points, you can create a new Constraint attribute rule on the points, using the arcade expression: if ($feature.IsFixed == 1)
{ return false; }
return true; and inserting it as follows:
... View more
10-26-2022
10:23 PM
|
0
|
0
|
2494
|
|
POST
|
Hi Bill, I see that too. But if you click the Play button: ...you should be able to watch/start the video. That works for me, does it work for you? -Tim
... View more
10-12-2022
08:31 AM
|
1
|
0
|
1550
|
|
POST
|
Hi Atish, this is not possible, but it's an interesting question. Can you provide some more information about your goal? What parts of the Parcel API are you interested in using to edit standard feature classes? It should be noted also that any parts of the API (geometry/editing/geodatabase etcetera) can be used on the parcel fabric feature classes, and that you are not limited to use the Parcel API exclusively when making customizations for the parcel fabric. -Tim
... View more
10-12-2022
08:26 AM
|
0
|
0
|
516
|
|
POST
|
Hi @DrewDowling - I've been working through your goal to add subtypes to connection lines and to fabric points. Thank you for your post. First, to answer your specific questions. Are subtypes supported in Parcel Fabric lines and points? Yes. Is the parcel fabric topology modifiable? Yes, but with some known limits, as described more fully below. Here are some key points: What you are attempting is possible with the parcel fabric. However, there may be a problem that you’re experiencing that I’ve not identified. Please respond here if this post does not solve any elements of your scenario, and we’ll continue work on figuring it out. Two software user interface defects were found, and they have workarounds. These are both described under a logged support item (Reference: BUG-000152163). These defects and workarounds are described below. There are some behaviors and user experiences that you may have encountered that are by design; some of these behaviors and user experiences are different from similar functionality in ArcMap. Software user interface defect 1: When a subtype code has a value of 0, it is not presented properly in the user interface when viewed in the topology properties. The topology rule is incorrectly shown to indicate that it applies to a subtype although it actually applies to the entire class. Workaround: Instead of using a 0 code, use subtype codes starting at 1. Software user interface defect 2: When a class level rule exists, and there is a subtype field on the class, if there is any row that contains a null in the subtype field, it should cause the topology validation to present an error message (this is by design.) The user interface defect is that when running validate, the validation does not show the expected error message dialog. The Validate does not run, and the dirty areas are not removed, but there is no information presented about why nothing happened. Workaround: Use the GP tool Validate instead to get this error message. For the specific error message that’s returned, you can solve it by making sure that your feature class with a subtype has valid and non-null subtype codes in their subtype field for all features. Related to the specifics of the fabric generated topology: - The Remove button is disabled for fabric generated topology rules. This is by design. We are considering allowing the removal of these rules in future releases. - You are not able to alter the fabric generated topology rules. In terms of adding new topology rules, when you click the Add button you do not get a new dialog; instead a new row is added to the grid on that page, and you can double click on the first cell for “Feature Class 1” in the first column to select the first feature class, and then do the same for the other columns. You can also click in the last row in the grid that says “Click here to add a new rule.” -Tim
... View more
09-08-2022
01:22 PM
|
1
|
0
|
3049
|
|
POST
|
Hi @LadyFranciscarKassama Here is how to do that: function NorthAzimuth2Quadbearing(azimuth){
return ConvertDirection( azimuth, {directionType:'North', angleType: 'Degrees'}, {directionType:'Quadrant', angleType: 'DMS', outputType: 'text', format: 'p d[-]mm[-]ss b'})
}
NorthAzimuth2Quadbearing($feature.Direction) Note, I have also made an update to the original answer. The updated code is reduced to a single line within the function, and shows how to use the text output type, and the use of formatting capabilities available on the ConvertDirection function. This approach is also included in the snippet above on this post for your request. To learn more about this function see: convertdirection -Tim
... View more
09-06-2022
06:27 PM
|
1
|
0
|
3828
|
|
POST
|
Hi Greg, yes you've correctly identified the workflow that should be used in 3.0. Running traverse courses from the point of commencement to the point of beginning should be considered as its own traverse. When you click the New button, the new traverse has its start point automatically set to the last point of the previous traverse. This is also documented here in a new section that was added for this update. The new section has the title "Create a parcel traverse with a connection from a point-of-beginning" : https://pro.arcgis.com/en/pro-app/latest/help/data/parcel-editing/createnewparceltraverse.htm
... View more
07-22-2022
04:48 PM
|
1
|
0
|
802
|
|
POST
|
Hi Marius, I'm responding here again, for the benefit of others who run into this scenario. Thanks for putting out this post. The geometry itself is not getting altered, but the circular arc is so flat that the geometry engine is not able to recompute the radius with any degree of precision that would return a meaningful value. If you use edit vertices, and move one end of the line you can see that the segment is still a circular arc. There is no discernible difference between the chord length and arc length, and the chord height is 0 (or very close to it). You can use the offset tool to see this: This is one of the reasons that it’s important to use/store the COGO attributes separate from the geometry. This is unfortunately a case where the geometry is not mathematically stable enough to get meaningful values, and so it thinks there is a straight line here… You can manually enter the radius and the arc length into the COGO attributes, but then you do need to be careful not to overwrite those again by using the Update COGO tool. For a future release we need to make the Update COGO tool smarter to avoid this problem where the COGO attributes are overwritten with straight line values for very flat circular arcs. The geometry engine starts to consider the circular arc to be a "straight line" for a central angle of around about 2 degrees. In this case the central angle is a lot smaller than that: (5.67/1640) radians x 180°/pi 0.00345732 radians x 180/pi = 0.198 degrees
... View more
05-18-2022
10:00 AM
|
1
|
0
|
1863
|
|
POST
|
This 11 minute demo covers two different approaches to divide the circular arc of a cul-de-sac, when only the chord lengths are given. Related to question this is an approach to use in 2.9 until this good idea for a future release, posted by @NickN, is implemented.
... View more
03-29-2022
01:24 PM
|
6
|
0
|
964
|
|
POST
|
My current understanding of the requirement: select points that are not used by any connections lines, not used by any parcel type lines, and not used by any historic parcel type lines. Depending on the subsequent action, control points may also need to be excluded from the resulting set. When I first tried this on Friday I found this is not as easy to do in a map with multiple parcel types. In working on this again today, I found the following approach worked: Select all points in the points layer. If you want to exclude control points from the final selection then start by only selecting points that are not control. for each line layer (connection lines, parcel type lines, historic parcel type lines) use the Select By Location to remove from the selection, using following the approach. Press Apply after each layer to keep the dialog up: This could also be automated via python scripting.
... View more
02-27-2022
02:24 PM
|
3
|
0
|
2173
|
|
POST
|
@LebowskiThis is a good candidate for the Parcel Fabric Ideas board Thanks, Tim
... View more
02-25-2022
02:12 PM
|
0
|
0
|
2196
|
|
POST
|
@DeanAnderson2- I just read from your original post that you are on 2.8.3. As mentioned in the prior response, this is fixed in 2.9.
... View more
02-14-2022
04:32 PM
|
1
|
1
|
1826
|
|
POST
|
@DeanAnderson2, this is a bug that is present in 2.8 and earlier. It has been fixed in 2.9. If you are already on 2.9, then please let us know so that we can follow up. The second line's COGO distance is calculated, so if you are using the parcel fabric, then you should see the COGO Type field set to "Computed".
... View more
02-14-2022
04:20 PM
|
2
|
0
|
1827
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 09-18-2024 12:38 PM | |
| 4 | 09-18-2024 01:01 PM | |
| 3 | 04-26-2024 11:14 AM | |
| 1 | 04-04-2024 03:04 PM | |
| 1 | 02-15-2024 04:08 PM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|