-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix topological errors within 380 and 220 kV level with respect to ENTSO-E map #10
Comments
Just to be sure, I should try to connect them by subgrid connection algorithms and if that doesn't work change openstreetmap.org? |
the subrid connection algorithm is already implemented by @lukasol ... Your task would be to change osm by looking at the ENTSO-E map. That way the algorithm would not be needed not that much and we get more realistic data and at the same time give that effort back to osm... |
Okay, sorry for misunderstanding. Up to now, I have never worked with osm. |
The key voltage defines the voltage of a cable in osm. If you take for example this power line from Lübeck to Siems at has a voltage of 110 kV. On the same route there is a 220 kV (ENTSO-E grid map) missing which you could add to openstreetmap. Actually it seems that there is not a line missing (see also satallite pictures like at bing or google) but there is 2 lines with each 6 cables (2 systems). It total there are 4 systems of 110kV but I would think that at least one the systems is a 220kV. If it is like that. It would be an relatively easy change. You would not have to add a new line and think about where to but it (including the poles) but only have to change the voltage level of the particular system from 110000 to 220000... |
if your about to have some trips to places it like that in Schleswig-Holstein you could also use and check out this app |
I just added a 220kV from Lübeck to Siems, hopefully that was right. |
Fix topological errors within 380 and 220 kV.pptx I've collected everything I've found in a PPP. In some cases I could not see anything causing the error. |
Cool, thx! Could you also upload it as a pdf? |
I would like to fix the errors but, apart from the Lübeck Siems connection, we have not discoussed how I should do this... |
I am sorry I am not sure about the 'take-home-message'. Can you fix what is wrong in osm? Change 110kV to 220kV(did I understand it more-or-less right?)? At the same time do you think you can fix it in the post-processing being part of the data processing (as we discussed it)? |
@lukasol I just mention you here so you are informed. Clara and I went through that presentation (see pdf above) which tried to cover the cases which popped up in the context of the ehv clustering. |
Yes, I would change the voltage level and delete a line I can't see on satelite pictures. |
I just changed some voltage levels from lines in Uchtelfangen in osm respecting bing and entso-e. |
I added the script to the feature branch. Up to now there are still some problems. |
I added electrical parameters to the lines, I took the one for transmission lines, as listed on GitHub. |
I was just looking at the problem again. I'm afraid I had to notice that the script I wrote won't work. It deletes buses which are needed for components like generators. In some cases, the power is very small and it can be reconnected to a bus with the same geom, but not always. |
Here are some new information about the subnetworks: In Berlin, there are 380kV lines and buses which shouldn't be there in respect to entso-e. Two buses (Umspannwerk Lichtenberg and Umspannwerk Biesdorf Nord) are used to connect a small solar generator and/or loads. In the osm both are tagged as 110kV stations, and there are 110kV buses in our data. That's why I suggest to reconnect the generator and the loads to the 110kV buses and delete the 380kV buses and lines. The industrial park in Höchst has a subnetwork due to a 220kV line inside. The osm is nor sure, if it's 220kV or 110kV. Looking at the website of the park, it says they only have high voltage and not extra high voltage. In addition there are mostly 110kV buses with the same geom like the 220kV buses. So I would change the voltage of the line to 110kV by reconnecting it to the 110kV buses and delete the 220kV buses. The subnetwork in Plattling is caused by a line, which looks different in osm. The substation is divided into two parts, one transforming from 380kV to 110kV and one only with 110kV. But in our data, both have an 380kV bus and are connected via a line which doesn't exists in osm and satellite pictures. There is a quite similar line, connecting the substation to the nearest 380kV line, which is missing in our data. I suggest to delete the line between the substation parts and add the missing line. The subnetwork in Weisweiler is just one 380kV bus. In our data, it's just connected via a transformer, but in the osm, there are connections to the next 380kV line as well. So I would add a line, like in the osm, that connects the 380kV bus to the 380kV line. All buses are already there, I just need to connect them. When you agree with the suggestions, I would test it local in the next days. |
nice @ClaraBuettner . Your suggestions sound reasonable. We just have to be very careful if we change voltage levels of buses. Especially when we change 380/220 kV buses to 110kV buses. |
For my thesis, I would reconnect the one-ports to existing buses, so it can be used as a post-processing. Most often, there are already 110kV buses when I need them, there is just one 220kV bus I need to change to 110kV. |
Can you check if the 380kV buses which you want to delete have loads and generators connected? |
I already did it, they are listed in the table as generators, loads and storages |
I finished the documentation and am currently testing most of the suggested options. Just the one in Pleiting is missing up to now. I need to connect the substation to an existing line, but there is no bus at the position I have to do that. So I'm wondering if pypsa needs lines with the same buses to know that they are connected, or if it's enough that they touch. I suggest the first option, but that would mean I have to split up an existing line. That's why I'm not sure what to do. |
Like you suggest it is not enough if they geographically touch. I think you would have to delete the existing line which you want to split up and then built a new bus and three new lines... The buses with generators/loads/storages attached are crucial. Can you check how much installed power these units have? It would be good to attach them to the most adequate bus around with respect to our assignment methodology. Maybe @IlkaCu can help you with that. By the way, are you working with the newest data set (v0.3.0)? The amount of storages in Berlin seem a bit weird to me... |
It worked! I created a new busmap overnight and could run the eHV-clustring with just one sub-network, which is the one in Plattling I havn't adjusted yet (as you can read above). Looking at the geometries with qGis, everything worked fine. So I just need to find a method for the last one. |
Ok, then I will adjust this like you said. |
For the generators and storages in Berlin, I somehow made a mistake in the documentation. There is only one 63kW solar generator and two storages with p_nom = 0 in each scenario. |
@ClaraBuettner: If you like, we can meet this week and discuss how your changes interact with the DP and how we can bring both together. |
That would be great! Can you tell me when you have time for that? |
good and thx @IlkaCu! the storages are extendable storages and therefore do not have p_nom values. They are optimization variables - so you do not have to care about them in this case. |
Tomorrow 15:30? |
Yes, that's fine. |
@ClaraBuettner: Is there anything which needs to be added to the branch feature/fix_eHV_subnetworks before merging it back into the dev branch? |
Some lines won't be needed anymore when it's included earlier. |
When abstracting the 380 and 220 kV grid some sub grids are occurring which obviously are stating errors mainly due to osm data issues. See this issue for more information on these locations.
Apart from developing and using subgrid connection algorithms we want to use the ENTSO-E grid map in order to fix these errors by changing openstreetmap.org
@ClaraBuettner : I think that could be a fun job for you. What do you think? Do you need any more details? Just contact me when you have time for this.
The text was updated successfully, but these errors were encountered: