OSGeo Planet

Cameron Shorter: Where is the Universal Code of Conduct?

OSGeo Planet - 1 hour 15 min ago
Diversity image: [source]OSGeo has adopted a Code of Conduct for use across events and projects [Press Release].
It draws very heavily upon upon prior work. In researching, it was interesting to see how Code-of-Conduct iterations have been steadily improving over time [200120102012201220142014]. Positive language has replaced authoritative tones; edge use cases are covered; and a gradual escalation process helps communities self police most infringements in a non-confrontational manner. Unfortunately, no one, has been collecting these improvements into a Universal Code of Conduct. It would have been really nice to simply reference an Industry Code of Conduct, similar to the Creative Commons Licenses for data, or Open Source licenses for Software.
Categories: OSGeo Planet

GeoTools Team: GeoTools 14-M0 Tech Preview

OSGeo Planet - Fri, 2015-05-29 09:22
GeoTools is pleased to announce GeoTools 14-M0 as a technology preview:This release is also available from our maven repository. This release is made in conjunction with GeoServer 2.8-M0 and the next release of GeoMesa.This release is a "technology preview" giving projects, specifically GeoMesa and GeoGig, a chance to try out a new version of GeoTools that uses EJML for matrix calculations.While we do not often release milestone releases please reach out to us if your project needs a new copy of GeoTools.Our release-notes are now available from their new home at osgeo-org.atlassian.net:
  • Change from vecmath to EJML
  • JAI-EXT integration in geotools, adding native support for NODATA in rasters
  • Allow extshape://arrow to receive parameters to specify its proportions [GEOT-5126]
  • Add AUTO:97001 and AUTO:97002 projections
  • Add read and write support for curves in Postgis data store [GEOT-5100GEOT-5112]
  • Add write support for curves in PropertyDataStore
  • Add support for by layer interpolation methods to StreamingRenderer [GEOT-5064]
  • Significantly speed up GML 3.x encoding speed for simple features [GEOT-5082]
  • New projections supported: sinuoidal, gnomonic
We encourage everyone to take this opportunity test their application against the new version of GeoTools. We are very interested in any accuracy or performance differences.CodeHaus MigrationWe previously a migration schedule for moving our issue tracker from CodeHaus to Atlassian cloud hosting.This migration is still ongoing. Issue title, description and comments have been ported over. Please wish Harrison Grundy well as he ports the remaining status and issue metadata.CodeHaus shuts down completely on May 29th.EJMLEfficient Java Matrix Library (EJML) is a linear algebra library for dense matrices. EJML has been integrated as a replacement for the Java 3D vecmath library which has been used previously. GeoTools uses linear algebra extensively during CoordinateReferenceSystem math transformations. In testing EJML we have noticed some difference with the accuracy of matrix inverse operations, but performance seems to remain steady.This milestone release completes the work of the FOSS4G code Sprint to replace vecmath.
Categories: OSGeo Planet

gvSIG Team: Guatemala pone en marcha la Comunidad gvSIG

OSGeo Planet - Fri, 2015-05-29 09:20

Flag_of_Guatemala.svgUna nueva comunidad se suma al ya extenso conjunto de comunidades organizadas del proyecto gvSIG.

Se conforma la Comunidad gvSIG Guatemala promovida inicialmente por cinco coordinadores con amplia experiencia en el mundo de los Sistemas de Información Geográfica.

A partir de aquí se comenzarán a promover acciones para divulgar y dar a conocer el proyecto gvSIG y su modelo de desarrollo basado en el conocimiento compartido.

Cualquier persona interesada en sumarse de forma activa a esta comunidad, que no dude en ponerse en contacto con nosotros.


Filed under: community, spanish Tagged: Guatemala
Categories: OSGeo Planet

GeoServer Team: GeoServer 2.8-M0 Released

OSGeo Planet - Fri, 2015-05-29 06:16

We are happy to announce the release of GeoServer 2.8-M0. Downloads are available (zip, war, dmg and exe) along with docs and extensions.

This is milestone release of GeoServer made in conjunction with GeoTools 14-M0.

We have both new features and a number of key “under the hood” changes to GeoServer. This technology preview is made available for your evaluation and feedback and is not intended for production.

