> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/data-analysis/creating-queries/parameterized-queries.md).

# Parameterized Queries

**Parameterized queries** use placeholder variables that GeoDin prompts for when the query runs. They let one query template serve many specific filters (e.g. "find objects in project ?ProjectID with depth > ?MinDepth").

Parameters are defined in the Query Builder with a name, type, and optional default value. At runtime, GeoDin shows a dialog listing each parameter and capturing the user's input before executing the query.

## Using result fields for Shape export

The **Result fields (Export)** node in the query wizard determines which data fields are included in the attribute table when the query result is exported as a Shape file.

To enable Shape export of measurement values (e.g. chloride concentrations):

{% stepper %}
{% step %}

#### Step 1: Open the display fields step

In the query wizard, go to the **Set display fields** step.
{% endstep %}

{% step %}

#### Step 2: Add the parameter fields

Drag the desired parameter fields (e.g. `GWC.CHLORIDE`) onto the **Result fields (Export)** node.
{% endstep %}

{% step %}

#### Step 3: Save the query

Save the query. In the Maps module, the query layer will now expose these fields for labelling, interpolation, and Shape export.
{% endstep %}
{% endstepper %}

Without result fields, the Shape export contains only geometry and the object ID. Adding measurement parameters here is the prerequisite for generating interpolation maps or contour layers from query results.

{% hint style="info" %}
Queries on the **Measurement Points** branch work the same way - result fields defined there are exported alongside the measurement point geometry.
{% endhint %}

For the comprehensive reference - full syntax, all options, edge cases - see [**Creating Queries**](/data-analysis/creating-queries.md) (long-form) and [**Query Builder Reference**](/data-analysis/query-builder-reference.md).


---

# 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.geodin.com/data-analysis/creating-queries/parameterized-queries.md?ask=<question>&goal=<endgoal>
```

`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.