OSGeo Planet

GeoSolutions: Developer’s Corner: Supporting Wind Barbs In GeoServer and GeoTools

OSGeo Planet - Fri, 2014-04-18 15:34


Dear All, in this post we would like to talk about the work we are doing to improve support in GeoServer for serving Meteorological and Oceanographic data, specifically the ability to render raster data for wind models using Wind Barbs. When ingesting and serving MetOc models (raster data) for Wind data you are now already able to render  them using an arrow symbology by concatenating:
  • the gs:rasterAsFeatureCollection Rendering Transformation to transform the raster dataset into a series of vector points where the bands of the input raster data are the attributes
  • a vector style to create arrows for each point with proper module and rotation controlled by the module and direction of the Wind data
With this approach you can obtain something like the following: [caption id="attachment_1438" align="aligncenter" width="512"]wind Rendering GFS Wind Model data as arrows in GeoServer[/caption] There are a few drawbacks in this approach which are trying to improve in GeoServer, namely:
  1. it is not uncommon to draw too many symbols depending on the resolution of the underlying data which makes the visualization slow and cluttered. It is possible to use the standard techniques in GeoServer to reduce the cluttering but this happens once you have generated the vector points with the gs:rasterAsFeatureCollection Rendering Transformation hence it is a slow process (think about collision detection and conflict resolution)
  2. meteorologists want Wind Barbs and not simple arrows
We are currently working to improve point 1, we will describe that work in a different post. As of point 2 we are going to provide native support for Wind Barbs by developing a new graphic factory for GeoServer (actually for its rendering engine which is developed using GeoTools) which would allow to render vector points a as Wind Barbs this way: <WellKnownName>windbarbs://default(<ogc:PropertyName>speed</ogc:PropertyName>)[m/s]</WellKnownName> which allows us to:
  • extract the speed from the respective speed attribute (yes, we have renamed the underlying raster band to speed)
  • specify the unit of measure of the speed. Note that Wind Barbs always deal with speed in knots. Therefore, specifying the input unit of measure allows the factory to do the proper conversion to knots.
rotation can be applied as usual for point vector symbologies. The full style can be found here below: <StyledLayerDescriptor version="1.0.0" xmlns="http://www.opengis.net/sld" xmlns:gml="http://www.opengis.net/gml" xmlns:ogc="http://www.opengis.net/ogc" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/sld ./StyledLayerDescriptor.xsd"> <NamedLayer> <Name>Wind</Name> <UserStyle> <Title>Wind</Title> <FeatureTypeStyle> <Transformation> <ogc:Function name="gs:RasterAsPointCollection"> <ogc:Function name="parameter"> <ogc:Literal>data</ogc:Literal> </ogc:Function> </ogc:Function> </Transformation> <Rule> <PointSymbolizer> <Graphic> <Mark> <WellKnownName>windbarbs://default(<ogc:PropertyName>speed</ogc:PropertyName>)[m/s]</WellKnownName> <Stroke> <CssParameter name="stroke">#000000</CssParameter> <CssParameter name="stroke-width">1</CssParameter> </Stroke> <Fill> <CssParameter name="fill"> <ogc:Literal>#f5ffff</ogc:Literal> </CssParameter> </Fill> </Mark> <Size>8</Size> <Rotation> <ogc:PropertyName>direction</ogc:PropertyName> </Rotation> </Graphic> </PointSymbolizer> </Rule> </FeatureTypeStyle> </UserStyle> </NamedLayer> </StyledLayerDescriptor>   notice the usage of the gs:RasterAsPointCollection Rendering Transformation to turn the raster into a series of vector points. This feature is being developed as we speak, it will be first available on the development series of GeoServer (2.6.x) and then will be backported to 2.5.x. More on the work that we are doing for improving the support for Meteorological and Oceanographic data will be reported in the next posts. It is worth mentioning that this work is being performed under our GeoSolutions Enterprise Services framework contract. If you are interested in learning about how we can help you achieving your goals with our Open Source products and professional services, do not hesitate to contact us! The GeoSolutions team, 320x100_eng
Categories: OSGeo Planet

gvSIG Team: 6as Jornadas gvSIG de Latinoamérica y Caribe: Taller “Cuencas hidrográficas”

OSGeo Planet - Fri, 2014-04-18 15:16

En el marco de las Jornadas LAC de gvSIG, que este año se realizan conjuntamente con el evento MundoGEO#Connect, serán realizados varios talleres de los que iremos ampliando información en este blog. Este taller sobre “Cuencas hidrográficas” será impartido por el profesor Gilberto Cugler tiene como objetivo mostrar la facilidad de generar los limites de cuencas y subcuencas hidrográficas utilizando las distintas herramientas disponibles en gvSIG.

Los ejercicios se realizarán sobre un área de aproximadamente 2000 km2, donde será delimitada la cuenca del Río Verde del municipio de Tapiraí, estado de São Paulo (Brasil) con una extensión de 35 km y un área de 317 km2. El proceso de delimitación de la cuenca utilizará también el número de Strahler y otros algoritmos que permiten realizar el análisis morfométrico de una cuenca hidrográfica.