Highlights from the release notes:

  • JAI-Ext integration for geospatial specific image processing operations  (github), adding direct support for NODATA in raster sources
  • Replacement of vecmath with EJML matrix library
  • Importer improvements, dalwarp/gdal_translate/gdaladdo transformations and ability to add a granule to a mosaic
  • Read/write PostGIS curve support
  • GetMap support for by layer interpolation methods
  • Stop shipping old Oracle JDBC driver
  • Pretty print option for style REST API
  • Allow environment variables to be used in freemarker template files

Also, looking at the GeoTools 14-M0 release notes, we have:

  • Significant increase in GML 3.X encoding speed
  • New projections supported: sinusoidal, gnomonic
  • New extshape://arrow with parameters controlling its proportions

Thanks to Jody (Boundless) for pulling this release together.

About GeoServer 2.8

GeoServer 2.8 is scheduled for September release. For more information:

We will add additional blog posts to this section as news is made available.

Categories: OSGeo Planet

Marco Bernasocchi: Tak Nødebo

OSGeo Planet - Wed, 2015-05-27 12:14
After a week with QGIS members from all over the world we arrived back home and can say that once again, the QGIS developer meeting #13 was a great event. It started with the QGIS User Conference where a lot… See more ›
Categories: OSGeo Planet

gvSIG Team: New gvSIG plugin: 3D View

OSGeo Planet - Tue, 2015-05-26 12:47

It is now available to be downloaded and tested, the new 3D viewer plug-in for gvSIG 2.2 based on NASA World Wind SDK. This new tool will allow users to create 3D visualizations from traditional 2D views in gvSIG.

This add-on is compatible with all vector and raster formats, databases and web services supported by gvSIG and can be installed either from the repositories “Official” and “Testing” as shown in this video.

Important! This add-on can be installed only on gvSIG 2.2 releases starting from the 2310; thus it is fully usable with the RC2 that can be downloaded from this page.

The main functions provided in this first version:

  • Rasterization of vector layers: it is possible to rasterize the vector layers loaded in 2D view and add them to 3D view. In such a way it is possible to use all the formats supported by gvSIG regardless of layer symbols or labels and use the full potentialities of gvSIG.

  • Load raster layer: it is possible to upload raster layer keeping all the properties of transparency, enhancement and colour tables. Moreover two raster layer are loaded as base maps to improve the 3D visualisation.

  • Upload digital terrain models: you can choose which raster load and use as a digital terrain model as well as use your own DTM. The 3D view incorporates however its global digital model to improve visualisation.

  • Synchronize changes: when you create a 3D view, it is linked to the 2D view from which it was created. This link enables you to apply the changes made in the 2D view such as symbols, layer order, viewing, adding and deleting layers. This synchronization can be performed manually or automatically.

  • Frame Sync: like the changes, you can also synchronize 2D view extension modifications in order to use all the zoom functions of gvSIG and improve the visualization and experience with the 3D view. This synchronization can be performed manually or automatically.

  • Full Screen: this tool displays the full screen 3D view and it can be very useful for presentations and conferences.

In this first version we did our best to provide gvSIG users with a tool to display vector layers, raster and 3D DTM. In the future, we plan to add more features as anaglyph, voxel models, 3D symbols…

In this first version, in order to activate the 3D tools, 2D views must be in EPSG: 4326.

Finally, we invite you to try and report any errors and bugs you find out. For more information, you can check the project Wiki and the user manual.

You can also have a look to this short video about the potentialities of this extension.


Filed under: english, gvSIG Desktop Tagged: gvSIG 3D
Categories: OSGeo Planet

GeoSolutions: INSPIRE Support in GeoServer made easy with HALE

OSGeo Planet - Tue, 2015-05-26 11:31

GeoServer

Dear readers,

The GeoSolutions team is working to make the job of publishing Inspire compliant data easier, by enabling the usage of a visual schema mappings editor, HALE, to configure the GeoServer app-schema extension.

Currently, to publish Inspire compliant data in a specific schema (defined through a set of  xsd files) using GeoServer, the app-schema extension can be used to map a set of existing data sources (for example shapefiles or PostGIS tables in a database) to given xsd schemas.

The extension allows to:

  • create Complex Features, required by many Inspire schemas, while common DataStores only enable the use of Simple Features
  • map existing simple features (configured as usual datastores and featuretypes) to elements of a given xsd to produce schema compliant objects
  • use Complex Features produced by the extension with standard WFS and WMS protocols
