Latest Contributions by RyanKelso

‎07-18-2014

First of all, I don't know if this is the right place to make a post in this new GeoNet... Anyways, ever since I updated to 10.2.2 I've noticed the Breakline tool in the parcel fabric editor sometimes not working correctly. The problem doesn't always happen, and I haven't been able to figure out how to reliably duplicate it. What happens is, the distance I enter into the Breakline dialog is not the distance that the break point gets added at. I think these attached screenshots illustrate it pretty clearly. Anybody else running 10.2.2 seeing this?

‎06-18-2014

Some fields in the parcel fabric are flagged as non-editable or read-only, and some are not. If you look at the properties of the Z field in the Control attribute table, you can see that Make field read only is checked, and we are not allowed to change this for some reason. I'd certainly want to do what you're trying to do, so I find this an odd restriction. If a parcel fabric field is not flagged as read-only, such as SurveyDate, then you can use Field Calculator. My idea for a work around... Export the control points to a regular feature class or shapefile. Do the join and field calculation as you were trying to do. Import the control points from this feature class or shapefile and set the import up so the imported control points will be merged with the existing control points, and in the process update the Z using the imported control point data.

‎03-31-2014

I ran into this a couple of weeks ago. I think you need to edit your parcel fabric's accuracy table, which I'm guessing is currently empty. In an edit session, run the Make Parcel Fabric Table View tool in the Parcel Fabric Tools toolbox > Layers and Table Views toolset. In the tool's dialog, change "Select Parcel Fabric Table" to Accuracy. Then you have a table to open and add accuracy categories to. I opened the tax parcel editing map template with the Bloomfield Township, MI sample data and just copied the values from that database's accuracy table. Viewing and editing the parcel fabric Accuracy table About accuracy in the parcel fabric -Ryan

‎03-21-2014

Hmm, I tried doing what you're describing and didn't have trouble creating a join link between a control point and the beginning point of an Origin Connection to POB line. It even populated the Associated Network PointID on the control point. The only time I could get that error you mentioned to pop up was trying to create a link on the POB connector line (a line point) to the control point. If you join the parcel without any links and it's placed in the right spot, you could then match the control point to the parcel point. I wouldn't think there is anything wrong with that, but hopefully one of the esri folks or anyone with more experience with this than I will chime in here. Sorry I couldn't be more helpful!

‎03-20-2014

Hi Jeff. That error is what pops up if you try to create a join link on a curve, which isn't allowed. If you try to create a link between two regular boundary points, does that work? If you constructed your parcel in its correct space but joined it without any links, then it's probably just floating there without being topologically connected to the surrounding parcels, albeit in the right place. So you'll want to rejoin it and establish the links. Also, after choosing Append File... if you just click Close, the parcel will come in as unjoined if that's ever something you'd want to do.

‎03-18-2014

Thanks for that info, Tim. I'll admit that it took me a while to understand the difference between the construction environment (multiple parcels) and creating a single new parcel. But this explanation sort of just echos what I was wondering about in the first place: that when creating a single new parcel, the Breakline, Planarize Lines, and Create Parallel Offset tools can't be used. They are only available with the construction environment. It seems like they should be available when creating a single new parcel as well, I thought it could be a bug or something rather than designed behavior. For example, I was creating a single new right-of-way parcel. I had an engineer's ROW plan that used multiple centerlines, stationing, and L/R offsets rather than metes and bounds. It was a complex construction and I didn't realize at first that these tools I've mentioned weren't available in this environment. They would have made it easier. And it would be nice to retain the ability to define attributes immediately.

‎03-18-2014

In case anybody else encounters this issue, there is a bug where a parcel's rotation value is not being applied to a line string. The workaround is to use multiple regular two-point lines instead of line strings, but hopefully this will be fixed soon as line strings are ideal for natural boundaries.

‎03-07-2014

When I create new parcels in my parcel fabric, I usually just click the New Parcel button on the Parcel Editor toolbar. From there I can change the plan or template if I need to. The problem is, using this method, the Planarize Lines, Breakline, and Create Parallel Offset tools aren't available. These tools are extremely useful when creating a new parcel!! The other way to create a new parcel is to open the Plan Directory, right-click a plan, and click Construction. Now this method allows me to use Planarize, Breakline, and Create Parallel Offset, hooray. But there are a new set of problems with this method. I can't set the properties of the parcel before it gets built, can't view the misclose or any other closure information, the Parallel Line and Centerline Offset tools become unavailable. Is it supposed to work this way or am I experiencing some unusual behavior with the tools? If this is working as intended... yikes... I'd like to hear an explanation that might help my understanding of using these tools. The inconsistencies between New Parcel and New Construction are both confusing and frustrating.

‎02-28-2014

