OSGeo Planet

Free and Open Source GIS Ramblings: New style: conveyor belt flows

OSGeo Planet - Thu, 2016-12-08 10:56

The QGIS map style I want to share with you today was inspired by a hand-drawn map by Philippe Rekacewicz that I saw on Twitter:

Visionscarto met en ligne quelques unes des archives #Chine, dans le contexte régional et dans la mondialisation https://t.co/51nFLHUSXM pic.twitter.com/ZIlnEUxJK3

— Visions carto (@visionscarto) November 25, 2016

The look reminds me of conveyor belts, thus the name choice.

You can download the symbol and a small sample dataset by adding my repo to the QGIS Resource Sharing plugin.

resourcesharing_conveyor

The conveyor belt is a line symbol that makes extensive use of Geometry generators. One generator for the circle at the flow line start and end point, respectively, another generator for the belt, and a final one for the small arrows around the colored circles. The color and size of the circle are data defined:

conveyor_details

The collection also contains a sample Geopackage dataset which you can use to test the symbol immediately. It is worth noting that the circle size has to be specified in layer CRS units.

It’s great fun playing with the power of Geometry generator symbol layers and QGIS geometry expressions. For example, this is the expression for the final geometry that is used to draw the small arrows around colored circles:

line_merge( intersection( exterior_ring( convex_hull( union( buffer( start_point($geometry), "start_size" ), buffer( end_point($geometry), 500000 ) ) ) ), exterior_ring( buffer( start_point( $geometry), "start_size" ) ) ) )

The expression constructs buffer circles, the belt geometry (convex_hull around buffers), and finally extracts the intersecting part from the start circle and the belt geometry.

Hope you enjoy it!

It’s holiday season, why not share one of your own symbols with the QGIS community?


Categories: OSGeo Planet

Fernando Quadro: FOSS4G Brasil 2017

OSGeo Planet - Wed, 2016-12-07 13:53

O FOSS4G (do inglês, Free and Open Source Software for Geographic Information System) é o evento mundial anual da Fundação Geoespacial de Código Aberto (OSGeo), e é reconhecido como o maior evento de geotecnologia livre do mundo, com organização em diferentes escalas (Locais, regionais ou globais). A proposta do evento é difundir o uso de tecnologias livre na área de geotecnologia, bem como fomentar a troca de conhecimentos, práticas, formação em novas tecnologias e entrada no mundo do código aberto.

A partir de 2013 a OSGeo começou a incentivar a comunidade a criar eventos locais do FOSS4G, para uma maior interação da mesma, tendo em vista que nem todos têm a oportunidade de ir ao evento global, que acontece cada ano em um continente diferente.

Desde então vários eventos locais têm acontecido ao redor do mundo, e em 2017 será a vez do Brasil. O primeiro FOSS4G Brasil será realizado nos dias 27, 28 e 29 de julho de 2017 na cidade de Curitiba (PR), acreditando que será uma ótima oportunidade para aqueles que estão em busca de novidades, conhecimento, networking e negócios.

Agende esta data, em breve você terá mais informações sobre o evento.

Posts RelacionadosZemanta
Categories: OSGeo Planet

Narcélio de Sá: Rótulos com guias no QGIS

OSGeo Planet - Wed, 2016-12-07 03:46

Essa dica é pra você que teve necessidade de colocar rótulos em feições com geometrias muito próximas e precisa mover os rótulos adicionando uma linha guia. Eu tive essa necessidade recentemente no trabalho e encontrei essa dica fantástica do Alexandre Neto, do blog SIG sem grilhetas.

O Alexandre usou uma view no Postgis para automatizar a criação de guias para os rótulos que são movidos de sua posição original. Veja o resultado abaixo:

guidelines

No meu caso eu consegui resolver meu problema com os rótulo usando essa solução QGIS + Postgis. Mas essa solução, ao meu ver, esbarra em alguns problemas.

