Parcel Fabric Control Points moved?

[MichaelSnook]

I've scoured the docs and can't find any answer to this. 

It appears that our imported control points have moved to the location of their corresponding fabric point.  Is this expected behavior?  What's more strange is that when I have the 'Maintain Control Points' dialog open, I can highlight the control point in question, which flashes its location...but...it's flashing where it was originally.  This, among other things, has me worried about what the control points are doing in the fabric.  Has anyone else seen this or have any insights?

Thanks,

Mike

see attachement for illustration.
[ATTACH=CONFIG]28025[/ATTACH]

[TimHodson]

Hi Mike,

What is the distance between the coordinate position and the geometry's position? Is the distance close to the XY tolerance for stored geometry as described in this help topic called The properties of a spatial reference ?

If this distance is small, and you are zoomed way in, then the XY tolerance may explain what you are seeing.

Also, is the parcel fabric in a geographic coordinate system, and you're projecting on the fly using the map's data frame; or is the fabric's spatial reference a projected coordinate system, and the same as the map's projected coordinate system?

Thanks,
-Tim

[TOMKONG]

I've scoured the docs and can't find any answer to this. 

It appears that our imported control points have moved to the location of their corresponding fabric point.  Is this expected behavior?  What's more strange is that when I have the 'Maintain Control Points' dialog open, I can highlight the control point in question, which flashes its location...but...it's flashing where it was originally.  This, among other things, has me worried about what the control points are doing in the fabric.  Has anyone else seen this or have any insights?

Thanks,

Mike

see attachement for illustration.
[ATTACH=CONFIG]28025[/ATTACH]

It's common issue. That two feature classes should be in the different resolution setting value, and when you import that shapfile with higher resolution value to your fabric dataset with lower resolution grid setting, some of their locations should be moved from original spot.
You should check if that fabric dataset resolution and tolerance setting fit your application, if the answer is yes, you don't need to consider these changes. If not, you should increase your fabric dataset resolution/tolerance setting value, then import that shapfile.

[MichaelSnook]

Hi Mike,
What is the distance between the coordinate position and the geometry's position?

If this distance is small, and you are zoomed way in, then the XY tolerance may explain what you are seeing.

Also, is the parcel fabric in a geographic coordinate system, and you're projecting on the fly using the map's data frame; or is the fabric's spatial reference a projected coordinate system, and the same as the map's projected coordinate system?

Tim,

The distance in this particular case is a bit under 5 feet from the original to the fabric control point...this varies across the fabric but the distances are much greater than the tolerance.  Also, what I've noticed, this seems to only occur with associated control/fabric points...not un-associated ones.

The fabric is in Montana State Plane 2500...no on-the-fly projection.

Thanks

[TimHodson]

Mike,

This is not something that I've heard reported before. I�??ve tried a few things that might explain what you�??re seeing, but nothing I�??ve done so far gives me the same results that you see. Note, that in terms of the fabric data, the parcel editing environment will always use the control point attributes over its geometry, but the control point geometry and fabric point geometry should still match their respective attributed coordinate locations.

Another possible scenario that would only partially explain what you're seeing is that your original import source data itself has this same 5ft discrepancy between its geometry and it's X/Y coordinate. In this scenario the control importer honors the source XY attributes and would not match the original geometry position of the source data, unless you checked the option on the control importer to use the shape field.
[ATTACH=CONFIG]28104[/ATTACH]

For your data, what happens if you make a temporary small edit (0.01ft change to one of the coordinates) to the control point, (using the Maintain Control Points dialog) save the edit, and then re-edit the control point back to its original value? Do those edits move the control point to the entered attribute position?

If none of this addresses or explains your case, please contact tech support to help us better understand what you are seeing. If there are any other readers of this forum that have experienced similar, please respond on this thread and also contact tech support referencing this post so that we can identify patterns and symptoms.

Thanks,
-Tim