Interesting, by snapping do you mean digitizing? If you simply digitized, I would agree with you that you shouldn't see mis-close for the resulting parcels. Can you submit a incident for this and submit the parent parcel as a Cadastral XML? Chris Yes, I was digitizing the river centerline/natural boundary as a line-string, snapping from the last segment added via the construction grid back to the point of beginning. Upon creation, the parcel has no mis-close, but it appears to me that when a parcel has a rotation value and a line-string, opening the parcel somehow distorts the line-string thus "breaking" the closure. I submitted an incident before you replied here, but I will make sure to add a cadastral XML.

‎02-25-2014

Well, I am trying to build a completely new parcel after deleting the inaccurate one, in this case the basis of bearing tool can't be used (it's grayed out). The survey I have uses true north, my coordinate system uses grid north, there is a rotation I can't account for when constructing a new parcel and trying to digitize the natural boundary with a line string off an ortho photo projected in my map. I tried creating a new parent parcel (a quarter-quarter section) and then constructing from parent so I could use the basis of bearing tool. I constructed new lines from the survey then digitized the natural boundary with a line string, using snapping so the parcel's closure was perfect. Everything looked good when I built the new parcel, but when I open it, there is a misclose. Not sure what is going on there. Ryan

‎02-24-2014

I'm using parcel fabric (10.1) and I've got a parcel with very poor accuracy that has a natural boundary (river). I'd like to delete it and construct a new parcel to replace it. The problem with this is, the survey has a basis of bearing which you can't apply when building a new parcel. So if I enter the lines off the survey then digitize the river boundary off an ortho as a line string, the river boundary gets improperly rotated when I rotate the parcel during the join process. This is obviously not the right way to do this, what would be a better way?

‎02-21-2014

I gave this a try (in 10.1) and Analyze Differences for me came up with 63 differences. I noticed that the vast majority of the differences were apostrophes being translated as spaces. Annoying but not a critical issue. Did you check if the "missing fields" were actually missing? Those fields you mentioned were there for me. Most of the remaining differences were: Dataset Property: ControllerMemberships="BuildingInteriorSpace_Topology 5 1 1 false" vs. "". I have no clue what that is. Two of the differences, Dataset Property: Height="1" vs. "4567" and Dataset Property: Width="1" vs. "6661" for Hillshade, are simply from exporting schema only. I agree that XRay should be able to do a better job of minimizing differences between exported/imported schemas, even if some of the differences are trivial.

‎02-21-2014

I noticed this too. jmward made a post a couple of days ago about how importing the LGIM schema into a new geodatabase turns out a large number of differences when you "Analyze Differences" between the new and old GDB with XRay. When I imported LGIM schema with XRay and ran the differences tool myself, I also had a large number of differences but I noticed that the vast majority of them are simply missing apostrophes. I tried exporting and importing an XML workspace document using geoprocessing tools rather than XRay and it did transfer the apostrophes correctly this way, but this doesn't allow you to change the spatial reference.

‎02-20-2014

Thanks for your reply, Chris. I'm interested in your thought about not maintaining anything in the fabric that isn't a true representation of the legal record, since that is basically everything for us. Gotta start somewhere. I do like your suggestions. Could you elaborate a little on your reasoning for this? For one thing, it seems to me that the parcel fabric editing tools are just not very well suited for the kinds of edits I described in the original post. Our tax parcels are also approximations of the legal record, some are pretty close and others not so much. As we are preparing to switch to parcel fabric, my testing strategy has been to recreate tax parcels using the recorded information as needed for further maintenance, and to move (join) existing points to the more accurate ones. You mentioned subdivisions; I have them but the data is even less reliable so I don't plan on importing them to the fabric. Ryan

‎02-19-2014

I'm glad you got the editing workflows functioning, I ran into a similar problem and was trying to remember what I had to do. I think, when trying to use the TaxParcelEditingMap.mxd template, I had to remove all of the parcel fabric layers from the map, enable the information model in the catalog window, then drag the fabric back into the map. Then the workflows functioned.

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by RyanKelso

Breakline not working correctly?

Re: Using the field calculator

Re: Accuracy Domain for Plans

Re: Append Cadastral XML file to parcel fabric

Re: Append Cadastral XML file to parcel fabric

Re: Using Breakline and Planarize Line to construct new parcels

Re: Construct a new parcel with a natural boundary

Using Breakline and Planarize Line to construct new parcels

Re: Construct a new parcel with a natural boundary

Re: Construct a new parcel with a natural boundary

Construct a new parcel with a natural boundary

Re: XRay for ArcCatalog shows 43 differences when "Analyze Differences" tool is run.

Re: X-Ray for ArcCatalog turning apostrophes into spaces

Re: Workflow for editing Right of Way in parcel fabric

Re: Enable Information Model and Parcel Workflows

Re: Expressions Not Being Honored By The Append To...

Re: Delete Features - Reset OBJECTID?

Re: Manage tile cache, anti-aliasing

Manage tile cache, anti-aliasing

Re: Cached map service without Server access to da...

Web AppBuilder Custom Widgets