O principal deles é que nem todo mundo usa o Postgis, ou outro banco de dados espacial suportado pelo QGIS como o SpatiaLite, MSSQL Spatial ou Oracle Spatial. Tudo bem que depois da versão 2.14 você poderia adotar o recurso Virtual layers e fazer isso sem precisar instalar um desses banco de dados na sua máquina.

Mas convenhamos que isso limita o uso dessa solução para uma grande parcela dos usuários que não manjam dos paranauês de banco de dados e linguagem SQL.

O outro problema é estético e operacional, leia-se frescuragem desse que vós fala, que é a necessidade da criação de uma nova camada para renderizar as guias dos rótulos. Ou seja uma camada a mais no meio de trocentas outras que temos que lidar no dia a dia.

No exemplo acima a camada labels_leaders, é quem renderiza a guia que conecta o rótulo ao centroide da feição.

Criando rótulos com guias no QGIS

Pois bem, quebrando um pouco a cabeça podemos chegar num resultado idêntico ao do Alexandre. Mas no nosso caso sem a necessidade de um banco de dados espacial e nem daquela camada extra para renderizar a guia. Iremos usar apenas a tabela de atributos e a função de geração de geometria para resolver nosso problema. Lembrando que para isso você vai precisar do QGIS 2.14 ou superior, uma vez que o Gerador de Geometrias não está presente nas versões anteriores. 

Veja o passo a passo no vídeo abaixo:

Expressões para a criação das guias no QGIS

Rótulo ao centróide com curva de 90º

make_line ( make_point( "X" , "Y" ), -- posição do rótulo make_point( "X", y(centroid( $geometry ))), -- posição do ponto intermediário make_point( x(centroid( $geometry )), y(centroid( $geometry ))) --posição do centroide da geometria )

Rótulo ao centróide

make_line ( make_point( "X" , "Y" ), -- posição do rótulo make_point( x(centroid( $geometry )), y(centroid( $geometry ))) --posição do centroide da geometria )

Rótulo ao ponto mais próximo

make_line ( make_point( "X" , "Y" ), -- posição do rótulo closest_point( $geometry, make_point( "X" , "Y" ) ) --posição do ponto mais próximo )

The post Rótulos com guias no QGIS appeared first on Narcélio de Sá.

Categories: OSGeo Planet

PyWPS team: PyWPS 4.0.0 released

OSGeo Planet - Wed, 2016-12-07 00:00
PyWPS 4.0.0 released

The PyWPS Development team announces the release of PyWPS 4.0.0.

Changes

Features of this version:

  • PyWPS 4.0.0 is completely rewritten “from scratch” of the software
  • PyWPS 4.0.0 uses MIT License
  • It uses modern libraries for XML serialisation and deserialization
  • Jobs queue with database back-end implemented, introduces possibility to control process-job’s life cycle
  • Introduces input data validation (for levels NONE to VERYSTRICT)
  • Multiprocessing Python module for asynchronous jobs starting

To download this version, please go to http://pywps.org/download

NOTE:

PyWPS-4 is completely rewritten from scratch - the logic of process definition remained the same, but processes are not compatible with previous 3.x version.

What is PyWPS:

PyWPS (Python Web Processing Service) is implementation of Web Processing Service standard from Open Geospatial Consortium (OGC(R)). Processes can be written using GRASS GIS, but usage of other programs, like R package, GDAL or PROJ tools, is possible as well.

You can find more in our PyWPS-4.0.0 presentation on SlideShare

Happy GISing!

PyWPS Development team

P.S. Happy birthday, Jorge!

Categories: OSGeo Planet

PyWPS team: PyWPS 4.0.0 released

OSGeo Planet - Wed, 2016-12-07 00:00
PyWPS 4.0.0 released

The PyWPS Development team announces the release of PyWPS 4.0.0.

Changes

Features of this version:

  • PyWPS 4.0.0 is completely rewritten “from scratch” of the software
  • PyWPS 4.0.0 uses MIT License
  • It uses modern libraries for XML serialisation and deserialization
  • Jobs queue with database back-end implemented, introduces possibility to control process-job’s life cycle
  • Introduces input data validation (for levels NONE to VERYSTRICT)
  • Multiprocessing Python module for asynchronous jobs starting