Los datos necesarios para el taller están disponibles en: http://www.sigrb.com.br/capacitacao/6as_lac.php opción 6as Jornadas da América Latina e do Caribe de gvSIG – 2014, tal y como muestra la imagen


Los asistentes al taller deberán traer su laptop con gvSIG y los datos indicados previamente instalados.

Para facilitar el desarrollo de los ejercicios previstos para el taller se recomienda utilizar el mismo lugar de trabajo; para esto se debe instalar el archivo gvSIG_1.11_SIG-RB_portable_PT_BR.exe aceptando como carpeta la propuesta (SigRibeira) y posteriormente descomprimir en esta carpeta los datos (Dados_6LAC.zip).

Para cualquier problema en descargar los archivos o con los datos estamos a disposición en sigrb@sigrb.com.br o gilbertocugler@gmail.com

Filed under: events, gvSIG Desktop, spanish
Categories: OSGeo Planet

gvSIG Team: gvSIG 2.1 for Linux 64bits

OSGeo Planet - Thu, 2014-04-17 10:56

tux-logo-gvsigOne of the objectives that we had set for gvSIG 2.2 was to have 64 bits distributions to avoid the possible installation problems that mainly Linux users found.
Nevertheless the process has been faster than we expected and there’s a gvSIG 2.1 distribution for Linux 64bits already. If you are interested in testing it you can find it at the usual development versions downloads page.

Uno de los objetivos que nos habíamos marcado para gvSIG 2.2 era disponer de distribuciones de 64 bits para evitar los posibles problemas de instalación que principalmente se encontraba el usuario de Linux.
Sin embargo el proceso ha sido mucho más rápido de lo que esperábamos y ya tenemos disponible una distribución de gvSIG para Linux de 64 bits. Si estás interesado en testearla la puedes encontrar en el sitio habitual de descarga de versiones en desarrollo.

Filed under: english, gvSIG Desktop, spanish, testing Tagged: 64, linux
Categories: OSGeo Planet

gvSIG Team: Calling for gvSIG Community: Translations

OSGeo Planet - Thu, 2014-04-17 07:47

The necessary tasks in gvSIG 2.1 for maintenance and management of translations in the different languages have been carried out already. Now they have to be updated in order to have the final version with as many languages as possible.

The participation of the Community is fundamental in order to get this objective.

If you are interested in collaborating with the existing languages updating, as well as in translating gvSIG 2.1 to a new language you can contact the gvSIG Project [info@gvsig.com].

Translations that aren’t finished when the final version is released will be published as a package to be loaded from the gvSIG Add-ons manager.

Llamamiento a la Comunidad gvSIG: traducciones

Ya se han realizado las tareas necesarias en gvSIG 2.1 para la gestión y mantenimiento de traducciones en los más diversos idiomas. Ha llegado el momento de actualizarlas de cara a tener la versión final disponible en el mayor número de idiomas posible.

Para conseguir este objetivo la participación de la Comunidad es fundamental.

Si estáis interesados en colaborar en la actualización de cualquiera de los idiomas ya existentes en versiones anteriores, así como en traducir gvSIG 2.1 a un idioma nuevo os podéis poner en contacto con el proyecto [info@gvsig.com].

Las traducciones que no estén finalizadas en el momento de la publicación de la versión final se publicarán como paquetes que podrán ser cargados directamente desde el Administrador de complementos de gvSIG.

Filed under: community, english, gvSIG Desktop, spanish
Categories: OSGeo Planet

GeoServer Team: GeoServer 2.4.6 Released

OSGeo Planet - Wed, 2014-04-16 06:45
The GeoServer team is pleased to announce the release of GeoServer 2.4.6: 

This release is made in conjunction with GeoTools 10.6.

The GeoServer 2.4.6 Release Notes detail changes in this maintenance release, which include:

  • Improved importer support for Oracle
  • Better labelling of top and bottom layers in groups
  • Demos now honour proxy base URL
  • Fixes for KML LookAt, time and elevation support, and a resource leak
  • Logging and documentation improvements

See also changes in the GeoTools 10.6 Release Notes.

Now is a good time to plan your upgrade to the 2.5 series. Our extended release schedule provides six month maintenance window allowing you to upgrade when ready.


Categories: OSGeo Planet

GeoTools Team: GeoTools 10.6 Released

OSGeo Planet - Wed, 2014-04-16 06:31

The GeoTools community is pleased to bring you GeoTools 10.6:Artifacts are also available from our Maven repository.
This is our first GeoTools maintenance release offering an extra six months of the GeoTools 10 series. This six month windows provides a grace period allowing you schedule your upgrade to GeoTools 11 while still receiving bug fixes. For more information see Changing Tracks on the the GeoTools Release Train.

