Planet OSGeo feeds

Subscribe to Planet OSGeo feeds feed
Planet OSGeo - http://planet.osgeo.org
Updated: 2 hours 38 min ago

Cameron Shorter: What could Open Government learn from us Open Technology folks?

Tue, 03/27/2018 - 23:27
Despite open government’s best intentions to prioritise collaboration, government bodies consistently duplicate each other’s effort. Collaborating as effectively as open communities is much harder than you’d think.

A number of us “open technologists” have drafted a paper describing the challenges government faces, along with our vision for how to address these. It is being presented as part of Australia’s updated Open Government National Action Plan.

Reading time: 20 minutes (8 pages).

For the technical reader: If you are a technologist and agree with this vision, please add your technical credibility by signing (see below). Diverse support will help sponsors wanting to back its recommendations.
Open letterThis letter is presented on behalf of the citizens, technologists and organisations signed below.

When addressing the updated Open Government National Action Plan, and actions from the plan, we request stakeholders:
  • Acknowledge that the indicators for success are more than just “value for money” and “mitigation of risk”. 
  • Measure and prioritise: 
    • “Effectiveness of collaboration”, 
    • “Sustainability in the face of rapid innovation”, and 
    • “Resilience to monopolistic behaviours”. 
  • Develop an “Open Government Maturity Model” which describes open government goals and the processes required to achieve them.
  • Measure effectiveness at realising open government goals.
  • Arm decision makers with accessible, evidence based research into what works, so they can trust, select and defend collaborative strategies which are often counter-intuitive within traditional hierarchically managed organisations.
  • Use, extend, or create open technologies, in that order:
    1. Use existing open material if it exists;
    2. Otherwise extend and give back;
    3. As a last resort, create your own system.
  • Embrace modular architectures backed by open standards.
  • Prioritise initiatives which can attract and sustain participation from multiple contributors and organisations.
  • Promote collaboration between all levels of government, and between nations.
  • Invest in the communities of the projects you depend upon. Ensure there is funding to maintain a core team. Reduce barriers to entry in order to attract a wide contributor base. Develop indicators for reporting on the success of these investment strategies.
  • Consider strategies to flatten government’s spending cycles, especially for community based projects. 
  • Prioritise agile, iterative development methodologies over “big bang”, “whole of government” purchases.
Background reasoningDemocracy is founded on collaborationDemocratic governments are based upon collaboration. They work on behalf of citizens, for their citizens’ benefit. Based on this social mandate, the Australian government committed to the principles of open government in 2010, and signed up to the international Open Government Declaration in 2015. This declaration emphasises how openness and technology is to be used to make governments more collaborative, transparent, accountable, responsive, effective, innovative, and empowering of citizens.

However, by 2018, government bodies are regularly not collaborating, even though individuals involved want to. Why? Old acquisition processes which prioritise "value for money" and "mitigation of risk" inadvertently cause agencies to duplicate effort. In the digital economy, success indicators additionally include “effectiveness of collaboration”, “sustainability in the face of rapid innovation” and “resilience to monopolistic behaviours”. If governments are to collaborate as effectively as “open” communities, like open source software or Wikipedia, we need to use these additional indicators.
Recommendation 1: Develop an “Open Government Maturity Model” which describes open government goals and the processes required to achieve them.Such a model should draw from open community processes, such as the Apache Foundation’s open source incubation processes.
The allure of “open”In the early days of the “open” movement, Eric Raymond prophesied in The Cathedral and the Bazaar:
“Perhaps in the end the open-source culture will triumph not because cooperation is morally right or software hoarding is morally wrong ... but simply because the closed-source world cannot win an evolutionary arms race with open-source communities that can put orders of magnitude more skilled time into a problem.” Successful open communities have shown it is possible to attract more contributors from outside the organisation than can ever mustered from within.
In the digital economy, collaboration out-competes competition. Principles of the digital economyIn the digital economy, free copying, free tools, and the interconnectivity of the Internet has made it possible to tap into the world’s collective intelligence. This has led to:
  • Exponential information growth;
  • Exceptionally complex systems;
  • Rapid innovation;
  • And on the flip side, rapid obsolescence.
While it will always be tempting to build your own system, any self-built system will likely be out-innovated and become obsolete.
Recommendation 2: Use, Extend, or Create open technologies, in that order:
  1. Use existing open material if it exists;
  2. Otherwise extend and give back;
  3. As a last resort, create your own.