To download this version, please go to http://pywps.org/download

NOTE:

PyWPS-4 is completely rewritten from scratch - the logic of process definition remained the same, but processes are not compatible with previous 3.x version.

What is PyWPS:

PyWPS (Python Web Processing Service) is implementation of Web Processing Service standard from Open Geospatial Consortium (OGC(R)). Processes can be written using GRASS GIS, but usage of other programs, like R package, GDAL or PROJ tools, is possible as well.

You can find more in our PyWPS-4.0.0 presentation on SlideShare

Happy GISing!

PyWPS Development team

P.S. Happy birthday, Jorge!

Categories: OSGeo Planet

Paul Ramsey: NRPP, It's Alive!

OSGeo Planet - Tue, 2016-12-06 23:00

Hey, good news zombie lovers, the project I’ve declared dead (or, at least, doomed) is not only still shambling around, it’s going to get the official political glad-handing treatment tomorrow:

NRPP, It's Alive!

We are excited to share an important Natural Resource Permitting Project (NRPP) milestone. Tomorrow—December 7—NRPP’s first service on the NRS Online Services website will be launched in Williams Lake at FrontCounter BC with Minister of State for Rural Economic Development Donna Barnett.

I always feel sad for the poor politician tasked with the “new website” announcement, because honestly, is there any announcement that feels like more of an empty gesture towards real action? “Yes, I understand you wanted $50M for addiction treatment, but… how about this new web site?”

Anyways, while she’s getting her demonstration of the new NRS Online Services website, here’s some questions Minister Barnett might like to ask:

  • Can I drive? Let me use the computer. Why don’t you ever let the Minister use the computer? I’m the Minister, dammit.
  • Why is it so slow? Surely for this kind of money it should be fast.

  • What are all those buttons across the top? What does the pencil mean? I’ve never seen those icons before. What do you mean “have I ever used ArcView?”, what’s ArcView?

  • You really expect me to click all those links to find out what impacts my project? There’s got to 20 of them!

  • Does it work on my phone? Ah, kind of, I see. No, I don’t know what a “bootstrap” is.

  • Honestly, why is it so slow? Am I clicking it wrong?

  • Does this work align with government priorities? Maybe you need to do some more transformation on it.

Congratulations, NRPP on your first step towards transforming the sector, have a great demo!

Addendum: In the press release, Minister Steve Thomson is quoted as “saying” (poor Ministers always sound so stodgy when they “speak” in press releases):

Through the Natural Resource Permitting Project, the Province is making a significant investment in helping communities balance economic development with protecting our natural resources.

My notes:

  • The province is surely making a “siginificant investment” in Deloitte and CGI. Whether that investment ends up “helping communities” is still very much a question in flux.
  • The purpose of NRPP is not “balance” between economic development and protected natural resources. The business case makes clear, the purpose of NRPP is to increase natural resource extraction rates, generating a permanent lift in royalties to offset the (significant) costs of NRPP. Sadly, even on those terms it’s likely to fail.

Such a short sentence, yet still so much misdirection.

Categories: OSGeo Planet

Jackie Ng: React-ing to the need for a modern MapGuide viewer (Part 7): Laying out the blueprints

OSGeo Planet - Tue, 2016-12-06 14:39
With the latest release of mapguide-react-layout out of the way, it's time to continue the journey of porting across the remaining fusion templates across.

One of the "problems" we have right now with this new viewer is that although we have got most of the foundational stuff right, the UI lacks stylistic cohesion. This is due to the viewer being a mish-mash of various react components, each with their own unique styling quirks. I really wanted a react-based UI toolkit that had a good enough baseline set of widgets/components with a unified look for building desktop-centric web applications (with an option to go mobile down the road).

Most of these UI toolkits however, take the reverse direction. They are mobile/tablet first, trying to emulate Material Design, iOS or Bootstrap and when trying to adapt such toolkits for a desktop-centric web application design, just look horribly out of place. Most of the UI toolkits that would've passed my desired criteria (like kendo, ExtJS, jQuery UI, etc) suffered from being imperative JavaScript APIs (meaning it would be a painstaking effort to interop with React and/or TypeScript), or some had incompatible/undesirable licenses to boot.