Unfortunately the app-schema extension doesn't have any graphical user interface or wizard to help with creating the configuration, therefore getting from data to a working set-up can be a tough job. To solve this problem we looked around and found that a tool to visually map existing data sources to be Inspire compliant already exists, and is the Humboldt Alignment Editor (HALE). This tool allows to:
  • import existing source schema(s) and data in various formats (shapefile, databases, xsd / xml)
  • import existing target schema(s) (xsd, databases, inspire schemas)
  • graphically design transformation mappings from the source to the target
  • interactively execute data transformations to verify the result of the mappings
  • interactively view data transformation that include geometries on a map
Hale Alignment Project When a set of mappings have been designed and saved (as an Alignment project), the transformations can be applied to existing data via the integrated ETL using the command line, or an ad hoc REST API service. HALE Data and Map Views All of these features make HALE the best candidate to become a configuration UI for the GeoServer app-schema extension, and this is why we are currently working with the HALE community to:
  • improve HALE itself adding new kind of transformations needed by our customers
  • improve HALE support for data sources, adding spatialite support
  • integrate an app-schema configuration generator to automatically create / update app-schema configuration file(s) from an HALE Alignment project
In the process, we hope to improve the app-schema extension itself, fixing bugs where needed, improving performance where possible and probably adding new mapping capabilities to match those available in HALE. The work is still in progress and some more time is needed to have a working user interface for app-schema, but we are on the way, so stay tuned and get in touch if you'd like to contribute to this effort. As usual, whatever we'll produce will be released as Open Source. Last but not least we would like to thanks LaMMa Consortium and the Austrian Meteorological Services (ZAMG) for funding this work under a GeoSolutions Enterprise Services support contract. The GeoSolutions team, http://www.geo-solutions.it
Categories: OSGeo Planet

Blog italiano di gvSIG: gvSIG 3D View plugin

OSGeo Planet - Tue, 2015-05-26 08:53

È da oggi disponibile, e pronta per essere testata, la nuova componente aggiuntiva Vista 3D per gvSIG 2.2 basata su World Wind NASA SDK. Questo nuovo strumento consentirà agli utenti di creare visualizzazioni 3D dalle viste tradizionali 2D di gvSIG. L’add-on è compatibile con tutti i formati vettoriali e raster, banche dati e servizi web supportati da gvSIG ed è installabile sia dal repository “Official” che da quello “Testing” come mostrato in questo video.

Importante! Per installare questo add-on è necessario usare una versione di gvSIG 2.2 successiva alla 2310 di gvSIG 2.2 La versione 2.2 RC2 può essere scaricata da questa pagina.

Le principali funzioni previste in questa prima versione:

  • Rasterizzazione di layer vettoriali: è possibile rasterizzare i layer vettoriali caricati nella vista 2D ed aggiungerli alla vista 3D. Questo consente di poter usare tutti i formati supportati da gvSIG a prescindere dalla simbologia ed etichettatura associata al layer, utilizzando tutte le potenzialità proprie di gvSIG.
  • Caricare layer raster: si possono caricare layer raster con tutte le proprietà di trasparenza, ottimizzazione e tabelle dei colori predefinite. Inoltre vengono caricati due layer raster di base per la vista 3D per migliorarne la visualizzazione.

  • Caricare modelli digitali del terreno: si può scegliere quale raster caricare ed usarlo come modello digitale del terreno ed è quindi possibile utilizzare anche un proprio MDT. La vista 3D incorpora comunque un suo modello digitale globale per migliorarne la visualizzazione.
  • Sincronizzazione delle modifiche: Quando si crea una vista 3D, questa è collegata alla vista 2D da cui è stata creata consentendo di applicare nella vista 3D le modifiche fatte nella visualizzazione 2D. Le modifiche supportate sono: simbologia, ordine dei layer, visualizzazione, aggiunta ed eliminazione dei layer. Questa sincronizzazione può essere eseguita manualmente o in maniera automatica.

  • Frame di sincronizzazione: come la sincronizzazione delle modifiche, è possibile anche registrare i cambiamenti dell’estensione della vista 2D. Grazie a questa funzione si possono usare tutte le funzioni di zoom di gvSIG migliorando così la visualizzazione e l’esperienza con la vista 3D. Questa sincronizzazione può essere eseguita manualmente o in maniera automatica.

  • Schermo intero: Visualizza la vista 3D a schermo intero e risulta molto utile per presentazioni e conferenze.

