OSGeo Planet

GeoServer Team: GeoServer 2.12-beta Released

OSGeo Planet - Fri, 2017-09-15 00:06

We are happy to announce the release of GeoServer 2.12-beta. Downloads are available (zipwardmg and exe) along with docs and extensions.

This is a beta release of GeoServer made in conjunction with GeoTools 18-beta.

We want to encourage people to test the release thoroughly and report back any issue found. With no further delay, let’s see what’s new, that is, what is there to test!

Rest API now using Spring MVC

In March, we upgraded the framework used by the GeoServer REST API from Restlet to Spring MVC. All the endpoints should remain unchanged, but they do need testing to ensure there weren’t any unintended side effects.

As part of this upgrade, we also have new REST documentation, providing detailed information about each endpoint.

Thanks again to the code sprint sponsors:

  • Boundless
  • GeoSolutions
  • Astun Technology
  • Gaia3D
  • Insurance Australia Group (IAG)
  • How 2 Map
  • FOSSGIS
  • Atol Conseils et Développements
  • Geodan
WMTS Cascading

Adds the ability to create WMS layers backed by remote WMTS layers, similar to the pre-existing WMS cascading functionality.

See GSIP-162 for more details.

Style Based Layer Groups

Adds the ability to define a listing of layers and styles using a single SLD file, in accordance with the original vision of the SLD specification. This includes a new entry type in the Layer Group layers list, and a new preview mode for the style editor.

See GSIP-161 for more details.

Options for KML Placemark placement

New options for KML encoding have been added, to control the placement of placemark icons, mostly for polygons. The syntax of the new options introduces three new top level format options keys:

&format_options=kmcentroid_contain:true;kmcentroid_samples:10;kmcentroid_clip:true

See GSIP-160 for more details.

GeoWebCache data security API

Add an extension point to GeoWebCache allowing for a security check based on the layer and extent of the tile. Adds an implementation of this extension point to GeoServer’s GWC integration.

This change mostly only affects developers, but will lead to improved security for users in the future.

See GSIP 159 for more details.

NetCDF output support for variable attributes and extra variables

Adds the following to the NetCDF output extension:

  1. An option to allow all attributes to be copied from the source NetCDF/GRIB variable to the target variable.
  2. Support for manual configuration of variable attributes, much like the current support for setting global attributes.
  3. Support for configuration of extra variables which are copied from the NetCDF/GRIB source to the output; initially only scalar variables will be supported. Extra variables can be expanded over “higher” dimensions, that is, values copied from one scalar per ImageMosaic granule are assembled into a multidimensional variable over, for example, time and elevation.

See GSIP 158 for more details.

New labeling features and QGIS compatibility

A number of small new features have been added to labeling to match some of QGIS features, in particular:

  • Kerning is on by default
  • New vendor option to strikethrough text
  • New vendor options to control char and word spacing

../../../_images/charSpacing.png

  • Perpendicular offset now works also for curved labels (previously only supported for straight labels):
  • Labeling the border of polygons as opposed to their centroid when using a LinePlacement (here with repetition and offset):

Along with this work some SLD 1.1 text symbolizer fixes were added in order to better support the new QGIS 3.0 label export, here is an example of a map labeling with background image, as shown in QGIS, and then again in GeoServer using the same data and the exported SLD 1.1 style (click to enlarge):

   

CSS improvements

The CSS styling language and editing UI have seen various improvements. The editor now supports some primitive code completion:

At the language level:

  • Scale dependencies can now also be expressed using the “@sd” variable (scale denominator) and the values can use common suffixes such as k and M to get more readable values, compare for example “[@scale < 1000000]” with “[@sd < 1M]”
  • Color functions have been introduced to match LessCSS functionality, like “Darken”, “Lighten, “Saturate” and so on. The same functions have been made available in all other styling languages.
  • Calling a “env” variable has been made easier, from “env(‘varName’)” to “@varName” (or “@varName(defaultValue)” if you want to provide a default value).

As you probably already know, internally CSS is translated to an equivalent SLD for map rendering purposes. This translation process became 50 times faster over large stylesheets (such as OSM roads, a particularly long and complicated style).

Image mosaic improvements and protocol control

Image mosaic saw several improvements in 2.12.

First, the support for mosaicking images in different coordinate reference systems improved greatly, with several tweaks and correctness fixes. As a noteworthy change, the code can now handle source data crossing the dateline. The following images show the footprints of images before and after the dateline (expressed in two different UTM zones, 60 and 1 respectively) and the result of mosaicking them as rasters (click to get a larger picture of each):

There are more good news for those that handle mosaicks with a lot of super-imposing images taken at different times. If you added interesting information into the mosaic index, such as cloud cover, off-nadir, snow cover and the like, you can now filter and sort over them, in both WMS (viewing) and WCS (downloading) by adding the cql_filter and sortBy KVP parameters.

Here is an example of the same mosaic, the first composite favoring smallest cloud cover, the second one favoring recency instead (click to enlarge):

     

GeoPackage graduation

The GeoPackage store jumped straight from community to core package, in light of its increasing importance.

