Configuring Linked Datasets
A linked dataset contains complementary attributes that relate to a features from a map layer.
When a user selects a feature from a standard map layer (the 'parent' dataset), Pozi fetches and displays associated records from any linked table (the 'child' dataset) based on an attribute that's shared between the two.
- owner details
- building and planning permits
- animal registrations
- associated land parcels
- intersecting planning zones and overlays
- council wards
The parent record contains various attributes, such as the ones that are visible in the Details panel, other hidden attributes, and also the record's geometry. Any of these can be used as a key for querying other datasets. And any child record can become a parent of another dataset, and so on.
In the above example:
Property Informationis queried using the parent record's property number
Property Parcelsis queried using the parent record's property pfi
Property Planning Overlaysand
Zonesboth use the parent record's geometry (ie, property boundary) in a spatial intersection query
Administrators can use QGIS to configure child datasets for viewing by internal users. The parent dataset can be an internal or external dataset.
Add the source table for the child dataset to a QGIS project. The project can be an existing project that contains map layers or it can be a dedicated project that contains no layers and only child datasets.
- open project file in QGIS
- Layer > Add Layer > pick from file or database options
- pick source table
- Project > Properties > QGIS Server
WFS capabilities > Published: tick on for the new dataset
- Project > Save (
Configure Child Settings
The parent/child settings are maintained in the child layer's QGIS Server keyword list. Pozi obtains these settings, along with any other keywords, when it loads and imports and project's catalogue.
Only the child dataset needs to be configured. There is no configuration required for the parent dataset for it to used by a child dataset.
Below are details of how to derive and combine the components of this setting.
parent dataset contains the features which, when selected, will trigger a data request to the child dataset.
For example, if the parent is the "Property" layer, then every time a user selects a feature in the Property layer, Pozi will trigger a request to the child dataset.
The parent layer can exist in the same QGIS project, or a different project, or even a layer from an external source.
parameter is an expression that contains instructions for filtering the child dataset to return only records that relate to an individual parent feature.
Use the layer's Query Builder to construct and test your expression.
- Layer Properties > Source > Query Builder
- double-click the name of the field to be used as the link - this will be added to the expression
IN, and add an open bracket (
- click the Sample button to obtain a list of existing values from the target field
- double click one of the sample values to add it to the expression
- add a close bracket (
- click Test
If the test query returns one or more rows, your expression is valid, and it can be used in the child parameter. Clear the Query Result dialog box, select your expression text, and copy it to your clipboard.
If your child data source is a MySQL table, and your test returns 0 records, try removing any double quotes from around the target field and try again.
Exit the Query Builder by clicking Cancel. DO NOT click OK. (If you accidentally click OK, re-open the Query Builder and clear the expression before saving.)
parameter text as follows:
EXP_FILTER=+ the expression from your test pasted from the clipboard
- remove any double quotes from around the target field
- replace the sample value with the name of the link field from the parent dataset where the target value is obtained, enclosed in a pair of square brackets (eg, replace
parameter=EXP_FILTER=Assess_NumberX IN ('[Property Number]')
Pozi will substitute any field names within square brackets with values from those fields from the parent.
These settings provide an override for some of the default layer behaviours in Pozi.
downloadable=false: prevent Pozi from showing a table view of the selected features
enabled=false: temporarily disable a dataset in Pozi (without having to remove it from QGIS)
infoPanelCollapse=true: collapse info results panel for this dataset
promoteDetails=true: display all child attributes instead of a preview
Combine and Configure
In the child dataset's Layer Properties, go to QGIS Server. Fill in the 'Keyword list' with the
parameter and optional settings derived above, each separated by commas.
parent=Property, parameter=EXP_FILTER=Assess_NumberX in ('[Property Number]')
EXP_FILTER doesn't support spaces in the child dataset's lookup field name. If this field contains any spaces, update the dataset's Attributes Form settings to use a alias name for the lookup field that doesn't contain spaces.
Click OK, then save the project.
Open your Pozi site in your browser, refresh the page, click on the map, select a parent record, and confirm that you can see the related child record(s) in the info panel.
Pozi automatically prevents the child table appearing in the layer panel due to the presence of the
parent keyword. Do NOT add the table to the list of excluded layers in the QGIS Server settings, except if you want to disable the child dataset lookup.
- check that the layer is enabled for WFS. In QGIS, go to Project > Properties > QGIS Server > WFS Capabilities > your dataset > Published (tick on), then Save the project
- ensure the parent keyword value is configured accurately with the parent dataset name
- in Pozi, click on a parent feature for which you know a child feature exists
- check that the names of the fields in the child and parent datasets that are used for the link are consistent with the names supplied with the child dataset's registration in Pozi
- check that there are no double quotes in the
Use QGIS to determine whether the layer also causes its project file to load slowly. Observe the progress bar at the bottom to see if any layers are taking more than a fraction of a second to load in QGIS. If it appears that a layer is taking longer, check the source data. Also check how long it takes for QGIS to show the dataset's table view (Layer > Open Attribute Table). Check that any join fields are properly indexed.
This can happen when querying a large selection because IIS has a default limit to the request length it will accept.
<security> section in the IIS QGIS Server
web.config file to allow longer requests:
<system.webServer> <security> <requestFiltering> <requestLimits maxQueryString="32768"/> </requestFiltering> </security> </system.webServer>