Enterprise Linux GIS

This page gathers links and information about running FLOSS GIS software on Enterprise Linux (shortened EL hereafter) and derivatives, that is Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux.

EL is a popular and robust platform for servers and computing-heavy workstations, and is therefore a good fit for the specific requirements of GIS.

The mailing list el@lists.osgeo.org is used for communication (with an online archive).

= Useful repositories for GIS software =
 * EPEL is an official Fedora project which repackages many Fedora packages which are not part of the standard EL distribution. It contains quite a few GIS packages and base libraries. Note that one of the rules of the packages maintained in EPEL is that they should never require to change the base EL distribution.
 * ELGIS repositories try to ensure that the latest stable version of the major FLOSS GIS software are available for Enterprise Linux. They maintain versions of packages which cannot be maintained in EPEL, or that EPEL does not want to keep at the latest stable version. This is where our packaging effort currently takes place, and can be seen as a kind of backport repository. It requires EPEL to be configured as a repository.

= RHEL/CentOS/SL 6 : Packages Status Summary =

ELGIS 6 is under development and a stable release will be available soon.

The latest stable versions of quite a few core packages are already available in the testing repository. See http://lists.osgeo.org/pipermail/el/2011-September/000670.html, in order to see how to install and test them.

In short: sudo rpm -Uvh http://elgis.argeo.org/repos/6/elgis-release-6-6_0.noarch.rpm and enable [elgis-testing] in /etc/yum.repos.d/elgis-testing.repo

There are older versions of some packages (GDAL, PostGIS) already available in the EPEL 6 repository.

= RHEL/CentOS/SL 5 : Packages Status Summary =

Detailed package lists for ELGIS are available here: http://elgis.argeo.org

Formats supported by GDAL
As of gdal-1.8.0-4:

LIBZ support:             external LIBLZMA support:          no  GRASS support:             no  CFITSIO support:           external PCRaster support:         internal NetCDF support:           yes LIBPNG support:           external LIBTIFF support:          external (BigTIFF=no) LIBGEOTIFF support:       external LIBJPEG support:          external 8/12 bit JPEG TIFF:       no  LIBGIF support:            external OGDI support:             yes HDF4 support:             yes HDF5 support:             yes Kakadu support:           no  JasPer support:            yes (GeoJP2=no) OpenJPEG support:         no  ECW support:               no  MrSID support:             no  MrSID/MG4 Lidar support:   no  MSG support:               no  GRIB support:              yes EPSILON support:          no  cURL support (wms/wcs/...):yes PostgreSQL support:       yes MySQL support:            yes Ingres support:           no  Xerces-C support:          yes NAS support:              yes Expat support:            yes Google libkml support:    no   ODBC support:              yes PGeo support:             yes PCIDSK support:           internal OCI support:              no  GEORASTER support:         no  SDE support:               no  Rasdaman support:          no  DODS support:              yes SQLite support:           yes SpatiaLite support:       yes DWGdirect support         no  INFORMIX DataBlade support:no GEOS support:             yes VFK support:              yes Poppler support:          no  OpenCL support:            no

./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --prefix=/usr --includedir=/usr/include/gdal/ --datadir=/usr/share/gdal/ --with-threads=yes --with-dods-root=/usr/lib64 --with-ogdi --with-cfitsio=/usr --with-geotiff=external --with-tiff=external --with-libtiff=external --with-libz --with-netcdf --with-hdf4 --with-hdf5 --with-geos --with-jasper --with-png --with-gif --with-jpeg --with-odbc --with-sqlite --with-mysql --with-curl --with-python --with-perl --with-pcraster --with-ruby --with-java --with-xerces --with-xerces-lib=-lxerces-c --with-xerces-inc=/usr/include --with-jpeg12=no --enable-shared --with-gdal-ver=1.8.0 --with-spatialite=yes

= If you want to contribute packages to the ELGIS repo =


 * Especially for new packages, please try to build them in mock first (the one from CentOS, not from EPEL!), so that all build dependencies are in the spec file. You can find some mock config files here. Don't hesitate to ask on the mailing-list if you need support for your first mock builds: this is much easier than it seems, and very clean


 * For existing packages, please always start from the spec files maintained in subversion, so that previous changes are integrated: https://projects.argeo.org/elgis/svn/factory/trunk/rpmbuild/elgis/ /SPECS/*.spec (or https://projects.argeo.org/elgis/svn/factory/trunk/rpmbuild/elgis-plus/ ...)