“Open” is just the startWhen adopting open technologies, we embrace “free access” to software, standards, and data. But there is more:
Openness is an enabler. It minimises legal and technical barriers to collaboration and sharing. Sharing ideas spawns more ideas and supercharges innovation. The reciprocity practices prevalent in collaborative communities inspire and empower individuals to contribute what they are passionate about, achieve their full potential, and collectively we all benefit. The “community litmus test”The Apache software foundation, like many open source foundations, emphasise the importance of diverse and sustainable communities for each of their projects. This applies the “wisdom of crowds” to validate the value and viability of each project. We believe governments should develop and apply similar criteria to validate the technical viability and community interest in projects they take on.
Recommendation 3: Prioritise initiatives which can attract and sustain participation from multiple contributors and organisations. “Copying” is not “collaboration”The Australian Digital Service Standard proudly states that it has been “adapted from the UK Government Design Principles”. This statement highlights a flaw in government’s approach to open principles. “Copying” instead of “collaborating” breaks a core principle of information management:
Retain a single point of truth. Government employees should be reaching out to their counterparts to collaboratively harmonise policies, processes, guides, best practices, software and more.
“Government collaboration” is not as good as “open collaboration”Collaboration in the “open” sense involves reciprocity, sharing, peer production, community building, trust, communication, inclusiveness, standards based interoperability, sustainability, and meritocracy.  Everyone involved is empowered to “scratch an itch”, develop an idea, and the community adopts the best ideas. This empowerment is a formula for rapid innovation.
However,
Traditional management views open collaboration as time consuming, imprecise, unreliable, hard to manage, rarely addresses short term objectives, hard to quantify in a business case, and rarely mentioned in acquisition guides. Yet, in a digital economy, collaborative communities are regularly out-innovating and out-competing closed or centrally controlled initiatives. By contrast, Government’s interpretation of collaboration has typically been based on the International Association for Public Participation (IAP2) using a spectrum of:
  • Inform: You will be told;
  • Consult: Your concerns will be considered;
  • Involve: Your concerns will be options;
  • Collaborate: Your advice will be sought;
  • Empower: You will decide what we implement.
There is no mention of co-development. In all these cases, the sponsoring agency still controls the process; still controls the allocation of funds; and still controls the management of labour. Bureaucratic overhead typically hampers contributions from external individuals or agencies. And here we encounter one of the subtle differences between open communities and open government:
Governments currently organise labour through command and control hierarchies while open communities typically coordinate themselves loosely around principles of self-direction, co-development, volunteering and reciprocity. When the Digital Transformation Agency was being launched, Malcolm Turnbull (who is now Prime Minister) stated,
"I'm a great believer in being much more global in our approach, ... we're all dealing with the same problems, pretty much. ...  We want to break down silos, break down all of the inertia that comes from empire building, so that citizens or businesses will have a seamless, straightforward way of dealing with government -- federal, state, or local."The first Open Government National Action Plan focuses at the national level, without mentioning state or local government.
Recommendation 4: Promote collaboration between all levels of government, and between nations. “Open” by itself is of little valueThe Australia’s Digital Services Design Principle 10 states: “Make things open: it makes things better.” As such, agencies have been publishing open datasets and software but have not been evaluating if they are being used effectively.
Making things open and hoping they will be used is like talking into the void and hoping others will hear. It is hit-and-miss. A digital asset only realises its value once it is discovered, and then integrated with other systems. The more widely it is used and extended, the more valuable it becomes.
Recommendation 5: Measure effectiveness at realising open government goals. Loving a community to deathCollaborative projects are susceptible to being “loved to death”. This happens when a project attracts an active user base without attracting matching contributions. The core team becomes overwhelmed, leaving insufficient capacity to cover essential operation and maintenance tasks.
Organisations shouldn’t overload a community they depend upon. As well as being not nice, it is bad business. Successful open projects have worked out how to apply a combination of:
  1. Politely saying “no” to “gifts” of unsupported extra functionality;
  2. Helping users become contributors, either in kind or financially;
  3. Minimising the onboarding effort for both contributors and the project’s core team.
If a sponsoring organisation isn’t ready to act as a good community citizen, actively supporting the long term sustainability of a project, then the sponsor will probably have a disappointing experience. The sponsor will make self-centered, short-term decisions, and won’t get the support required when most needed. The sponsor will likely be better off with proprietary systems, and the open community would be better off without the sponsor.
Attracting communityA team from the University of Massachusetts researching the success characteristics of open source projects found that projects which were successful at startup typically possessed:
  1. A clearly defined vision;
  2. Clear utility;
  3. And leaders who led by doing.
The projects which grew tended to:
  1. Attract larger user communities;
  2. Attract external developers, with half attracting a developer from another country;
  3. Provide fine-scaled task granularity, making it easier for people to contribute;
  4. And often attracted financial backing.
There are two approaches to attracting co-contributors to complex systems:
  1. Design modular systems, with fine-scaled task granularity, minimal ramp-up effort, and attract many contributors.
  2. Cultivate and retain core contributors who contribute across multiple years of involvement.
There is an inverse relationship between episodic and core contributors. Making episodic contributions trivial creates work for the core team, and vise-versa. Key to success is sustaining a core team focused on attracting and simplifying episodic contributions.
Recommendation 6: Invest in the communities of the projects you depend upon. Ensure there is funding to maintain a core team. Reduce barriers to entry in order to attract a wide contributor base. Develop indicators for reporting on the success of these investment strategies. Modularity and standardsA key strategy for managing complexity is to divide large systems into modular subsystems. It means you can improve one module, without impacting the rest of your system. This helps with maintenance, innovation, and keeping up with latest technologies.
Recommendation 7: Embrace modular architectures, backed by open standards. Modular systems include the following advantages:
  • Enable interoperability;
  • Facilitate collaboration;
  • Reduce system complexity;
  • Mitigate risks of obsolescence and vendor lock-in;
  • Facilitate sustained innovation.