The WMS/WFS/WPS output formats are still part of community. Currently GeoPackage vector does not support spatial indexes, but stay tuned, it’s cooking!

New community modules

The 2.12 series comes with a few new community modules, in particular:

  • Looking into styling vector tiles and server side using a single language? Look no further than the MBStyle module
  • For those into Earth Observation, there is a new OpenSearch for EO module in the community section
  • Need to store full GeoTiff in Amazon S3? The “S3 support for GeoTiff” module might just be what you’re looking for
  • A new “status-monitoring” community module is about to be merged, providing basic statistics system resource usage. Check out this pull request to follow its progress and merge.

Mind, community modules are not part of the release, but you can find them in the nightly builds instead.

Other assorted improvements

There are many improvements to look at in the release notes, cherry picking a few here:

  • SLD files not deleted when SLD is deleted in web admin
  • Reproject geometries in WMS GetFeatureInfo responses when info_format is GML
  • Include Marlin by default in bin/win/osx downloads, add to war instructions
  • Handle placemark placement when centroid of geometry not contained within
  • Enable usage of viewParams in WPS embedded WFS requests
  • Add GeoJson encoder for complex features
  • Allow image mosaic to refer a GeoServer configured store
  • Duplicate GeoPackage formats in layer preview page
  • ExternalGraphicFactory does not have a general way to reset caches
  • Generating a raster SLD style from template produced a functionally invalid style, now fixed
  • Style Editor Can Create Incorrect External Legend URLs
  • Namespace filtering on capabilities returns all layer groups (including the ones in other workspaces)
Test, test, test!

Now that you know about all the goodies, please go, download and test your favourite ones. Let us know how it went!

About GeoServer 2.12

GeoServer 2.12 is scheduled for September 2017 release.

Categories: OSGeo Planet

GeoTools Team: GeoTools 18-beta Released

OSGeo Planet - Thu, 2017-09-14 21:15
The GeoTools team is pleased to announce the release of GeoTools 18-beta:This release is also available from our Maven repository.
This release is made in conjunction with GeoServer 2.12-beta.
Highlights from our issue tracker release-notes:
  • Support NetCDF >4 dimensions, including runtime
  • Make MongoDB usable as a data store in app-schema
  • Allow CSS scale denominators to use SI metric prefixes, "k", "M" and "G"
  • Create a CoverageReader for remote WMTS layers
  • New vendor option to control label character spacing
  • ExternalGraphicFactory does not have a general way to reset caches
  • Upgrade PostgreSQL JDBC driver to 42.1.1
  • Remove "-gt-" prefixes from CSS vendor options
  • GeoPackage tile order inverted along y-axis
  • SLDParser / SLDTransformer fails to round-trip empty nodes.
  • GridCoverageRenderer can miss part of an image when the source data overlaps the dateline on both sides