Then send you spec file to the mailing-list or give download access to an SRPM.

= Collaboration with Fedora and EPEL = The following principles clarify the collaboration with the Fedora and EPEL projects and which packages are supposed to be maintained in the ELGIS repository:


 * in general, Fedora packages are the upstream source for Enterprise Linux packages (be they in the EPEL or ELGIS repos)
 * the ELGIS repos depends on the EPEL repo, they complement it and sometimes override it
 * for EL 5, the GIS packages in EPEL will most probably not be updated, so the mission of the ELGIS repos is to provide up to date packages until there is no more interest for them (as will be discussed on a case by case basis on the ELGIS list)
 * for EL 6, the GIS packages will mostly be provided by EPEL. Later on in the life cycle of the platform, if EPEL doesn't want to keep the packages up to date, the ELGIS repos may take over as it did for EL 5
 * packages that cannot be in EPEL (typically because they require to update the base platform) can be maintained in the ELGIS Plus repo (it is expected that there will be very few of them at the beginning of the EL6 life cycle)
 * our goal is not primarily to provide packages but also to serve as a knowledge base for FLOSS GIS software usage on Enterprise Linux. Therefore EL specific questions related to GIS packages from EPEL are welcome on the ELGIS list and information about them will be documented in the other resources provided by the OSGeo foundation (wiki, trac, etc.)

= How To =