Destabilising effects of episodic spendingOpen projects are vulnerable to the destabilising effects of episodic spending.

Organisations are often willing to pay a once-off fee to add extra features to a project, but are reluctant to pay for core project maintenance. Such investment results in high ramp-up costs as developers come on board, and then a loss of expertise when sponsorship ends. Technical debt is created for the new software without resources to maintain it.

Governments are prime culprits of episodic spending. Government budgets are managed around the financial year, with delayed budget approvals, resulting in discretionary spending centered around the last quarter of the year.

Proprietary business models are better structured to handle episodic funding. They can legally restrict software use unless a fee is paid, enabling spreading of development costs over time. Consequently, government’s propensity toward episodic spending inadvertently favours proprietary over open business models.
Recommendation 8: Consider strategies to flatten government’s spending cycles, especially for community based projects. Fragmented spendingGovernment taxes are collected centrally then split between departments, then split between divisions, then split between teams, and so on, until a group is funded to address a requirement. This hierarchical breakdown of budgets is appropriate for funding physical tasks such as building roads or collecting garbage; however, for the implementation of generic software functionality, it is usually more efficient for agencies to pool resources and collaboratively work on a common code base.
Fragmented spending results in narrow, short term solutions instead of solving broad, holistic and long term problems. Think agile instead of “big bang” purchasingIt’s tempting to address “fragmented spending” by aggregating budgets from multiple agencies into a central “whole of government” contract. From an accounting perspective, you’d think that the easiest way to acquire technology is by defining scope, acquiring budget, insource or outsource the work, and then manage the developers implementing the specification.

However due to the complexity of IT, developers and users will continuously provide ideas for improvement. Projects which adopt agile development methodologies, which continuously adjust direction to incorporate feedback, have a track record of producing better quality outcomes than traditional “waterfall” acquisition methodologies prevalent within government.  
Recommendation 9: Prioritise agile, iterative development methodologies over “big bang”, “whole of government” purchases. Chasing funds instead of collaboratorsOpen source communities typically become sustainable and scale by attracting a growing pool of collaborators. Government projects typically become sustainable and gain prominence by attracting funding and “empire building”.  Collaborating and sharing credit with external organisations typically weakens the importance of the individuals and teams. We need to adjust recognition and incentives to reverse this.
Call to ActionWe need to recognise that government agencies are consistently duplicating effort; that government approaches to collaboration have typically been sporadic and unsustainable; and that best practices in open communities exist but are not readily available to government decision-makers.
Recommendation 10: Arm decision makers with accessible, evidence based research into what works, so they can trust, select and defend collaborative strategies which are often counter-intuitive within traditional hierarchically managed organisations. Research and guides should be developed collaboratively, between agencies, nations, organisations and citizens.

We need to be bold enough to challenge widely established practices; we need to be aware of established wisdom; we need to be opportunistic and pragmatic; and we need to have the insight to know when to choose one over the other.
Related Reading
  1. Shorter, Cameron (August 2017). Making GovHack (and Open Government) more impactful.
  2. Ward, Dan (October 2011), Lieutenant Colonel, US Air Force. Acquisition Lessons from a Galaxy Far, Far Away.
  3. United States Assistant Secretary of Defense (Networks & Information, Integration) / DoD Chief Information Officer and the Under Secretary of Defense for Acquisition, Technology, and Logistics (May 2011). Open Technology Development: Lessons Learned & Best Practices.
  4. U.S. Public Participation Playbook
  5. Australian Government Digital Transformation Agency. Digital Service Standard.
  6. Australian Government Digital Transformation Agency. Design Principles.
  7. Australian Government Prime Minister and Cabinet. Open Government National Action Plan 2016-18
  8. Waugh, Pia (January 2015). Collaborative innovation in the public service: Game of Thrones style.
SignedIf you are a technologist and agree with this vision, please add your technical credibility by signing. Add a comment below, or email <cameron . shorter AT g m a i l .c o M>. Diverse support will help sponsors wanting to back this vision.