The GeoTools 10.6 Release Notes detail changes since 10.5. These include:
  • app-schema improvements handling nulls and undefined namespaces
  • SpatialLite supports now supports views in addition to tables
  • Oracle support continues to approve with better CRS axis name and spatial index support
  • Small fixes for GeoJSON, GeoTIFF, process annotations
 About the GeoTools 10.x SeriesSummary of the features for the GeoTools 10.x series:
  • Structured grid coverage readers allow raster data sources that publish composite data products to expose individual rasters (ie granules) for processing, while still providing a seamless experience for rendering. The mosaic and NetCDF modules are the first ones to implement these new interfaces.
  • Efficient support for multiple coverages in GridCoverageReader provides ad-hoc access to raster formats that publish more that one data product. A image mosaic made of NetCDF granules and single file NetCDF sources are the first implementors of these new capabilities
  • new implementation of Shapefile DataStore (based on ContentDataStore superclass). This upgrade should be seamless for all users using DataStoreFactoryFinder. If you explicitly made use of the ShapefileDataStore or IndexedShapefileDataStore class please check the upgrade instructions.
  • The transform module graduated to supported status, providing a seamless way to rename, retype and hide SimpleFeatureSource attributes, as well as creating new ones based on OGC Expression
  • Additional OGC modules for the WCS 2.0 and WCS 2.0 EO models as well as adding XML parsers and encoders
  • Support for fills made with randomized symbols
The 10.x series features a number of research and development activities:
  • NetCDF has been updated to take advantage of the new coverage API introduced above
  • GeoPackage: a sample implementation of the geopackage spec that is currently being developed by the OGC
If you are interested in helping out please introduce yourself on geotools-devel mailing list.
Enjoy,The GeoTools Communityhttp://geotools.org
Categories: OSGeo Planet

Boundless Blog: Thoughts from State of the Map US 2014

OSGeo Planet - Tue, 2014-04-15 20:43

Gretchen PetersonThe State of the Map US 2014 conference, a two-day conference covering all things OpenStreetMap, was held this past weekend in Washington DC. It was nice to attend as part of the Boundless contingent and meet — in person — tons of people whom I had only heretofore known via the internets.

Aside from the inspiration provided by the gorgeous weather and the cherry blossoms, there was also inspiration in abundance at the conference for cartographers. Every cartographer should become familiar with OpenStreetMap data if they aren’t already. It’s a bit of a bear to work with because it is in a different structure than we are normally used to (nodes and ways mean anything to you?) but you’ll see the benefits if you download a state-wide or city-wide extract from one of several sites (such as geofabrik or Metro Extracts) and start using it in your map-making medium of choice. The dataset provides a comprehensive collection of roads, buildings and building types, points of interest, and so on. And it’s free!

There were many talks I didn’t get to see because there were two concurrent tracks, but the ones that I attended focused heavily on tools that for using OpenStreetMap data, including GeoGit, TileMill, Esri, QGIS, and PostGIS. However, there were still some cartographic takeaways.

  • Kate Watkins, Seth Fitzsimmons and Alan McConchie told us that a great way to build a stylistically cohesive basemap is to focus on three main hues, along with variations on those hues.

  • In that same talk we saw some great examples of labels that break all the rules: the leading and kerning (that’s line spacing and character spacing, basically) are decreased to negative values and the halos are very large and black. Of course this is the opposite of what most texts will recommend but it just proves that breaking the rules once in a while can make for some neat cartographic effects.

  • Eric Theise showed us that applying some of the devices of experimental film to maps, such as perception distortion, can be a creative way to get people thinking. Eric and I were discussing this later on in the day when he mentioned that he thought it would be interesting to have a map that taunted you if you tried to click on a feature to find out more about it. Something like, “You’d like to know what this building is, wouldn’t you?!”

  • Kevin Bullock told a great story about a map of India that was produced in the 1800s with crude tools, took 70 years to complete, and astonishingly accurate despite these and other limitations. And you thought your map products took a long time to produce!

  • Our own Jeff Johnson rounded out the weekend with a more technical talk that examined the ways in which GeoGit could lead to a more distributed and decentralized architecture for OSM.

There was a lot more material covered, of course, and these points focused just on the cartography aspect of OpenStreetMap use. All the talks are now posted on the schedule part of the conference website so definitely take the time to watch them!

If you’re still curious about State of the Map, I recommend this great recap from Peter Batty which provides more details about the event and reviews other issues in the OpenStreetMap community including vector tiles, licensing, passive crowdsourcing, geocoding and more.

The post Thoughts from State of the Map US 2014 appeared first on Boundless.

Categories: OSGeo Planet

FOSS4G 2014: Regular Session and Academic Track proposals due today!

OSGeo Planet - Tue, 2014-04-15 18:01

The time for procrastination dwindles…

Regular Sessions and Academic Tracks are both due today.



Bonus points to anyone who knows where in PDX this clock is located.



Categories: OSGeo Planet

Peter Batty: Report on another great State of the Map conference

OSGeo Planet - Tue, 2014-04-15 05:02
Summary I spent the past weekend in Washington DC for State of the Map (SotM) US, the OpenStreetMap conference. It ended up selling out, with around 500 attendees, making it the largest OpenStreetMap event yet. As with previous SotM events I’ve attended (the last one being in Denver in 2011), I found it very enjoyable and interesting, and there was great energy about it as always, much more than
Categories: OSGeo Planet

