OSGeo Planet

QGIS Blog: User question of the Month – Jan19 & answers from Dec

OSGeo Planet - Mon, 2019-01-07 21:03

In December, we wanted to know what QGIS.ORG should focus on in 2019.

Portuguese 

selection_002

Based on these results, in today’s PSC meeting, we’ve decided that the 2019 grant programme will be focusing on bug fixing and polishing existing features. So thanks to everyone who provided feedback!

New question

This month, we’d like to know if you have ever contributed to improving QGIS and – if yes – how. As you’ll see, there are many different ways to contribute to QGIS, so please go ahead and take the survey.

The survey is available in English, Spanish, Portuguese, French, Italian, Ukrainian, and Danish. If you want to help us translate user questions in more languages, please get in touch!

Categories: OSGeo Planet

Free and Open Source GIS Ramblings: PyQGIS101 part 10 published!

OSGeo Planet - Sat, 2019-01-05 14:31

PyQGIS 101: Introduction to QGIS Python programming for non-programmers has now reached the part 10 milestone!

Beyond the obligatory Hello world! example, the contents so far include:

If you’ve been thinking about learning Python programming, but never got around to actually start doing it, give PyQGIS101 a try.

I’d like to thank everyone who has already provided feedback to the exercises. Every comment is important to help me understand the pain points of learning Python for QGIS.

I recently read an article – unfortunately I forgot to bookmark it and cannot locate it anymore – that described the problems with learning to program very well: in the beginning, it’s rather slow going, you don’t know the right terminology and therefore don’t know what to google for when you run into issues. But there comes this point, when you finally get it, when the terminology becomes clearer, when you start thinking “that might work” and it actually does! I hope that PyQGIS101 will be a help along the way.

Categories: OSGeo Planet

GRASS GIS: GRASS GIS 7.4.4 released

OSGeo Planet - Fri, 2019-01-04 20:00
We are pleased to announce the GRASS GIS 7.4.4 release
Categories: OSGeo Planet

Fernando Quadro: O GeoServer e o Java 11

OSGeo Planet - Fri, 2019-01-04 12:52

O Java Code Sprint 2018 foi um evento ambicioso que reuniu projetos Java da OSGeo para analisar a compatibilidade com Java 11. Com uma ótima resposta da comunidade, o GeoServer agora pode rodar no Java 11!


GeoServer Server Status Page

Esse sprint foi uma resposta importante da comunidade às mudanças do Java. A motivação imediata é dar aos usuários a opção de usar o Java 11 na próxima versão do GeoServer (2.15.x), agora que o OpenJDK está assumindo como projeto principal. Também temos o prazer de informar que o Java 8 continuará sendo suportado (graças ao compromisso da RedHat e da Adopt OpenJDK), dando a todos a oportunidade de migrar quando estiverem prontos.

É importante observar que o Java 11 não suporta mais o mecanismo de extensão usado para as bibliotecas JAI e ImageIO nativas. Onde as bibliotecas podiam ser instaladas diretamente no Sistema Operacional para aumento de performance das mesmas.

Como experimentar:

1. Faça o download e instale o Java 11 (jdk.java.net/11)

2. Faça o download do GeoServer 2.15-M0

3. O GeoServer 2.15-M0 será executado sob o Java 11 sem configuração adicional no Tomcat 9 ou mais recente e no Jetty 9.4.12 ou mais recente.

4. A distribuição binária inclui uma versão compatível do Jetty.

Fonte: GeoServer Blog

Categories: OSGeo Planet

GeoTools Team: GeoTools Java 11 Code Sprint Results

OSGeo Planet - Fri, 2019-01-04 08:05
With the recent GeoTools 21-M0 Milestone release available for everyone to try out ... we can finally report back on our success at the OSGeo Java 2018 Code Sprint. References: Java 11 Quickstart shows how to use the GeoTools with the new module system Java is still free for background on Java 8 and Java 11 support options (or our Java Install page  summary table) Technical Challenge The
Categories: OSGeo Planet

gvSIG Team: Digitalizing prospection areas. GIS applied to Archeology

OSGeo Planet - Thu, 2019-01-03 10:45

We publish the second module (of seven) of the free ‘GIS applied to archaeology’ course, where you will learn to create geographic information through the editing tools offered by the open source software called ‘gvSIG Desktop’.

