> For the complete documentation index, see [llms.txt](https://docs.os.uk/more-than-maps/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/more-than-maps/advanced-applications/os-ngd-data-in-dashboards/os-power-bi-map-visual/os-power-bi-map-visual-getting-started-guide/adding-data-to-the-map/styling-features-on-the-map.md).

# Styling features on the map

Once you have added features to the Features Layer, you can control how they are displayed. You can control the colour of features according to values of a field from your Power BI data, or all together, as well as adjusting the opacity of features and size of any points present.

{% hint style="info" %}
At present you can't vary the size of points in the Features Layer based on a field from your Power BI data. You can only do this for the Marker Points Layer.
{% endhint %}

Feature display is controlled by selecting the *Features Layer* dropdown under the *Symbology Settings pane* of the Format Visual controls:

<figure><img src="/files/da3c429cb049690bb19cd4d8b214aeaf3e134397" alt="Screenshot of the symbology settings window showing colour, opacity, and size settings being applied to the Features Layer" width="375"><figcaption><p>A screenshot of the Symbology Settings window</p></figcaption></figure>

The controls that appear under this pane will vary depending what other data you have added to the visual. If you have not added any data to the *Features Layer: Colour field*, you will not see the 'Min feature fill colour' and 'Feature % clip' controls.

## Varying the colour of features

The colour of features in the Features Layer is controlled in the same way as points in the Marker Points Layer, so the instructions for the Marker Points Layer on the [Styling points on the map page](/more-than-maps/advanced-applications/os-ngd-data-in-dashboards/os-power-bi-map-visual/os-power-bi-map-visual-getting-started-guide/adding-data-to-the-map/styling-points-on-the-map.md) apply equally to the Features Layer.

This allows you to create several different types of map:

* By mapping polygon features and adding a numeric field (or field summary) to the *Features Layer: Colour* field you will create a **choropleth** map.
* By mapping polygon features and adding another type of field, you will create a **categorical** (or **chorochromatic**) map. Categorical data in the Features Layer will be coloured according to the same process as in the Marker Points Layer.

{% hint style="info" %}
If you have categorical data in both layers and choose to use default colours for both, then a different colour palette will be used for each layer to ensure that they can be distinguished
{% endhint %}

* Point and / or line features can also be symbolised with colours varying according to a numeric or categorical data field.

## Controlling the appearance of unmatched features

If you have chosen to [upload spatial data into the visual](/more-than-maps/advanced-applications/os-ngd-data-in-dashboards/os-power-bi-map-visual/os-power-bi-map-visual-getting-started-guide/adding-data-to-the-map/creating-a-map-with-polygons-or-other-features.md#uploading-spatial-data-into-the-visual) to populate the Features Layer, you may have features in your uploaded data which do not match any value provided in the data model through the field added to the *Features Layer: Linking identifier* field well.

If so, you can choose to include these unmatched features on the map. They will be styled using a single symbol, which you can configure using the *Unmatched uploaded features* dropdown pane of the *Symbology Settings*:

<figure><img src="/files/dafdabaf8c0294cfc4b5d2b04a6ab5b5da91b0f2" alt="Screenshot of the Symbology Settings window showing styling settings being applied to the Umatched Uploaded features layer" width="375"><figcaption><p>A screenshot of the Symbology Settings window.</p></figcaption></figure>

This allows a couple of advanced mapping features.

Firstly you could combine this with a slicer to create a map that allows interactive highlighting of a particular subset of features, while leaving all the other features visible:

<figure><img src="/files/abdddfab0854229fd096793eae0e7348003c6e5f" alt="A map configured to display buildings between 5-7 metres height as a choropleth, with other buildings also visible for context"><figcaption><p>A map configured to display buildings between 5 and 7 metres height as a choropleth, with other buildings also visible for context.</p></figcaption></figure>

Secondly, you could populate the features layer by using one of the other two means (via GSS codes or via geometry from the data model), and then upload a separate dataset which will then be entirely unmatched (because you are not adding data to the Linking Identifier field). This allows you to effectively display an entirely separate dataset for contextual information:

<figure><img src="/files/b43a13affd3ca5ab1b3cbc6fdd084d2fdd711a73" alt="A screenshot of a map created by adding a WKT geometry field representing some buildings from the data model to the Features Layer: WKT or GeoJSON geometries field and styled using a categorical field"><figcaption><p>A screenshot of a map created by adding a WKT geometry field representing some buildings from the data model to the Features Layer: WKT or GeoJSON geometries field and styled using a categorical field.</p></figcaption></figure>

This map has been created by adding a WKT geometry field representing some buildings from the data model to the *Features Layer: WKT or GeoJSON geometries* field well, and styling it using a categorical field. A separate dataset representing site ownership polygons has been uploaded via the Upload Manager and is being displayed as unmatched data in grey. Both sets of features respond to pop-ups.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.os.uk/more-than-maps/advanced-applications/os-ngd-data-in-dashboards/os-power-bi-map-visual/os-power-bi-map-visual-getting-started-guide/adding-data-to-the-map/styling-features-on-the-map.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.