How to import Net Loads using a GeoJSON
Revision as of 15:12, 30 January 2024 by Frank@tygron.nl (talk | contribs)
It is possible to import a GeoJSON file to add net loads to a project.
It is also possible to select the option of importing data in the Net wizard. In both cases, it is recommended to import all network geojson files at the same time where possible: net lines, net line definitions, and net loads.
The net loads GeoJSON file should be composed of point data with the following attributes.
Attribute | Description | Example | Remark |
---|---|---|---|
NAME | The name of the net load. | NetLoad 49 | |
NET_TYPE | The type of network this net load belongs to | HEAT | Note that when connecting net loads and net nodes or net lines of different network types while importing, this is considered incorrect input and behavior of the Tygron Platform will be undefined. |
STATE | Whether the net load is connected or not. | NOTHING | Any of the timestates mentioned in this article are valid. |
NODE_ID | The ID of the net node this load belongs to. | 17 | If this file is being imported along with a net lines file, this NODE_ID should match the START_NODE_ID or END_NODE_ID of one of the simultaneously imported net lines. Otherwise, the load will not automatically be associated with a node. |
CLUSTER_ID | The ID of the net cluster this load should belong to. | 4 | The cluster of net loads this net load should belong to. A cluster is not created automatically, but after importing these clusters can be created using a cluster generation algorithm. |
ROOT_LOAD | Whether this net load is a root load or not | 0 | 1 = root load (producer), 0 = a regular load (consumer) |
ADDRESSCODE | The postcode this net load is related to. | 2514EG 46 | When a net load has a postcode which is also associated to a building, the net load is automatically linked to that building. |