Purpose of the construction work N7 autosnelweg Groningen

Hello and Sorry, I can’t write in Dutch.

In Groningen there is a major construction site on the N7 that has been going on for two years and does not seem to be finished yet. Is the purpose of the construction work to turn the N7 autosnelweg into an A7 motorway?

Thank you very much for an answer.

I don’t know the area myself but according to these websites, it will take another two years until it is fully finished. It seems like there are numerous things changing, such as part of the autosnelweg shall be lowered underground and several junctions will be greatly changed.

The websites are in dutch and i can’t seem to find an official translated page for it.


Map of current construction: https://slimmekaart.groningenbereikbaar.nl/nl/embed/key/ukonist#!/

I can help myself with a translation machine. Thank you for the links. :slight_smile: In fact, OpenStreetMap is used there :sunglasses::
(scroll down)

No, afaik it will stay an “autoweg” (motorroad) even though the profile becomes more highway-like: no junctions with lights anymore, all on- and offramps, and a tunnel under the “Sterrebos”.

With the help of your infos, I was able to find a visualisation of the desired state on Youtube. In particular, the redesign of the traffic-light-crossing at the “Julianaplein” and the tunnel under the “Sterrebos” become clear. In this video at 1:05 min, the road is still labelled “N7”.

If anyone is interested:

Theoretically, one could use it to map the complete “whatever=construction”-site on OSM. However, this could lead to the current stäte being poorly recognisable. The disadvantages could outweigh the advantages.

At the moment OSM navigators do not consider that the longest main route of the Netherlands, the Rijksweg 7, is long-term interrupted in Groningen between “Knooppunt Euvelgunne” and “Europaweg”:

By means of a webcam at the exit on the Europaweg it can be seen on the Internet, that there is no physically existing road.

IMHO, at least that should be mapped in OSM. Otherwise it is not useful even for large scale navigation. For example, for me passing border from Germany at Nieuweschans, it is more convenient to leave the Rijksweg already at the exit Westerbroek and from there to use the Europaweg.

This would be routed by the OSM Navigator, if there were a construction site markings on the Rijksweg. This is how we do it in Germany. I do not know if this is also common in the Netherlands. If no objection, I would map the section as a construction site.

Besides this break, there are many routes around the exits of Rijksweg 7 that can’t be used either. But those could only be mapped by someone with signed local knowledge, which I don’t have and therefore don’t do. I only experience the interruption of the Rijksweg.

Those roads will be open again by the end of August. I consider this as a short term interruption.
As stated on the Wiki :
“As OSM data is often used offline (and therefore may be several months old), only tag construction sites if they are planned to be closed for at least six to nine months.”

Even for short term road closures you can tag the road with conditional restrictions. For example:

access:conditional=no @ (start_date - end_date)

But as Henk rightfully mentioned the value of this tag is rather limited.

I’m not sure if this is still valid. More and more apps use either “live” data or refresh data more often than once every six months.

What is the harm to use a conditional access? If a router can’t handle it, no harm is done. If it can handle it, it should use an alternative route during the time given in the conditional access, even if we (mappers) forget to re move the conditional tag when the construction site is gone.

My stance on roadworks like these:

  • If the new situation is similar to the old situation: don’t close or use conditional closures (depending on road status and construction duration)
  • If the new situation if different from the old situation (different layout of junctions, alignment moved etc), close them off immediately after they are closed on the ground. If possible, map the new situation already and open on the day it opens.

In this case the second option should be chosen.

People who use (near-)live maps will have the right maps.
People who update infrequently will always have problems. They might get a snapshot of a road just when it was closed. But they might miss roads that are new or completely moved overnight (e.g. a bridge that was closed and a new bridge opened a few hundred metres further down the river). There is no solution to make both people happy. I would chose for

It would be cool if you could map conditional construction, something along the lines of

highway:conditional=construction @ (jan 1 2022 - jun 30 2022); motorway @ (jul 2022 - )
construction:conditional=motorway @ (jan 1 20222, jun 30 2022) 

such that at july 2022 the road would automatically jump from construction to motorway.

