A20 motorway (Netherlands)

The A20 motorway is a motorway in the Netherlands. It is approximately 39 kilometers in length.

A20 motorway
Rijksweg 20
Location of the A20 motorway
Major junctions
West endNaaldwijk
East endInterchange Gouwe
Location
ProvincesSouth Holland
Highway system

The A20 is entirely located in the Dutch province South Holland and connects the N213 road from the Westland municipality with the cities of Rotterdam and Gouda, where it connects to the A12 motorway at the interchange Gouwe.

The 80 km/h zone near Rotterdam.

Rotterdam

The section near Rotterdam, between the interchanges with the A4 and A16 motorways, is the northern part of the so-called Ring Rotterdam, the beltway around the city.

On a part of this section, the maximum speed is reduced to 80 km/h, which is being enforced by speed cameras calculating the average speed of a vehicle on the stretch between the cameras.

European routes

From the first exit, exit 6 (Maasdijk), the European route E25 follows the A20 motorway all the way to its terminus at interchange Gouwe.

Besides, the European route E19 follows the A20 along the 6 kilometers short stretch between interchanges Kleinpolderplein and Terbregseplein, just north of Rotterdam.

Exit list

The entire route is in South Holland.

MunicipalitykmmiExitDestinationsNotes
Westland106.2 N223 – NaaldwijkContinues as road N213 to Westland
127.56 N220 – Maasdijk
Maassluis17117Maassluis
Vlaardingen21138Vlaardingen-West
22149Vlaardingen
Schiedam2314 A4 (Interchange Kethelplein)
241510Schiedam-NoordNoord means north
261611Schiedam
Rotterdam271712Spaanse Polder
291813 A13 (Interchange Kleinpolderplein) – Overschie
311914CentrumCentrum means center
322015CrooswijkEastbound exit and westbound entrance only
3522 A16 (Interchange Terbregseplein)
382416Prins Alexander
Nieuwerkerk aan den IJssel432717 N219 – Nieuwerkerk aan den IJssel
Moordrecht462918Moordrecht
Gouda4930 A12 (Interchange Gouwe)Exit from westbound A12 and entry to eastbound A12 only
1.000 mi = 1.609 km; 1.000 km = 0.621 mi
gollark: Basically, if I want to run a search it just goes `SELECT * FROM page_tokens WHERE token = 'one token in search query'` or something like that, and it now has a list of pages with the right token, and SQLite can execute this query relatively fast.
gollark: I mean, as far as I can tell there isn't really a faster *and* more storage-efficient way to do search than the inverted-index page_tokens thing.
gollark: ```sqlCREATE TABLE crawl_queue ( id INTEGER PRIMARY KEY, url TEXT NOT NULL UNIQUE, lockTime INTEGER, added INTEGER NOT NULL, referrer TEXT);CREATE TABLE pages ( id INTEGER PRIMARY KEY, url TEXT NOT NULL UNIQUE, rawContent BLOB NOT NULL, rawFormat TEXT NOT NULL, textContent TEXT NOT NULL, updated INTEGER NOT NULL);CREATE TABLE page_tokens ( id INTEGER PRIMARY KEY, page INTEGER NOT NULL REFERENCES pages(id), token TEXT NOT NULL, weight REAL NOT NULL);CREATE TABLE links ( id INTEGER PRIMARY KEY, toURL TEXT NOT NULL, fromURL TEXT NOT NULL, lastSeen INTEGER NOT NULL, UNIQUE (toURL, fromURL))```Here is the database.
gollark: To be fair, the text content field isn't that necessary, as for search it uses the page_tokens table anyway and it can be rebuilt from the HTML if I need it.
gollark: The frequency of every word *must* be stored for quick (O(log n) time or something) search, the raw HTML or at least might be needed if I come up with a better way to weight frequency or something, the links are useful for (future) better search ranking algorithms.

Media related to Rijksweg 20 at Wikimedia Commons

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.