> For the complete documentation index, see [llms.txt](https://water-strategy.gitbook.io/waterstrategy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://water-strategy.gitbook.io/waterstrategy/ardw/ma-lng-ky-bnyad/node-types/water-transport/link-node.md).

# Link Node

## عمومی تفصیل

دی **link node** پانی کے نظام یا دلچسپی کے دوسرے نقطہ میں ایک لنک کی نمائندگی کرتا ہے جہاں زیادہ سے زیادہ یا کم سے کم بہاؤ کی رکاوٹ یا مختص کی ترجیح تفویض کی براہ کرم Pywr میں نوٹ کریں، کناروں (لنکس) کو بہاؤ کی حدود تفویض نہیں کی جاسکتی ہے اور لہذا لنک نوڈس اکثر اس مقصد کے لئے استعمال ہوتے ہیں۔ [API حوالہ](https://pywr.github.io/pywr-docs/master/api/generated/pywr.nodes.Link.html).

## بنیادی خصوصیات

\_بہاؤ

<table><thead><tr><th width="181.33333333333331">نام</th><th width="342">تفصیل</th><th>مطلوبہ</th><th></th><th></th></tr></thead><tbody><tr><td>مختص جرمانہ</td><td>نوڈ کے ذریعے فی یونٹ لاگت بہاؤ</td><td>اختیاری</td><td></td><td></td></tr><tr><td>زیادہ سے زیادہ_</td><td></td><td></td><td></td><td></td></tr><tr><td>بہاؤ</td><td>نوڈ پر زیادہ سے زیادہ بہاؤ کی رکاوٹ اختیاری</td><td>منٹ</td><td>نوڈ پر کم سے کم بہاؤ کی رکاوٹ</td><td>اختیاری</td></tr></tbody></table>

## مثالیں

جلد آرہا ہے...


---

# 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://water-strategy.gitbook.io/waterstrategy/ardw/ma-lng-ky-bnyad/node-types/water-transport/link-node.md?ask=<question>&goal=<user_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.