In questa prima versione abbiamo cercato di fornire uno strumento per visualizzare layer vettoriali, raster e 3D MDT. In futuro, si prevede di aggiungere ulteriori funzionalità come viste anaglifo, modellazione voxel, livelli vettoriali, simboli 3D…

In questa prima versione, per poter attivare gli strumenti 3D, le viste 2D devono essere esclusivamente in EPSG: 4326.

Infine, vi invitiamo a provare e segnalare ogni eventuale errore riscontrato. Per ulteriori informazioni, è possibile controllare il Wiki del progetto e scaricare il manuale utente.

Di seguito un breve video sulle potenzialità di questa estensione.


Categories: OSGeo Planet

gvSIG Team: gvSIG 3D View plugin

OSGeo Planet - Tue, 2015-05-26 08:28

Ya está disponible para testear el nuevo complemento 3D View para gvSIG 2.2 basado en World Wind NASA SDK. El nuevo complemento permitirá a los usuarios crear vistas 3D a partir de las vistas 2D convencionales de gvSIG. El complemento es compatible con todos los formatos vectoriales y ráster, bases de datos y servicios web soportados por gvSIG.

Principales funcionalidades que aporta en esta primera versión:

  • Rasterización de capas vectoriales: el complemento es capaz de rasterizar las capas vectoriales cargadas en la vista 2D y añadirlas a la vista 3D. Esto nos permite soportar todos los formatos aceptados por gvSIG sin importar la simbología o etiquetado asociado a la capa, aprovechando todo el potencial que ofrece gvSIG en este aspecto.
  • Carga de capas ráster: el complemento es capaz de cargar capas ráster con todas las propiedades de transparencia, realce y tablas de color definidas. Además, el complemento proporciona dos capas ráster como base de la vista 3D para mejorar las visualización de la vista 3D.
  • Carga de modelos digitales de terreno: permite definir que capa ráster se cargará como modelo digital de terreno pudiendo así cargar tus propios MDT. Sin embargo, la vista 3D incorpora un modelo digital global para mejorar la visualización de la vista 3D.
  • Sincronización de cambios: cuando una vista 3D se crea, esta queda enlazada a la vista 2D de la que fue creada. Esto permite registrar los cambios efectuados sobre la vista 2D y reproducirlos sobre la vista 3D. Los cambios soportados son: cambios de simbología, cambios en el orden de las capas, cambios de visibilidad y cambios al añadir o quitar capas. Esta sincronización puede realizarse de forma manual o de forma automática.
  • Sincronización de encuadres: al igual que la sincronización de cambios, también se puede registrar los cambios en el encuadre de la vista 2D. Con esta funcionalidad se pretende aprovechar todas las funciones de zoom que proporciona gvSIG mejorando así la visualización y experiencia con la vista 3D. Esta sincronización puede realizar de forma manual o automática.
  • Pantalla completa: permite visualizar la vista 3D en pantalla completa, muy útil para realizar presentaciones y ponencias.

En esta primera versión se ha querido dar un paso y proporcionar un complemento para visualizar capas vectoriales, raster y MDT en 3D. En un futuro, se espera añadir más funcionalidades como vistas anaglifas, modelado de modelos voxel, capas vectoriales, simbología 3D…

En esta primera versión las Vistas 2D deben estar en EPSG:4326. En caso contrario no se activan las herramientas de 3D.

¡Importante! Para instalar este complemento es necesario instalar la versión gvSIG 2.2. RC2. Podéis descargar gvSIG  2.2 de aquí.

Finalmente, os animamos a que probéis y reportéis posibles errores que encontréis. Para más información, podéis consultar la Wiki del proyecto aquí y descargar el manual de usuario aquí.

Una pequeña demo de lo que ofrece la extensión 3D View:

Nota final: Para instalarlo debemos utilizar el administrador de complementos, seleccionando la opción de instalación por URL. Tanto el repositorio por defecto (frozen this version),como el repositorio de testeo (testing gvSIG) nos mostrarán entre los paquetes disponibles la extensión 3D. Debemos seleccionar la que se corresponde a nuestro sistema operativo (hay 3 versiones, una para Windows, una para Linux 32bits y otra para Linux 64 bits).


