Network Data Model and Network Feature Editing (NFE) Model Metadata Views

5.14 Network Data Model and Network Feature Editing (NFE) Model Metadata Views

Two sets of network metadata views can be created for each schema (user): xxx_SDO_NETWORK_xxxxxx and xxx_SDO_NFE_MODEL_xxxxxx, where the initial xxx can be USER or ALL. These views are created, as needed, by Spatial.

The xxx_SDO_NFE_MODEL_xxxxxx metadata views relate to Feature Modeling Using Network Feature Editing (NFE).

Parent topic: Network Data Model Overview

5.14.1 xxx_SDO_NETWORK_METADATA Views

The following views contain information about networks:

USER_SDO_NETWORK_METADATA contains information about all networks owned by the user.
ALL_SDO_NETWORK_METADATA contains information about all networks on which the user has SELECT permission.

If you create a network using one of the CREATE_<network-type>_NETWORK procedures, the information in these views is automatically updated to reflect the new network; otherwise, you must insert information about the network into the USER_SDO_NETWORK_METADATA view.

The USER_SDO_NETWORK_METADATA and ALL_SDO_NETWORK_METADATA views contain the same columns, as shown Table 5-38, except that the USER_SDO_NETWORK_METADATA view does not contain the OWNER column. (The columns are listed in their order in the view definition.)

Table 5-38 Columns in the xxx_SDO_NETWORK_METADATA Views