Well, I think my wish for such a toolkit has now been fulfilled, and its name is Blueprint.

What sold me on this particular UI toolkit was:
  • It is React-based
  • It has a good wide range of components that covers most of what I need to port across the remaining Fusion templates
  • It comes with a diverse set of icon fonts
  • It has a friendly license (BSD)
  • It is written in TypeScript and the library comes bundled with TypeScript definitions
  • It looks good!
With so many good selling points, I've decided to adopt Blueprint as the UI foundation for all my viewer templates. This means.
We have better looking modal dialogs (as seen in our updated Aqua template)



We have better styled UI for certain tools
 

And we have key components needed to start bringing across the other remaining Fusion templates, like the TurquoiseYellow template.
Compare the original Fusion template



With our blueprint-powered version


Looks good enough doesn't it?

Now there is one executive decision I'm making with the Fusion templates I'm porting over. The overview map will always be present as a toggle-able button on the main map viewer component and not outside of the map viewport.

Part of the problem is having the OpenLayers OverviewMap control render its content outside of the map viewport doesn't really play nice with React component updates in my attempts thus far, so I've taken the creative decision to not bother trying to get everything 1:1 when porting these templates over. As long as the main elements and styles are there, it's good enough for me.

Now sadly, despite having made several existing libraries and React components redundant (and they have been removed as a result), taking on Blueprint has added a lot of extra weight to our final bundle

Fortunately, this is still significantly under the current Fusion production bundle size, and as we are still in the process of reaching functional parity with our existing AJAX/Fusion viewers, bundle optimization is not a priority at the moment. When that time comes, we can look at things like custom OpenLayers build profiles and moving to Webpack 2 for its tree shaking feature, which should make some in-roads in cutting down our production bundle size to more acceptable levels.
Categories: OSGeo Planet

gvSIG Team: gvSIG Batoví, article about GIS applied to educational environments based on gvSIG Desktop

OSGeo Planet - Mon, 2016-12-05 17:44

gvsig_uruguay_students300The online publication specializing in Geographical Information Technologies Directions Magazine has published an article highlighting gvSIG Batoví as an example of cooperative planning and creative partnership.

Read more:

http://www.directionsmag.com/entry/it-takes-a-village-intersections-between-geospatial-professionals-gove/482096


Filed under: english, gvSIG Desktop, gvSIG Educa Tagged: Education, gvSIG Batoví, uruguay
Categories: OSGeo Planet

gvSIG Team: Course about geographic scripting with gvSIG Desktop (documentation released)

OSGeo Planet - Mon, 2016-12-05 10:41

gvsig_scriptingLast week Andrea Antonello (HydroloGIS) shared a very interesting documentation related to a course about geographic scripting (python) with gvSIG Desktop. The course was done as part of a Master of the University of Potsdam.

The documentation includes:

  • The scripting composer and python
  • Geographic scripting
  • Raster Data
  • From Geo into your report

You can find the documentation linked in the original post:

http://jgrasstechtips.blogspot.com.es/2016/11/course-slides-geographic-scritping-in.html


Filed under: english, gvSIG Desktop, scripting, training Tagged: documentation, python
Categories: OSGeo Planet

Tom Kralidis: Software is Hard: Through the Years