We will start by creating a new layer of information that will represent our prospection areas. In that layer we will create new geometries and we will fill its attribute table in with alphanumeric information.

We will also see how to add information to an existing layer using the ‘table join’ tool.

To follow these exercises you will start with the project created in the first module of the course, so if you have not done already we recommend you start there.

The data to follow the course can be downloaded compressed in a .zip file on this link.

Remember that for doubts about software use, carrying out the exercises, and problems that you find when carrying out the course, you can use the gvSIG users mailing list.

Module 2: Creating geographic information

Previous modules:

Module 1: Preparation of an archaeological project

Categories: OSGeo Planet

gvSIG Team: Digitalizar zonas de prospecciones. SIG aplicados a Arqueología

OSGeo Planet - Thu, 2019-01-03 10:12

Os traemos el segundo módulo (de siete) del curso gratuito de SIG aplicados a arqueología, donde aprenderemos a crear información geográfica mediante las herramientas de edición que ofrece el software libre y gratuito gvSIG Desktop.

Comenzaremos creando una nueva capa de información que representará nuestra zona de prospecciones. En esa capa iremos creando nuevas geometrías y rellenando su información alfanumérica.

También veremos como agregar información a una capa existente mediante la herramienta de unión de tablas.

Para realizar estos ejercicios partiremos del proyecto creado en el primer módulo del curso, por lo que si aún no lo has hecho te recomendamos que empieces por ahí.

Los datos para poder seguir el curso los podéis descargar comprimidos en un fichero .zip en este enlace.

Recuerda que para dudas en el manejo del software, realización de los ejercicios y problemas que puedan surgir en la realización del curso, podéis utilizar la lista de usuarios de gvSIG.

Tema 2: Crear información geográfica

Temas anteriores

Tema 1: Preparación de un proyecto arqueológico: vistas, capas y tablas

Categories: OSGeo Planet

GeoServer Team: Java 2018 Code Sprint Results

OSGeo Planet - Thu, 2019-01-03 01:23

The Java 2018 code sprint was an ambitious event gathering up OSGeo Java projects to look at Java 11 compatibility. With a great response from the GeoServer community we are pleased to announce the GeoServer can now run in Java 11!

This sprint was an important response by our community to changes in the Java roadmap. The immediate motivation is to give our users the option of using Java 11 in the coming year now that OpenJDK is taking over as lead project. We are also pleased to report that Java 8 will continue to be supported (thanks to the commitment of RedHat and Adopt OpenJDK) giving everyone a chance to migrate when ready.

We had 11 participants for the sprint – thanks to everyone who attended!

  • David Vick (Boundless), Devon Tucker (Boundless), Jim Hughes (CCRi), Jody Garnett (Boundless) Kevin Smith (Boundless), and Torben Barsballe (Boundless) gathered at the Boundless office in Victoria, Canada.
  • Andrea Aime (GeoSolutions) and Antonello Andrea (Hydrologis) participated from Andrea’s home office in Italy.
  • María Arias de Reyna (GeoCat), Ian Turton (Astun), Landon Blake (BKF Engineers), and Brad Hards participated remotely.

With support from OSGeo and event sponsors many individuals were able to meet up in person, with those hosed at the Boundless Victoria office enjoying the occasional break outside.

How to try it out:

To get started:

  1. Download and install Java 11 from jdk.java.net/11
  2. Download the GeoServer 2.15-M0 milestone release of GeoServer
    • The GeoServer 2.15-M0 will run under Java 11 with no additional configuration on Tomcat 9 or newer and Jetty 9.4.12 or newer.
    • The binary distribution includes a compatible version of Jetty.

We need your help:

  • pulling together running on java 11 instructions for additional application servers, please download the WAR bundle to help out
  • testing the windows installer
Sponsors

Thanks to Gaia3D for leading with a silver sponsorship, and ASTUN Technology, OSGeo:UK, and ATOL for their bronze sponsorships.

Gaia3d

AstunLogo.png

uk.osgeo.org Atol

These sprints also require people to function, and we appreciate Boundless, GeoCat, ASTUN Technology, GeoSolutions and CCRi for their in-kind participation.

Boundless

