> For the complete documentation index, see [llms.txt](https://openup.gitbook.io/wazimap-ng/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://openup.gitbook.io/wazimap-ng/point-mapper/shaping-data-for-point-collections.md).

# Shaping Data for Point Collections

The easiest tool to create or edit .csv files is Google Sheets — it can open both .csv and .xlsx files, and can export .csv files for upload to Wazimap NG. Any point collection requires the following three fields (as highlighted in red in Figure 2, below):

1. **`name`**;
2. **`longitude`**; and
3. **`latitude`**.

<figure><img src="/files/jCeIvd9uEoXXagzz42w7" alt=""><figcaption><p>Figure 2: The three fields (in red) required for any point collection</p></figcaption></figure>

As shown in Figure 2, above, additional fields can be included as attributes for each point in the collection. In the Point Mapper view, these additional attributes are displayed in the More Info section of each point’s tooltip (refer to [**`Navigating Point Mapper`**](/wazimap-ng/point-mapper/navigating-point-mapper.md)).

The **`name`** field (column) of your point collection cannot be formatted as a number. It may be necessary to format the entire column to plain text by selecting the entire column and clicking **`Format > Number > Plain text`** (see Figure 3, below).

{% hint style="warning" %}
Since the attributes under the `name` column are displayed on the tooltip in Wazimap NG, it is important to label your points appropriately (refer again to [**`Navigating Point Mapper`**](/wazimap-ng/point-mapper/navigating-point-mapper.md)).
{% endhint %}

<figure><img src="/files/iYbrPNngcCX5Fi9eZPuv" alt=""><figcaption><p>Figure 3: Formatting the Name column to plain text in Google Sheets</p></figcaption></figure>

Additionally, column headings cannot start with a number (e.g., <mark style="color:red;">**`2019`**</mark>**` ``HDI`**), contain periods (e.g., **`SDG 3`**<mark style="color:red;">**`.`**</mark>**`1`**), or contain square brackets (e.g., **`HDI over the Years`` `**<mark style="color:red;">**`[`**</mark>**`Average`**<mark style="color:red;">**`]`**</mark>).

{% hint style="warning" %}
No cell within the first row below the column headers can be left blank either — if no attribute exists in these cells, simply add **`no data`**. A blank cell will result in that attribute not being displayed for any points (even if they have a value).
{% endhint %}

Once your point collection is complete (has the three required fields, is formatted correctly, and contains no blank cells in the first row), it can be exported as a .csv file. To do this, click **`File > Download > Comma-separated values (.csv)`** (see Figure 4, below).

<figure><img src="/files/kGakJsnv1bMMnvFFPZRd" alt=""><figcaption><p>Figure 4: Exporting a point collection as a .csv file from Google Sheets</p></figcaption></figure>

{% hint style="warning" %}
Take note of where this .csv file downloads to — you will need to locate it for upload to Wazimap NG later.
{% endhint %}


---

# 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://openup.gitbook.io/wazimap-ng/point-mapper/shaping-data-for-point-collections.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.