OSGeo Planet - Mon, 2016-12-05 01:50
In 1999 I went to a GIS conference and watched a vendor presentation on their WMS product.  A key feature was being able to reproject data on the fly.  This appealed to me as this was early days of JavaScript development for me, along withe Mike Adair (which eventually, much later, led to the proj4js […]
Categories: OSGeo Planet

Paul Ramsey: NRPP, Still Doomed

OSGeo Planet - Sun, 2016-12-04 15:00

I have found it extremely difficult to extract information about NRPP from the government. FOIs have come with very large fee assessments, or documents have been completely redacted – you’d think I was out to get them or something.

NRPP, Still Doomed

New flash: I am not out to get them. In fact, they are the best-run IT mega-project I’ve seen so far in the BC government. But that doesn’t change the fact that, like the dinosaurs before them, they are doomed, dooooomed.

Fortunately, the FOI process can be indiscriminate, information can leak out despite the best efforts of the project team, and last month there was great tidbit about NRPP.

Hiding inside an FOI request to the Environmental Assessment Office (EAO) were a number of interesting documents.

Who’s On First?

In an email on June 24, 2016, Wilf Bangert, the Assistant Deputy Minister (ADM) for NRPP, invited the steering committee of ADMs to a meeting to:

define the meaning of ‘sector transformation’ by documenting a model that will enable its implementation.

Or put another way, after three years and $50M, the “Natural Resources Sector Transformation Secretariat” (NRSTS) still isn’t clear on what “transformation” means, and is looking for guidance.

It’s not too hard to figure out what’s going on.

Lacking any operational mandate themselves, NRSTS has been going around looking for partners with operational permitting processes: “come work with us, we’ll re-structure your business work-flow and make it ‘better’ with cool software we haven’t built yet”.

To me, this sounds good (cool software! better!); to NRSTS, this sounds good (re-structure!); to the permitters it sounds like “we’re going to waste a bunch of your (scarce) time in workshops making you talk about abstractions instead of doing your job, then we’re going to upend your office in the service of ‘transformation’, while we experiment with software that is as yet unwritten”.

You know what happened to the guy who had the first human heart transplant? In IT terms, the procedure was a success – he didn’t die on the table. He died 18 days later of pneumonia, with his heart still pumping away.

Back to High School

After asking for advice on ‘transformation’ from the ADMs, Bangert then tells them he needs a “subject matter expert” (at a “decision making level”!) from each of them to attend “several” workshops in the summer and a week-long workshop in the fall. So, presumably a manager or director, whose time is sufficently low value that it can be donated to NRSTS for days at a time.

Model UN

But that’s not even the best part. The best part is the structure of that five-day fall workshop. NRPP is going to be running (has already run?) a “Model UN” process with all these managers and directors.

My favourite bullet points! From the “How Will it Work” section:

  • An unlimited number of delegates are allowed per Ministry. Attendance and pre-work completion is mandatory before and for the duration of the workshop.

Because more is better, and mandatory homework makes fast friends! From “Who Should Attend”

  • Folks who are highly motivated to make the Natural Resources Sector “processes” work better.
  • Extroverted communicators and people connectors.
  • Introverted thought leaders and thinkers.
  • Creative problem solvers.

Great combination! Anyone not invited?

Still, so far we’re just talking about a standard “consultant-facilitated workshop time vortex”, of a sort we’ve all participated in and/or inflicted on others. The bit that is really transcendent is the “engagement model UN process”:

  • There is a general assembly component
  • Only voting delegates attend
  • Voting on resolutions prepared by committees
  • Decision making body for the process
  • Mandatory that voting delegate attends
  • Fixed time for debate and voting
  • A chairperson oversees
  • Process repeats [emphasis added] until all aspects of the work flow have been reviewed, resolution prepared, and voted on.

How could this possibly go wrong?!?

The Smell of Desperation

Once again, inputs:

Outputs:

  • “What exactly do you mean by ‘transformation’, really?”
  • “Lend us your SME’s for a week, so we can figure out a generic process to stuff your business into.”
  • Also, some unimpressive deliverables.

Desperation

If a core early problem with NRSTS was that nobody wanted to be the first organization to be subjected to their tender mercies, imagine how they are perceived now, as they come up on the end of their Phase 1 funding and still haven’t even figured out what “transformation” means?

Would you trust your staff time and business process to an organization that looks likely to be blown up in the next 24 months? If so, why?

Addendum: Commenters, please weigh in on whether the recent departure of the Executive Director, Technology to work with major project consultant CGI is (a) a sign of good things to come (CGI positioning to win follow-on work in Phase Two) or (b) a sign of imminent disaster (man-in-the-know getting out while the getting is good).

Categories: OSGeo Planet
Syndicate content