Dataset Crossing

Data features can cross or lay on a dataset border. When this happens, MultiNet® indicates these conditions through Relationships, split indicators, and conversion records.

See "Dataset and Section Crossing" for a description of rules and examples for dataset crossing in both Shapefile and GDF formats. Section crossing is also explained in that section but does not apply to Shapefile or OSL file.

Below are examples of a line feature on a dataset border and an area feature crossing a dataset border in Shapefile format.

Line Feature on a Dataset Border

Figure: Line Feature on a Dataset Border

ID FEATTYP TABEXT TOID
98400000331677 4110 nw 368400001784447

Explanation:

In the Shapefile conversion record (cn), the internal (From) dataset is 9 (Connecticut). The foreign dataset is 36 (New York),the country code is 840 for both (United States), the feature type that lays on the section border is a road element (4110) found in the network file (nw). The internal feature ID (From feature) is 98400000331677 and the corresponding feature ID in the foreign feature (To feature) is 368400001784447. See map of the above example below.

Figure: Map of the Line Feature on a Dataset Border Example

Area Feature Crossing a Dataset Border

Figure: Area Feature Crossing a Dataset Border

ID FEATTYP TABEXT TOID
18261605004044 9200 oa06 18260621700190

Explanation:

In the Shapefile conversion record (cn), the internal (From) dataset is 21 (Scotland). The "foreign" dataset is 27 (England) ,the country code is 826 for both (Great Britain), the feature type that crosses the section border is an Index Area (9200) found in the Other Named Areas file (oa06). The internal feature ID (From feature) is 18261605004044 and the corresponding feature ID in the "foreign" feature (To feature) is 18260621700190. The Name field in both tables is Dumfriesshire. See map of the above example below.

Figure: Index Area Dumfriesshire (oa06) Crossing Dataset Borders