Help

Edits with DNC NIS data

The NIS is a centralized data storage repository, which means that once all the appropriate data is compiled or loaded to the NIS, it's stored and maintained there. Libraries can then be extracted directly from the NIS using the Checkout DNC Replica tool. This tool allows you to edit a subset of data in a file geodatabase child replica. When using an enterprise geodatabase for your production environment, your editing workflow will consist of the following:

  1. Load source data.
  2. Create an edit version of the NIS.
  3. Checkout DNC replica.
  4. Edit data.
  5. Perform quality control and verify if necessary.
  6. Synchronize changes to the edit version of the NIS.
  7. Reconcile and resolve conflicts.
  8. Post changes to default.

Fundamentals of working with one scale

Guidelines for editing one scale of data, such as coastal, are similar to working with multi-scale data. In this environment, topology will be provided in the geodatabase, and a default value is assigned to the Library_Chart_Type field.

Fundamentals of working with multi-scale data

The following are recommended guidelines when editing and working with more than one scale:

  • Create a child version of the DEFAULT NIS database and edit in the checkout DNC replica database.
    • DEFAULT is the published version of the database, representing the current state of the system being modeled. You maintain and update the DEFAULT version over time by posting changes to it from other versions.
  • Use a schema that does not contain topology.
    • Polygons representing the same land area may exist more than once at different scales. If topology is run, you'll get false errors.
  • One person edits one area of interest (AOI).
    • Divide jobs or AOIs independent of each other. Each editor should work in separate geographic areas. Two editors working on the same version or a different version, can produce conflicts.
    Example of three AOIs
    • Conflicts occur in the following instances:
      • The same feature is updated in both the current version being edited and the target version.
      • The same feature is updated in one version and deleted in the other.
      • A topologically related feature or relationship class is modified in the current version being edited and a target version.
  • When working with a job or AOI, be aware of any features that cross the border into other extents at the same scale.
    Coastline crossing the AOIs
  • Enter the Library_Chart_Type field when creating new features.
    • Each feature must be assigned to a Library_Chart_Type field scale and cannot be NULL.
  • After synchronizing your edits to the NIS, reconcile and post your changes to the DEFAULT NIS.
  • If you no longer need the version you posted from, you can delete it.
    • Deleting unneeded versions simplifies version management. The fewer versions there are, the shorter the list to manage.