Cartaro

Geospatial CMS

Documentation

Frequently Asked Questions (FAQ)

Installation and hosting

How to try out Cartaro?

To give Cartaro a try we recommend running the OSGeo Live DVD or using the Docker container.

What are the requirements for running Cartaro?

Cartaro is not limited to specific operating systems. It is necessary to run PostgreSQL, GeoServer by Tomcat and Webserver mit PHP (e.g. Nginx or Apache). By default, we recommend Debian Linux or Ubuntu Linux.

Is there a cloud hosted service?

In general, Cartaro is an open source project and can run on any platform you like. The source code is available for download and there is also a Docker image available. If you seeking for a ready to use hosting environment geOps offers special hosting plans for Cartaro.

Features

How about integration and interoperability with ArcGIS and other geospatial software?

For the integration with other geospatial software Cartaro mainly relies on the use of OGC webservices. If you want to view and edit data at the same time in Cartaro and e.g. in ArcGIS we recommend to persist data within Cartaro and to setup a workflow based on WFS and WFS-T.

Does Cartaro support large datasets?

Thanks to the use of PostgreSQL and PostGIS data are stored as true geometries including specialized spatial indices. This is the main prerequisite to allow to work with even very large datasets.

Does Cartaro support fast response searching and indexing?

By default, tsearch2 as Extension for PostgreSQL is getting used. For advanced searching, Apache Solr can be implemented.

Roles and permissions

Does the software support provenance (auditing)?

Within Cartaro you can track every change made to the data. By default you see the creator of a record as well as the person who last modified the data. If you need more control you may want to consider extensions like the Workbench module which allows to setup arbitrarily complex editorial workflows.

Does it support version controlling and manage permissions?

Yes, you can configure Cartaro to save any modification to the data as a separate revision. Cartaro includes a large set of predefined permissions. A simple user interface allows to manage the permissions for each feature type. By writing some code it is possible to add more permissions that will integrate seamlessly with the default ones.

Can the software integrate with an existing Active Directory domain?

This is possible via ADFS or direct LDAP access. Both options needs special setups depending on the local environment.

Is it possible to grant some users admin authority over a specific group of other users?

This not possible by default, but it is possible with some rather simple extensions to the source code.

Can content beassigned to specific users or groups of users with varying levels of privilege?

Basic access control on the level of a feature type is a core feature of Cartaro. For more control you may use one of the existing extensions like the Workbench module. If you need to differentiate permissions at the level of single records this is possible with your onw code.

Do you have further questions?

Please contact us and we'll get back to you.


« Back to Documentation index