Custom Data Render |
A Custom Data Renderer instructs GeoBase how custom data should be displayed. This data may come from a CustomTable that was populated during an Alchemy import, or it may be included in a Table that resides in a TransactionalRepository. A Custom Data Renderer can be used to render three types of custom data:
Syntax | BEGIN CUSTOM blockname '['table_name']' [reversed] |
Example | cam BEGIN CUSTOM lines [my_rail] [line_number == 0],PEN<(64,64,64),1:railway> END CUSTOM |
The type of data to render. Must be one of:
A string which specifies which data table to use for this block. This must be enclosed by square brackets.
As with any other block, this means that render instructions will be processed in reverse order. Optional.
Example | cam RENDER [type > 3], ... |
All custom render commands take a common filter format. You may specify a simple expression on a single column in the table. If the expression evaluates to true then that row is rendered. Using relative operators on string columns always returns false. Valid operators are:
< | Less than |
> | Greater than |
== | Equal |
& | Bitwise And (Integer only) |
If more complex filters are required, they should be done during an Alchemy import.