Cadastre Microstation-Bentley

Microstation Geographics, connect to Database

Although Geographics is a legacy version of Bentley, after Benley Map and Cadastre are here to stay, here are some notes for a student who wants to connect a database of Geographics project maps.

From previous topics

In some post I've explained before how some guts of Geographics work, this summary of almost 15 entries shows that I really enjoyed it.

What happens is that Geographics was always like that, a software that had to be known smoked things to implement it at the administrator level. While users had to learn to do basic routines to apply it, yet it is a tool that despite the fact that Bentley does not respond in support, it is still defended tooth and nail by users who do not want to let it go.

What to connect

Geographics can be connected to at least Oracle, SQLServer or Access databases, preferably via ODBC, although they are not the only databases or the only connection mode. The connection is created, as I explained in item 6 of the previous list.

What to connect

Geographics, in these versions it works via object connection links (Engeneering links), which can be a line, point, cell, or polygon. This connection works as follows:

The connecting object must be on the map, suppose a tab number of the 425876 form.
The MsLink is a number that is not repeated on a map and is associated once the object is linked to the database.
The MapID is a number that associates the mslink with the registered map, so an MsLink can be repeated from one map to another, the difference is in the map registration number, which I explained in 12 in the top list.
Once linked, it is possible to view other tables in the database in Geographics, such as the taxpayer registry, cadastral values ... And with these, perform operations such as topological analysis, thematic maps, annotations to the map, etc.

The database

In order to interact with a Geographics project, the database must contain the following tables:

category
feature
Mapsmscatalog
Ugcategory
Ugcommandugfeature
Ugjoin_cat
Ugmap
Ugtable_cat

In addition, the table to which it is desired to connect, such as the cadastral register (suppose it is called plug) a column called MsLink should be added to it, as I write it, with the M and L in uppercase. And this must be of the autonumeric type, so each time a new card is created it is assigned a number that will not be repeated.
Also to the table must be added the following columns:

Reserved, the name of these columns does not matter, what does matter is that it is numeric with two decimal places. This will be to update the area of the property in the database.

Perimeter, Just like the previous one, to store the value of the sum of the sides of the property.

x1, Y1, x2, y2. These are four columns where the coordinates that define the range of the property will be stored, and that will be useful to go to the property (locate) Selected, just as it is to be published in Geoweb Publisher.

Then, in the database, in the mscatalog table you have to include the registry table and assign it an identifier. This is so that the table can be seen from Geographics in the next step and can be registered in the catalog.

The maps

The map must be registered, this is done from Project / setup / register map / dgn file. With this, the map acquires a number in the ugmaps table.
The created table must also be created from geographics. For this you have to go to Project / setup / tables / table catalog. Here it is created, placing TICKET in the name, MSLINK (with capital letters) in the primary key and an alias, in this case FC. Then Commit. With this, we are ready to flirt.

MSLINK

He calls

The object will be linked to a field in the table plug, Through the Mslink As primary key and based on a coincidence with the column Key_file.

There must be a unique match between the object to be linked (let us suppose token number on the map) and an identifier in the register. It may well be the file number or cadastral key, but it should not be repeated on the same map.

MSLINK To switch on, a fence, then Database / text manager. We leave only the chip number level on, to proceed to the league. Then we choose the name of the table where we want to link and the column that contains the match. In this case, the Tab table and the column Key_file.

We activate the option Use Fence, We choose the button Join And click on the screen.

Ready, Gegraphics searched for all those fields of the tab number on the map, which matched the database tab number in the table plug And column Key_file. And made a flirt through the Mslink auto-numeric existing in that column. The way to test it is using the command Review attributes, You should lift the associated table.
To update Area and perimeter, the levels or Features of land boundary and block, and centroids. Then it is done Database / area perimeter u
ddate.
To update coordinates, Database / coordinate update.
Insertion Is to create a new record in the database, Update To make an update.