> For the complete documentation index, see [llms.txt](https://docs.os.uk/osngd/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/osngd/code-lists/code-lists-overview/tidalboundarycontinuoushighdescriptionvalue.md). # tidalboundarycontinuoushighdescriptionvalue This code list is used in association with the Description attribute which is present within the Tidal Boundary Continuous High Feature Type. The code list describes the state of the tide that the feature represents (for example, Mean High Water or Normal Tidal Limit).
LabelDefinition

Mean High Water

The average alignment of the high tide line that occurs halfway between spring and neap tides. Represented in England and Wales only.

Mean High Water Springs

The average alignment of the high tide line that occurs when the effects of the sun and moon are in alignment, resulting in a larger than normal tidal range. Represented in Scotland only.

Normal Tidal Limit

The highest point in tidal rivers to which mean tides (in Scotland, mean spring tides) flow at high water where there is no other feature present.
--- # 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/osngd/code-lists/code-lists-overview/tidalboundarycontinuoushighdescriptionvalue.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.