## 2 Methods and Data
### Topology and Inputs
From the first one, the unique ID and the UNP coordinates of each bus can be extracted, and from the second one, the line types can be read. Consumer IDs, the types, and IDs of the objects where the consumers are connected, and the UNP coordinates, are available from files belonging to the consumers. Finally, by opening all but the first three of the fifteen files and recursively searching for each connected object, the network can be built, and clear consumer-line assignments can be specified. UNP coordinates are required because in the INIS data structure, consumer-line pairs are defined. Thus, in each case, based on the distance data, it can be decided to which end of the line the given consumer can be connected. This INIS query was refined as follows. Typically, in the INIS registry, as it was mentioned earlier, some buses are not created. In this case, the consumers connected to these buses will be connected elsewhere. (In practice, some lines are merged in the INIS data structure, and each of their consumers are connected to the endpoints of the merged lines.) According to the standard method of E.ON, the following process is carried out using the contribution of the company's internal Neplan-Excel conversion as well. E.ON DSO's LV grid mostly consists of overhead lines. The database of the DSO currently does not contain information on the individual poles, only the line segments, though customers are always connected to the networks at poles. The DSO possesses geographical data on the position of the customer's consumption meter from the periodic readings or the installation of new meters. Therefore, creating segments with the length of the usual distance between poles offers a possibility to estimate the connection point of customers with the assumption that the customer is connected to the nearest 'virtual' pole. This method reduces the error of the voltage profile and loading estimation, as the distribution of the loads and generators are closer to the actual positions, while it does not require the process of any connection plans. To achieve this, the line segments in the examined network are scanned continuously, one after the other, and their length is checked. If it is below 50 m, it can be assumed that a line segment of this length between two poles can exist, so the algorithm continues the iteration to the next line. However, for line segments longer than this, the scanned length is divided by 30 m as the typical pole distance. Thus, an approximate number of pieces can be obtained for how many line segments the given element can actually consist of. The algorithm calculates the floor and the ceiling of this approximate number, from which it is advisable to choose the one that results in a segment length closer to 30 m. Thus, in the case of \(l_{l}\), the line will be divided by the floor of the approximate number; and in the case of \(l_{c}\), the line will be divided by the ceiling of the approximate number, and each consumer will be connected to the nearest bus. This algorithm (referred to as manipulated INIS model) is shown in Figure 3, where the red arrow indicates the case where manipulation is required due to a line longer than 50 m.  
It must be emphasized that this approach does not neglect any element of the network itself but the connection between the LV branch and the point of delivery. This situation is usually also handled by the planning principles of the network (as there is a difference between the prescribed voltage limits for the LV branch and the point of delivery--currently 2.5% of nominal voltage in Hungary). These short lines (typically only a few meters) connect the customers as parallel elements; therefore, they do not alter the electrical attributes of the network significantly, which is accessible at the DSO information systems. This method--which is based on the modeling approach currently used by the DSO as well--can be automated and assigns the customers to the 'virtual' poles to assume the loading distribution accurately.