Australia:
  1. Cameron Shorter, Technology Demystifier; spent over a decade consulting to government on implementing Gespatial Open Source Software, Open Standards and Open Data; ex board member of the Open Source Geospatial Foundation (OSGeo); mentor in OSGeo Incubation committee; co-author of OSGeo Incubation processes; co-founder of OSGeoLive Open Source project.
  2. Nicholas Gruen, Chair, Open Knowledge Foundation (Australia), CEO of Lateral Economics, Former Chair of the Australian Government 2.0 Taskforce (2009) and of Innovation Australia in 2013-14.
  3. Arjen Lentz, Exec. Director Open Query Pty Ltd; former Community Relations Manager, MySQL AB; co-founder, Open Source Industry Australia, Inc
  4. Lev Lafayette, President, Isocracy Network; former President, Linux Users of Victoria, 2011-2014
  5. Steven De Costa, Steering Group member, CKAN Association (Open Source Data Portal) & Executive Director of Link Digital
  6. Bruce Bannerman, Director, GeoInnovations Pty Ltd; ex IT Manager, Australian Federal Government; Charter Member Open Source Geospatial Foundation (OSGeo); Mentor in OSGeo incubation committee; Former voting member, Open Geospatial Consortium Technical Committee.
  7. Stuart Guthrie, Co-CEO, Polonious Pty Ltd, Former President Open Source Industry Australia, Open Source Software developer and business owner. Current business, based on Open Source Software with offices in Australia, the US and the UK. Verticals in Case Management, Industries: Banking, Insurance, Government, Universities and Schools.
  8. Luke Carbis, Director of Product & Innovation at XWP.
  9. Evan Leybourn, CEO, Business Agility Institute.
  10. John Bryant, Principal, Mammoth Geospatial & Co-Chair, Free and Open Source Software for Geospatial and State of the Map Oceania Conference, 2018.
  11. David Collins, Independent Developer, Trilobite Solutions
  12. Alex Leith, Principal Spatial Analyst, Auspatious and Co-Chair, Free and Open Source Software for Geospatial and State of the Map Oceania Conference, 2018
New Zealand:
  1. Brent Wood, Information Delivery Programme Leader, NIWA. Ex Council member, New Zealand Open Source Society (NZOSS), Charter Member Open Source Geospatial Foundation (OSGEO).
Europe:
  1. Dirk Frigne, president Open Source Geospatial Foundation Europe (OSGeo Europe vzw), OSGeo Charter member, Former Vice president of  OSGeo, CEO Geosparc nv.
  2. Jo Cook, Astun Technology, UK, OSGeo advocate, founder and chairman of Open Source Geospatial Foundation (OSGeo) UK local chapter, vice chair FOSS4G 2013 international conference (Free and Open Source Software for Geospatial)
  3. Vasile Crăciunescu, researcher Romanian National Meteorological Administration, Open Source Geospatial Foundation board member.
  4. Suchith Anand, founder of Geo4All, the Open Source Geospatial Foundation's network of educational institutions.
United States of America:
  1. Patrick Hogan, NASA WorldWind Project Manager, NASA
  2. Charles Schweik, Professor, School of Public Policy, University of Massachusetts, Amherst
Other nationalities:

Text in this document is licensed under the Creative Commons Attribution 4.0 Licence.

Fernando Quadro: Especialização em SIG na UCPel

Tue, 03/27/2018 - 12:30

A UCPel acaba de lançar o curso de Especialização em Sistemas de Informações Geográficas que busca atender a demanda local e regional, de acordo com as necessidades dos profissionais ligados direta ou indiretamente a esta específica área do conhecimento.

A universidade considera de suma importância o envolvimento da comunidade acadêmica e profissional, de forma mais direta aos gestores do espaço urbano e rural, comprometendo-se com a formação de profissionais preocupados com a meio-ambiente (urbano e rural) e questões de sustentabilidade com vias a melhor qualidade de vida da população e das relações humanas que ocorre nestes ambientes.

O curso é baseado em assuntos que estão em envidência no mercado como Big Data, CAR, entre outros. Abaixo segue as disciplinas que serão abordadas neste curso de pós-graduação:

  • Introdução aos Sistemas de Informações Geográficas
  • Cartografia
  • Ajustamentos
  • Levantamentos Topográficos
  • Levantamentos Geodésicos
  • Sensoriamento Remoto I e II
  • Processamento Digital de Imagens
  • SIG Aplicado I e II
  • Georreferenciamento de Imóveis Rurais
  • Sistemas de Informações Ambientais
  • GEODireito
  • Cartografia Temática
  • Estatística Espacial
  • Banco de Dados Geográfico
  • Publicação de dados espaciais na WEB
  • Big Data e SIG

Se quiser saber mais informações deste curso basta clicar aqui.

gvSIG Team: Video about The Horton Machine plugin available: new geoprocesses for gvSIG

Tue, 03/27/2018 - 10:30

The recording of the video about The Horton Machine plugin is now available. This plugin adds hundreds of new geoprocesses to gvSIG.

This presentation was given during the 3rd gvSIG Festival, and it shows how to work with this new extension, that includes a lot of interesting tools: geomorphology analysis (drainage direction, network and watershed extraction, rescaled distances and hydrologic attributes, slope, curvatures, hydrologic indexes, geomorphologic attributes, statistics, peakflow, Saint Venant, tools to prepare data for HECRAS, Shalstab, debrisflow…), LESTO (LiDAR Empowered Sciences Toolbox Opensource), raster map calculator, mobile tools…

At this post you can find more information about how to install it.