Filed under: gvSIG Desktop, spanish Tagged: gvSIG 3D
Categories: OSGeo Planet

gvSIG Team: gvSIG 2.2 RC2 disponible

OSGeo Planet - Tue, 2015-05-26 07:46

Ya está disponible gvSIG 2.2 RC2, la segunda distribución candidata a versión (Release Candidate) de gvSIG 2.2.

Os animamos a que la probéis y a que nos reportéis los posibles errores y sugerencias que encontréis a través de la lista de usuarios.

Las principales novedades de esta versión son:

  • Nueva edición incluyendo nuevas funcionalidades
  • Etiquetado por escalas
  • Leyendas por escalas
  • Hiperenlace a carpetas
  • Publicación servicios OGC
  • Formatos de sísmica
  • Biblioteca de símbolos de navegación

Gracias por vuestra colaboración.


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

Paulo van Breugel: Another stab at creating a Tanaka-style contour map

OSGeo Planet - Mon, 2015-05-25 21:25
In a recent post Anita Graser (aka underdark) showed how to create illuminated or Tanaka contours in QGIS using various functions available in the toolbox and some custom functions. Here I want to explore a slightly different way to achieve the same, using GRASS GIS to compute the azimuth, brightness and line width. I’ll use […]
Categories: OSGeo Planet

gvSIG Team: gvSIG 2.2 RC2 is now available

OSGeo Planet - Mon, 2015-05-25 17:06

The second gvSIG 2.2 Release Candidate (gvSIG 2.2 RC2) is now available.

We encourage you to test it and send us any errors and suggestions in the users mailing list.

The main new features of this version are:

– New editing extension, including new functionalities
– Labeling by scale
– Legend by scale
– Hyperlink to folders
– OGC services publishing
– Seismic formats
– Sailing symbols library

Thanks for your collaboration!


Filed under: english, gvSIG Desktop, testing Tagged: gvSIG 2.2
Categories: OSGeo Planet

From GIS to Remote Sensing: Unleash the Landsat archive: SCP 4.3 allows for downloading from the entire archive of Landsat 4, 5, 7 and 8.

OSGeo Planet - Mon, 2015-05-25 17:03

This post is about a major update for the Semi-Automatic Classification Plugin for QGIS, version 4.3.0.

Following the changelog:-added support for image download of Landsat 4,5, 7 and 8
-improvements to the interface
In version 4.2 of SCP I have added the function to search and download Landsat 8 images from Amazon Web Services.





Categories: OSGeo Planet

Even Rouault: GDAL 2.0 driver metadata

OSGeo Planet - Mon, 2015-05-25 14:20
Among the many improvements that GDAL 2.0 will bring (hint: its beta2 is now available. Test it!) is the fact that vector drivers (OGR drivers) can now expose metadata about their capabilities, as a side effect of the GDAL/OGR unification. Previously, you had to refer only to the documentation page of each driver. Now, you can know them by exploring the driver metadata, which should make it possible to have automatically generated user interfaces (thinking to QGIS for example).
In addition to the existing dataset and layer creation options that were available for vector drivers, open options have been added. Those are user specified options provided to the driver when opening an existing dataset to modify its default behaviour. Up to now they used to be modeled through global configuration options, that were generally specified as environment variables. The new approach brings the benefit of being able to specify precisely for which dataset you want to apply the open option, and to be able to validate them against the published list of available options.
Let's look at the output of driver metadata for the PostgreSQL driver :
$ ogrinfo --format postgresql
Format Details:
  Short Name: PostgreSQL
  Long Name: PostgreSQL/PostGIS
  Supports: Vector
  Help Topic: drv_pg.html
  Supports: Open() - Open existing dataset.
  Supports: Create() - Create writeable dataset.
  Creation Field Datatypes: Integer Integer64 Real String Date DateTime Time IntegerList Integer64List RealList StringList Binary
  Supports: Creating fields with NOT NULL constraint.
  Supports: Creating fields with DEFAULT values.
  Supports: Creating geometry fields with NOT NULL constraint.

<CreationOptionList />