Boundless Blog: Harvesting Metadata from OpenGeo Suite using CSW

OSGeo Planet - Mon, 2014-04-14 15:49

Justin DeoliveiraThe release of OpenGeo Suite 4.0 added Catalogue Services for the Web (CSW) support to the impressive list of OGC services supported by the product. CSW is an open standard defined by the Open Geospatial Consortium (OGC) that makes it easier to search for and discover geospatial data in a machine-readable way. With CSW support, metadata about data and web services is more discoverable, making it easier to manage and advertise data as holdings grow. We explained how to install the CSW plugin and described the mechanics of how a CSW service works in a previous post, but this post will describe how to harvest metadata from GeoServer.

Because CSW can be automatically harvested, its easier to integrate new services into existing spatial data infrastructures. GeoServer offers a minimal implementation of the CSW specification that is limited when compared to implementations in more full-fledged catalogs. This is by design, as it is meant to be as lightweight as possible while still providing the capability to offer metadata about the contents of a GeoServer instance. This metadata can easily be consumed by a more complete CSW implementation that supports harvesting. While specific to GeoNetwork, the same workflow is possible with other servers such as pycsw or Esri GeoPortal Server.

Getting Started

The first step is to install OpenGeo Suite with the CSW plugin. For this post we used OpenGeo Suite 4.0.2 and the installation instructions from our previous post. Once the source catalog is installed, the next step is to download and install a catalog into which to harvest metadata. For this post we used GeoNetwork 2.10.2 and followed the detailed instructions in the documentation.

We installed both OpenGeo Suite and GeoNetwork on the same local machine so all links reference http://localhost. One important note is that since OpenGeo Suite and GeoNetwork use the same default port (8080), one must be changed if you intend to run them on the same machine. For this post we set OpenGeo Suite to run on port 9080 by following the documentation.

Configuring Harvesting

Once OpenGeo Suite is up and running, visit the GeoServer administration page at http://localhost:9080/geoserver. If the CSW plugin has been installed correctly, you’ll see a link to the capabilities document on the right hand side of the page. Copy this link as you’ll need it shortly.

Ensure that GeoNetwork is started and visit http://localhost:8080/geonetwork. Login with the “admin” account — by default the password for this account is “admin”. Once logged in, visit the “Administration” page and go to the “Harvesting Management” link about halfway down the page.

The harvesting page allows us to add a link to another CSW from which to harvest metadata. The goal here is to harvest from GeoServer. Start by clicking the “Add” button, then expand the “Type” drop down and select “Catalogue Services for the Web ISO Profile 2.0”.

This results in a form requesting information about the server from which to harvest. For this step we must fill out the following:

  • Set “Name” to “GeoServer CSW” and “Service URL” to the capabilities url we copied previously.

  • Uncheck “Use account” since in this case our CSW is not secured by a username and password.

  • Choose “Datasets” under the “CATEGORIES” list.

Once the service has been added, return to the harvesting page and select the “GeoServer CSW” service, then click the “Run” button. After a few seconds click the “Refresh” button. Upon success you should see the “Last run” timestamp updated.

Search & Discover

Once the harvest job has completed, GeoNetwork should have all the metadata provided by GeoServer. In this example, GeoServer is publishing a number of layers featuring Natural Earth data. Let’s examine one such layer: parks and protected areas.

Metadata from GeoServer such as title, abstract, and keywords have all been defined. Once GeoNetwork has harvested all this metadata it becomes possible to search using the form on the GeoNetwork home page. As expected, entering the search term “parks” returns on the appropriate layer.

Since the metadata returned by GeoServer provides information about other services, such as WMS, we can browse the data directly in GeoNetwork as well.

The post Harvesting Metadata from OpenGeo Suite using CSW appeared first on Boundless.

Categories: OSGeo Planet

Jackie Ng: Announcing: mapguide-rest 0.7

OSGeo Planet - Mon, 2014-04-14 14:14
Before we continue our blogging journey into the rest of mapguide-rest's data publishing framework, here's the second release of mapguide-rest.

Here's what this new release offers

ACLs for published data sources

We now let you have some level of control as to what users and groups can access a given published data sources, which is important if you are exposing representations that support POST/PUT/DELETE operations and even more important if this is on a public-facing site. You don't want Joe Anonymous MapGuide user to be able to POST/PUT/DELETE to your data sources willy nilly unless you have configured such data sources to allow for such things to happen.

