> 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/points-of-interest/points-of-interest-classification-scheme/attractions.md). # Attractions ## 16 Botanical and zoological * **0231** Aquaria and sea life centres * **0232** Bird reserves, collections and sanctuaries * **0233** Butterfly farms * **0235** Farm-based attractions * **0236** Horticultural attractions * **0237** Salmon ladders * **0239** Zoos and animal collections ## 17 Historical and cultural * **0240** Archaeological sites * **0241** Battlefields * **0244** Historic buildings including castles, forts and abbeys * **0245** Historic and ceremonial structures * **0246** Historical ships * **0248** Museums * **0813** Art galleries ## 18 Recreational * **0252** Commons * **0253** Country and national parks * **0254** Picnic areas * **0255** Playgrounds * **0814** Municipal Parks and Gardens ## 19 Landscape features * **0257** Designated scenic features * **0259** Trigonometric points ## 20 Tourism * **0263** Laseria, observatories and planetaria * **0264** Model villages * **0265** Railways (heritage, steam and miniature) * **0266** Theme and adventure parks * **0267** Sightseeing, tours, viewing and visitor centres * **0268** Information centres * **0269** Unspecified and other attractions ## 58 Bodies of water * **0804** Lakes and waters * **0805** Lochs and lochans * **0806** Tams, pools and meres * **0807** Reservoirs --- # 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/points-of-interest/points-of-interest-classification-scheme/attractions.md?ask=&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.