And here you have the video about the presentation:

gvSIG Team: ‘Just Side’, herramienta para identificar injusticias sociales y ambientales en Iberoamérica

Mon, 03/26/2018 - 21:31

Una red de universidades y empresas iberoamericanas liderada por la Universidad portuguesa de Coimbra y en la que participa la Asociación gvSIG desarrollará durante los próximos años la herramienta ‘Just Side’, un programa basado en el ‘geoderecho’ que identificará las injusticias sociales y ambientales para su posible prevención. Esta herramienta a desarrollar se pondrá a disposición de los gobiernos de los países iberoamericanos.

El proyecto, que acaba de arrancar, estudiará 16 casos concretos en territorios donde se hayan desarrollado políticas cuyo resultado haya sido nocivo desde el punto de vista económico o ambiental para la población.

Para desarrollar ‘Just Side’, se estudiarán principalmente territorios con dificultad de acceso a los servicios públicos esenciales, lugares donde se suelen construir infraestructuras con impactos negativos, tales como vertederos de residuos o incineradoras.

El programa dispondrá de una solución con base cartográfica sobre la que ser irán superponiendo variables, tales como la renta per cápita, el tipo de vivienda, distancias a servicios públicos o acceso a vías de comunicación. Toda la información, territorial y social, será analizada mediante procesos geoespaciales que ayuden en la visualización y detección de problemas y patrones. Precisamente la Asociación gvSIG forma parte de esta red como experto en el desarrollo de Sistemas de Información Geográfica con software libre.

La futura herramienta tendrá un doble objetivo: identificación de los problemas relacionados con injusticias territoriales y  la puesta a disposición de los gobiernos de una solución en software libre, facilitando el que puedan corregir dichos desequilibrios mediante políticas adecuadas.

En la creación de la herramienta la Asociación gvSIG trabajará con 40 investigadores de las universidades de Buenos Aires, Santa Catarina (Brasil), Costa Rica, Santiago de Chile, la Autónoma de México, Uruguay, y la española de La Rioja, además de con la empresa brasileña Geodereito. Para el desarrollo de la solución la Asociación gvSIG pondrá a disposición la Suite gvSIG, su catálogo de soluciones en software libre para gestión de información territorial.

Como ejemplo, en el caso de Chile, la red de investigadores evaluará la iniciativa que pondrá en marcha el Gobierno en la Isla de Pascua, con la que pretende restituir a la población indígena de esta zona, los míticos Rapa Nui, los terrenos que les fueron arrebatados el siglo pasado.

De esta manera, mediante la nueva herramienta también se podrán analizar la formas de compensar injusticias históricas.

En el caso de Portugal, los estudios se centrarán en los embalses de la cuenca alta del río Duero, tanto los que están en activo como los que se pretenden construir, con el fin de analizar los niveles de desempleo o los impactos ambientales.

Esta red iberoamericana, financiada por CYTED, y cuyos trabajos se extenderán hasta 2021, se presentará el próximo 20 de abril en la Universidad de Coimbra, formando parte de una conferencia que contará con expertos sobre geoderecho y geomática de Portugal, España y Noruega, especializados en la vulnerabilidad social a partir del territorio.

gvSIG Team: Video of the presentation about ‘Emergency management and prevention with gvSIG Online’ available

Mon, 03/26/2018 - 18:32

During the 3rd gvSIG Festival there was a presentation about “Emergency management and prevention with gvSIG Online“, a different application of the platform for Spatial Data Infrastructures implementation based on open source software, carried out by the gvSIG Association.

At this presentation we show how gvSIG Online has improved the ability to act in case of an emergency, facilitating the work and allowing to manage geographic information in an easy way. This platform has been implemented in the fire brigade department in Valencia (Spain), and it would be able to be applied in any country for prevention and emergencies. Here you can watch the video with the presentation:

gvSIG Team: Recording of “gvSIG applied to geology and mining” presentation available

Mon, 03/26/2018 - 16:13

During the 3rd gvSIG Festival there has been a presentation about gvSIG applied to geology and mining. Exploration, investigation, exploitation…each one of these steps include different tasks that can be benefited by their inclusion in a gvSIG analysis. Find out more about open source GIS applied to geology and mining…

The video of this presentation is available here:

Jackie Ng: Announcing: MapGuide Open Source 3.1.1 Release Candidate

Mon, 03/26/2018 - 15:09
I am pleased to announce the release candidate of MapGuide Open Source 3.1.1 is now available.

Of the ton of bug fixes and minor enhancements since the 3.1 release, the key changes of note in 3.1.1 are:

Have a gander at the full list of changes for more information.
This is a release candidate, and not the final release as it's been so long since the 3.1 release that I want to make sure our release process is still sound after such a long break between releases. Barring anything of a show-stopping nature, the final release of 3.1.1 will drop one week from now.
Download/Release Notes

Fernando Quadro: Novos módulos no GeoServer 2.13

Mon, 03/26/2018 - 12:30

