Exercise 8: Making versioned edits as a read/write user

This topic applies to ArcEditor and ArcInfo only.

Complexity: Beginner Data Requirement: ArcGIS Tutorial Data Setup Goal: Log in as a read/write user, connect to a version other than the default version, and edit versioned data.

To see another way users with nonadministrative permissions can edit the data, you will log in as editor1, edit a feature class in ArcMap, then reconcile and post the edits to the edit version.

Logging in as editor1

Log off the computer and log back in as editor1.

Steps:

1. Click the Start button on the Windows task bar and click Log off.
2. If prompted, confirm you want to log off by clicking Log Off on the Log Off Windows dialog box.
3. When the login dialog box appears, change the user name to editor1.
4. Choose your computer name from the Log on to drop-down list and click OK.

   You are now logged in to the computer as editor1.

5. Start ArcMap, open the Catalog window, then expand the Database Servers node in the Catalog tree.

Connecting to a different version and saving the connection

By default, database server connections are always to the DEFAULT version. To change which version of a geodatabase you are connected to, you will use the Change Version dialog box. If you were to close ArcMap, the next time you started ArcMap and connected to the geodatabase through the database server node, you would again be connected to the DEFAULT version.

To save your connection to a specific version, you can save a spatial database connection to this version. This creates a connection file under the Database Connections node in the Catalog tree.

Database connections save the connection properties you assign until you change them. That means the next time you start ArcMap as editor1, you will still have a connection to the version of the geodatabase you want without having to change any settings.

Note:

Connections made to geodatabases through the Database Connections node are not used for administration, only for data access.

Steps:

1. Double-click the database server in the Catalog window to connect to it.
2. Right-click the Osokopf geodatabase and click Change Version.
3. Make sure Version type is set toTransactional.
4. Choose the railroadv1 version and click OK.

   The connection for the Osokopf geodatabase now shows you are connected to railroadv1.

5. To save the connection to this version of the geodatabase, right-click the Osokopf geodatabase and click Save Connection.

   This creates a connection file for this version of the geodatabase under the Database Connections node.

6. Expand the Database Connections node in the Catalog window.

   You can see a new connection has been created to the geodatabase. The default connection name is Connection to <machine_name>_<sql_server_express_instance>.

   Tip:

   You can change the name of the connection by right-clicking the connection, clicking Rename, then typing a new name.

7. Right-click this connection and click Connection Properties.

   As you can see, all the connection information has been completed for you. Server name is populated, the direct connection information is in the Service text box (geodatabases on database servers do not use ArcSDE services, only direct connections can be used), the database name is in the Database text box, operating system authentication is chosen for the authentication mode, and the connection is being made to the railroadv1 transactional version of the geodatabase.

8. Close the Spatial Database Connection Properties dialog box.

Making edits to a versioned dataset

In Exercise 7 Connect as a geodatabase administrator, load data, register it as versioned, and create a version, manager1 imported a feature class, railroads, and registered it as versioned. You are going to edit that feature class in the railroadv1 version.

Preparing to edit

Add the versioned dataset and reference data to ArcMap.

Steps:

1. Expand the new connection to the Osokopf geodatabase.
2. Click and drag the railroad feature class into ArcMap.
3. For reference, add the streets and villages feature classes and the park_areas feature dataset to the map.
4. Expand the buildings geodatabase on the database server and drag the gov_bldgs, schools, and utilities feature classes onto the map for reference as well.

To help orient yourself on the map, you will label the streets feature class.

Steps:

1. Right-click the Streets layer in the ArcMap table of contents and click Label Features.

   The names of streets for which a name attribute exist are drawn on the map.

Since the data you will edit is registered as versioned, be sure ArcMap is set to perform versioned edits.

Steps:

1. Click Editor on the Editor toolbar and click Options on the drop-down list.

   This opens the Editing Options dialog box.

2. Click the Versioning tab.
3. Be sure the Edit a version of the database with the ability to undo and redo box is checked. If not, check it.
There are other options on this dialog box you can set to control the behavior of a versioned edit session. These include setting which sorts of edits can be considered conflicts, which edits to use during auto-reconciliation, and whether to automatically save edits after auto-reconciliation. For more information on these options, see A quick tour of reconciling a version.



4. You will use the default settings, so click OK to close the Editing Options dialog box.

Now start an edit session.

Steps:

1. Click Editor on the Editor toolbar and click Start Editing.
2. Choose Railroads from the list of layers to edit and click OK.

Performing edits

You will add one new rail line and one side rail to the railroads feature class. You will also extend an existing side rail.

Add a rail line

Steps:

