This package is auto-updated.
Last update: 2021-03-29 10:46:01 UTC
The Virtual Map Forum 2.0 allows the searching and viewing of historic and georeferenced maps and offers further capabilities for the georeferencing of historic maps (dependencies to vk2-georeference. The application is developed as an extension for the CMS TYPO3.
The extension uses the TYPO3 core extension
felogin, for allowing users to register and login into the application. Furthermore it uses the extensions
SA authentication for TYPO3 and
Salted user password hashes.
The TYPO3 extension could be configured via a FlexForm from within the TYPO3 backend. Therefor go in the page tree to WEB>PAGE and choose the page where you have installed the
Virtual Map Forum 2.0 Extension. Click then edit and go to the Plugin tab.
In the Plugin tab you got a couple options:
URL Elastic Search:
ElasitcSearch is the central search index used by the application. It is also used by the georeference backend to publish results. Define here the ElasticSearch endpoint.
Nominatim Service URL:
In this field the placename services should be linked. It expects a Nominatim based placename services like
3D Terrain Tile Provider:
In this field the terrain tile provider is configured. For example:
This parameter tells the client code if georeference is active. It is used for a couple of client decisions and has to be in sync with the
Virtual Map Forum 2.0 Extension can me run in two modes. The
Search and Visualization allows user to search and display georeference maps. It doesn't support the georeferencing of them, so there has to be now georeference backend. Further because of missing georeferencing is also doesn't need a user authentification. The mode
Search, Visualization and Georeferencing futher allows the georeferencing of maps. Therefor also a georeference backend has to be set.
Defines the endpoint of the georeferencing backend. The TYPO3 extension routes requests regarding this georeferencing directly to this endpoint and is tightly bind to it.
Dynamic WMS URL:
This is also only necessary when georeferencing is active. It defines the URL of the dynamic wms, which is used in the user history application.
- OpenLayers 3 / Cesium for Mapping 2D / 3D
- Closure Library as Utitlity Library
# install dependencies via npm npm install # install dependencies via bower node_modules/bower/bin/bower install # install closure compiler cd node_modules/closure-compiler/ npm install
For proper working of the closure compiler make sure a
openjdk-8 is installed.
If you change dependencies or add new files to library the deps files has to be updated. This can be done with the following command:
python Resources/Public/lib/closure-library/closure/bin/build/depswriter.py --root_with_prefix="src ../../../../src" > src/vk2-deps.js
For building a minified version of the library the google closure compiler is used. Therefor the
extern are saved in the directory
Build/vk2/externs. Also the compiler can be used with a gulpfile. The configuration therefor could be find in the
Build/vk2/gulpfile.js file. It could be run via the following command:
The compiled version of the library could be found in the
To build an custom OpenLayers version run the following commands from the
With this commands you can build a debug version of OpenLayers.
node tasks/build.js config/ol-debug.json ./ol-debug.js