<LayerCreationOptionList>
  <Option name="GEOM_TYPE" type="string-select" description="Format of geometry columns" default="geometry">
    <Value>geometry</Value>
    <Value>geography</Value>
    <Value>BYTEA</Value>
    <Value>OID</Value>
  </Option>
  <Option name="OVERWRITE" type="boolean" description="Whether to overwrite an existing table with the layer name to be created" default="NO" />
  <Option name="LAUNDER" type="boolean" description="Whether layer and field names will be laundered" default="YES" />
  <Option name="PRECISION" type="boolean" description="Whether fields created should keep the width and precision" default="YES" />
  <Option name="DIM" type="integer" description="Set to 2 to force the geometries to be 2D, or 3 to be 2.5D" />
  <Option name="GEOMETRY_NAME" type="string" description="Name of geometry column. Defaults to wkb_geometry for GEOM_TYPE=geometry or the_geog for GEOM_TYPE=geography" />
  <Option name="SCHEMA" type="string" description="Name of schema into which to create the new table" />
  <Option name="SPATIAL_INDEX" type="boolean" description="Whether to create a spatial index" default="YES" />
  <Option name="TEMPORARY" type="boolean" description="Whether to a temporary table instead of a permanent one" default="NO" />
  <Option name="UNLOGGED" type="boolean" description="Whether to create the table as a unlogged one" default="NO" />
  <Option name="NONE_AS_UNKNOWN" type="boolean" description="Whether to force non-spatial layers to be created as spatial tables" default="NO" />
  <Option name="FID" type="string" description="Name of the FID column to create" default="ogc_fid" />
  <Option name="FID64" type="boolean" description="Whether to create the FID column with BIGSERIAL type to handle 64bit wide ids" default="NO" />
  <Option name="EXTRACT_SCHEMA_FROM_LAYER_NAME" type="boolean" description="Whether a dot in a layer name should be considered as the separator for the schema and table name" default="YES" />
  <Option name="COLUMN_TYPES" type="string" description="A list of strings of format field_name=pg_field_type (separated by comma) to force the PG column type of fields to be created" />
</LayerCreationOptionList>

  Connection prefix: PG:
<OpenOptionList>
  <Option name="DBNAME" type="string" description="Database name" />
  <Option name="PORT" type="int" description="Port" />
  <Option name="USER" type="string" description="User name" />
  <Option name="PASSWORD" type="string" description="Password" />
  <Option name="HOST" type="string" description="Server hostname" />
  <Option name="ACTIVE_SCHEMA" type="string" description="Active schema" />
  <Option name="SCHEMAS" type="string" description="Restricted sets of schemas to explore (comma separated)" />
  <Option name="TABLES" type="string" description="Restricted set of tables to list (comma separated)" />
  <Option name="LIST_ALL_TABLES" type="boolean" description="Whether all tables, including non-spatial ones, should be listed" default="NO" />
</OpenOptionList>
For drivers that do not work directly on filenames, they expose a connection prefix, "PG:" in that instance (can be discovered through the GDAL_DMD_CONNECTION_PREFIX="DMD_CONNECTION_PREFIX" driver metadata item). It also lists the various open options available (through GDAL_DMD_OPENOPTIONLIST="DMD_OPENOPTIONLIST" driver metadata item). In the above example, most open options had to be passed in the connection string, with the exception of LIST_ALL_TABLES that was available as the PG_LIST_ALL_TABLES configuration option.
This is enough to know that "ogrinfo PG: -oo DBNAME=autotest -oo PORT=5432" is a correct syntax. The historical "ogrinfo 'PG:dbname=autotest port=5432'" syntax is of course preserved for backward compatiblity, but if you switch between PostreSQL/MySQL/OCI, you had to remember subtle differences. For example "MYSQL:autotest,port=3306". Now by exploring metadata, you can see you can use "ogrinfo MYSQL: -oo DBNAME=autotest -oo PORT=3306"
Admitedly not all drivers have been modified to use those new capabilities, or some obscure configuration options might not yet be available through open options, but at least the mechanism now exists.
The -oo option can be used with most GDAL (a few raster drivers have also open options such as the PDF driver) and OGR utilities. For ogr2ogr, in update or append mode, you can also use -doo (destination open option) for the target dataset.
Worth noting: we also have now dual drivers that can accept both raster & vector data.
  PCIDSK -raster,vector- (rw+v): PCIDSK Database File
 JP2ECW -raster,vector- (rw+v): ERDAS JPEG2000 (SDK 3.x)
 JP2OpenJPEG -raster,vector- (rwv): JPEG-2000 driver based on OpenJPEG library
  JPEG2000 -raster,vector- (rwv): JPEG-2000 part 1 (ISO/IEC 15444-1), based on Jasper library
  PDF -raster,vector- (rw+vs): Geospatial PDF
  GPKG -raster,vector- (rw+vs): GeoPackage
  PLSCENES -raster,vector- (ro): Planet Labs Scenes API
  HTTP -raster,vector- (ro): HTTP Fetching Wrapper
