Engineering-Tech Wiki

imp user/pass file=/bz10m/roads2_network-1.0.dmp full=y

Create network (needs to be done once):

INSERT INTO USER_SDO_NETWORK_METADATA(
                network, network_category, geometry_type,
                node_table_name, node_geom_column,
                link_table_name, link_geom_column,
                link_cost_column, link_direction)
        VALUES(
                'BZ_ROADS2_NET', 'SPATIAL', 'SDO_GEOMETRY',
                'BZ_ROADS2_NODE$', 'GEOMETRY',
                'BZ_ROADS2_LINK$', 'GEOMETRY',
                'COST', 'UNDIRECTED');

Current version: 1.0 (1/10/2008)

This is the TeleAtlas table we got from the Creaform on November the 12th. The table contains linestrings (in GEOMETRY column), which represent roads segments. The most important change here is the number of lanes (NUMCORSIE). Whenever NUMCORSIE=0, it is assumed NUMCORSIE=2 (one lane per one direction, bi-directed road).

The imported network data model will contain two tables: BZ_ROADS_LINK$ and BZ_ROADS_NODE$

The links are taken directly from the Spatial table road segments (linestrings). The nodes are created by generating a node for each segment start and end points.

We are working on the meanings of the columns:
BZ_ROADS:

Explanations from an old table (may not match):

If you want to use any spatial operators (such as finding all segments within distance, retrieving bounding rectangle etc.) you need to create an index for this table. How to do this for the LINK table (same for NODE, just substitute LINK$ with NODE$):

DELETE FROM USER_SDO_GEOM_METADATA WHERE TABLE_NAME='BZ_ROADS2_LINK$';
INSERT INTO USER_SDO_GEOM_METADATA(TABLE_NAME, COLUMN_NAME, DIMINFO, SRID)
       VALUES('BZ_ROADS2_LINK$', 'GEOMETRY',
              SDO_DIM_ARRAY(SDO_DIM_ELEMENT('X', 0, 0, .001),
                            SDO_DIM_ELEMENT('Y', 0, 0, .001),
              82344)
       );
CREATE INDEX BZ_ROADS2_LINK$_INDEX ON BZ_ROADS2_LINK$(GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX;