> 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/italiano/nozioni-di-base-sulla-modellazione/node-types/water-transport/riversplit-node.md).

# RiverSplit Node

## Descrizione generale

Le **RiverSplit node** è una spaccatura nella rete fluviale. È destinato a un caso semplice in cui è necessario distribuire un rapporto di flusso fisso su più rotte a valle. [API Riferimento](https://pywr.github.io/pywr-docs/master/api/generated/pywr.domains.river.RiverSplit.html).

## Attributi primari

).

<table><thead><tr><th width="180.33333333333331">Nome</th><th width="355">Descrizione</th><th>Richiesto</th></tr></thead><tbody><tr><td>fattori</td><td>I fattori da imporre alle divisioni aggiuntive. Numero di extra_si presume che lo slot sia inferiore di uno alla lunghezza dei fattori (come da documentazione <em>pywr.nodes.MultiSplitLink</em></td><td>Slot</td></tr><tr><td>opzionale_nomi</td><td>Gli identificatori a cui fare riferimento agli slot quando ci si connette da questo Nodo. La lunghezza deve essere maggiore di uno rispetto al numero di slot aggiuntivi richiesti.</td><td>Facoltativo</td></tr></tbody></table>

## Esempi

presto in arrivo...


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://water-strategy.gitbook.io/waterstrategy/italiano/nozioni-di-base-sulla-modellazione/node-types/water-transport/riversplit-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 `build a script that syncs our docs to a CMS` 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.