Astun.png   Ccri.

Geosolutions GeoCat

Key accomplishments:
  • GeoServer was upgraded to Spring 5. Thanks to David Vick and everyone for this (especially the Spring Security upgrade with James).
  • Kevin went through the same steps for GeoWebCache for a difficult couple of days.
  • The EMF models that drive much of our parsing technology were upgraded. Thanks to Ian who worked through this, putting us in a much better spot to make changes to our codebase.
  • Torben helped remove countless references to internal “com.sun” classes.
  • A big thanks to Andrea for stepping up where needed (i.e. everywhere) and encouraging everyone through out the week
  • Thanks to Andrea and Brad for preliminary work that made this sprint possible.
  • Thanks to Jody for doing the milestone release.

Outstanding issues:

Certain components and dependencies could not be upgraded as no Java 11-compatible versions have been released. These have been removed or replaced by different libraries where possible, but some incompatible libraries remain.

The remaining issues are primarily either Internal API usage or Illegal access. These will only cause problems when running on Java 11:

Internal API usage

Some components and dependencies reference internal Java API. Depending on the nature of this API, calling this code may cause a runtime error or a warning when running on Java 11. If you run into any unusual failures when running under Java 11, please report them.

Examples of libraries producing these warnings:

  • freemarker template library (used for GetFeatureInfo responses)
  • ehcache library used for image mosaic performance
  • Java Advanced Imaging used for image processing
Illegal Access

Java 11 introduces stricter access constraints on reflective operations. For now, such issues will only cause a warning in the logs, of the form:

WARNING: Illegal reflective access by …

In future versions of Java, this will instead cause a runtime error.

Known warnings you can expect when running in Java 11:

  • org.hsqldb.persist.RAFileNIO
  • org.parboiled.transform.AsmUtils
  • org.fest.reflect.util.Accessibles
  • com.google.protobuf.UnsafeUtil
  • net.sf.cglib.core.ReflecUtils

If you run into a reflective access warning about a package not in this list, please report it.

Community Modules

The following community modules do not yet support Java 11:

  • printing
  • script
  • spatiallite
  • monitor-hibernate
Further reading:
Categories: OSGeo Planet

Gary Sherman: Plugin Builder 3.1

OSGeo Planet - Wed, 2019-01-02 09:00

We've released version 3.1 of the Plugin Builder for QGIS 3.x. This version contains a number of bug fixes and performance enhancements.

Here are some of the changes included since version 3.0.3:

  • Fix issue with reload on generated plugins
  • Move dialog creation to run method to improve startup performance
  • Move help file generation files to proper method
  • Include missing tags file
  • Attempt to compile resources.qrc when plugin is generated (requires pyrcc5 in path)
  • Set deployment directory in Makefile based on user OS (pb_tool is recommended over make)
  • Check for valid URL format for tracker and repository

Compiling Resource File

If you have the resource compiler pyrcc5 in your path, the resource file will be compiled automatically when you generate your new plugin. This means it's ready to deploy and test without any further steps.

Using pb_tool

Although a Makefile is created when you generate a new plugin, you are encouraged to use pb_tool for compiling, deploying, and managing your plugins. It runs everywhere and simplifies your plugin development.

pb_tool works with both Python 2.x and 3.x.

See http://g-sherman.github.io/plugin_build_tool/ for information.

Installing Plugin Builder

You can install Plugin Builder 3.1 from the Plugins -> Manage and Install Plugins... menu. Version 3.1 works on QGIS versions 3.0 and up.

Plugin Builder Links

Pull requests and code contributions are encouraged.

Categories: OSGeo Planet

From GIS to Remote Sensing: Very Happy New Year by From GIS to Remote Sensing

OSGeo Planet - Tue, 2019-01-01 08:00
This post is to wish you all a very happy new year!

2018 has been a great year for the Semi-Automatic Classification Plugin (SCP), with the release of the version 6 for QGIS 3.
I'm very grateful to all the people who have contributed to this project, through their work translating the interface and the user manual, fixing bugs and reporting issues, and donating.



