> 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/maps-and-imagery-portfolio/os-mastermap-topography-layer/os-mastermap-topography-layer-technical-specification/gml-overview/gml-examples.md). # GML examples ## GML examples of feature types and their attributes This sub-section provides examples of how the feature types in the product are presented in GML format. ### TopographicPoint ```xml 10085 1 2014-01-15 Water 8.0m 2013-11-12 New Inland Water Culvert Manmade 50 451492.790,1204378.760 ``` ### TopographicLine ```xml 10046 2 2014-01-15 Land 8.0m 2008-10-30 New 2010-03-15 Restructured 2013-12-06 Modified General Feature Overhead Construction true Manmade 51 454659.199,1201041.044 454727.470,1201075.210 ``` ### TopographicArea ```xml 10203 3 2008-11-18 Water 2.085024 2001-02-17 New 2005-11-10 Attributes 2008-11-13 Attributes Tidal Water Foreshore Natural 50 454554.900,1202300.000 454554.000,1202300.100 454553.300,1202299.500 454553.400,1202299.000 454553.800,1202298.400 454554.600,1202298.500 454554.900,1202299.200 454554.900,1202300.000 ``` ### BoundaryLine ```xml 10131 4 2008-04-20 Administrative Boundaries 2.5m 1999-05-12 New 2002-06-26 Attributes 2005-11-10 Attributes 2008-04-16 Reclassified Political Or Administrative District 50 Boundary 454331.400,1202522.200 454332.400,1202517.400 ``` ### CartographicSymbol ```xml 10082 2 2006-03-01 Water 1994-02-14 New 2005-11-10 Position Inland Water Direction Of Flow 3303 50 Indicator 452648.430,1204142.340 ``` ### CartographicText ```xml 10090 2 2002-07-13 Water 450063.500,1203882.000 1994-11-25 New Inland Water Natural 50 4 1 11 0 Ponds ``` --- # 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/maps-and-imagery-portfolio/os-mastermap-topography-layer/os-mastermap-topography-layer-technical-specification/gml-overview/gml-examples.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.