Community

GISPulse is built in the open. Whether you are a GIS analyst, a data engineer, or a spatial developer, there are many ways to get involved.

GitHub

The source code, issues, and discussions all live on GitHub:

• Repository: github.com/imagodata/gispulse
• Stars and forks are appreciated — they help others discover the project.

Discussions

Have a question, an idea, or want to share how you use GISPulse?

• GitHub Discussions is the place for open conversations.
• Categories: Q&A, Ideas, Show and Tell, General.
• Please search existing discussions before creating a new one.

Issues

Found a bug or want to request a feature?

• Open an issue with a clear description.
• For bugs: include your GISPulse version, Python version, OS, and steps to reproduce.
• For features: describe the use case and why existing capabilities do not cover it.

Contributing

We welcome contributions of all kinds: code, documentation, bug reports, and ideas.

• Read the Contributing Guide to get started.
• First-time contributors: look for issues labeled good first issue.
• All contributions go through pull requests with code review.

Blog

Technical articles, release announcements, and deep dives into spatial processing:

• GISPulse Blog
• Topics: rules-as-config patterns, engine benchmarks, use case walkthroughs, migration guides.

Contact

• General inquiries: contact@gispulse.dev
• Sales & Enterprise: sales@gispulse.dev
• Security issues: security@gispulse.dev (please do not open public issues for security vulnerabilities)

Roadmap

GISPulse follows a public roadmap driven by community feedback and production needs:

• Short term — Stability, test coverage, documentation
• Medium term — Additional capabilities (validation, topology), template marketplace, improved portal UX
• Long term — Horizontal scaling, cloud-native deployment, STAC integration, advanced raster processing

The roadmap is shaped by real user needs. Share your priorities to influence what comes next.

Sponsors

GISPulse is an independent open-source project. If your organization benefits from GISPulse, consider supporting its development:

• Pro/Team/Enterprise subscriptions directly fund development
• Sponsorship opportunities — contact contact@gispulse.dev
• In-kind contributions — testing, documentation, translations, and advocacy all help

Every contribution, large or small, helps keep GISPulse independent and sustainable.