1. Click the Zoom In button on the ArcMap Tools toolbar.
2. Hold down the mouse button and draw a box around the north-eastern portion of the island.

   

The section of rail line you will add starts at the existing Cross Island line between Serpent and Sandpiper streets, east of Pilot street, and ends at the tip of the existing Centremont East line.

Tip:

To identify features on the map, click the Identify button on the ArcMap Tools toolbar and click a feature. This opens the Identify window, which shows the attributes of the feature.



3. Click Railroads in the Create Features window.
4. Click Line under the Construction Tools.
5. Pause the pointer on the Cross Island line between Serpent and Sandpiper until you see you are on the edge of the railroad line.

   

6. Right-click, click Snap to Feature, then click Edge.

   This snaps the first vertex of the new line to the edge of the Cross Island line.

7. Extend the line between Dock and Sandpiper until you reach the end of the Centremont East line.

   

8. Right-click, click Snap to Feature, then click Endpoint to place an end vertex for your new feature.
9. Right-click and click Finish Sketch to add the new feature to the railroads feature class.

   

10. Click Editor on the Editor toolbar and click Save Edits to save the changes you have made so far.
11. Click the Attributes button on the Editor toolbar.

    The Attributes dialog box opens.

12. Click in the field next to Owner and type Oso Rail.
13. Close the attribute window.

Add a side rail

Change your extent by panning to the area where the next feature will be added.

Steps:

1. Click the Pan button on the ArcMap Tools toolbar.

   Your cursor changes to the pan symbol.

2. Click in the center of the map, hold down the mouse button, and pull the map down until both the College Sports Park and the sewage treatment plant are visible.

   

You will add a new side rail on the Cross Island line, east of Serpent.



3. Click railroad in the Create Feature window and click line.
4. Pause the pointer on the Cross Island rail line in the location indicated in the previous graphic until you are over the railroad edge.
5. Right-click, click Snap to Feature, then click Edge.
6. Draw a curved line that tends toward the north-east. Click to add vertices to create the curve.

   

7. Double-click the end vertex to finish the sketch.
Note:

For the purpose of this tutorial, edits do not have to be exact. When you edit your own data, you will be much more precise when adding features.

8. Click the Attributes button on the Editor toolbar.
9. Type Oso Rail in the field next to Owner.
10. Click Editor on the Editor toolbar and click Save Edits to save the changes you have made so far.

Extend the Cross Island college side rail

The college side rail should be visible in your current extent. If it is not, pan to it.

You are going to extend this line.

Steps:

1. Click the Edit Tool button on the Editor toolbar.
2. Click the Cross Island college side rail to select it.
3. Click the Edit Vertices button on the Editor toolbar.

   The vertices of the college side rail are visible on the map.

4. Right-click the college side rail line just before the end vertex and click Insert Vertex.
5. Pause the pointer on the end vertex until handles appear around the vertex.

   

6. Click and drag the vertex until it is closer to Morris Street.

   

7. Right-click and click Finish Sketch.
8. Click Editor on the Editor toolbar and click Save Edits to save the changes you have made so far.

Reconciling edits and posting changes

You have finished the edits you will do on the railroads feature class. Now you will reconcile and post your edits to the DEFAULT version.

Steps:

1. Open the Versioning toolbar if it is not already open. Click Customize, point to Toolbars, then click Versioning. (You may need to scroll down the menu to see Versioning.)
2. Click the Reconcile button on the Versioning toolbar.

   The Reconcile dialog box opens.

The dbo.DEFAULT version is already chosen as the target version, so you do not need to choose a target version. You will also use the default setting for defining conflicts, so leave By object (by row) selected. However, you will change how conflicts are resolved.
3. Click In favor of the Edit Version on the Reconcile dialog box.
4. Click OK.
No other users were editing this data in the DEFAULT version, so no conflicts were detected. This is a common result, especially when you are using geodatabases on a database server. It is uncommon for other users to be editing the same features (rows) in the same feature class as you. If you choose to define conflicts based on attributes (columns), you might be more likely to see conflicts. However, even if conflicts are based on attribute changes, conflicts still only occur if someone is editing the same feature class as you.

Since you did not encounter any conflicts, you can now post your changes to the DEFAULT version.

5. Click the Post button on the Versioning toolbar.

   Your edits are moved into the DEFAULT version. Now, anyone who connects to the DEFAULT version can see your changes.

6. Click Editor on the Editor toolbar and click Stop editing.

You logged in with a login that has read and write access to the geodatabase and performed a set of versioned edits on a feature class. You then reconciled and posted your edits to the DEFAULT version of the geodatabase.