Depending on the open flags provided to the new GDALOpenEx() and the actual content of the dataset, GDALOpenEx() will return a NULL handle for example if you asked for vector data only and there is only raster data (this is behaviour of the legacy OGROpen() format).If you wonder why JPEG 2000 drivers are listed, this is because now that GDAL supports the GMLJP2 v2 standard, vector features can be embedded into/read from a GMLJP2 v2 box.
Categories: OSGeo Planet

gvSIG Team: Ampliado plazo de recepción de comunicaciones para 7as Jornadas gvSIG LAC

OSGeo Planet - Mon, 2015-05-25 08:24

Se ha ampliado el plazo de recepción de comunicaciones para 7as Jornadas gvSIG de Latinoamérica y Caribe. La fecha límite para enviar vuestras propuestas es el 5 de junio.

En las próximas semanas iremos publicando información sobre los numerosos talleres que tendrán lugar en estas jornadas.

Un acontecimiento que no os podéis perder. Os animamos a participar no solo como asistentes, si trabajáis con gvSIG…es el momento de contarlo. Toda la información sobre el envío de comunicaciones podéis encontrarla aquí.

Por último os recordamos que ya está abierta la inscripción como asistente.


Filed under: opinion
Categories: OSGeo Planet

Free and Open Source GIS Ramblings: How to create illuminated contours, Tanaka-style

OSGeo Planet - Sun, 2015-05-24 10:19

In the category “last night on Twitter”, a challenge I couldn’t resist: creating illuminated contours (aka Tanaka contours) in QGIS. Daniel P. Huffman started the thread by posting this great example:

CFnWnA5UkAAuFm9

This was quickly picked up by Hannes Kröger who blogged about his first attempt at reproducing the effect using QGIS and GIMP. Obviously, that left the challenge of finding a QGIS-only solution.

Everything that’s needed to create this effect is a DEM. As Hannes describes in his post, the DEM can then be used to compute the contour lines, e.g. with Raster | Extraction | Contour:

gdal_contour -a ELEV -i 100.0 C:\Users\anita\Geodata\misc\mt-st-helens\10.2.1.1043901.dem C:/Users/anita/Geodata/misc/mt-st-helens/countours

Screenshot 2015-05-24 11.17.49

contours

In order to be able to compute the brightness of the illuminated contours, we need to compute the orientation of every subsection of the contours. Therefore, we need to split the contour lines at each node. One way to do this is using v.split from the Processing toolbox:

Screenshot 2015-05-24 11.23.11

When we split the contours and visualize the result using arrows, we can see that they all wrap around the mountain in clockwise direction (light DEM cells equal higher elevation):

split_contours

After the split, we can compute the orientation of the contour subsections using, for example, a user-defined function:

Screenshot 2015-05-24 19.09.12

This function can then be used in a Field calculator expression:

Screenshot 2015-05-24 19.11.53

Based on the orientation, we can then write an expression to control the contour line color. For example, if we want the sun to appear in the north west (-45°) we can use:

color_hsl( 0,0, scale_linear( abs( ( CASE WHEN "azimuth"-45 < 0 THEN "azimuth"-45+360 ELSE "azimuth"-45 END ) -180), 0, 180, 0, 100) )

This will color the lines which are directly exposed to the sun white hsl(0,0,100) while the ones in the shadows will be black hsl(0,0,0).

Screenshot 2015-05-24 11.55.50

Use the Overlay layer blending mode to blend contours and DEM color:

illuminated_contours

