ATM is built upon linked data infrastructures from key academic and cultural heritage institutions in the Netherlands, including CLARIAH and Adamnet. Among the building blocks for the implementation of the Amsterdam Time Machine’s vision, we provide access to OS historical maps (tiles), which can be used for various applications; and 3D/4D reconstructions. One of the aims of the Amsterdam Time Machine is in fact to develop a 3D/4D urban model where socio-historical data about the city can be mapped and queried. Manually modelling each building individually is, however, a time-consuming task. The most efficient approach entails the semi-automatic generation of buildings. Ideally, the 3D scene is based on underlying GIS data, as they represent the most common way to store historical information when they can be anchored to a given location. We are currently developing basic 3D models of the entire city for selected years in the period 1550 – present, using a rule-based and parametric modelling strategy which allows a GIS-driven creation of large 3D scenes. These can serve as a basis for more detailed reconstructions of individual blocks and buildings. In the meantime, check out these models. On the data page, you can find examples of both maps and 3D urban models.

Linked Data

Researchers, historians, heritage institutions and the city administration are interlinking their data and creating an Amsterdam Linked Data Cloud (ALiDa). ALiDa shows datasets relevant to the history of Amsterdam. The image below is a representation of current datasets that are linked, but behind the scenes we are working on providing access points!

LOD Cloud

Of course ALiDa is linked to the rest of the world. We’ve all seen the famous LOD cloud diagram, so dense now it’s becoming harder to read everyday.
(part of) the LOD cloud

Contributing your dataset to the ALiDa cloud

To claim a spot in the ALiDa cloud in the near future, your dataset should
  • be relevant to the history of Amsterdam
  • be connected to at least one dataset already in the ALiDa cloud. This means, either your dataset uses URIs from the other dataset, or vice versa.
  • be open. This means, your dataset should be licensed in a way other people can freely use it.
  • be accessible. This means, it should be published on the web in a way people can download or harvest it in its entirety
Not sure if your set is linked to datasets in ALiDa or how to go about doing this? Don’t hesitate to contact us!