Logo GISdevelopment.net

GISdevelopment > Proceedings > GITA > 2002


GITA 2002 | GITA 2001 | GITA 2000 | GITA 1999 | GITA 1998 | GITA 1997
Sessions

Applications

Data Development & Evolution

E-Biz

GeoSolucions

Mobile

Municipal Perspective

Network Operations Management

New Technology

Project Management

System Architecture

System Integration

The Human Factor

User Presentations

Work Management


GITA 2002


Systems Architectures


Telecommunications Network Modeling


The following tables show the information stored for feature “ID10”.



Figure 6: Sample Network Data in Complex CONNECTOR Table


The CONNECTOR table stores the administrative counts of the source of each network feature. In this example, administrative identifier “2B”, counts “25-30” are transported on cable “ID10”.

If the display of historical (previously named) ranges is required, another primary key column might (depending on the GIS vendor) need to be added to the CONNECTOR table. This would allow the historical ranges to be classified as different entities, so they can exist in the same version as the current or proposed ranges. Another solution might cache the count labels, using triggers to repopulate the cache.



Figure 7: Sample Network Data in Complex CONNECTION Table


The source connection of each connector is stored in the CONNECTION table. Each connector can only have one source connection, and the primary key (FEATURE_ID, ADDRESS_SPACE, CONNECTOR_NUM, and VERSION) reflects that fact, as there can only be one row for each unique primary key combination.



Figure 8: Range Based Complex Network Model


Page 4 of 7
| Previous | Next |

Applications | Technology | Policy | History | News | Tenders | Events | Interviews | Career | Companies | Country Pages | Books | Publications | Education | Glossary | Tutorials | Downloads | Site Map | Subscribe | GIS@development Magazine | Updates | Guest Book