How to enable the ELGIS repository
sudo rpm -Uvh http://elgis.argeo.org/repos/5/elgis-release-5-5_0.noarch.rpm
 * enable the EPEL repository (see https://fedoraproject.org/wiki/EPEL/FAQ#howtouse)
 * execute
 * if you want to install QGIS, edit the /etc/yum.repos.d/elgis.repo file and enable the 'elgis-plus'. WARNING: this updates the base distribution

How to hack and locally build the ELGIS packages
For the time being, the ELGIS packages (that is, those not maintained by EPEL) are versioned by and distributed through argeo.org.

You can see the currently versioned packages here:


 * Testing
 * ELGIS : https://projects.argeo.org/elgis/svn/factory/trunk/rpmbuild/elgis
 * ELGIS Plus: https://projects.argeo.org/elgis/svn/factory/trunk/rpmbuild/elgis-plus
 * Stable
 * ELGIS: https://projects.argeo.org/elgis/svn/factory/branches/5-stable/rpmbuild/elgis
 * ELGIS Plus: https://projects.argeo.org/elgis/svn/factory/branches/5-stable/rpmbuild/elgis-plus

Note: simply accept the self-signed certificate

You can checkout all the packages: svn co https://projects.argeo.org/elgis/svn/factory/trunk/rpmbuild rpms

Or one by one, for example: svn co https://projects.argeo.org/elgis/svn/factory/trunk/rpmbuild/elgis/gdal gdal

Each package directory follows the directory structure expected by rpmbuild (see how to set an rpmbuild environment).

We version only the spec files (under /SPECS/ .spec) and the patches or some light sources (under /SOURCES). The source packages of the underlying libraries needs to be downloaded in the SOURCES directory.

Please send patches to the spec files to the el@lists.osgeo.org mailing-list.

In order to actually build, you can then configure %_topdir in your ~/.rpmmacros file to point to where you checked out a package, for example:

%_topdir %(echo $HOME)/dev/rpmbuild %rhel 5 %packager Mathieu Baudier  %dist .el5.elgis

A more persistent alternative is to have the two following files in each package directory:

include: /usr/lib/rpm/rpmrc macrofiles: /usr/lib/rpm/macros:/usr/lib/rpm/ia32e-linux/macros:/usr/lib/rpm/redhat/macros:/etc/rpm/macros.*:/etc/rpm/macros:/etc/rpm/ia32e-linux/macros:~/.rpmmacros: /rpmmacros (note the ': /rpmmacros' appended at the end of the macrofiles line)
 * /rpmrc

%_topdir %rhel 5 %packager Mathieu Baudier  %dist .el5.argeo
 * /rpmmacros

And then call rpmbuild as follow cd rpmbuild --rcfile=rpmrc -ba SPECS/ .spec

These two files are registered in svn:ignore and can typically be automatically generated by scripts or a build framework.

How to deploy GeoServer 2.1 (standard packages not using the ELGIS repository)
This how-to goes through the various steps required to have GeoServer 2.1 running as a Java web application inside the standard Tomcat 5 container. It has been tested with CentOS 5.6 x86_64.

Basic install (with base OpenJdk)
sudo yum install java-1.6.0-openjdk-devel tomcat5 sudo yum install tomcat-native cd ~/Downloads wget http://sourceforge.net/projects/geoserver/files/GeoServer/2.1.1/geoserver-2.1.1-war.zip/download?use_mirror=ignum sudo /sbin/service tomcat5 stop sudo tar -czf /srv/backups/geoserver/geoserver-data-110624.tar.gz /var/lib/geoserver/data sudo mv /var/lib/tomcat5/webapps/geoserver* /srv/backups/geoserver/2.0.2/ cd /var/lib/tomcat5/webapps/ sudo unzip ~/Downloads/geoserver-2.1.1-war.zip geoserver.war sudo mkdir -p /var/lib/geoserver cd /var/lib/geoserver sudo jar -xvf /var/lib/tomcat5/webapps/geoserver.war data sudo chown -R tomcat.tomcat /var/lib/geoserver JAVA_OPTS="-showversion -server -Xmx512m -Xms64m -XX:SoftRefLRUPolicyMSPerMB=36000 -XX:MaxPermSize=128m -XX:+UseParallelGC" JAVA_OPTS="$JAVA_OPTS -DGEOSERVER_DATA_DIR=/var/lib/geoserver/data" ...    GEOSERVER_DATA_DIR /var/lib/geoserver/data  ...  ProxyPass ajp://localhost:8009/geoserver/ # Uncomment to forbid non ssl access #RequireSSL  setsebool -P httpd_can_network_connect=1 sudo /sbin/service tomcat5 start tail -500f /var/log/tomcat5/catalina.out sudo /sbin/service httpd restart
 * Install the required packages
 * (optional) Install tomcat-native frop EPEL
 * Download GeoServer
 * (optional) Backup previous deployment
 * 1) Stop Tomcat
 * 1) Backup previous data dir
 * 1) Backup up previous install
 * Unpack to Tomcat webapps
 * (new installs only) Create a separate data directory
 * Update /etc/tomcat/tomcat5.conf to add the recommended Java settings and to point to the data directory. You can increase/decrease the maximum memory allocated to Java with the -Xmx flag (-Xms is the initial allocation):
 * 1) Geoserver recommended
 * 2) http://docs.geoserver.org/stable/en/user/production/container.html
 * (optional ?) Update web.xml to take the data directory (seems to work with only the system property specified)
 * Add an AJP proxy in the Apache configuration (e.g. in /etc/httpd/conf.d/geoserver.conf)
 * (optional) If using SELinux, allow the proxying by setting the appropriate boolean
 * Start Tomcat
 * (optional) You can tail Tomcat logs to make sure that it is starting properly
 * Restart Apache
 * Visit http://yourhost.org/geoserver/
 * Log in as admin (default password is 'geoserver')

With Sun/Oracle JRE and JAI native (recommended by GeoServer)
GeoServer documentation recommends to use a Sun/Oracle JRE with the JAI and JAI-ImageIO native extensions. There was an obvious performaince gain inthe tile generation by doing so

