|
POST
|
Brandon, I'm sorry to hear that you’re experiencing problems. Since you were able to successfully complete the fabric adjustment, it implies that the cogo record data is good; the adjustment report will also help you to find any problem distances or bearings, close points, and so on. With regard to your case of the problem geometry, we have seen cases where a bug in the software created some incorrect line-point locations in certain workflows; this bug was fixed in the 10.3 release. Without seeing your data it’s hard to know if these “bad” line-points are the cause for the problems you’re seeing. (I’ll message you separately to see if I can arrange to get your data and to help you. Please also contact tech support directly.) Otherwise, here are some things you could try: Ensure that you have the latest parcel fabric patch for your particular release, you can find the list of patches here. In the Catalog window, right-click the Fabric and click “Check Parcel Fabric” to get a report on the data in the fabric. If there are any errors reported this may provide some clues as to the cause. There is an Add-in that will help detect and delete “bad” records such as bad line points. You can get that from here, and it includes documentation on how to use and what it does. Select the 600 parcels and run the Regenerate command. (If you are using a pre-10.3 release you’ll need to add this command via Customize-> Customize Mode, click on the Commands tab, type “Regen” in the search text box, then drag the command from the list onto the Parcel Editor toolbar.) -Tim
... View more
03-31-2015
10:58 AM
|
0
|
5
|
2320
|
|
POST
|
Jennifer, I'm not certain of your specific scenario, but you could try unjoin the parcel and then rejoin it. Another idea would be to use the Mean Points tool, if there is no line between the points. -Tim
... View more
03-04-2015
03:58 PM
|
0
|
0
|
486
|
|
POST
|
Chad, I noticed a few things that may help to resolve this. The sequence of lines from point 15 to point 2 (or 21?) should have their category set to "Origin Connection". On the second line of the lines grid, should the From point be set to 2? The first line in the grid goes from 1 to 2, but then it does not look like 2 is connected to another boundary line. The boundary lines should form a closed loop, and the other lines would be marked as "connection", or "origin connection" lines. You could change these categories in the construction after you've pasted the lines. The difference between Origin connection lines and Connection lines, is that the origin connection lines are entered first, starting at a commencement point, with bearings headed towards the parcel's point of beginning, whereas connection lines are added after the boundary loop has been formed, they are added with bearings that are in a direction away from the parcel boundary point. Also, note that once the parcel has been entered, it may still need to be joined/connected to the rest of the fabric. There can be rotation on the parcel, prior to joining, because it may have a different basis of bearing from the existing parcel data. -Tim
... View more
03-04-2015
12:25 PM
|
0
|
0
|
554
|
|
POST
|
Jamie, we are working on an update to the Attribute Assistant so that it will work with Parcel Fabric edit events. Previously attribute assistant rules only worked on fabrics by manually running them on a parcel selection. Once these attribute assistant add-in enhancements are available, they should help you with this task. We did a demonstration of it at today's Land Records meetup, using your question as an example. If you want to take a look, the meetings are recorded; today's recording will be available in the next week or so from http://bit.ly/1BBAerr (You need to be logged in to get the recordings) Stay tuned! -Tim
... View more
02-26-2015
01:32 PM
|
0
|
0
|
600
|
|
POST
|
Jeff, I have reproduced the scenario you describe. As you demonstrate, the 2 parcels do not have rotations that are significantly different from one another, and so you should not be seeing this effect at all. (It is unrelated to the rotation tolerance I described previously.) Thank you for reporting this, and for all your work to communicate the problem. Graphics are always appreciated. It will be logged in our system as a bug, and an incident will also be logged with tech support on your behalf. I’ll investigate/research an interim solution. Thanks again, -Tim
... View more
12-11-2014
11:19 AM
|
0
|
1
|
2545
|
|
POST
|
Jeff, The compiled flag does have an influence on the weighting of lines when they are used in a fabric adjustment. First a quick overview on the accuracy category structure (see also help doc here). In general the accuracy categories are assigned hierarchically. An accuracy category (or adjustment weighting) is required at the Plan level, whereas they are optional on the parcels and on the lines. A parcel inherits it weight from the Plan, and a line inherits its weight from its parcel. However, any particular parcel can have a weight assigned to it, and that accuracy over-rides the Plan’s accuracy category, and similarly, any particular line can have a weight category assigned to it, and its accuracy over-rides the parcel’s (and plan’s) accuracy category. With regards to the compiled flag, you’ll notice that it is set at the parcel level only. It is the equivalent of setting the accuracy on the parcel to accuracy category 5, but it only comes into play if the parcel accuracy has not been explicitly set. For example, if the parcel accuracy category has been set to category 3, then the parcel accuracy is assigned that value of 3, regardless of whether or not it has been flagged as compiled. So the compiled flag serves a dual role of: indicating that one or more lines of the parcel have been calculated/derived from other sources assigning the parcel an accuracy category of 5, but only if the accuracy category on the parcel has not been explicitly set Hope this helps. (Apologies for the delayed response.) -Tim
... View more
12-09-2014
04:13 PM
|
0
|
1
|
697
|
|
POST
|
Jeff, This can happen when the parent parcel and the new parcel have different rotations (or scales). I suspect that you may be running into the conundrum/decision of whether to: copy the exact record values from the original lines from both parcels when creating the new remainder’s lines, thereby forgoing good misclose or recomputing the record values using a consistent scale rotation for the new Remainder parcel The approach you choose is not really a decision that is made on an edit by edit basis, but rather a general approach, and may be based on how much of a rotation difference there is between the two original parcels, before using the one approach over the other. For more specifics, and for info on how to make this choice via a fabric property, please see the documentation that comes with the Add-in called Extended Fabric Properties. After installing the Add-in, start ArcMap or ArcCatalog, right-click the fabric in the Catalog window, then click Extended Fabric Properties. To access the documentation, click the question mark button in the dialog title bar, then click the Minimum rotation tolerance entry field for the information. -Tim
... View more
12-05-2014
12:59 PM
|
0
|
3
|
2545
|
|
POST
|
The Stated Area field is populated when the parcel has a misclose ratio of better than 1:5000. If the field is empty, like when there’s a new parcel, or if you intentionally remove the string, then the system will compute an area for you and enter the string based on the record values on the lines; it’ll use the plan’s area unit to compute it and will then add the suffix such as “sq.ft”. If the field already has a string value in it then that value is left alone and the value will not be overwritten. The reason for the misclose ratio limit is that since the area is computed based on the record distances and bearings, if there is a large misclose indicating an incorrectly entered record distance or bearing, then the calculated area is also going to be incorrect. The stated field is considered by the fabric to be record information, and so you can overwrite the string and type, for example, “10 Acres” or whatever else is stated on the legal record. As mentioned before, any string found in this field will not be overwritten automatically by the Parcel Editor. If you want the Parcel editor to re-calculate the area, then you need to first remove the string in this field, then make the change to the record value and save the parcel again. If you’d like to change the ratio limit of 1:5000, you can do this by adding a registry key as follows: Run regedit.exe (for example by typing it into the entry field after you click the windows Start button) Navigate to HKEY_CURRENT_USER\Software\ESRI\Desktop10.2\ArcMap\Cadastral Enter a new string value called “HighAreaMiscloseRatio” and give it a value less than 5000, example 500 (representing 1:500) -Tim
... View more
12-04-2014
12:05 PM
|
2
|
10
|
2545
|
|
POST
|
Hi Jeff, The plan would show up in the unjoined parcels list if it contains an historic parcel that is unjoined, and the historic parcel has been filtered out from the Parcel explorer tree-view. You can turn on viewing the historic parcels by right-clicking the white-space in the parcel explorer window and checking on the option that says "View Historic Parcels" We're planning to update the software at the 10.3 release for the parcel explorer in the way that it handles historic parcel filtering, so that we can avoid this confusion in the future. Thanks for reporting the problem! On your other question, the only valid reason that I'm aware of for the check-box to be disabled and checked on, is if the parcel is already unjoined. If you are seeing that the check-box is checked on and disabled for joined parcels, then please contact tech support, as that would be a software defect that needs to be fixed. Thanks, -Tim
... View more
05-29-2014
11:56 AM
|
0
|
0
|
602
|
|
POST
|
Hi, There are counties in Oregon and Washington that are using the parcel fabric. Please contact the Olympia Regional Office for more info. I'll also let the relevant folks at the regional office know to expect your call, and I can help as needed with any further questions that you may have. (I'm also in Olympia.) Thanks, -Tim
... View more
05-28-2014
08:07 PM
|
0
|
0
|
366
|
|
POST
|
Hi Ryan, When in the construction environment you�??re working with line-work prior to actually creating the parcels. This environment is usually best used when pre-defining the line-work for multiple parcels at once, in a subdivision, for example. The parcels are only present after you�??re done with defining the lines, and after you click Build; this is why you are not able to attribute individual parcels--they are not present yet. Since the construction is a network of lines, there is no single misclosure. In the other case where you are creating a single parcel, the attributes can be defined immediately, and the closure can be reported right away. This is because the parcel lines can (should) immediately form a single sequence of boundary lines to create a closed loop. (The exception being if it�??s defined as an unclosed parcel.) -Tim
... View more
03-17-2014
03:46 PM
|
0
|
0
|
802
|
|
POST
|
JS, If you don't get an answer from this Land Records forum, you could also try the cartography forum, or the map automation forum. -Tim
... View more
03-03-2014
08:49 AM
|
0
|
0
|
315
|
|
POST
|
Hi Christina, Here are few things to note and to check. Note: When you are zoomed in to a scale greater than 1:1, and the extent of your whole map measures in the 1/100ths of a foot, then you may see this effect: the cartography is not optimized for these highly zoomed in views, especially as your map extents begin to approach the XY tolerance of the feature dataset. This value defaults to 0.001m. There�??s a good help topic on the resolution and xy tolerance; you should not need to change these default numbers. Check 1: An important test is to figure out whether or not the geometry operations of GP tools and of the other tools in ArcMap detect any difference/gap. These geometry functions should see these lines as being the same. For example, one test in this case would be to do a select by location, starting by selecting one of the parcels that have the curve, then attempt to select the curved lines based on the �??share a line segment�?� option, as indicated in this graphic: [ATTACH=CONFIG]30056[/ATTACH] If both curved lines are selected after this, then the system identified them as equivalent, and the result is as expected. Check 2: Take a look at the attributes for each of the curves in question. Do they have different radius attribute values? Also find the radial point location for these curves. (the point at the center of the curve) Does each curve have its own radial point? If the attributed radius for each curve is the same, these radial points need to be merged into a single point that is shared by both the circular arc curves. After merging the radial points re-run the fabric adjustment. Check 3: There�??s a tool under the customize environment called Regenerate Fabric that you can use on selected parcels or on the whole fabric (whole fabric if there is no selection.) This tool will let you update the fabric geometry based on the point positions. See the graphic below on info about how to get it: drag the tool onto a toolbar, close the customize dialog, select the parcel, then click this button: [ATTACH=CONFIG]30057[/ATTACH] See also the last paragraph in this help topic. Regenerate may not change anything if, for example, the Check 2 test passes the line equivalence test. -Tim
... View more
12-20-2013
05:56 PM
|
0
|
0
|
990
|
|
POST
|
Hi Brandon, We fixed a bug at 10.1 that addressed a problem like the one you describe. This fix is also available on the latest service pack 5 for 10.0. If you are using ArcGIS Desktop 10.0 sp5 or later, and you'd created the topology while using 10.0 sp5 or later, then it is not the same issue, and we'll need to get more information to learn why it's happening. Please contact tech support if the problem persists. Thanks, -Tim
... View more
12-19-2013
07:50 PM
|
0
|
0
|
675
|
|
POST
|
Hi Ryan, There is this Add-in that gives some extended abilities to help you remove inconsistent records such as these. It includes a tool that lets you drag a box around the orphan points to delete them, and a utility accessed via the fabric context menu, that reports and optionally removes inconsistent records for the whole fabric. See also this thread about orphan points. Regarding your question about LGIM not showing features: you may need to calculate the Type for the particular parcel layer. For example, the Tax Parcels layer has the following definition query: (SystemEndDate IS NULL) AND ("Type" = 7) To make them appear, drag a new instance of the fabric's parcel class onto the map from the catalog window, start editing, and select the parcels that are to become tax parcels. Use the field calculator and assign the Type = 7 on the selection, then save your edits. You can then remove the extra instance of the layer you added, and those Tax parcels should now appear in LGIM fabric. Another approach would be to temporarily remove the definition query on the Tax parcels layer, make the same edit, and then set the definition query on the layer back to (SystemEndDate IS NULL) AND ("Type" = 7) -Tim
... View more
11-22-2013
01:13 PM
|
0
|
0
|
986
|
| 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 |
Monday
|