And as an addition: for longer-duration closures, construction should be used and not “access”. It is very inconvenient to have to debug routing when no visual cues are available to see why a certain route is not taken.
I have experienced this myself when I had made a highway-offramp close to my house accessible only during peak hours (which was the actual case for 3 months) then left it at that value for 3 years before noticing this when I changed the final version. All the time I had wondered why Osmand at times suggested me the one route, at other times the other one.

Current construction is maintained by 85Bas. I don’t agree with all his ediits, but in general he follows the thoughts mentioned above.
The final end of construction should be 2025, with 2024 as the year traffice should be able to use the Julianaplein again.
The Julianaplein will become a multi-level crossing hidden in a hill, allready known locally as the ‘teletubby-hill’. A hill I can ‘admire’ out of my window.

Short constructionworks/closures should not be tagged as there are clearly marked detours. These detours are specifically designed to prevent congestion on minor roads and additional traffic in living aerea’s. Routers however tend to reroute using the shortest route, which is undesirable to those who live along these streets.
If, like Tirkon suggests, all traffice from Germany would use exit Westerbroek, the Europaplein would become congested. That is why the official detour is using the north and west of the ‘ring’.

@IIVQ I tried a conditional construction on a cycleway once, but found that routers don’t deal with them.

You’d be forgiven for thinking that, since you’re probably used to the infamous German Baustellen. However, this part of the road is only closed for six weeks and like others have said this should not be represented on the base layer (besides, optionally, access:conditional).

While it is true that I do a lot of edits pertaining to the southern ring road, I am definitely not the only one. So many things are changing every week and I cannot possibly keep track of everything. I am very thankful others are making edits as well and this project is by no means “claimed” by me.

One thing I don’t have time for, for example, is adding conditional access tags to every short term road closure (and there are many). Other mappers are very welcome to add those if they feel like it.

I personally use navigation apps with a secondary traffic layer that keeps track of road closures and other traffic problems, on top of the OSM base layer. To me, this is the most logical way to display temporary changes. I believe that is the standard we should follow when mapping (as mentioned in the wiki article linked by HenkL). There is no mapping service on earth that would add changes as temporary as the current N7 closure to its base layer.

Thank you for this information. I did not find it in Dutch. Something like that is the reason I posted it on the forum before I put a hand on OSM.

I fully agree and therefore will not change anything.

Wouldn’t you like to publish with this exclusive view a photo series of the formation of the Teletubby hill ehm … of the Knooppunt Julianaplein on Wikimedia Commons for this Wikipedia article?:

Currently there is no hill but a crater. Construction has reached it’s lowest point, a conrete basin for rainwater.
The final situation is here: https://i.regiogroei.cloud/1104x620/dbd25fcc-ca11-3274-bd8f-83f32be84068.jpg
( seen from the south , A28 )

There are several video’s on youtube documenting the construction.
You could also take a look at this website, in Englisch: https://www.groningenbereikbaar.nl/en/current-traffic-situation
It will give you an impression of the vast number of traffic disruptions. Even we locals can’t keep up.

As for Wikipedia. The article misses out on one thing. In the original design of the ‘ring’ a second more outworth laying ring was included. So planning was futureproof. However, it was decided not to build this second ring. That was a political/financial decision.

I agree. One of the major obstacles in the use of OSM is that all information is on a single layer. Seperating ( and highlighting ) items involves designing your own viewer and mapstyles. I use off-line maps for cycling with a layer added for cycleways in good old-fashioned fat red lines ( for the below 50 members: the style of the old paper ANWB maps ).
All the information is in the database, but getting to it requires some work.

Regarding the conditional closure on OSM:

We have two navigation services on osm.org. I have noticed on the basis of another street that the closing on a date works at the service of the company Graphhopper. On the following piece of street you can see which condition I entered three days ago:

And indeed: Right on time since today it is routed via the detour:

It does not work on the other navigation service OSRM. As far as I know, it is maintained by volunteer OSM community members. And the server is run by the german OSM-Chapter called Fossgis.

For the smartphone navigation service OSMAND, I don’t have an updated map since my edit.

Edit one day later:
I do not know why. But one day later on July 27, 04:29 it no longer works on Graphhopper.

FOSSGIS is not related to OSM but to OSGeo.