In 2019 I'll continue the development of the SCP, in particular designing the new version 7 (which should be released in the early 2020), and of course maintaining the version 6.
In the new version 7 I'll focus on the development of new features for automating and improving the processing of remote sensing images, in particular:
  • development of parallel processing in order to reduce the computational time;
  • integration with ESA SNAP software for the preprocessing of Sentinel-2 images;
  • development of standalone APIs to use the tools through the command line or Python;
  • improvement of the user interface.
I'll consider updating the version 6 with some of these new features during 2019. And of course I'll write new tutorials about applications and case studies.
Again, I wish you a very happy new year!

For any comment or question, join the Facebook group about the Semi-Automatic Classification Plugin.
Categories: OSGeo Planet

BostonGIS: Using pg_upgrade to upgrade PostgreSQL 9.3 PostGIS 2.1 to PostgreSQL 11 2.5 on Yum

OSGeo Planet - Tue, 2019-01-01 06:48

In a previous article Using pg upgrade to upgrade PostGIS without installing older version I demonstrated a trick for upgrading to a newer PostgreSQL instance from PostGIS 2.2 - 2.whatever without having to install the older version of PostGIS in your new PostgreSQL service. Unfortunately that trick does not work if coming from PostGIS 2.1 because in PostGIS 2.2 we renamed a c lib function that backed sql functions in 2.1.

Fear not. There is still a way to upgrade from 2.1 to 2.5 without installing an older version of PostGIS in your new PostgreSQL instance. To do so, you need to add a step and that is to remove the functions in 2.1 that are backed by this renamed lib function. In upcoming PostGIS 3.0, we've added this function back and have it throw an error so that even coming from PostGIS 2.1, you can upgrade just the same as you do from later versions.

Continue reading "Using pg_upgrade to upgrade PostgreSQL 9.3 PostGIS 2.1 to PostgreSQL 11 2.5 on Yum"
Categories: OSGeo Planet

GeoServer Team: GeoServer 2.15-M0 Milestone Release

OSGeo Planet - Tue, 2019-01-01 05:56

We are happy to share a GeoServer 2.15-M0 milestone release with downloads (zip|war|exe), documentation (html|pdf) and extensions.

This milestone release is provided for everyone considering a Java 11 operational environment in 2019.  A milestone release provides a technology preview and a chance to support the development team with early feedback:  your assistance and participation is requested!

This release is a result of participation in the OSGeo Java 2018 Code Sprint and is made in conjunction with GeoTools 21-M0 and GeoWebCache 1.15-M0. We would like to thank organizations participating in the code sprint (Boundless, GeoSolutions, GeoCatAstun TechnologyCCRi) along with sprint sponsors (Gaia3Datol, osgeo:uk, Astun Technology). Our gratitude goes out to the individuals who worked so hard to bring everything together.

Java 11 Support

The provided binary download works with either Java 8 or Java 11. Tomcat 9 or newer is required for the WAR install.

We will the update the user guide compatibility list based on your feedback and testing of this 2.15-M0 milestone release. Please note that Java 11 no longer supports the Java 2 extension mechanism used for native JAI and native ImageIO.

This is a good opportunity to review your operational environment and help test GeoServer with the environment you intend to use in 2019.

Java Roadmap Considerations

Our initial concerns with respect to continued availability of the Java 8 platform have been alleviated by industry action and commitment. Extensive Java 8 support options are now available, with RedHat making a public commitment to contribute fixes to the OpenJDK 8 codebase, and a range of organizations committed to making OpenJDK 8 builds available on a range of platforms.

Oracle has changed to a six month release schedule, donating additional components to OpenJDK to make it lead platform. Long term support (beyond six months) is being offered from a range of organizations notably RedHat OpenJDK  and Adopt OpenJDK.

The net effect of these changes:

  • If you have been using Oracle JDK up until now it is time to review your options
  • Java 8 will continue to be available
  • The Java ecosystem is now led by the open-source Open JDK project

See the GeoTools user guide for a table outlining the Java 8 and Java 11 alternatives to consider in the year ahead.

About GeoServer 2.15 Series

Additional information on the GeoServer 2.15 series:

Categories: OSGeo Planet

GeoTools Team: GeoTools 21-M0 Milestone Released

