MapStore is a framework to build web mapping applications using standard mapping libraries, such as OpenLayers and Leaflet.
MapStore has several example applications:
- MapViewer is a simple viewer of preconfigured maps (optionally stored in a database using GeoStore)
- MapPublisher has been developed to create, save and share in a simple and intuitive way maps and mashups created selecting contents by server like OpenStreetMap, Google Maps, MapQuest or specific servers provided by your organization or third party.
For more information check the MapStore documentation.
You can download the WAR file from the latest release here.
There are two quick ways to test out MapStore. Either using Docker or a local java web container like Apache Tomcat
Pull the latest image from Docker Hub:
docker pull geosolutionsit/mapstore2
docker run --name mapstore -p8080:8080 geosolutionsit/mapstore2
Then you can access MapStore using the following URL:
http://localhost:8080/mapstore
Use the default credentials (admin / admin) to login and start creating your maps!
After downloading the MapStore war file, install it in your java web container (e.g. Tomcat), with usual procedures for the container (normally you only need to copy the war file in the webapps subfolder).
If you don't have a java web container you can download Apache Tomcat from here and install it. You will also need a Java7 JRE
Then you can access MapStore using the following URL (assuming the web container is on the standard 8080 port):
http://localhost:8080/mapstore
Use the default credentials (admin / admin) to login and start creating your maps!
You can find more documentation about how to build, install or develop with MapStore on the documentation site.
MapStore is Free and Open Source software, it is based on OpenLayers, Leaflet and ReactJS, and is licensed under the Simplified BSD License.
We have the following instances:
- a DEV instance, which can be accessed here, where all the changes are deployed once they are published on the Master branch of our repo
- a QA instance, which can be accessed here, that becomes active 1 week before any release, during the hardening phase, and deploys the release branch whenever a fix is pushed onto it.
- a STABLE instance, which can be accessed here, that gets deployed on demand after each release.
As a user you need to be aware of STABLE and DEV, QA is used internally before a release; for 1 Week it will diverge from STABLE as it is actually anticipating the next stable. So, if you want to test latest features use DEV, if you are not that brave use STABLE. You might forget that QA exists unless you are parte of the developers team.
Clone the repository:
git clone https://github.com/geosolutions-it/MapStore2.git
Install latest NodeJS, if needed, from here.
- recommended versions: NodeJS >= 12, npm >= 6
- minimal versions: NodeJS >= 10, npm >= 5
- deprecated versions: NodeJS <10
If you are using Node >= 12 you can remove the -max_old_space_size=2048 config for the compile script
Install docma to build the documentation
npm install -g docma
Start the demo locally:
npm cache clean (this is useful to prevent errors on Windows during install)
npm install
npm start
The demo runs at http://localhost:8081 afterwards.
Install latest Maven, if needed, from here (version 3.1.0 is required).
Build the deployable war:
./build.sh [version_identifier]
Where version_identifier is an optional identifier of the generated war that will be shown in the settings panel of the application.
Deploy the generated mapstore.war file (in web/target) to your favourite J2EE container (e.g. Tomcat).
Read more on the documentation site.
MapStore is being developed by GeoSolutions hence you can talk to us for professional support. Anyway the project is a real Open Source project hence you can contribute to it (see section below).
We currently have two mailing list, one for users and one for developers. The first one is for those who are willing to use MapStore and need help/directions, the latter is for those trying to extend/proposed fixes for MapStore.
We welcome contributions in any form:
- pull requests for new features
- pull requests for bug fixes
- pull requests for documentation
- funding for any combination of the above
For more information check this page.