The final step, to get as close to the original design as possible, is to create the effect of discrete elevation classes instead of a smooth color gradient. This can easily be achieved by changing the color interpolation mode of the DEM from Linear to Discrete:

Screenshot 2015-05-24 12.11.01

This leaves us with the following gorgeous effect:

tanaka_contours

As Hannes pointed out, another important aspect of Tanaka’s method is to also alter the contour line width. Lines in the sun or shadow should be wider (1 in this example) than those in orthogonal direction (0.2 in this example):

scale_linear( abs( abs( ( CASE WHEN "azimuth"-45 < 0 THEN "azimuth"-45+360 ELSE "azimuth"-45 END ) -180) -90), 0, 90, 0.2, 1)

datadefined_line_width

Enjoy!


Categories: OSGeo Planet

Free and Open Source GIS Ramblings: Time Manager workshop at #QGIS2015

OSGeo Planet - Fri, 2015-05-22 20:28

Today was the final day of #QGIS2015 the first joint QGIS conference and developer meeting. I had the pleasure to meet Time Manager co-developer Karolina Alexiou aka carolinux in person and give a talk including a hands-on workshop on Time Manager together. Time Manager makes it possible to explore spatio-temporal data by creating animations directly in QGIS.

The talk presents QGIS visualization tools with a focus on efficient use of layer styling to both explore and present spatial data. Examples include the recently added heatmap style as well as sophisticated rule-based and data-defined styles. The focus of this presentation is exploring and presenting spatio-temporal data using the Time Manager plugin. A special treat are time-dependent styles using expression-based styling which access the current Time Manager timestamp.

To download the example data and QGIS projects download Time_Manager_Examples.zip.


Categories: OSGeo Planet

GeoSolutions: GeoSolutions Enterprise Services 2015

OSGeo Planet - Fri, 2015-05-22 18:23

geosolutions enterprise services

The GeoSolutions Enterprise Services 2015 offer support services for creating an Enterprise SDI based on the Open Source frameworks GeoServer, GeoNetwork and MapStore. Our support services are available in different sizes because we care about clients with small budgets as well as about clients willing to implement sophisticated infrastructures and therefore looking for highly specialized support. Thanks to GeoSolutions you will happily join the Open Source world, forget about licenses and decide the budget for the features you are looking for with the support from the developers of the software you are using!

You can find everything you need to know about our support plans here, so download the flyer and get in touch: our sales representatives will talk to you about how to best support your users rather than about how many licenses you should buy!

The GeoSolutions team, logo_geo-solutions
Categories: OSGeo Planet

From GIS to Remote Sensing: Brief Introduction to Remote Sensing (3/3): Landsat image conversion

OSGeo Planet - Fri, 2015-05-22 16:41


This is the third part of some basic definitions of remote sensing that are already in the user manual of the Semi-Automatic Classification Plugin.This post provides information about the Landsat conversion to reflectance implemented in SCP Landsat.Landsat images downloaded from http://earthexplorer.usgs.gov or through the SCP tool Download Landsat are composed of several bands and a metadata file (MTL) which contains useful information about image data.

Radiance at the Sensor’s ApertureRadiance is the “flux of energy (primarily irradiant or incident energy) per solid angle leaving a unit surface area in a given direction”, “Radiance is what is measured at the sensor and is somewhat dependent on reflectance” (NASA, 2011, p. 47).
The Spectral Radiance at the sensor’s aperture (Lλ) is measured in [watts/(meter squared * ster * μm)] and for Landsat images it is given by (https://landsat.usgs.gov/Landsat8_Using_Product.php):

Lλ=ML∗Qcal+ALwhere:
  • ML = Band-specific multiplicative rescaling factor from Landsat metadata (RADIANCE_MULT_BAND_x, where x is the band number)
  • AL = Band-specific additive rescaling factor from Landsat metadata (RADIANCE_ADD_BAND_x, where x is the band number)
  • Qcal = Quantized and calibrated standard product pixel values (DN)

Top Of Atmosphere (TOA) Reflectance“For relatively clear Landsat scenes, a reduction in between-scene variability can be achieved through a normalization for solar irradiance by converting spectral radiance, as calculated above, to planetary reflectance or albedo. This combined surface and atmospheric reflectance of the Earth is computed with the following formula” (NASA, 2011, p. 119):

Categories: OSGeo Planet
Syndicate content