A versão 2.13 vem com alguns novos módulos, em particular:

– Você deseja gerar saídas compatíveis com GHRSST a partir de entradas do GHRSST? Experimente o novo módulo de saída do GHRSST NetCDF.
– O módulo MongoDB fornece um wrapper fácil de usar no armazenamento de dados mongodb do GeoTools, permitindo que você publique dados geoespaciais armazenados no seu mongodb.
– Há também um novo módulo que introduz perfis NSG para os serviços WFS e WMTS.

Os módulos existentes também receberam algum “carinho”, em particular:

– O módulo de download WPS agora permite baixar mapas grandes e também criar animações, gerando MP4 cortesia da biblioteca jcodec. Ambos os processos podem (e devem!) ser invocados de forma assíncrona para lidar melhor com longos tempos de geração. Aqui está um exemplo de saída de animação:

http://www.fernandoquadro.com.br/html/wp-content/uploads/2018/03/response.mp4

– O processo de download do WPS agora também permite o controle da estrutura de saída do GeoTiff (tiling, compression) em downloads rasterizados, bem como o download de parte de grânulos de um mosaico heterogêneo em seu CRS nativo e resolução nativa.

– Várias melhorias de desempenho JDBCConfig e JDBCStore, reduzindo o número de consultas de configuração de banco de dados realizadas para cada solicitação OGC. As consultas de configuração também são registradas de maneira consistente para análise posterior.

Note que os módulos não fazem parte do lançamento; em vez disso, você pode encontrá-los nas nightly builds.

Fonte: GeoServer Blog

Free and Open Source GIS Ramblings: Processing script template for QGIS3

Sun, 03/25/2018 - 11:08

Processing has been overhauled significantly for QGIS 3.0. Besides speed-ups, one of the most obvious changes is the way to write Processing scripts. Instead of the old Processing-specific syntax, Processing scripts for QGIS3 are purely pythonic implementations of QgsProcessingAlgorithm.

Here’s a template that you can use to develop your own algorithms:

from qgis.PyQt.QtCore import QCoreApplication, QVariant from qgis.core import (QgsField, QgsFeature, QgsFeatureSink, QgsFeatureRequest, QgsProcessing, QgsProcessingAlgorithm, QgsProcessingParameterFeatureSource, QgsProcessingParameterFeatureSink) class ExAlgo(QgsProcessingAlgorithm): INPUT = 'INPUT' OUTPUT = 'OUTPUT' def __init__(self): super().__init__() def name(self): return "exalgo" def tr(self, text): return QCoreApplication.translate("exalgo", text) def displayName(self): return self.tr("Example script") def group(self): return self.tr("Examples") def groupId(self): return "examples" def shortHelpString(self): return self.tr("Example script without logic") def helpUrl(self): return "https://qgis.org" def createInstance(self): return type(self)() def initAlgorithm(self, config=None): self.addParameter(QgsProcessingParameterFeatureSource( self.INPUT, self.tr("Input layer"), [QgsProcessing.TypeVectorAnyGeometry])) self.addParameter(QgsProcessingParameterFeatureSink( self.OUTPUT, self.tr("Output layer"), QgsProcessing.TypeVectorAnyGeometry)) def processAlgorithm(self, parameters, context, feedback): source = self.parameterAsSource(parameters, self.INPUT, context) (sink, dest_id) = self.parameterAsSink(parameters, self.OUTPUT, context, source.fields(), source.wkbType(), source.sourceCrs()) features = source.getFeatures(QgsFeatureRequest()) for feat in features: out_feat = QgsFeature() out_feat.setGeometry(feat.geometry()) out_feat.setAttributes(feat.attributes()) sink.addFeature(out_feat, QgsFeatureSink.FastInsert) return {self.OUTPUT: dest_id}

This script just copies the features of the input layer to the output layer without any modifications. Add your logic to the processAlgorithm() function to get started.

Use Create New Script from the Toolbox toolbar:

Paste the example script:

Once saved, the script will show up in the Processing toolbox:

Free and Open Source GIS Ramblings: Revisiting point & polygon joins

Sat, 03/24/2018 - 12:25

Joining polygon attributes to points based on their location is a very common GIS task. In QGIS 2, QGIS’ own implementation of “Join attributes by location” was much slower than SAGA’s “Add polygon attributes to points”. Thus, installations without SAGA were out of good options.

Luckily this issue (and many more) has been fixed by the rewrite of many geoprocessing algorithms for QGIS 3! Let’s revisit the comparison:

I’m using publicly available datasets from Naturalearth: The small scale populated places (243 points) and the large scale countries (255 polygons with many nodes). Turns out that QGIS 3’s built-in tool takes a little less than two seconds while the SAGA Processing tool requires a litte less than six seconds:

Like in the previous comparison, times were measured using the Python Console:

In both tools, only the countries’ SOVEREIGNT attribute is joined to the point attribute table:

import processing t0 = datetime.datetime.now() print("QGIS Join attributes by location ...") processing.runAndLoadResults( "qgis:joinattributesbylocation", {'INPUT':'E:/Geodata/NaturalEarth/vector_v4/natural_earth_vector/110m_cultural/ne_110m_populated_places.shp', 'JOIN':'E:/Geodata/NaturalEarth/vector_v4/natural_earth_vector/10m_cultural/ne_10m_admin_0_countries.shp', 'PREDICATE':[5],'JOIN_FIELDS':['SOVEREIGNT'], 'METHOD':0,'DISCARD_NONMATCHING':False,'OUTPUT':'memory:'}) t1 = datetime.datetime.now() print("Runtime: "+str(t1-t0)) print("SAGA Add polygon attributers to points ...") processing.runAndLoadResults("saga:addpolygonattributestopoints", {'INPUT':'E:/Geodata/NaturalEarth/vector_v4/natural_earth_vector/110m_cultural/ne_110m_populated_places.shp', 'POLYGONS':'E:/Geodata/NaturalEarth/vector_v4/natural_earth_vector/10m_cultural/ne_10m_admin_0_countries.shp', 'FIELDS':'SOVEREIGNT','OUTPUT':'C:/Users/anita/AppData/Local/Temp/processing_8b1bbde78de5490285dd530e115cca52/099660d88bf14c54a853cc230e388e55/OUTPUT.shp'}) t2 = datetime.datetime.now() print("Runtime: "+str(t2-t1))

It is worth noting that it takes longer if more attributes are to be joined to the point layer attribute table. For example, if the JOIN_FIELDS parameter is empty:

'JOIN_FIELDS':[]

instead of

'JOIN_FIELDS':['SOVEREIGNT']

then the the Join attributes by location takes almost 16 seconds. (The country layer contains 71 attributes after all.)

(The SAGA tool currently allows only joining one attribute at a time.)

Fernando Quadro: Melhorias na interface gráfica do GeoServer

Fri, 03/23/2018 - 11:30

Ainda como parte das melhorias realizadas na versão 2.13 do GeoServer, a interface para digitar URLs para arquivos de dados foi melhorada com a funcionalidade de autocomplete – agora o GeoServer irá verificar o caminho que já foi digitado e sugerir arquivos existentes dentro desse caminho.

Além disso, o suporte ao preenchimento automático foi adicionado a vários menus suspensos que contêm uma longa lista de valores, como stores e layers. Agora você pode começar a digitar o nome de uma opção e as opções visíveis serão filtradas de acordo com o que você digitou.

A edição dos parâmetros da camada raster tornou mais fácil, pois ao invés de apenas campos texto de entrada, alguns campos foram substituídos por campos com controles apropriados, dependendo do tipo de parâmetro. Aqui está uma comparação do “antes e depois”:

Finalmente, as mensagens de erro agora são exibidas na parte superior (como de costume) e na parte inferior (nova!) em todas as páginas de configuração. Isso deve facilitar a localização de mensagens de erro, especialmente durante a edição de estilos:

Fonte: GeoServer Blog

GRASS GIS: GRASS GIS 7.2.3 LTS released

Thu, 03/22/2018 - 22:44
We are pleased to announce the GRASS GIS 7.2.3 LTS release

gvSIG Team: Cómo utilizar gvSIG Mobile, el SIG en software libre para toma de datos en campo

Thu, 03/22/2018 - 19:11

Durante el 3er Festival gvSIG se ha realizado una presentación práctica sobre cómo trabajar con gvSIG Mobile, el SIG en software libre para toma de datos en campo, y su integración con gvSIG Desktop, el SIG en software libre que permite una edición y análisis avanzados, geoprocesamiento…

La aplicación gvSIG Mobile se puede instalar desde Google Play Store.

Durante la presentación se han mostrado las diferentes herramientas disponibles en esta interesante aplicación, y cómo importar/exportar datos desde/a gvSIG Desktop. También se ha explicado cómo instalar el complemento disponible para gvSIG Desktop que permite gestionar la cartografía de gvSIG Mobile.Los enlaces directos a las diferentes herramientas que se han mostrado durante el video son los siguientes:

El vídeo completo de la presentación es el siguiente:

gvSIG Team: How to use gvSIG Mobile, open source GIS for field data gathering

Thu, 03/22/2018 - 17:23

During the 3rd gvSIG Festival there has been a practical presentation about how to work with gvSIG Mobile, the open source GIS for field data gathering, and its integration with gvSIG Desktop, the open source GIS that allows an advance editing, analysis, geoprocessing…

gvSIG Mobile can be installed from Google Play Store.

During the presentation we have shown the different tools that are available in this interesting application, and how to import/export data from/to gvSIG Desktop. We also explained how to install the plugin available for gvSIG Desktop to manage gvSIG Mobile cartography.

Here you have a direct link to the different tools that have been shown during the video:

And here you have the complete video:

If you have any doubt or problem with the applications you can use the mailing lists.

gisky: Easily testing the latest version of GDAL

