Improvements to conditions in GIS file formats
Digi3D.NET has for about a year a tool that allows to differentiate codes in different geometries stored in the same database table in file formats SIG such as Geomedia and Shapefile. In the program Code Table Editor we can add conditions to the field Conditions associated with each code. In these conditions we can basically put the name of a field and a value. We can put as many conditions as we want. In this way, if for example we have a table named VIAS_DE_COMUNICACION that stores (surprisingly) transportation route geometries, and this has among others the fields state and CARRILES, we can indicate to Digi3D.NET if there is in this table a geometry that has the following values:
ESTADO=27
that considers that geometry a Highway or Highway, but if instead of those values, it encounters a geometry with values:
ESTADO=44
that considers that geometry as a highway under construction. This has been with us for about a year. What we have added today is the possibility of using different operators, since until now the only operator that was accepted was the equal operator, so that only you could check if the attribute X is equal to the value Y. We have added the following operators:
| Operator to enter in the code table | Meaning |
|---|---|
| < | Less than |
| <= | Less than or equal to |
| = | Equal to |
| >= | Greater than or equal to |
| > | Greater than |
this way, if for example we want to differentiate between road and motorway based on the number of lanes, and assuming that the number of lanes is stored in the CARRILES field, we could do something like this: Add to the Road code these conditions:
ESTADO=27
CARRILES<=2
To the code of Road under construction the conditions:
ESTADO=44
CARRILES<=2
To the code of Highway the conditions:
ESTADO=27
CARRILES>2
To the code of Highway under construction the conditions:
ESTADO=44
CARRILES>2
You can download the example video below from the following URL: http://digi21.blob.core.windows.net/ejemplos/OperadoresEnCondicionesDeCodigos.zip and below you have a video where you can see this functionality in action: