> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-downloads/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/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification/example-records.md).

# Example records

The following section provides example records for both the CSV and GML supplies. Please note that the data given is to provide an example only and should not to be used as accurate data.

## CSV supply <a href="#id-5.1_csv_supply" id="id-5.1_csv_supply"></a>

### Original feature – AddressBase CSV <a href="#id-5.1.1_original_feature_-_addressbase_csv" id="id-5.1.1_original_feature_-_addressbase_csv"></a>

{% code overflow="wrap" %}

```
100100077917,"osgb1000002283010753",4201646,"","", "","","",166,"","LLANDAFF
ROAD","CARDIFF","","","CF11 9PX","S",316348.00,177163.00, 50.7268511, -3.5366289, 1,"E","I",2001-05- 10,2001-05-10,2007-08-29,"R"
```

{% endcode %}

### COU feature – AddressBase CSV <a href="#id-5.1.2_cou_feature_-_addressbase_csv" id="id-5.1.2_cou_feature_-_addressbase_csv"></a>

{% code overflow="wrap" %}

```
Changed fields are highlighted in red. 100100077917,"osgb1000002283010753",4201646,"","", "","","",166,"","LLANDAFF
ROAD","CARDIFF","","","CF11 9PX","S",316348.00,177163.00, 50.7268511,- 3.5366289, 2,"E","U",2001-05- 10,2001-05-10,2010-06-04,"R"
```

{% endcode %}

## GML supply <a href="#id-5.2_gml_supply" id="id-5.2_gml_supply"></a>

### Original feature – AddressBase GML <a href="#id-5.2.1_original_feature_-_addressbase_gml" id="id-5.2.1_original_feature_-_addressbase_gml"></a>

Please note how not all attributes are provided where the field is null.

<pre class="language-xml" data-overflow="wrap"><code class="lang-xml">
  
<strong>    100040205844
</strong>    osgb1000002274362298
    8782432
    FLAT C
    PEMBROKE HOUSE
<strong>    4
</strong>    BYSTOCK TERRACE
    EXETER
    EX4 4HY
    S
<strong>    
</strong>      
        291640.00 93040.00
      
    
    
<strong>      
</strong>        50.7268511 -3.5366289
      
    
<strong>    1
</strong>    E
<strong>    I
</strong>    2001-04-04
    2001-04-04
    2001-04-04
    R
  

</code></pre>

### COU feature – AddressBase GML <a href="#id-5.2.2_cou_feature_-_addressbase_gml" id="id-5.2.2_cou_feature_-_addressbase_gml"></a>

<pre class="language-xml" data-overflow="wrap"><code class="lang-xml">Changed fields are highlighted in red.

<strong>  
</strong>    100040205844
    osgb1000002274362298
    8782432
    FLAT C
    PEMBROKE HOUSE
    4
    BYSTOCK TERRACE
    EXETER
    EX4 4HY
    S
    
      
        291640.00 93040.00
      
    
    
      
        50.7268511 -3.5366289
      
    
    2
    E
    U
    2001-04-04
    2001-04-04
    2010-06-04
    R
  

</code></pre>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification/example-records.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.