I Need Advice on Best Practices for Implementing Open Source GIS in Local Government Projects

Hello there,

I am working on a project aimed at implementing GIS solutions for a local government agency; and I am looking for advice and best practices from those who have experience in this area. The agency is relatively new to GIS and is keen on utilizing open-source tools to manage spatial data; improve decision making; and enhance public services.

With so many open-source GIS options available; I am wondering which tools would be most effective for a local government context. What combinations of software have you found most efficient for tasks such as land management; urban planning; and public infrastructure management?

The agency already uses several proprietary systems for data management and public service delivery. What challenges have you encountered when integrating open-source GIS with existing systems, and how did you overcome them?

Since the agencys staff is new to GIS; I would appreciate any advice on training programs or resources that have been successful in building GIS capacity within local government teams.

Also, I have gone through this post; https://discourse.osgeo.org/t/how-would-you-like-to-add-new-categories-for-projects-or-committees-power-bi/ which definitely helped me out a lot.

What are the best practices for managing and sharing spatial data in a local government setting, especially when dealing with sensitive information or working with multiple departments?

Thank you in advance for your help and assistance.

I have no idea how going through that post (on setting up discourse categories helps) other than provide an example of how we make it up as we go along :slight_smile:

One thing that can help is list of foss4g projects (which gather useful information). And the choose-a-project guide which helps you explore what is available on different topics.

It can be quite an art evaluating technology at the best of time … and foss4g software can be more intimidating for two reasons:

a) There is no sales person to help you.
b) There is so much transparency (you can see how the sausages are made).

Some things to keep in mind:

  • This is a different procurement model then purchasing proprietary systems. You have more purchasing power, but you left with more responsibility. I made a presentation this topic. The take home is to choose the appropriate technology (the responsibility), and have several service providers to work with (the negotiation power).
  • The transparency foss4g projects lets you answer health and happiness questions that you can only speculate about with a proprietary system. Example: Check out the oldest bug in the issue tracker; see if you can determine why it has not been fixed.
  • You should be able to tell what organizations take part in the technology (bluntly where the money comes from). Go through similar risk assessment as if you were considering a partnership with these organizations.
  • Consider your options for a local service provider. Ideally they could help you run a pilot, although many will focus on specific technologies they have been successful with. I can also recommend my employer
  • Connect with a local chapter in your area. These range for big groups putting on events, to small gatherings at the pub.
  • If you possibly can send some of your staff at different skill levels to a regional foss4g conference. These events offer some of the only hands-on training, and even better connections with folks on the same journey.

Tip: Do not consider this as moving your agency towards open source - but as your agency moving towards standards. Standards promote a market, which gives you a selection of great free and open source components to choose from.

Finally: foss4g technology is not without cost - it takes your time. There is a lovely presentation on Earning you Support instead of Buying it (video).

I am going to stop now …