For more information see the 18-beta release notes.
    Categories: OSGeo Planet

    Paul Ramsey: PostGIS Operators in 2.4

    OSGeo Planet - Thu, 2017-09-14 16:00

    TL;DR: If you are using ORDER BY or GROUP BY on geometry columns in your application and you have expectations regarding the order or groups you obtain, beware that PostGIS 2.4 changes the behaviour or ORDER BY and GROUP BY. Review your applications accordingly.

    The first operators we learn about in elementary school are =, > and <, but they are the operators that are the hardest to define in the spatial realm.

    PostGIS Operators in 2.4

    When is = equal?

    For example, take “simple” equality. Are geometry A and B equal? Should be easy, right?

    But are we talking about:

    1. A and B have exactly the same vertices in the same order and with the same starting points?
    2. A and B have exactly the same vertices in any order? (see ST_OrderingEquals)
    3. A and B have the same vertices in any order but different starting points?
    4. A has some extra vertices that B does not, but they cover exactly the same area in space? (see ST_Equals)
    5. A and B have the same bounds?

    Confusingly, for the first 16 years of its existence, PostGIS used definition 5, “A and B have the same bounds” when evaluating the = operator for two geometries.

    However, for PostGIS 2.4, PostGIS will use definition 1: “A and B have exactly the same vertices in the same order and with the same starting points”.

    Why does this matter? Because the behavour of the SQL GROUP BY operation is bound to the “=” operator: when you group by a column, an output row is generated for all groups where every item is “=” to every other item. With the new definition in 2.4, the semantics of GROUP BY should be more “intuitive” when used against geometries.

    What is > and <?

    Greater and less than are also tricky in the spatial domain:

    • Is POINT(0 0) less than POINT(1 1)? Sort of looks like it, but…
    • Is POINT(0 0) less than POINT(-1 1) or POINT(1 -1)? Hm, that makes the first one look less obvious…

    Greater and less than are concepts that make sense for 1-dimensional values, but not for higher dimensions. The “>” and “<” operators have accordingly been an ugly hack for a long time: they compared the minima of the bounding boxes of the two geometries.

    • If they were sortable using the X coordinate of the minima, that was the sorting returned.
    • If they were equal in X, then the Y coordinate of the minima was used.
    • Etc.

    This process returned a sorted order, but not a very satisfying one: a “good” sorting would tend to place objects that are near to each other in space, near to each other in the sorted set.

    Here’s what the old sorting looked like, applied to world populated places:

    Geometry sorting in PostGIS 2.3

    The new sorting system for PostGIS 2.4 calculates a very simple “morton key” using the center of the bounds of a feature, keeping things simple for performance reasons. The result is a sorted order that tends to keep spatially nearby features closer together in the sorted set.

    Geometry sorting in PostGIS 2.4

    Just as the “=” operator is tied to the SQL GROUP BY operation, the “>” and “<” operators are tied to the SQL ORDER BY operation. The pictures above were created by generating a line string from the populated places points as follows:

    CREATE TABLE places_line AS SELECT ST_MakeLine(geom ORDER BY geom) AS geom FROM places;
    Categories: OSGeo Planet

    gvSIG Team: 13th International gvSIG Conference: Program with presentations and workshops available

    OSGeo Planet - Thu, 2017-09-14 11:58

    The program with presentations and workshops of the 13th International gvSIG Conference is now available. The conference has been moved earlier this year, and it will be held from October 18th to 20th at School of Engineering in Geodesy, Cartography and Surveying (Universitat Politècnica de València, Spain). Friday will be dedicated to a gvSIG developers meeting.

    Workshops will have independent registration, with limited capacity and having the possibility to get a certificate. Registration for workshops, that are free of charge, will be available at the website soon. Workshops available are:

    • Workshop 1: Introducción a gvSIG
    • Workshop 2: Geoestadística con gvSIG
    • Workshop 3: gvSIG aplicado a criminología
    • Workshop 4: Introducción al desarrollo en gvSIG con Scripting
    • Workshop 5: Hydro-geomorphological Modelling in gvSIG with the JGrasstools plugins in English)
    • Workshop 6: gvSIG Online y gvSIG Mobile
    • Workshop 7: Desarrollo avanzado en gvSIG con scripting

    This year there won’t be simultaneous interpretation (Spanish-English and English-Spanish), so presentations and workshops will be given in their original language.

    In the next days, all the information about workshops will be published at the gvSIG blog, with the cartography, and what you have to install in case you have to take your own computer to the workshop.

    In addition, registrations of the conference are free of cost too (limited capacity) and must be done through the application form on the Conference web page. We recommend you to register as soon as possible because of the limited capacity.

    We expect your participation!


    Filed under: community, english, events, training Tagged: 13th gvSIG Conference, presentations, workshops
    Categories: OSGeo Planet

    gvSIG Team: 13as Jornadas Internacionales de gvSIG: Programa de ponencias y talleres disponible

    OSGeo Planet - Thu, 2017-09-14 11:43

    Ya está disponible el programa con las ponencias y talleres que se van a dar en las 13as Jornadas Internacionales de gvSIG, que este año se adelantan respecto a las fechas en que se han ido celebrando en los últimos años. Concretamente tendrán lugar del 18 al 20 de octubre en Valencia (España), en la Escuela Técnica Superior de Ingeniería Geodésica, Cartográfica y Topográfica (Universitat Politècnica de València), dedicándose el día 20 para reunión de los desarrolladores del proyecto.

    Al igual que el año pasado, los talleres se realizarán mediante inscripción independiente, con un número de plazas limitadas, y pudiéndose obtener certificado tras ellos. La inscripción se podrá realizar en los próximos días desde los enlaces que se habilitarán en la web de las jornadas. Los talleres que se impartirán, totalmente gratuitos, son los siguientes:

    • Taller 1: Introducción a gvSIG
    • Taller 2: Geoestadística con gvSIG
    • Taller 3: gvSIG aplicado a criminología
    • Taller 4: Introducción al desarrollo en gvSIG con Scripting
    • Taller 5: Hydro-geomorphological Modelling in gvSIG with the JGrasstools plugins
    • Taller 6: gvSIG Online y gvSIG Mobile
    • Taller 7: Desarrollo avanzado en gvSIG con scripting

    Este año no se dispondrá de traducción simultanea Español-Inglés y viceversa, por lo que las ponencias y talleres se darán en su idioma original.

    En los próximos días se irá publicando la información sobre los distintos talleres en el blog de gvSIG, con la cartografía necesaria y lo que hay que llevar instalado en caso de que en el taller se deba llevar ordenador propio.

    Por otro lado, la inscripción a las jornadas, independiente de la de los talleres, sigue abierta, siendo el aforo limitado, por lo que recomendamos realizarla lo antes posible. Las inscripciones son gratuitas.

    ¡Os esperamos!


    Filed under: community, development, events, scripting, spanish, training Tagged: 13as Jornadas gvSIG, ponencias, talleres
    Categories: OSGeo Planet

    GeoNode: Docs For Devs

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Translate

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Improve

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Future

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Patches

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Contribute

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Extend

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Arch

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Testing

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Env Dev

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Management Commands

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Backups

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Other Languages

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Ssl

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet

    GeoNode: Troubleshoot

    OSGeo Planet - Thu, 2017-09-14 11:41
    Categories: OSGeo Planet
    Syndicate content