Column Name	Data Type	Purpose
OWNER	VARCHAR2(32)	Owner of the network (ALL_SDO_NETWORK_METADATA view only)
NETWORK	VARCHAR2(24)	Name of the network
NETWORK_ID	NUMBER	ID number of the network; assigned by Spatial.
NETWORK_CATEGORY	VARCHAR2(12)	Contains `SPATIAL` if the network nodes and links are associated with spatial geometries; contains `LOGICAL` if the network nodes and links are not associated with spatial geometries. A value of `LOGICAL` causes the Network Data Model PL/SQL and Java APIs to ignore any spatial attributes of nodes, links, and paths.
GEOMETRY_TYPE	VARCHAR2(24)	If `NETWORK_CATEGORY` is `SPATIAL`, contains a value indicating the geometry type of nodes and links: `SDO_GEOMETRY` for non-LRS SDO_GEOMETRY objects, `LRS_GEOMETRY` for LRS SDO_GEOMETRY objects, `TOPO_GEOMETRY` for SDO_TOPO_GEOMETRY objects.
NETWORK_TYPE	VARCHAR2(24)	User-defined string to identify the network type.
NO_OF_HIERARCHY_LEVELS	NUMBER	Number of levels in the network hierarchy. Contains 1 if there is no hierarchy. (See Network Hierarchy for information about network hierarchy.)
NO_OF_PARTITIONS	NUMBER	(Not currently used)
LRS_TABLE_NAME	VARCHAR2(32)	If `GEOMETRY_TYPE` is `SDO_GEOMETRY`, contains the name of the table containing geometries associated with nodes.
LRS_GEOM_COLUMN	VARCHAR2(32)	If `LRS_TABLE_NAME` contains a table name, identifies the geometry column in that table.
NODE_TABLE_NAME	VARCHAR2(32)	If `GEOMETRY_TYPE` is `SDO_GEOMETRY`, contains the name of the table containing geometries associated with nodes. (The node table is described in Node Table.)
NODE_GEOM_COLUMN	VARCHAR2(32)	If `NODE_TABLE_NAME` contains a table name, identifies the geometry column in that table.
NODE_COST_COLUMN	VARCHAR2(1024)	If `NODE_TABLE_NAME` contains a table name, identifies the cost column in that table, or a PL/SQL function to compute the cost value.
NODE_PARTITION_COLUMN	VARCHAR2(32)	(Not currently used).
NODE_DURATION_COLUMN	VARCHAR2(32)	If `NODE_TABLE_NAME` contains a table name, identifies the optional duration column in that table. This column can contain a numeric value that has any user-defined significance, such as a number of minutes associated with the node.
LINK_TABLE_NAME	VARCHAR2(32)	If `GEOMETRY_TYPE` is `SDO_GEOMETRY`, contains the name of the table containing geometries associated with links. (The link table is described in Link Table.)
LINK_GEOM_COLUMN	VARCHAR2(32)	If `LINK_TABLE_NAME` contains a table name, identifies the geometry column in that table.
LINK_DIRECTION	VARCHAR2(12)	Contains a value indicating the type for all links in the network: `UNDIRECTED` or `DIRECTED`.
LINK_COST_COLUMN	VARCHAR2(1024)	If `LINK_TABLE_NAME` contains a table name, identifies the optional numeric column containing a cost value for each link, or a PL/SQL function to compute the cost value.
LINK_PARTITION_COLUMN	VARCHAR2(32)	(Not currently used)
LINK_DURATION_COLUMN	VARCHAR2(32)	If `LINK_TABLE_NAME` contains a table name, identifies the optional duration column in that table. This column can contain a numeric value that has any user-defined significance, such as a number of minutes associated with the link.
PATH_TABLE_NAME	VARCHAR2(32)	Contains the name of an optional table containing information about paths. (The path table is described in Path Table.)
PATH_GEOM_COLUMN	VARCHAR2(32)	If `PATH_TABLE_NAME` is associated with a spatial network, identifies the geometry column in that table.
PATH_LINK_TABLE_NAME	VARCHAR2(32)	Contains the name of an optional table containing information about links for each path. (The path-link table is described in Path-Link Table.)
SUBPATH_TABLE_NAME	VARCHAR2(32)	Contains the name of an optional table containing information about subpaths. (The subpath table is described in Subpath Table.)
SUBPATH_GEOM_COLUMN	VARCHAR2(32)	If `SUBPATH_TABLE_NAME` is associated with a spatial network, identifies the geometry column in that table.
PARTITION_TABLE_NAME	VARCHAR2(32)	For a partitioned network: the name of the partition table. (The partition table is described in Partition Table.
PARTITION_BLOB_TABLE_NAME	VARCHAR2(32)	For a partitioned network for which any partition BLOBs have been generated: the name of the partition BLOB table. (The partition BLOB table is described in Partition BLOB Table.
COMPONENT_TABLE_NAME	VARCHAR2(32)	The name of the table containing information about precomputed connected components, as explained in Precomputed Analysis Results. (The connected component table is described in Connected Component Table.)
NODE_LEVEL_TABLE_NAME	VARCHAR2(32)	The name of the table containing information about node levels in a multilevel network. Specify this table as the `node_level_table_name` parameter with the SDO_NET.GENERATE_NODE_LEVELS procedure.
TOPOLOGY	VARCHAR2(32)	For a spatial network containing SDO_TOPO_GEOMETRY objects (creating using the SDO_NET.CREATE_TOPO_NETWORK procedure), contains the name of the topology.
USER_DEFINED_DATA	VARCHAR2(1)	Contains Y if the network contains user-defined data; contains N if the network does not contain user-defined data.
EXTERNAL_REFERENCES	VARCHAR2(1)	(Not currently used)
CHILD_NETWORK	VARCHAR2(32)	Name of the child network, if a network hierarchy is involved.
HIERARCHY_TABLE_NAME	VARCHAR2(32)	Name of the hierarchy table, if a network hierarchy is involved.

Parent topic: Network Data Model and Network Feature Editing (NFE) Model Metadata Views

5.14.2 xxx_SDO_NETWORK_CONSTRAINTS Views

The following views contain information about network constraints (described in Network Constraints):

USER_SDO_NETWORK_CONSTRAINTS contains information about all network constraints owned by the user.
ALL_SDO_NETWORK_CONSTRAINTS contains information about all network constraints on which the user has SELECT permission.

These views are automatically maintained by the SDO_NET.REGISTER_CONSTRAINT and SDO_NET.DEREGISTER_CONSTRAINT procedures. You should not directly modify the contents of these views.

The USER_SDO_NETWORK_CONSTRAINTS and ALL_SDO_NETWORK_CONSTRAINTS views contain the same columns, as shown Table 5-39, except that the USER_SDO_NETWORK_CONSTRAINTS view does not contain the OWNER column. (The columns are listed in their order in the view definition.)

Table 5-39 Columns in the xxx_SDO_NETWORK_CONSTRAINTS Views

Column Name	Data Type	Purpose
OWNER	VARCHAR2(32)	Owner of the network constraint (ALL_SDO_NETWORK_CONSTRAINTS view only)
CONSTRAINT	VARCHAR2(32)	Name of the network constraint
DESCRIPTION	VARCHAR2(200)	Descriptive information about the network constraint, such as its purpose and any usage notes
CLASS_NAME	VARCHAR2(4000)	Name of the Java class that implements the network constraint
CLASS	BINARY FILE LOB	The Java class that implements the network constraint

Parent topic: Network Data Model and Network Feature Editing (NFE) Model Metadata Views

5.14.3 xxx_SDO_NETWORK_USER_DATA Views

The following views contain information about network user-defined data, which is the information (not related to connectivity) that users want to associate with a network representation:

USER_SDO_NETWORK_USER_DATA contains information about all network user-defined data owned by the user.
ALL_SDO_NETWORK_USER_DATA contains information about all network user-defined data on which the user has SELECT permission.

The USER_SDO_NETWORK_USER_DATA and ALL_SDO_NETWORK_USER_DATA views contain the same columns, as shown Table 5-39, except that the USER_SDO_NETWORK_USER_DATA view does not contain the OWNER column. (The columns are listed in their order in the view definition.)

Table 5-40 Columns in the xxx_SDO_NETWORK_USER_DATA Views

Column Name	Data Type	Purpose
OWNER	VARCHAR2(32)	Owner of the network constraint (ALL_SDO_NETWORK_USER_DATA view only)
NETWORK	VARCHAR2(32)	Name of the network
TABLE_TYPE	VARCHAR2(12)	Type of the table containing the user-defined data: `NODE`, `LINK`, `PATH`, or `SUBPATH` If feature user data is registered through the xxx_SDO_USER_NETWORK_USER_DATA views. TABLE_TYPE is set to the name of the feature table.
DATA_NAME	VARCHAR2(32)	Name of column containing the user-defined data
DATA_TYPE	VARCHAR2(12)	Data type of the user-defined data: `VARCHAR2`, `INTEGER`, `NUMBER`, `DATE`, `TIMESTAMP`, or `SDO_GEOMETRY`
DATA_LENGTH	NUMBER(38)	If DATA_TYPE is `VARCHAR2`, the length of the user-defined data
CATEGORY_ID	NUMBER	User data category ID (non-negative number, default 0). The category ID allows for grouping of user data for different applications. Category 0 is reserved for general-purpose user data that is useful for all applications. User data for different purposes can be grouped into different categories, so that during network analysis, only the relevant user data categories are loaded into memory, reducing memory consumption at runtime. For example, for a road network, category 0 user data can include the speed limit and function class of links, and the x, y coordinates of nodes; trucking-related user data might belong to category 1; and traffic-related user data might belong to category 2.

To use user-defined data, you must set the USER_DEFINED_DATA column value to Y in the appropriate xxx_SDO_NETWORK_METADATA views (described in xxx_SDO_NETWORK_METADATA Views).

For an example of using user-defined data, see User-Defined Data Examples (PL/SQL and Java).

For user data defined through the xxx_SDO_NETWORK_USER_DATA views, the default user data I/O implementation (LODUserDataIOSDO) is used to access the user data during network analysis. However, some user data is not included in the node or link table, and thus cannot be registered through xxx_SDO_NETWORK_USER_DATA views. For such user data, you must provide your own implementation of the user data I/O interface. A typical way of implementing a custom user data I/O interface is to generate BLOBs corresponding to node and link user data , one BLOB for each partition, and then retrieve user data information from the BLOBs during network analysis.

You can also associate multiple categories of user-defined data (categorized user data) with a single network. For example, in a multimodal network (described in Multimodal Network and Temporal Examples), if you must associate driving-related attributes (such as speed limit) with a link in addition to the link's multimodal attributes, you can organize user-defined data in two categories: one for driving-related attributes and the other for multimodal attributes.

Parent topic: Network Data Model and Network Feature Editing (NFE) Model Metadata Views

5.14.4 xxx_SDO_NETWORK_FEATURE Views

The following views contain information about network feature layers (described in Features and Feature Layers):

USER_SDO_NETWORK_FEATURE contains information about all network feature layers owned by the user.
ALL_SDO_NETWORK_FEATURE contains information about all network feature layers on which the user has SELECT permission.

The USER_SDO_NETWORK_FEATURE and ALL_SDO_NETWORK_FEATURE views contain the same columns, as shown Table 5-39, except that the USER_SDO_NETWORK_FEATURE view does not contain the OWNER column. (The columns are listed in their order in the view definition.)

Table 5-41 Columns in the xxx_SDO_NETWORK_FEATURE Views

Column Name	Data Type	Purpose
OWNER	VARCHAR2(32)	Owner of the network feature layer (ALL_SDO_NETWORK_FEATURE view only)
NETWORK	VARCHAR2(32)	Name of the network on which the feature layer is defined
FEATURE_LAYER_NAME	VARCHAR2(32)	Name of the feature layer
FEATURE_LAYER_ID	NUMBER	ID of the feature layer (assigned by Oracle Spatial)
FEATURE_LAYER_TYPE	NUMBER	Type of the feature layer (see Table 5-2 in Features and Feature Layers)
FEATURE_TABLE_NAME	VARCHAR2(32)	Name of the feature table (see Feature Table)
RELATION_TABLE_NAME	VARCHAR2(32)	Name of the feature element relationships table, which maps feature elements with network elements (nodes and links) (see Feature Element Relationships Table)
HIERRCHY_TABLE_NAME	VARCHAR2(32)	Name of the feature hierarchy table, which defines parent-child relationships between features (see Feature Hierarchy Table)

To use user-defined data, you must set the USER_DEFINED_DATA column value to Y in the appropriate xxx_SDO_NETWORK_METADATA views (described in xxx_SDO_NETWORK_METADATA Views).

For an example of using user-defined data, see User-Defined Data Examples (PL/SQL and Java).

Parent topic: Network Data Model and Network Feature Editing (NFE) Model Metadata Views

5.14.5 xxx_SDO_NFE_MODEL_FTLAYER_REL Views

The following views contain information about network feature layers related to NFE models. (This topic assumes you are familiar with the concepts explained in Feature Modeling Using Network Feature Editing (NFE).)

USER_SDO_NFE_MODEL_FTLAYER_REL contains information about feature layers that are related to all NFE models that are owned by the user.
ALL_SDO_NFE_MODEL_FTLAYER_REL contains information about feature layers that are related to NFE models on which the user has SELECT permission.

The USER_SDO_NFE_MODEL_FTLAYER_REL and ALL_SDO_NFE_MODEL_FTLAYER_REL views contain the same columns, as shown in Table 5-42, except that the USER_SDO_NFE_MODEL_FTLAYER_REL view does not contain the OWNER column. (The columns are listed in their order in the view definition.)

Table 5-42 Columns in the xxx_SDO_NFE_MODEL_FTLAYER_REL Views

Column Name	Data Type	Purpose
OWNER	VARCHAR2(32)	Owner of the NFE model (ALL_SDO_NFE_MODEL_FTLAYER_REL view only)
MODEL_ID	NUMBER	Identifier of the model related to a feature layer.
FEATURE_LAYER_ID	NUMBER	Identifier of the related feature layer.
HIERARCHY_LEVEL	NUMBER	Hierarchical level for the feature layer in the model. The default is 0 (zero). Higher levels are on top of lower levels.
Z_ORDER	NUMBER	Depth of the feature layer among other feature layers in the same hierarchy level. Normally used to determine the order of drawing the feature layer elements on a canvas: the lowest order is the first to be presented.
PATH_LAYER	VARCHAR2(1)	Indicates whether the feature layer is a path generated from an analysis operation. `Y` indicates a path feature layer (generated from an analysis operation); `N` or null indicates a common feature layer.

Parent topic: Network Data Model and Network Feature Editing (NFE) Model Metadata Views

5.14.6 xxx_SDO_NFE_MODEL_METADATA Views

The following views contain information about NFE models. (This topic assumes you are familiar with the concepts explained in Feature Modeling Using Network Feature Editing (NFE).)

USER_SDO_NFE_MODEL_METADATA contains information about NFE models that are owned by the user.
ALL_SDO_NFE_MODEL_METADATA contains information about NFE models on which the user has SELECT permission.

The USER_SDO_NFE_MODEL_METADATA and ALL_SDO_NFE_MODEL_METADATA views contain the same columns, as shown in Table 5-43, except that the USER_SDO_NFE_MODEL_METADATA view does not contain the OWNER column. (The columns are listed in their order in the view definition.)

Table 5-43 Columns in the xxx_SDO_NFE_MODEL_METADATA Views

Column Name	Data Type	Purpose
OWNER	VARCHAR2(32)	Owner of the NFE model (ALL_SDO_NFE_MODEL_METADATA view only).
ID	NUMBER	Model identifier (assigned by Oracle Spatial).
NAME	VARCHAR2(100)	Name of the model.
EDITION_MODE	NUMBER	Can be `1` (SDO_NFE.FROM_SCRATCH) for models using a new network, creating features along with underlying network elements, or `2` (SDO_NFE.OVER_EXISTING_NETWORK) for models built on top of a currently existing network (in which network elements cannot be modified).
VERSIONABLE_IND	VARCHAR2(1)	Indicates whether the model will allow different versions or branches. `Y` indicates a they are allowed; `N` indicates they are not allowed.
TABLE_REG_TAB	VARCHAR2(50)	Name of the table in which the names of the Network Feature Editing (NFE) Model Tables are registered. This table is automatically created and maintained, and it has the columns described in Table 5-44.
SEQUENCE_REG_TAB	VARCHAR2(50)	Name of the table in which the sequences associated with the model’s tables are registered. This table is automatically created and maintained, and it has the columns described in xxx_SDO_NFE_MODEL_METADATA Views.
NETWORK_NAME	VARCHAR2(50)	Name of the network associated with the model.

Table 5-44 Columns in the TABLE_REG_TAB Table

Column Name	Data Type	Purpose
TABLE_TYPE	VARCHAR2(50)	Primary Key. Type of the table to be registered. Possible values: SDO_NFE.FT_CLASS, SDO_NFE.FT_CLASS_REL, SDO_NFE.FT_CLASS_ATTR_CON, DO_NFE.FT_USR_DATA, SDO_NFE.FT_USR_DATA_CAT, SDO_NFE.FT_USR_DATA_CVAL, SDO_NFE.FT_CLASS_DEF_PTS, SDO_NFE.LINE_LINE_RULES, SDO_NFE.LINE_POINT_RULES, SDO_NFE.RULE_INSTANCE, SDO_NFE.FT_RULE_REL, SDO_NFE.RULE_DEC_HANDLER, SDO_NFE.POINT_CARD_RULES, SDO_NFE.POINT_ATTR_DEF
TABLE_NAME	VARCHAR2(50)	Name assigned to the table. When you use SDO_NET.ADD_CHILD_FEATURE, by default this name is created in the form `[TABLE_TYPE]_[model_id]$`.

Table 5-45 Columns in the SEQUENCE_REG_TAB Table

Column Name	Data Type	Purpose
TABLE_NAME	VARCHAR2(50)	Primary key. Name of the table associated with the sequence..
SEQUENCE_NAME	VARCHAR2(50)	Name of the sequence..

Parent topic: Network Data Model and Network Feature Editing (NFE) Model Metadata Views

5.14.7 xxx_SDO_NFE_MODEL_WORKSPACE Views

The following views contain information about workspaces related to NFE models. (This topic assumes you are familiar with the concepts explained in Feature Modeling Using Network Feature Editing (NFE).)

USER_SDO_NFE_MODEL_WORKSPACE contains information about workspaces that are related to all NFE models that are owned by the user.
ALL_SDO_NFE_MODEL_WORKSPACE contains information about workspaces that are related to NFE models on which the user has SELECT permission.

These views are automatically maintained by Spatial using the NFE Java and PL/SQL interfaces for creating and deleting Workspace Manager workspaces. You should never directly modify the content of these views.

The USER_SDO_NFE_MODEL_WORKSPACE and ALL_SDO_NFE_MODEL_WORKSPACE views contain the same columns, as shown in Table 5-42, except that the USER_SDO_NFE_MODEL_WORKSPACE view does not contain the OWNER column. (The columns are listed in their order in the view definition.)

Table 5-46 Columns in the xxx_SDO_NFE_MODEL_WORKSPACE Views

Column Name	Data Type	Purpose
OWNER	VARCHAR2(32)	Owner of the NFE model (ALL_SDO_NFE_MODEL_WORKSPACE view only)
ID	NUMBER	Identifier of the workspace. Assigned by Oracle Spatial.
MODEL_ID	NUMBER	Identifier of the model to which the workspace belongs.
WORKSPACE_NAME	VARCHAR2(50)	Name of the workspace.
MBR_IND	VARCHAR2(1)	Indicates whether the workspace represents an MBR (minimum bounding rectangle) region in the model. `Y` indicates the workspace represents an MBR; `N` indicates the workspace does not represent an MBR
LOWER_X	NUMBER	If MBR_IND is `Y`, the X value for the lower coordinate of the MBR.
UPPER_X	NUMBER	If MBR_IND is `Y`, the X value for the upper coordinate of the MBR.
LOWER_Y	NUMBER	If MBR_IND is `Y`, the Y value for the lower coordinate of the MBR.
UPPER_Y	NUMBER	If MBR_IND is `Y`, the Y value for the upper coordinate of the MBR.
LOCK_IND	VARCHAR2(1)	Indicates whether the workspace is locked for editing by others (that is,, unable to be edited by others). `Y` indicates the workspace is locked; `N` indicates the workspace is not locked.

Parent topic: Network Data Model and Network Feature Editing (NFE) Model Metadata Views