Latest Contributions by ChristineLeslie

Right-click the Lots and Units layer, click Properties to open the Layer Properties dialog box and go to the Symbology tab. Click Add Values - the custom type should show up in the Add Values dialog box... When you click it and click OK, it should appear as a new symbol under the symbol list. Does that work? Christine ... View more

You can run a topology directly on the parcel fabric feature classes as well, without the need to export them to feature classes. But to fix the errors, you do need open up the parcels or rejoin them. http://resources.arcgis.com/en/help/main/10.1/#/Creating_a_new_topology_with_a_parcel_fabric/008500000009000000/ ... View more

Hi There are actually two boundary lines for a common boundary in the parcel fabric - one line for each parcel. Common boundary lines are never represented as a single boundary line in the parcel fabric. To get rid of a boundary point, you do have to open each parcel, delete the two boundaries split by the point you want to get rid of and re-create the boundary as a single line without the point. The reason you do it this way so that the COGO dimensions on the boundaries do not fall out of sync with the geometry of the lines. Any change in line geometry should be reflected in the COGO dimensions of the lines. Hope this helps Christine ... View more

You are correct, if you have modified your lines using the C&L tool, you may want to regenereate the polygons from the lines so that they match correctly, with the correct curves. You can use the Integrate geoprocessing tool to enforce coincidence between boundaries - this should help you line up your overlapping boundaries better and minimize topology errors. Christine ... View more

Hi Chris When you did Construct from Parent, did you add a straight, split line between the end points of the curve, ie between points 2 and 3, then built the parcels and nothing happened? Right now it looks like the software thinks the two lines are the same, and are overlapping. It doesnt understand that the curve between points 2 and 3 is different from the straight, split line that is added between points 2 and 3. This is a bug. To get around this, you have to add two straight lines between points 2 and 3, then build. During the build process it will merge these two straight lines and you should get two parcels. One parcel being the corner clip. Is this what you were trying to do? Christine Parcel Editing team ... View more

I feel I should also add that you are really only limited to 6 categories as the 7th category is an "exclude" category - lines/parcels with the 7th category do not influence the outcome of the adjustment but will still move with connected points. Also when editing ppm values (which should only be done by those people who thoroughly understand these numbers and how they are used), they still should reflect the accuracy level and be in an order of highest to lowest - ie ppm/std dev values for accuracy 3 should not be higher than those for accuracy 1. Christine ... View more

Hi Dan Just FYI, you can edit the ppm and standard deviation values in the Accuracy table. YOu are limited to 7 categories, but you are not limited to the values you can use. If you edit the ppm and std deviation values, the LSA will use them instead of the defaults. Use the Make Parcel Fabric Table View GP tool to view and edit the Accuracy table Christine ... View more

If a standard feature class such as a zoning polygon is associated with the fabric - the idea is that if the fabric is adjusted to control using the fabric least-squares adjustment, the zoning polygon can receive those adjustments as well (afterwards) and remain in sync with the fabric. When the fabric is adjusted to control, the coordinate changes are saved as vectors. The vectors are then used in a feature adjustment to adjust any associated feature classes. So the vectors stored from the fabric least-squares adjustment are used in a rubbersheeting process to adjust overlaying feature classes (similar to the spatial adjustment functionality.) Christine Parcel Editing team ... View more

Hi You can import more than one traverse txt file at a time. See this help link: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Importing_traverse_files/001t0000012p000000/ "To import more than one traverse file, hold the SHIFT key down and select the traverse files you want to import. When more than one traverse file is selected, parcels are imported as a parcel group" Hope this helps Christine Parcel Editing team ... View more

