# Creating a point map

Follow the steps below to add points to the Marker Points Layer of the map. Note that the three ways of adding points (via coordinates, postcodes, or Unique Property Reference Numbers – UPRNs) are mutually exclusive; you can only use one at once.

## Adding points on a map using Longitude / Latitude or Eastings / Northings

If your data has a list of Longitude / Latitude or Eastings / Northings, then you’re able to plot these on a map by simply dragging and dropping the relevant columns in your data into the Points: X and Points: Y fields of the visual.

<figure><img src="/files/ff6f8136152f1c701d368d3bbad125ae36962fcc" alt="A screenshot of points: X and points: Y data fields in Power BI with no data added." width="188"><figcaption><p>A screenshot of points: X and points: Y data fields in Power BI.</p></figcaption></figure>

{% hint style="info" %}

### Displaying longitude / latitude data on a map

* The visual can display up to 30 000 individual points on the map.
* To see any errors, turn on the 'Show more detailed messaging' toggle under *Format visual* > *Map Settings* in the Visualizations pane.
* If the fields won’t populate with your data, make sure that on Table View the data type for your longitude / latitude data is set to *Decimal number* and **NOT** *Text*.
* The visual determines whether the coordinates received are latitude/longitude or easting/northing based on the range of the numbers – it does not receive any additional coordinate system information, so it cannot recognise coordinates in other reference systems such as UTM.
  {% endhint %}

<figure><img src="/files/d151ff08b9f0ad56d15b1e76c958649f51c30aa8" alt="A screenshot of the Longitude type field set to Decimal number in Power BI." width="188"><figcaption><p>A screenshot of the Longitude type field set to Decimal number in Power BI.</p></figcaption></figure>

## Adding points on a map using UPRNs or Postcodes

If your data has a list of postcodes or UPRNs, then you’re able to plot these on a map by simply dragging and dropping the relevant column in your data into the *Points: Postcodes or UPRNs* field of the visual.

<figure><img src="/files/14e978c0688d23e70b9e4cdab48755549af12402" alt="A screenshot of the &#x27;Points: Postcodes or UPRNs&#x27; data field in Power BI, allowing users to plot Postcodes or UPRNs on their map." width="188"><figcaption><p>The 'Points: Postcodes or UPRNs' data field in Power BI.</p></figcaption></figure>

{% hint style="info" %}

### Displaying point data on a map

* Postcodes are plotted according to their corresponding centroid.
* The visual can display up to 30 000 individual points on the map.
* Please note, if points appear on the same location, Points: pop-ups will have to be populated with a data attribute that splits out the points (see ['Adding clickable point pop-ups' 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#adding-clickable-point-pop-ups)).
  {% endhint %}

<figure><img src="/files/d151ff08b9f0ad56d15b1e76c958649f51c30aa8" alt="A screenshot of the Longitude type field set to Decimal number in Power BI." width="188"><figcaption><p>A screenshot of the Longitude type field set to Decimal number in Power BI.</p></figcaption></figure>

{% hint style="info" %}

### Good to know

* In order to retrieve locations for postcodes or UPRNs, the values you add to this field will be sent out of the visual to our geocoding service
* The values are checked first to make sure they fit the format of a UK postcode or UPRN. Any data mistakenly added to this field that doesn't match the format won't be sent out of the visual
* Once retrieved the locations are cached in the report and won't be re-requested by that copy of the visual
  {% endhint %}

## Missing UPRN or postcode points

If you have incorrect or out-of-date postcodes and UPRNs in your data, they won’t geocode as points on the map. Clicking on the notification panel (the bell icon in the bottom left of the Power BI UI) will let you know which UPRNs or postcodes failed to geocode and are incorrect.

<figure><img src="/files/a7fd5f940aa89950f8254e9747ee99e5112b0135" alt="A screenshot of the notification panel in Power BI showing a series of incorrect postcodes that failed to geocode"><figcaption><p>A screenshot of the notification panel in Power BI showing a series of incorrect postcodes that failed to geocode</p></figcaption></figure>

More detailed information, such as how many postcodes / UPRNs the visual attempted to geocode and how many succeeded, can be found by clicking on the notification panel after turning on the 'Show more detailed messaging' toggle found under *Format visual* > *Map Settings* in the Visualizations pane.

<figure><img src="/files/77e1f97fe41c998272be886b75031b0d699efd31" alt="Map Settings menu in the Visualizations pane showing the &#x27;Show more detailed messaging&#x27; toggle turned on." width="375"><figcaption><p>Map Settings menu in the Visualizations pane showing the 'Show more detailed messaging' toggle turned on.</p></figcaption></figure>


---

# Agent Instructions: 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:

```
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/creating-a-point-map.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
