Observations on the training and stratigraphic position of the Lower Rhine-Main terrace formation in the area of the Süchtelner Hochnzug and the Schwalm-Nette area
Open data API in a single place
Provided by Bundesamt für Kartographie und Geodäsie
Get early access to Observations on the training and stratigraphic position of the Lower Rhine-Main terrace formation in the area of the Süchtelner Hochnzug and the Schwalm-Nette area API!
In the area of the Süchtelner elevation between Herongen and Viersen, as well as in the west adjacent Schwalm-Nette area, the quaternary sequence of strata consists mainly of the 2,6-0.5 million years of under-pleistozene deposits. They are part of the Lower Rhine-Main terraces formation of the Rhine-Maas system. Between the two deposition areas of the Rhine and Maas, there is a four-seneper jump separating the Krefelder plaice (high plaice) to the east from the Venloer Scholle (deep plaice) in the west. As a result of the different tectonic movements, the altitude is not only different, but also the severity of the terrace sequences varies significantly between the two areas. Powerful profiles on Venloer plaice contrast with low-power profiles on the Krefeld plaice, which are difficult to parallel with each other.
Studies of gerl stocks, heavy minerals and the number of flints on taps and drilling profiles brought new findings. For example, in the Schwalm-Nette area, there is a more or less complete sequence of the Lower Rhine-Main terraces from the older to the younger main terraces. In addition, the sands and Kiese present in the plateau area of the Süchtelner elevation at the altitude of + 80 to + 85 m NHN are to be classified as deposits of the teagel layers.
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.