OSGeo Planet - Tue, 2019-01-01 05:36
GeoTools project is closing out 2018 with a GeoTools 21-M0 milestone release featuring Java 11 compatibility: geotools-21-M0-bin.zip geotools-21-M0-doc.zip geotools-21-M0-userguide.zip geotools-21-M0-project.zip maven repository This milestone release is a preview of GeoTools 21 giving everyone a chance to help test Java 11 compatibility. This release works with both Java 8 and Java 9,
Categories: OSGeo Planet

Cameron Shorter: Community Inside

OSGeo Planet - Sat, 2018-12-29 19:44

Community insideParody of "intel inside®" logo,
a trademark of Intel Corporation.
Image SVG.
"Community inside" is the "intel inside®" of Open Source Software. It's an indicator of quality and long term sustainability.

Why? Because in the digital economy, collaboration out-competes competition!
So prioritise software developed by healthy communities. Look for diverse, supportive, meritocratic, productive, welcoming and inspiring teams. Then engage productively with them.

More ...
Categories: OSGeo Planet

Tom Kralidis: Cheers to 2018

OSGeo Planet - Fri, 2018-12-28 17:59
What a year!  Following on from 2017, in no particular order, here goes: Bonn Code Sprint: talk about a worthwhile event!  It was great to meet old and new OSGeo hackers.  Serious progress made on many projects (keep reading) OWSLib: thanks to Carsten Ebrecht, we finally have a much better handling on tests (moving to […]
Categories: OSGeo Planet

Even Rouault: SRS barn raising: 7th report

OSGeo Planet - Fri, 2018-12-28 13:12
This is the 7th progress report of the GDAL SRS barn effort.

On the PROJ side, things are consolidating up. Tens of "random" fixes have been pushed due to the GDAL autotest suite triggering a number of interesting cases. The C API has also been enhanced to accommodate for the needs of GDAL and libgeotiff. We also have received feedback from an early adopter (a developer of a pyproj binding based on PROJ master). The major development items have been the move of the WKT 1 syntax validation from GDAL to PROJ, as well as the development of an equivalent WKT 2 syntax validator in PROJ (this task has been useful to uncover a few minor issues in the draft of the future WKT2:2018 standard). A reorganization of the PROJ source tree (with a conversion of most C files to C++ files) has also been done, as a preliminary step, for a pull request to better integrate the new ISO-19111 functionality I developed those last months with the existing C API.
Regarding libgeotiff, a v1.4.3 maintenance version has been released with the fixes of the last two years, before the new works for the integration of PROJ master are done. libgeotiff development has been moved from Subversion to https://github.com/OSGeo/libgeotiff. As a preliminary step, continuous integration capability has been added to test compilation under Linux/GCC and Windows/Visual Studo, with a few runtime tests.A pull request is ready with the integration of PROJ master with libgeotiff. It features:
  • PROJ master / PROJ 6 as a required depedency of libgeotiff
  • Use of the proj.db database to resolve the various coded values, mostly in the GTIFGetDefn() "normalization" function of libgeotiff, instead of using the .csv files previously generated from the EPSG database. Typically an EPSG code identifying a projected CRS is resolved them into its base elements: projection method, projection parameters, base geodetic CRS, etc..
  • Complete removal of those .csv files and associated functionality
This work will be merged once the above mention PROJ pull request that affects naming of the new functions of the C API has been merged and taken into account. This gdalbarn branch of libgeotiff has also been succesfully integrated in the internal libgeotiff copy of the GDAL gdalbarn branch.
Regarding GDAL, a maintenance v2.3.3 and feature v2.4.0 versions have been released for the same reasons as above.Most methods of the OGRSpatialReference class have now been re-implemented to rely on the PROJ C API to do queries and state changes, which avoids potentially lossy import / export to WKT 1. Similarly to the libgeotiff work, the ImportFromEPSG() functionality now relies on proj.db, and consequently all EPSG or ESRI related .csv files have been removed from the GDAL data directory. I've also drafted a plan regarding on how to be able to take into account WKT 2 by GDAL raster drivers, and proposed changes regarding how to better handle the gap between the axis order as mandated by the CRS authority (for example latitude first, longitude second for geographic CRS in the EPSG dataset) and the actual order of the values in raster metadata or vector geometries. The first part (use of OGRSpatialReference in raster driver) has been implemented in the gdalbarn branch and the second part is in good progress, with the drivers now advertizing their data axis to CRS axis mapping. The ongoing work is to make  OGRCoordinateTransformation use the PROJ API to automatically compute the best transformation pipeline, enabling late-binding capabilities.


Categories: OSGeo Planet

GeoTools Team: GeoTools 19.4 released

OSGeo Planet - Sun, 2018-12-23 09:59
The GeoTools team is pleased to announce the release of GeoTools 19.4: geotools-19.4-bin.zip geotools-19.4-doc.zip geotools-19.4-userguide.zip geotools-19.4-project.zip maven repository This release is the last community sponsored maintenance release for the 19.x series and as such users and downstream projects should consider moving to the 20.x series. This release is made in conjunction
Categories: OSGeo Planet

GeoServer Team: GeoServer 2.13.4 released

OSGeo Planet - Sun, 2018-12-23 09:42

We are happy to announce the release of GeoServer 2.13.4. Downloads are available (zipwar, and exe) along with docs and extensions.

This is a maintenance release recommended for production use (for newer projects please use the 2.14.x series, as this is last community sponsored 2.13.x release).
This release is made in conjunction with GeoTools 19.4 and GeoWebCache 1.13.4.

Highlights of this release are featured below, for more information please see the release notes (2.13.4 | 2.13.32.13.2 | 2.13.1 | 2.13.02.13-RC1 | 2.13-beta).

Improvements and Fixes
  • Significant speedup in WMTS capabilities document generation when source data is not in WGS84
  • GeoPackage improvements, speed up raster reading and reprojection, make sure global coverage GeoPackage can be displayed
  • Removed gml:id attribute from GML 3.1 encoding (was added in previous releases by mistake)
  • NetCDF output format improvement, fixing projection coefficients in some cases, make sure data packing takes into account all data slices when calculating linear transformation coefficients
  • WCS 2.0 compliance improvements, DescribeCoverage output schema compliance fixes when using GeoServer extensions, returning correct exception type when subsetting request is out of range on time/elevation/custom dimension axis
  • KML request handling fixes, support for sortBy and CQL filtering on layer groups
  • GWC related fixes, could not modify blobstore configuration without changing its name too, wrong axis order in configuration when saving EPSG:4326 gridset configurations
  • Styling related improvements, cannot read dynamic SLD served by an apache server, SLD 1.1 posted to the REST API resulted in garbled content
  • And various others, please see the release notes for details
About GeoServer 2.13 Series

Additional information on the 2.13 series:

 

Categories: OSGeo Planet

PyWPS team: PyWPS-4.2.0 Released

OSGeo Planet - Thu, 2018-12-20 00:00
PyWPS-4.2.0 Released

At long last, a new PyWPS release is out. A new chapter in the PyWPS 4 story is now complete and as 2018 comes to an end, it is time to look back at what happened since the major release in December of 2016.

PyWPS remains fully reliant on pro bono contributions without any sort of commercial organisation around it. This means the project largely depends on how the community is able to contribute at any given time. However, it also means there are no clients to attend or shareholders to appease, no hard deadlines or sales demos. PyWPS evolves organically, to the tune of the community’s wishes.

Relying on voluntary contributions does not mean progress is slow, much to the contrary. In recent times PyWPS has had more simultaneous contributors than at any moment before in its history. This is largely due to the major step taken with PyWPS 4 towards modern Python technologies, but also to regular contributions from the Google Summer of Code (GSoC) programme and various students thesis. During these two years the Project Steering Committe (PSC) was expanded to six members, and last May PyWPS finally graduated as an OSGeo project.

In order to manage development, the Project Steering Committe (PSC) meets regularly (usually at FOSS4G events) and performs basic housekeeping: issues are reviewed and split among a series of milestones that set out a development plan. As development progresses, new issues naturally pop up, and there is always a patch or an improvement that developers wish to include in the next release. Like the Red Queen from Alice in Wonderland, the backlog for the next release seems to always have as many issues resolved as new ones to resolve. Time drags on and the perfect tidy release remains ellusive. So in the end PyWPS 4.2 is mostly a commemorative release, celebrating two years since the major release and making official all the improvements introduced since.

What are then the main improvements introduced with PyWPS 4.2? Foremost is the progressive improvement of the class model, step by step making the library more solid, agile and easier to maintain. Among other things, the input/output handling classes were refactored, the test battery was expanded and streamlined with continuous integration tools. Other relevant improvements include:

  • Introduction of Jinja2 templates to automate the generation of outputs.
  • Support for process execution in HPC environments, using Slurm or GridEngine.
  • Support for streamed URL-based data inputs (e.g. OpenDAP).
  • Automated process documentation with Sphinx.
  • New validators for JSON, DODS links and netCDF formats.

And along the way, many bugs were fixed.

The organic nature of the project has meant that the goals set out by the PSC are not always met. For instance, PyWPS 4.2 still does not fully support version 2 of the WPS standard. But such is the nature of community driven projects: evolution goes along the needs of the community and not necessarily according to grand plans. There are instead other great improvements in the pipeline, like the containerisation of processes, or the automatic storage of outputs in a database. Please get involved if these developments interest you, or if you would like other improvements to be introduced.

A word also regarding the WSGI applications provided as example services using PyWPS. pywps-flask remains the most popular but a backlog of small issues has built up. During the holiday season developers will be lending attention to these issues. Usability issues with the containers of both pywps-flask and pywps-django will also be addressed during this time.

Finally the PSC would like to thank everyone that has contributed to PyWPS these past two years: from those doing the code heavy lifting, to testers, bug reporters, documentation contributors. Every bit of contribution is precious. Thank you all for making PyWPS what it is today!

Merry Christmas and a Happy New Year.

Categories: OSGeo Planet

gvSIG Team: Free Course: GIS for Archaeologists

OSGeo Planet - Wed, 2018-12-19 12:10

In recent years, Geographic Information Systems (GIS) have radically evolved the way in which spatial data are collected, analyzed and interpreted. Because of their characteristics, GIS have become useful applications for archaeologists. The appearance of gvSIG, with a complete suite of GIS solutions in open source software, has meant that more and more professionals in the sector are adopting gvSIG as a working tool.

However, there is still a wide ignorance of the potential of GIS in archaeology, and there are only a few free teaching materials that allows training in its use. For these reasons, from the gvSIG Association, we launch a course that will allow to know of these technologies. A free course, with open source software (gvSIG Desktop).

In this first post we want to present the main characteristics of the course, together with the first video-tutorial. As of January 2019, we will publish all the modules weekly until the agenda is completed. To follow the course, it is recommended that participants have prior knowledge about how archaeological projects are carried out.

Registration of the course and how it works

It is not necessary to register anywhere. The course is online and can be followed from anywhere in the world. The course will be available in English and Spanish.

Each week we will publish a post on this blog that will contain a video-tutorial with exercises and access to the course data. Therefore, you only need to follow the video-tutorials to complete the course.

For doubts or problems in the use of software, or about the exercises, you can use the gvSIG users mailing list:

http://www.gvsig.com/en/community/mailing-lists

List of topics

The list of topics is composed of 7 modules. Each module will contain a video-tutorial with practical exercises. The data to follow the course can be downloaded in a .zip file from this link.

  1. Preparation of an archaeological project: views, layers and tables
  2. Create geographic information: Alphanumeric information and digitalization
  3. Prospecting results analysis: Vector geoprocesses
  4. Managing old maps: Georeferencing of images
  5. Reservoir territorial analysis: Raster geoprocesses and digital terrain models (MDT)
  6. Hydrological analysis to locate materials or archaeological sites
  7. Graphical output of an archaeological project: Maps
And if you want to get a certificate?

Such as in other previous courses that we have published, many of you asked us about the possibility to obtain a certificate. To cover this possibility, at the end of the course we will publish a practical exercise to be solved, and to demonstrate that you have acquired the knowledge imparted during the course. This exercise is completely optional, only for those who want to get the certification.

To pay for the evaluation time of the exercises and the issuance of the certificate, apart from delivering the correctly solved exercise, 25 € will have to be paid. The way of payment will be indicated at the end of the course.

Module 1: Preparation of an archaeological project: Views, layer and tables

Ready? Well, let’s start with the first topic, where besides learning where to download gvSIG Desktop – the software that we will use for the course – we will see how to prepare an archaeological project working with the main components of a GIS: Views, layers and tables.

Categories: OSGeo Planet
Syndicate content