08.04.2014 Views

Exponare 5.1 Administration User Guide - Pitney Bowes Software

Exponare 5.1 Administration User Guide - Pitney Bowes Software

Exponare 5.1 Administration User Guide - Pitney Bowes Software

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 2: About <strong>Exponare</strong> Server and Clients<br />

Layers and Features<br />

As mentioned above, a key part of a workspace is the definition of different map Layers. Each Layer<br />

normally represents only one type of information. For example, a map for displaying residential<br />

areas might have separate Layers for properties, roads, sewerage, electricity, water and so on. Each<br />

Layer has a set of Features that represent physical objects or other map data. When working with a<br />

map, the user can select Features from one or more Layers and view information about those<br />

specific Features.<br />

SQL Support Tables<br />

SQL Support Tables are tables of spatial or non-spatial data used in the processing of Data Binds<br />

and Queries. SQL Support Tables can be part of the workspace file, or loaded separately from TAB<br />

Files. Only workspaces and TAB Files can be loaded into a Work Context, but TAB Files can refer to<br />

external database tables if required. Only those tables that are explicitly loaded are available for use<br />

in a Work Context.<br />

Selections and Queries<br />

<strong>Exponare</strong> offers the ability to work with selected Features on the Layers of a map. Indicating the<br />

Features to work with can be achieved in two separate ways: (1) by using map selection tools, or (2)<br />

by activating Queries. The first method, map selection tools, is the most simple and suffices for most<br />

requirements.<br />

Queries are a more complex (and more powerful) selection method than the visual tools. A Query is<br />

a logical statement that defines the Features that should be selected. For example, a simple Query<br />

might read:<br />

Select all the Avenues in Smallville.<br />

This Query indicates that all of the roads in ‘Smallville’ whose type is ‘Avenue’ should be selected,<br />

regardless of what is currently visible in the map display.<br />

Once a set of Features has been selected, either by map selection tools, or by Queries, two<br />

separate actions occur. The first is that the selected Features are visually defined on the map. For<br />

example, linear Features might by highlighted and area Features shown with a shaded background.<br />

The second is that information related to the selected Features may be displayed. The system for<br />

linking Features to a set of information is called Data Binding.<br />

Running a Query only causes Features to be selected. A Data Bind must be configured for<br />

information to be displayed regarding the selected Features.<br />

Data Binds<br />

Data Binds are links from Feature identifiers to Feature information. Any loaded SQL Support Table<br />

can be used for a Data Bind. For example, on a map containing a set of roads, we may have<br />

information about each of the roads, such as “Name’, “Maintenance schedule’, and “Current<br />

condition’. To set up the Data Bind, each road is given a Feature ID, and a database table is created<br />

that has a primary column of Feature IDs, and associated columns for “Name’, “Maintenance<br />

schedule’, and “Current condition’ and other information. Whenever a set of roads is selected, the<br />

set of Feature IDs is obtained and the database table can be consulted to access the associated<br />

information.<br />

<strong>Administration</strong> <strong>Guide</strong> 17

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!