> For the complete documentation index, see [llms.txt](https://docs.moasure.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moasure.com/en/moasure-1-and-2-series/what-you-can-measure/measure-tree-or-sprinkler-locations-on-a-lawn.md). # Measure Tree or Sprinkler Locations on a Lawn Trees, sprinklers and other locations within a lawn or open space can be measured using Moasure. There are two ways to capture these locations: * Using a **single measurement** * By measuring the lawn first and then adding a [**new layer**](/en/moasure-1-and-2-series/measure-and-edit/master-layers/measure-layers.md) Both methods are explained below. *** ## Single Measurement ### 1. Measure the Lawn Perimeter * Start by measuring the lawn perimeter as a closed shape. * Return to the start point without ending the measurement. ### 2. Capture Tree or Sprinkler Locations * Change the path type to **Points Path**. * Move toward the first tree or sprinkler location. * Place the device at the required position and wait for confirmation. * Repeat until all locations are captured. If a location cannot be reached within the recommended **6–8 second movement time**, switch temporarily to **Ignore Path** while moving and stop as needed along the route. Any intermediate stops will be marked as **Ignore Points** so they can be visually distinguished from measured locations. You can also ignore points after measurement if required. ### 3. Complete the Measurement * End the measurement once all tree or sprinkler locations are marked. *** ## Layers ### 1. Measure the Lawn Perimeter * Start by measuring the lawn perimeter. * Return to the start point. * End the measurement. ### 2. Add a New Layer * Tap the **Layers** icon in the lower-right corner of the app. * Tap **Add Layer**. You will be prompted to place the device at the **shared origin**, which is the start point of the first measurement layer. Once the device is stationary at the shared origin, the app will guide you to move along the original starting edge. These steps allow Moasure and the app to align the new layer with the original measurement so both layers share the same position and orientation. During this alignment process, the app temporarily uses **Ignore Path** before prompting you to begin measuring the new layer. ### 3. Capture Tree or Sprinkler Locations * Change the path type to **Points Path**. * Move toward the first tree or sprinkler location. * Place the device at the required position and wait for confirmation. * Repeat until all locations are captured. If a location cannot be reached within the recommended **6–8 second movement time**, switch temporarily to **Ignore Path** while moving. Any intermediate stops will be marked as **Ignore Points** so they can be visually distinguished from measured locations. You can also ignore points after measurement if required. ### 4. Complete the Measurement * End the measurement once all locations are marked. *** ## Viewing Trees and Sprinkler Locations ### 1. View in the App #### Single Measurement When using a single measurement, both the lawn perimeter and location points appear within the same layer. #### Layers When using Layers, the lawn perimeter and location points appear on separate layers. Layers can be shown or hidden as required, making larger or more complex projects easier to manage. Tap any point, whether on the perimeter layer or points layer, to view its **X, Y and Z coordinates**. You can also **label or annotate points** to make tree, sprinkler or feature locations easier to identify later. [Labels ](/en/moasure-1-and-2-series/measure-and-edit/master-edit-tools/edit-label.md)and [annotations](/en/moasure-1-and-2-series/measure-and-edit/master-edit-tools/annotate.md) can improve clarity when reviewing, sharing or exporting measurements. #### Choosing Between Methods **Single Measurement** * Faster and simpler * Suitable for smaller projects * Keeps everything within one measurement **Layers** * Better organisation * Allows boundaries and points to be managed separately * Offers greater flexibility for editing later Choose the method that best suits your project and workflow. *** ### 2. View on PDF If you wish to display coordinates on a PDF export, points must be **labelled before exporting**. Coordinates from **Points Path** or **Ignore Path** that are not labelled will not appear on the PDF. You can label or annotate locations such as trees, sprinklers or landscape features to make them easier to identify later and when sharing measurements. If coordinate visibility on the PDF is not required, you may skip labelling and the points will still appear visually within the drawing. If points are labelled: * Their coordinates appear on the PDF export * Labels appear within the **Labelled Points** section of the PDF * Point locations become easier to identify and reference later *** ## Best Practice For the best results: * Use **Single Measurement** for smaller lawns or fewer locations * Use **Layers** for larger or more complex projects * Use **Ignore Path** when moving between distant locations * Label points before exporting if coordinates are required on a PDF * Allow each point to fully confirm before moving again *** ## Result Once complete: * Tree and sprinkler locations appear within the drawing * Coordinates can be viewed in the app * Labels and annotations help identify locations more easily * Labelled points can be displayed on PDF exports * Lawn boundaries and location points can be managed together or separately depending on your chosen method --- # 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://docs.moasure.com/en/moasure-1-and-2-series/what-you-can-measure/measure-tree-or-sprinkler-locations-on-a-lawn.md?ask=&goal= ``` `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.