> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/forms/form-elements/form-features-plotted-sections.md).
# Form Features - Plotted Sections
## Overview
This article explains how to configure the **Plotted Sections** element.
This article explains:
* [How **Plotted Sections** work](#how-plotted-sections-work)
* [How to configure **Plotted Sections**](#how-to-configure-plotted-sections)
* [Demo of **Plotted Sections** with a Building Inspection Example](#demo-building-inspection-example)
## Getting Started
### How Plotted Sections work
The **Plotted Sections** element uses a sketch as the entry point for a [**Repeated Section**](/forms/form-sections-and-repeated-sections/sharinpix-form-sections-and-repeated-sections-1.md).
Each time a user places a marker on the sketch:
* A new repeated section item is created.
* That item stores the details related to that marker.
* The form can capture structured data for every marked location.
This creates a direct link between the marker location and the data entered for it.
This pattern works well when users need to mark a visual position first, then describe what was found.
{% hint style="info" %}
Use the repeated section template to define which fields are created for each marker, such as **Area Inspected**, **Condition**, **Issues Present**, or **Description of Issues**.
{% endhint %}
### How to configure Plotted Sections
Follow these steps to configure **Plotted Sections** on your form.
* On the Form Editor page, add the **Plotted Sections** element to your form.
* Open the **Plotted Sections** configuration.
* Click **Edit section** to define the repeated section template that will be created for each marker.
* Add the background image and configure the markers that users will work on.
* Add the fields that users must complete for each marked point, such as **Area Inspected**, **Condition**, **Are there any issues?**, and **Description of Issues**.
Each time a user places a marker on the sketch, the form creates one repeated section item linked to that marker.
{% hint style="info" %}
**Info:**
For more information on configuring repeated section items, please follow the article: [SharinPix Form - Repeated Section](/forms/form-sections-and-repeated-sections/sharinpix-form-sections-and-repeated-sections-1.md)
{% endhint %}
### Demo: Building Inspection Example
This section demonstrates how to use **Plotted Sections** in the context of a building inspection. The inspector marks locations on a building sketch, then captures the condition and any issues found for each marked area.
Follow these steps to configure **Plotted Sections** on your form:
* Add the **Plotted Sections** element to the form.
* Open **Edit section** and add the fields that should be completed for each marker:
* **Area Inspected (Interior/Exterior)**
* **Condition**
* **Are there any issues?**
* **Description of Issues**
* When filling out the form, place a marker on each inspected area of the sketch.
* Complete the repeated section item created for each marker.
### Results:
#### Example 1 - Single Inspection Point
* When the inspector places one marker on the building sketch, the form creates one repeated section item for that location.
* The inspector can then record whether the area is **Interior** or **Exterior**, describe the condition, and note any issues.
#### Example 2 – Multiple Inspection Points
* If the inspector places several markers on the sketch, the form creates one repeated section item for each marker.
* This allows every inspection point to keep its own details while staying linked to its location on the sketch.
---
# 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.sharinpix.com/forms/form-elements/form-features-plotted-sections.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.