Below is a sample of code that will export the selected fabric parcels sublayer to a feature class. In this solution, a form comes up prompting the user for the name of the output feature class. This was written quite a while ago, so you may not need to unlock fields like this code does. Hope this helps Christine private void btnOK_Click(object sender, EventArgs e)         {             m_App = (IApplication)m_FMxApp;             m_MxDoc = (IMxDocument )m_App.Document;             m_FeatLayer = (IFeatureLayer)m_MxDoc.SelectedLayer;             m_Layer2 = (ILayer)m_FeatLayer;             m_FeatSel = (IFeatureSelection)m_Layer2;             m_Map = m_MxDoc.FocusMap;             for (int i = 0; i <= m_Map.LayerCount - 1; i++)             {                 m_Layer = m_Map.get_Layer(i);                 if (m_Layer is ICadastralFabricLayer)                 {                     m_FabricLayer = (ICadastralFabricLayer)m_Layer;                     m_Featlayer2 = m_FabricLayer.get_CadastralSubLayer(esriCadastralFabricRenderer.esriCFRParcels);                     if (m_Featlayer2 == m_FeatLayer)                     {                         IFieldsEdit m_OutputFields = new FieldsClass();                         m_cadfabric = m_FabricLayer.CadastralFabric;                         //get parcels table                         m_FabricParcelsTable = m_cadfabric.get_CadastralTable(esriCadastralFabricTable.esriCFTParcels);                         //get parcels feature class info                         m_FeatClass = (IFeatureClass)m_FabricParcelsTable;                         string shpName = m_FeatClass.ShapeFieldName;                         long ShpFld = m_FeatClass.FindField(shpName);                         m_Dataset = (IDataset)m_FeatClass;                         m_FCName  = m_Dataset.FullName;                         //clone parcel table fields                         m_fields = m_FabricParcelsTable.Fields;                         long FldCnt = m_fields.FieldCount;                         for (long j = 0; j <= FldCnt-1; j++)                         {                             m_Field = m_fields.get_Field (System.Convert.ToInt32 (j));                             if (j == ShpFld)                             {                                 m_GeomDef = m_Field.GeometryDef;                                 m_GeomDefEdit = (IGeometryDefEdit)m_GeomDef;                             }                             //clone the field                             m_CloneFld = (IClone)m_Field;                             m_OutClone = m_CloneFld.Clone();                             m_FldEdit = (IFieldEdit)m_OutClone;                             if (j != ShpFld)                             {                                 m_FldEdit.Required_2 = false;                                 m_FldEdit.DomainFixed_2 = false;                             }                             m_OutputFields.AddField(m_FldEdit);                                                     }                                               //create new feature class                         m_FeatClName = new FeatureClassNameClass();                         m_FDatasetName = new FeatureDatasetNameClass();                                                m_dataset3 = (IDataset)m_WS2;                         m_OutWSName = m_dataset3.FullName;                         m_WSName = (IWorkspaceName)m_OutWSName;                         if (Fdataset == true) //export to feature class in feature dataset                         {                             m_FDatasetName.Name = m_dataset2.Name;                             m_FDatasetName.WorkspaceName = m_WSName;                             m_FeatClName.FeatureDatasetName = m_FDatasetName ;                             m_FeatClName.ShapeType = ESRI.ArcGIS.Geometry.esriGeometryType.esriGeometryPolygon;                             m_DatasetName = (IDatasetName)m_FeatClName;                             m_DatasetName.Name = featClassname;                                                         m_QF = new QueryFilterClass();                             IFeatureClassName m_InputFeatClassName = (IFeatureClassName)m_FCName;                             IDatasetName m_InputDSName = (IDatasetName)m_FCName;                             IFeatureDatasetName m_FeatDatasetName = (IFeatureDatasetName)m_FDatasetName;                             if (m_FeatSel.SelectionSet.Count == 0)                             {                                 m_featureConverter = new FeatureDataConverterClass();                                 m_InvObj = m_featureConverter.ConvertFeatureClass(m_InputFeatClassName, m_QF, m_FeatDatasetName, m_FeatClName, m_GeomDef, m_OutputFields, null, 0, 0);                                 frmTxt.Text = null;                                 frmExportCFPolygon.ActiveForm.Close();                             }                             else if (m_FeatSel.SelectionSet.Count != 0) //only export selected parcels                             {                                 m_featureConverter2 = new FeatureDataConverterClass();                                 m_InvObj = m_featureConverter2.ConvertFeatureClass(m_InputDSName, m_QF, m_FeatSel.SelectionSet, m_FeatDatasetName, m_FeatClName, m_GeomDef, m_OutputFields, null, 0, 0);                                 frmTxt.Text = null;                                 frmExportCFPolygon.ActiveForm.Close();                             }                         }                         else if (FStandAlone == true) //export to stand alone feature class                         {                             m_GeomDefEdit.GridCount_2  = 1;                             m_GeomDefEdit.set_GridSize(0, 0);                             m_GeomDefEdit.SpatialReference_2 = m_GeomDef.SpatialReference;                                                                                     m_FeatClName.ShapeType = ESRI.ArcGIS.Geometry.esriGeometryType.esriGeometryPolygon;                             m_DatasetName = (IDatasetName)m_FeatClName;                             m_DatasetName.Name = featClassname;                             m_DatasetName.WorkspaceName = m_WSName;                                                                                     m_QF = new QueryFilterClass();                             IFeatureClassName m_InputFeatClassName = (IFeatureClassName)m_FCName;                             IDatasetName m_InputDSName = (IDatasetName)m_FCName;                             if (m_FeatSel.SelectionSet.Count == 0)                             {                                 m_featureConverter = new FeatureDataConverterClass();                                 m_InvObj = m_featureConverter.ConvertFeatureClass(m_InputFeatClassName, m_QF, null, m_FeatClName, m_GeomDef, m_OutputFields, null, 0, 0);                                 frmTxt.Text = null;                                 frmExportCFPolygon.ActiveForm.Close();                             }                             else if (m_FeatSel.SelectionSet.Count != 0)                             {                                 m_featureConverter2 = new FeatureDataConverterClass();                                 m_InvObj = m_featureConverter2.ConvertFeatureClass(m_InputDSName, m_QF, m_FeatSel.SelectionSet, null, m_FeatClName, m_GeomDef, m_OutputFields, null, 0, 0);                                 frmTxt.Text = null;                                 frmExportCFPolygon.ActiveForm.Close();                             }                         }                                                                   }                 }             } ... View more

Hi Carlos I do have an example, -just need to dig it out, put it together and post it. I will do so shortly - keep watching this thread... PS this can be done pretty easily in python as well. Christine ... View more

Take a look at the Survey Editor documentation http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=An_overview_of_Survey_Analyst Christine ... View more

Hi Jason As Nick said, its pretty simple - you create an empty fabric, add in some control points, traverse in a parcel or a subdivision and then join it to the control point or points. Here are the steps in some more detail: 1. First you need to create your empty parcel fabric in a feature dataset. You will define a spatial reference for the feature dataset and that is what your fabric will use. 2. Load the empty fabric into the map and begin adding control points. In the attached screenshot, EmptyFabricAndPLSSLines, I have loaded some PLSS lines (feature class) as a reference and an empty fabric. 3. Next, I will enter in the coordinates of a control point. You will need control point coordinates to enter. If you dont have these, you could estimate them from PLSS corners for now and update them later. To manually enter a control point click Maintain Control Points on the Parcel Editor toolbar. See the attached AddControlPt screenshot. Control points can also be migrated in. 4. Once I added my first control point, I traversed in a single parcel. To create a new parcel, I clicked the New Parcel in New Plan button on the Parcel Editor toolbar. You can use the default <map> plan or go and create a new plan in the plan directory. Just traverse in your parcel, it doesnt matter where you start on the map, you will position/join the parcel once its complete. See the attached TraverseInParcel screenshot. 5. Once the parcel is complete, I clicked Keep Changes to Parcel Data and Join on the parcel details dialog box, and used the Join dialog to join the connection line of the parcel to the control point. See the attached JoinToControl screenshot. 6. Once you have added your first parcel, just keep on traversing in parcels and joining. Now it would be better to have more that one control point to join to for correct scale and rotation purposes. So the options are to: -Enter a larger block of parcels and then join the block to two or more control points -Bring in more control points at a later stage and run Least-squares adjustment which would take care of the scate and rotation, and have the added benefit of identifying any errors. Parcel corners can be linked to control points at any stage. Lastly, if you dont have any control points, you could simply traverse in parcels, and when you join them, simply click OK to drop/place the parcel in the map. In this case, no join links are established. You could use a background layer that can act as a reference as to where you can drop your first parcel. Later on, you can then bring in control points and run a least squares adjustment to adjust the parcels to the more accurate control network. I hope this helps Christine Parcel Editing team ... View more

The other thing you could do is to run the Integrate GP tool before migration to the fabric: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Integrate/00170000002s000000/ "Integrate is used to maintain the integrity of shared feature boundaries by making features coincident if they fall within the specified x,y tolerance. Features that fall within the specified x,y tolerance are considered identical or coincident" Hope this helps Christine Parcel Editing team ... View more