... JAVA_HOME=/opt/jdk1.6.0_21 ... cd /opt/jdk1.6.0_21 sudo sh ~/Downloads/jai-1_1_3-lib-linux-amd64-jdk.bin sed s/+215/-n+215/ jai_imageio-1_1-lib-linux-amd64-jdk.bin > jai_imageio-1_1-lib-linux-amd64-jdk-fixed.bin sudo sh ~/Downloads/jai_imageio-1_1-lib-linux-amd64-jdk-fixed.bin sudo /sbin/service tomcat5 restart
 * Download in install Sun/Oracle JDK in /opt (a JRE should be enough)
 * Hack the /usr/bin/dtomcat5 script to add an explicit reference to Sun/Oracle JDK at the beginning (did not find any better way neither through /etc/tomcat5/tomcat5.conf nor /etc/init.d/tomcat5 nor the alternatives system, ideas welcome...)
 * Go into the Sun JDK directory:
 * Download and install JAI from http://download.java.net/media/jai/builds/release/1_1_3
 * Download JAI-ImageIO from http://download.java.net/media/jai-imageio/builds/release/1.1
 * Note: On x86_64 the archive of JAI-ImageIO to download as of 1.1 is corrupted, fix it with the command below and run the fixed archive (thanks to http://jgrasstechtips.blogspot.com/2009/07/jai-tail-cannot-open-215-for-reading-no.html for the tip)
 * Install JAI-ImageIO
 * Restart Tomcat
 * Visit your GeoServer status page in order to make sure that native JAI is taken into account

LDAP Authentication
This will allow you to have you user referential in LDAP (tested with base CentOS 5 openldap-servers). Your users need to be inetOrgPerson under ou=People,dc=my_org,dc=org Your GeoServer administrators need to belong to the cn=administrator,ou=Roles,dc=my_org,dc=org role: dn: cn=administrator,ou=Roles,dc=my_org,dc=org objectClass: top objectClass: groupOfNames cn: administrator member: uid=mbaudier,ou=People,dc=my_org,dc=org Other roles can be defined similarly under ou=Roles,dc=argeo,dc=org, and should be added mnaually when defining rules in GeoServer. You can of course adapt the following configuration with your specific LDAP settings.

Caveats:
 * the list of users won't be properly displayed in GeoServer.
 * as usual with autentication via HTTP make sure that users are using SSL (https://) when they authenticate, otherwise their credentials will be sent in clear. If you want to mix public with private data and stay compatible with client which don't support HTTPS, this is not necessarily easy.

Procedure: cd /var/lib/tomcat5/webapps/geoserver/WEB-INF/lib sudo wget http://search.maven.org/remotecontent?filepath=org/springframework/ldap/spring-ldap/1.3.1.RELEASE/spring-ldap-1.3.1.RELEASE-all.jar -O spring-ldap-1.3.1.RELEASE-all.jar  
 * Download spring-ldap and copy it to the WEB-INF/lib directory of GeoServer:
 * Extract applicationContextSecurity.xml from the main-jar (in /var/lib/tomcat5/webapps/geoserver/WEB-INF/lib/)
 * Copy it to /var/lib/tomcat5/webapps/geoserver/WEB-INF/
 * Add the following at the beginning of the applicationContextSecurity.xml file (after the tag)

  ou=People   (uid={0}) </constructor-arg> <constructor-arg index="2"> </constructor-arg> <property name="searchSubtree"> false <bean id="ldapAuthenticationProvider" class="org.springframework.security.providers.ldap.LdapAuthenticationProvider">  <bean class="org.springframework.security.providers.ldap.authenticator.BindAuthenticator"> <constructor-arg ref="contextSource"/> <property name="userSearch"> </constructor-arg>  <bean class="org.springframework.security.ldap.populator.DefaultLdapAuthoritiesPopulator">  </constructor-arg>  ou=Roles </constructor-arg> <property name="groupRoleAttribute"> cn 				<property name="rolePrefix"> ROLE_ <property name="convertToUpperCase"> true </constructor-arg>

<bean id="filterChainProxy" class="org.springframework.security.util.FilterChainProxy"> <property name="filterInvocationDefinitionSource"> ... ... <bean id="authenticationManager" class="org.springframework.security.providers.ProviderManager">
 * Modify the following section

... ...     contextConfigLocation</param-name> classpath*:/applicationContext.xml WEB-INF/applicationSecurityContext.xml</param-value> </context-param> ... sudo /sbin/service tomcat5 restart
 * Modify /var/lib/tomcat5/webapps/geoserver/WEB-INF/web.xml to use WEB-INF/applicationSecurityContext.xml instead of classpath*:/applicationSecurityContext.xml
 * Restart Tomcat

= Historical Reference =
 * September 2011 - Introduction of ELGIS 6: http://lists.osgeo.org/pipermail/el/2011-September/000670.html
 * December 2010 - Collaboration with Fedora and EPEL: http://lists.osgeo.org/pipermail/el/2010-December/000338.html
 * August 2010 - Announcement of the ELGIS repositories: http://lists.osgeo.org/pipermail/el/2010-August/000018.html
 * May/June 2010 - Original mails suggesting to coordinate EL GIS through OSGeo and describing the rationale and the approach
 * On the Live GIS CD mailing-list: http://lists.osgeo.org/pipermail/live-demo/2010-May/001724.html
 * On the Discuss mailing list: http://lists.osgeo.org/pipermail/discuss/2010-June/007231.html