Consider this example from a recent post

    "Source": {
        "Type": "MapGuide",
        "FeatureSource": "Library://Samples/Sheboygan/Data/Parcels.FeatureSource",
        "FeatureClass": "SHP_Schema:Parcels"
    "Representations": {
        "xml": {
            "Adapter": "FeatureSetXml",
            "Methods": {
                "GET": {
                    "MaxCount": 500
                "POST": {},
                "PUT": {},
                "DELETE": {}

This configuration will now deny all users because no ACLs have been defined for it. A configuration like this

    "Source": {
        "Type": "MapGuide",
        "FeatureSource": "Library://Samples/Sheboygan/Data/Parcels.FeatureSource",
        "FeatureClass": "SHP_Schema:Parcels"
    "Representations": {
        "xml": {
            "Adapter": "FeatureSetXml",
            "Methods": {
                "GET": {
                    "MaxCount": 500,
                    "AllowGroups": ["Everyone"]
                "POST": {
                    "AllowUsers": ["Administrator", "Author"]
                "PUT": {
                    "AllowUsers": ["Administrator", "Author"]
                "DELETE": {
                    "AllowUsers": ["Administrator", "Author"]

This will define the following access rules:
  • GET: Anybody can access the data source
  • POST: Only the Administrator and Author users (and related session IDs) can access the data source. Everyone else will be denied access.
  • PUT: Only the Administrator and Author users (and related session IDs) can access the data source. Everyone else will be denied access.
  • DELETE: Only the Administrator and Author users (and related session IDs) can access the data source. Everyone else will be denied access.
Auto-API documentation for published data sources

Thanks to the integration of Swagger UI for our REST API documentation needs, and the fact that all published data sources will offer a "fixed" REST API to interact with it, we now can provide automatic REST API documentation for any published data source.

Simply append a doc/index.html to access a data source's API documentation

New REST API routes

This release includes plenty of new routes to play with
  • GET /library/{resourcePath}.WebLayout/viewer (Load the given Web Layout into the AJAX viewer)
  • GET /library/{resourcePath}.ApplicationDefinition/viewer/{template} (Load the given Flexible Layout in Fusion with the given template)
  • POST /library (Load a package file into the repository)
  • GET /services/getschemamapping.{type} (Get the schema mapping for a given FDO provider and partial connection string)
  • GET /library/{resourcePath}.FeatureSource/preview (Launch a schema report preview on the given Feature Source)
  • GET /library/{resourcePath}.LayerDefinition/preview (Launch a AJAX viewer preview of the given Layer Definition)
  • GET /library/{resourcePath}.MapDefinition/preview (Launch a AJAX viewer preview of the given Map Definition)
  • GET /library/{resourcePath}.SymbolDefinition/preview (Render a preview of the given Symbol Definition)
  • GET /library/{resourcePath}.WatermarkDefinition/preview (Launch a AJAX viewer preview of the given Watermark Definition)
  • GET /session/{sessionId}/{resourceName}.WebLayout/viewer (Load the given Web Layout into the AJAX viewer)
  • GET /session/{sessionId}/{resourceName}.ApplicationDefinition/viewer/{template} (Load the given Flexible Layout in Fusion with the given template)
  • GET /session/{sessionId}/{resourceName}.FeatureSource/preview (Launch a schema report preview on the given Feature Source)
  • GET /session/{sessionId}/{resourceName}.LayerDefinition/preview (Launch a AJAX viewer preview of the given Layer Definition)
  • GET /session/{sessionId}/{resourceName}.MapDefinition/preview (Launch a AJAX viewer preview of the given Map Definition)
  • GET /session/{sessionId}/{resourceName}.SymbolDefinition/preview (Render a preview of the given Symbol Definition)
  • GET /session/{sessionId}/{resourceName}.WatermarkDefinition/preview (Launch a AJAX viewer preview of the given Watermark Definition)
You can use the provided interactive REST API documentation to find out more information about these new routes
Improved HTML representation of the site repository

The default HTML representation of the site repository is very bare-bones and primitive.

With the power of Bootstrap 3, we've brought the HTML representation into the 21st century :)

Most of the resource options now show their results inline

Any Web Layout or Application Definition resources now expose new options for you to launch them in their respective AJAX or Fusion viewer

This is still experimental code, so standard disclaimer: use in production at your own risk.

Categories: OSGeo Planet

Slashgeo (FOSS Articles): Batch Geonews: Get Your Google Glass on April 15, TopoJSON, GDAL/OGR for ArcGIS, Ukraine Maps, and much more

OSGeo Planet - Sun, 2014-04-13 19:05

Here's the recent geonews in batch mode.

On the open source / open data front:

On the Esri front:

On the Google front:

Discussed over Slashdot:

In the everything else category:

In the maps category:

Forward logo Google Plus One Facebook logo Twitter logo LinkedIn logo
Categories: OSGeo Planet

Jo Cook: Complexity vs Quality

OSGeo Planet - Sun, 2014-04-13 14:28

Recently I had need to evaluate a Proprietary Desktop GIS (PDG for short) to document the procedure for doing a Thing for a client. To avoid any mud-slinging and name calling , I’m naming neither the PDG or the Thing, I’ll just say that the Thing is something that the PDG claims to be able to do. This is not a blog post excoriating PDGs by the way, it’s a reflection on the virtues of simplicity, good documentation, and being honest and open.

So, I download a trial version of the PDG and spend 2 hours installing and licensing it. During this time I have to consult the documentation on exactly what licensing options I wanted for a TRIAL piece of software. I also have to consult the documentation on exactly how to apply the license. No mind, I get the software installed and working and try and do the Thing. I remember from several years ago, last time I tried to do the Thing with the PDG, that it was slightly tricky, but several versions have been and gone, all of which claim to be able to do the Thing. Consequently though, I cut the PDG a bit of slack when it can’t do the Thing, and I try the work-around. Yes, that still works, though I don’t know how you’d guess that from the error messages or the documentation. It’s not ideal to need two methods of doing the Thing but hey ho. I also cut the PDG some slack when it tells me that I can only do the Thing if I adhere to some very unusual naming conventions, which will mean that, should I need to do this for real, I will have a lot of work to do renaming a bunch of stuff.

Let’s take this up a level. I don’t only need to do the Thing, but also the related Slightly More Complicated Thing (SMCT for short) too. I confess that the documentation doesn’t really say out and out that the PDG can do this, but it certainly implies it. Only, it doesn’t seem to be able to without a license for it’s rather more expensive elder brother, the Proprietary Server GIS (PSG for short). However, to explain this to the client, I will need some documentary proof. I can find blog and forum posts admitting it’s true, and for all I know there might be lots of information in the knowledge base for the PDG and PSG but you have to have a customer number to access this and because I am only evaluating the software, I haven’t purchased it yet, so I don’t have one of those.

So, I ask some questions of colleagues, and while waiting for them to get back to me, I try some work-arounds for the SMCT. Needless to say, they don’t work either.

A colleague finally gets back to me. After some incredulity that the PDG really can’t do the SMCT when everything implies that it can, said colleague, in his other role as a re-seller for the PDG rings them up and asks. “Yes, we can do that” says the first person, let me find a Thing-specialist to explain how. “No, we can’t do that” says the Thing-specialist. “Our reasons are very complicated, but here’s some obscure documentation that actually admits that we can’t do it”. We let the client know the good news.

As I said earlier, this is not a post excoriating PDG, it’s a reflection on the virtues of simplicity, good documentation, and being honest and open.

Reflection One: The whole process of installing the PDG and discovering the various methods of doing the Thing was needlessly over-complicated. This may be due to the long history of the PDG, and the enormous feature-set, but it feels like bloat. Complexity and a huge feature-set do not necessarily equate to quality, and similarly simplicity and a smaller feature-set are not a bad thing.

Reflection Two: Why hide documentation behind what’s effectively a pay-wall? Had I actually been in the market for purchasing this software, I would have given up at that point. Documentation should be freely available to everyone.

Reflection Three: We really should not have needed to get a re-seller to ring up, and speak to two different people, just to get a definitive answer on the capabilities of a piece of software. This is wrong on so many levels.

In my opinion, these points have nothing to do with the license applied to the source code of the software, or the name on the box: Don’t fall prey to Zawinski’s Law, do make your documentation comprehensive and easily accessible, and do be honest about your capabilities. I’d pay good money for that.

Categories: OSGeo Planet

Markus Neteler: Workshop at FOSS4G 2014: Spatio-temporal data handling and visualization in GRASS GIS 7

OSGeo Planet - Sat, 2014-04-12 12:30

Drowning in too many maps? Have some fun exploring fascinating geometries of changing landscapes in Space Time Cube and creating 2D and 3D animations from time series of geospatial data. Learn about the new capabilities for spatio-temporal data handling in GRASS GIS 7 (http://grass.osgeo.org/grass7/) and explore various techniques for dynamic visualizations.

First, we will introduce you to GRASS GIS 7, including its spatio-temporal capabilities and you will learn how to manage and analyze geospatial data time series. Then, we will explore new tools for visualization of spatio-temporal data. You will create both 2D and 3D dynamic visualizations directly in GRASS GIS 7. Additionally, we will explain the Space Time Cube concept using various applications based on raster and vector data time series. You will learn to manage and visualize data in space time cubes (voxel models). No prior knowledge of GRASS GIS is necessary, we will cover the basics needed for the workshop. All relevant material including an overview of the tools and hands-on practical instructions along with the sample data sets will be available on-line. And, by the way, GRASS GIS is a free and open source geographic information system (GIS) used for geospatial data management, analysis, modeling, image processing, and visualization which runs on Linux, MS Windows, Mac OS X and other systems.

Presenters: Vaclav Petras, Anna Petrasova, Helena Mitasova, Markus Neteler

When:  FOSS4G 2014, Sept 8th-13th 2014, Portland, OR, USA

Register at: https://2014.foss4g.org/schedule/workshops/#wshop-526

Categories: OSGeo Planet

Paulo van Breugel: Add multiple raster or vector map layers to current map display in GRASS GIS

OSGeo Planet - Sat, 2014-04-12 10:00
If your mapset contains many raster or vector layers GRASS offers a very handy feature to quickly select the layers you want to add to your current map display. In the layer manager, click Ctrl+Shift+L to open the ‘add selected map … Continue reading →
Categories: OSGeo Planet

FOSS4G 2014: Regular Session and Academic Track proposals due early next week (4/15)

OSGeo Planet - Fri, 2014-04-11 16:41

April 11, 2014
Portland, OR, USA

Regular Session and Academic Track proposals due

A reminder to all FOSS4G attendees – the proposal submission deadline for both the Academic Track and Regular Sessions is next Tuesday, April 15th. For the Regular Sessions, we strongly recommend reviewing our advice for successful proposals before submitting.

The community voting on the Regular Sessions will directly follow the deadline, April 18th to 28th.

Travel Grant Announcement

We realize that traveling to and attending a conference can be expensive, and that not everyone who uses or develops open source software has provided funding to pay their way or the means to pay for it themselves. To make sure that as many deserving people as possible can attend FOSS4G, we’re creating a travel grant program with funds to cover registration and travel costs. Watch for details coming soon.

One additional reminder: Early Bird Registration is open!

Important Conference Dates

See the full calendar for more details.

  • April 15th: Academic Paper/Presentation Proposals Due
  • June 15th: Early bird registration ends
  • Sept 8th-9th: Workshops
  • Sept 10th-12th: Main Conference
  • Sept 13th: Code Sprint


See you in Portland,


FOSS4G PDX Local Organizing Committee

About FOSS4G

Put on by OSGeo, the annual FOSS4G conference is the premiere global gathering for people working with and creating open source geospatial software. It brings together developers, users, decision makers, and observers from a broad spectrum of organizations and fields of operation for six days of workshops, presentations, discussions, and cooperation. From this melting pot of great spatial ideas and industry flow numerous successful geospatial products, standards and protocols.

FOSS4G has been held all over the world and draws attendees from over 40 countries. Nottingham, England hosted the conference in 2013. In 2014, Portland, Oregon, USA will host FOSS4G’s tenth year.

About OSGeo

The Open Source Geospatial Foundation was founded in 2006 to support and build the highest-quality open source geospatial software. The foundation’s goal is to encourage the use and collaborative development of community-led projects, data development and education. Many projects live under the OSGeo umbrella, including FOSS4G. http://osgeo.org

About PDX OSGeo – Portland Area and Oregon OSGeo Chapter

The PDX-OSGeo chapter of OSGeo has been meeting, discussing and promoting the use of open source geospatial technology since 2009. Chapter members often organize or present on open source software at regional geospatial conferences. PDX is the airport code and like the PDX airport, the group has a wide catchment area.

Sponsors: Silver Level Sponsors



Bronze Level Sponsors

azaveacartodb_150x53 logo_klein_foss4g



AppGeoFOSS4G2014 camptocamp_logolocate-press-150mapgears_rgb_transparent_nb_150x81NBT_logo_150x60logo_terrestris

Media Partner

directionsmagazine_logo geoconnexion_logo Geospatial-World-FOSS4G-2014_v2-NEW- Logo GIM-voor drukkerkopie 150gis-news

GISusrNews  LBxJournal systems_and_sensors_logoslashgeo_logo VSlogobanner1_ 3dvisworld2800_square_trans_small2


For more information or to keep informed from the FOSS4G Organizing Committee, follow @foss4g on Twitter, subscribe to our announcements list, or contact: foss4g2014-info@osgeo.org

Darrell Fuhriman, Chair of the FOSS4G Organizing Committee, email: darrell@garnix.org

Categories: OSGeo Planet

GeoSolutions: Released the support for NGMP (NATO Geospatial Metadata Profile) in GeoNetwork

OSGeo Planet - Fri, 2014-04-11 15:31


Dear all,

we have committed in the GeoNetwork official repository a schema plugin that deals with NGMP the Nato GeoSpatial Military Profile which is available here.

As you may know, GeoNetwork has introduced in v2.8 a mechanism for supporting pluggable schemas, that is:

A schema in GeoNetwork is a directory with stylesheets, XML schema descriptions (XSDs) and other information necessary for GeoNetwork to index, view and possibly edit content from XML metadata records. 

The XML records we are dealing with are metadata following the NGMP standard, an ISO19139 application profile developed by DGIWG and NATO in order to extend the information about accessibility, releasability and classification of the data. In our use case GeoNetwork is used as a backend for harvesting prepared metadata and expose them through a CSW endpoint; it means that no editing capabilities were required.

The workplan needed to create some templates with placeholders; such templates were then processed by custom scripts that, by replacing the placeholders with information extrapolated from the real data, generated the final metadata files to be ingested in GeoNetwork .   

Editing the metadata in GeoNetwork was not needed, but creating templates by hand is extremely error prone, so as a first step we implemented the validation part, by adding the NGMP schema and writing  Schematron rules to enforce some major constraints. This first step allowed us to validate the templates and also to check the validity of the processed metadata.

  1.  The ingested metadata need then to be published. Metadata dissemination is performedusing GeoNetwork itself as a viewer, so the related XSL presentation files have been developed
  2. through CSW: we implemented some conversion XSL files in order to present the metadata records as base ISO19139 records (e.g. mapping some NGMP specific codelist into keywords)
  3.  exporting the XML files from the GUI: we reused the XSL templates in order to offer both the NGMP record and the record "flattened" in plain ISO19139.

If you are interested in learning about how we can help you achieving your goals with our Open Source products and professional services, do not hesitate to contact us!

 The GeoSolutions team,


Categories: OSGeo Planet

Faunalia: QGIS PT users group: Portuguese speaking community

OSGeo Planet - Thu, 2014-04-10 16:42
It’s with an enormous pleasure that we announce what we believe to be a very important step for the QGIS Portuguese speaking community, the creation of the QGIS PT users group. The QGIS PT users group arise from the notorious growth of QGIS usage  in Portugal, with the objective of become a platform for sharing […]
Categories: OSGeo Planet

Boundless Blog: Support story: Deterministic rendering order in SLDs

OSGeo Planet - Thu, 2014-04-10 13:39

MassGIS As with our first support story, this one comes from MassGIS, the official state agency assigned to the collection, storage, and dissemination of geographic data. When a layer has overlapping lines or polygons, we often want to control which ones are rendered on top and which ones are rendered below. The classic example is when we have a roads layer that contains overpasses that we want to appear above regular roads at ground level. MassGIS was dealing with a land-usage layer which required one type of polygon to be rendered with a solid color and other types to be rendered above with specific patterns.

The Aral Sea Example

We can simulate this problem by taking a layer that has both current and historical extents of bodies of water. In particular we’ll look at the Aral Sea, which shrunk considerably in the twentieth century. We’ll want to style the historical extents using hatching and then overlay the current lake in a plain blue style. What we don’t want is to have the historical bounds drawn over the modern lake.

You can test on your own GeoServer install with the data and SLDs in this ZIP.

SLD Rules

Our first attempt at creating an SLD to draw the two polygons in the correct order is to use two rule statements: the first will match our historical layer (where attribute type is equal to historical) and the second will match the modern layer (where the attribute type is equal to modern). We expect this to draw the historical lakes first and then the modern lakes on top:

<sld:StyledLayerDescriptor version="1.0.0" xmlns:sld="http://www.opengis.net/sld"> <sld:NamedLayer> <sld:Name>Lakes</sld:Name> <UserStyle xmlns="http://www.opengis.net/sld"> <FeatureTypeStyle> <Rule> <Name>Historical area</Name> ... </Rule> <Rule> <Name>Modern area</Name> ... </Rule> </FeatureTypeStyle> </UserStyle> </sld:NamedLayer> </sld:StyledLayerDescriptor>

Unfortunately, this gives us the opposite effect: the historical area has been rendered above the modern area.

Since this ordering of the rules didn’t work, we can try switching them around in the SLD, putting the rule for modern lakes first and historical lakes second. If you test this in GeoServer, however, you will see that the image that we get back is not affected.

Since reordering rules in an SLD does not affect the output image, we had to provide another approach.

SLD FeatureTypeStyle

The answer to the problem is to use the rules in separate <FeatureTypeStyle> sections of our SLD document:

<sld:StyledLayerDescriptor version="1.0.0" xmlns:sld="http://www.opengis.net/sld"> <sld:NamedLayer> <sld:Name>Lakes</sld:Name> <UserStyle xmlns="http://www.opengis.net/sld"> <FeatureTypeStyle> <Rule> <Name>Historical area</Name> ... </Rule> </FeatureTypeStyle> <FeatureTypeStyle> <Rule> <Name>Modern area</Name> ... </Rule> </FeatureTypeStyle> </UserStyle> </sld:NamedLayer> </sld:StyledLayerDescriptor>

Why does this work?

Our first approach did not work since rules inside a single FeatureTypeStyle are applied to features as they arrive from the data source. GeoServer was drawing the modern Aral Sea first and the historical Aral Sea second simply because that is the order in which they were stored in the shapefile.

Even if the order had been correct, it would have been dangerous to rely on it for styling since that order could change at any time.

To reliably control the rendering order, therefore, we need the multiple FeatureTypeStyle blocks. GeoServer will draw each of these independently and then merge them in the defined order as the last step.

Benjamin Trigona-Harany leads our global support team from our offices in Victoria, BC. Interested in support or training for your enterprise? Contact us to learn more.

The post Support story: Deterministic rendering order in SLDs appeared first on Boundless.

Categories: OSGeo Planet

GIS for Thought: UK Rail Network Visualized by Operator

OSGeo Planet - Thu, 2014-04-10 08:00

The United Kingdom’s railway network is split up into regional franchises, these franchises are run by private companies who bid on the work. So for example ScotRail, which runs the trains in Scotland is owned by the FIrst Group, who also run a number of other regional franchises. This can however change, when the contracts are up for bid.

Interestingly there is also a governmental holding company (Directly Operated Railways), which can take over a franchise if necessary, they currently run East Coast Trains.

For this visualization I have grouped Serco-Abellio and Abellio as Serco/Abellio.

EDIT: Like mentioned in the Scotland to the Rest of the UK, lines are drawn between stations on a route. So a direct route from Glasgow to London would be a direct line between the two terminus stations.

UK Railway Network by Operator

Inspired by Scotland’s connections to the rest of the UK.


Train lines: GTFS Data Exchange

Country outline: Natural Earth

Categories: OSGeo Planet
Syndicate content