Thu, 03/22/2018 - 17:17
GDAL is one of the cornerstones of the open source geospatial stack (and actually of many of the proprietary systems as well).
If you want to use or test the latest features this can be done quite easily by setting a few environment variables:

I save this commands in a file new_gdal.sh. After running

source new_gdal.shYou will be able to use all the latest gdal tools.

johan@x1:~$ source ~/latest_gdal.sh
johan@x1:~$ gdalinfo --version
GDAL 2.3.0dev, released 2017/99/99


Actually if you use this command, also tools dynamically linked to gdal will be using this latest version.

johan@x1:~$ saga_cmd io_gdal
____________________________

##### ## ##### ##
### ### ## ###
### # ## ## #### # ##
### ##### ## # #####
##### # ## ##### # ##
____________________________

SAGA Version: 6.4.0


Library: GDAL/OGR
Category: Import/Export
File: /usr/local/lib/saga/libio_gdal.so
Description:
Interface to Frank Warmerdam's Geospatial Data Abstraction Library (GDAL).
Version 2.3.0dev

Note that this will work well for packages dynamically linked to the C api. If packages are linked to the C++ api, they may need recompilation.

If you are on windows, you could have a look at SDKShell.bat (part of the builds from Tamas Szekeres).

Note: I actually wrote this blogpost because in his presentation on FOSDEM Jeremy Mayeres recommended using Docker for using the latest version of GDAL. I think that solution is overkill for desktop usage, and using environment variables is easier.

gvSIG Team: Vídeo de presentación de las novedades de gvSIG Desktop 2.4

Thu, 03/22/2018 - 16:35

Como parte del 3er gvSIG Festival se ha realizado un webinar de presentación de las principales novedades de la última versión de gvSIG Desktop.

Si eres usuario de gvSIG Desktop no te pierdas este vídeo para descubrir todas las mejoras de la versión 2.4:

Puedes descargar gvSIG Desktop, tanto en su versión instalable como portable, desde aquí:

http://www.gvsig.com/es/productos/gvsig-desktop/descargas

gvSIG Team: gvSIG aplicado a Medio Ambiente. Grabación del webinar disponible.

Thu, 03/22/2018 - 14:48

La necesidad de medir, gestionar y analizar la información de los estudios ambientales ha hecho de los Sistemas de Información Geográfica una herramienta fundamental. Lo demuestra su aplicación en campos como el ámbito forestal (áreas de aprovechamiento forestal, valoración de zonas afectadas por incendios, control de plagas…), conservacionista (monitoreo de especies protegidas, gestión de humedales,…), agrícola (establecimiento de zonas óptimas de cultivo, gestión de recursos hídricos,…), etc.

Os traemos la grabación del webinar ‘gvSIG aplicado a Medio Ambiente’ realizado durante el 3er gvSIG Festival. Durante el mismo se introducirá en el uso de gvSIG al trabajo medioambiental.

Y si os interesa el tema, y queréis formaros en el uso de estas tecnologías para Medio Ambiente, no os perdáis este curso gratuito.

gvSIG Team: Video about the gvSIG Desktop 2.4 new features is now available

Thu, 03/22/2018 - 14:45

The new features of the last gvSIG version (gvSIG 2.4) have been presented during the 3rd gvSIG Festival.

At this presentation we have shown the different plugins that have been included in this powerful version, and all the improvements, both in the existing functionalities and on the application behaviour.

If you have any doubt about this last version you can use the gvSIG mailing lists.

The video of this presentation is available here:

gvSIG Team: Recording of “gvSIG applied to archaeology” presentation available

Thu, 03/22/2018 - 12:49

During the 3rd gvSIG Festival there has been a presentation about gvSIG applied to archaeology.

At this video the speaker showed several successful cases studies in this sector, carried out by several users in the last years with gvSIG.

At the end of the video, gvSIG Online was shown too, with data related to archaeology loaded on a geoportal.

The video of this presentation is available here:

Fernando Quadro: Workspaces isolados no GeoServer

Thu, 03/22/2018 - 11:30

O conceito de “Espaços de Trabalho Isolados (Isolated Workspaces)” foi adicionado ao GeoServer na versão 2.13.0, para permitir a reutilização de um namespace entre vários espaços de trabalho (workspace).

Em particular, um espaço de trabalho isolado permite a reutilização de um namespace já utilizado por outro espaço de trabalho, mas os seus recursos (camadas, estilos, etc.) só podem ser recuperados ao utilizar os serviços virtuais desse espaço de trabalho que só serão exibidos nesses documentos.

Ao reutilizar um namespace entre espaços de trabalho, exatamente um deles deve ser não-isolado, e o restante deve ser isolado; Por exemplo, espaços de trabalho isolados não têm restrições no uso de um namespaces, mas as restrições existentes ainda se aplicam a espaços de trabalho não isolados.

Isso é particularmente útil para quem publica esquemas complexos para conformidade com o INSPIRE (Europa). Para mais detalhes, consulte a proposta original desta funcionalidade.

Fonte: GeoServer Blog

Pages