What is BizzJUMP?
BizzJUMP is an open source desktop GIS program written in the Java programming language. Being an open source program means that you have the freedom to modify and redistribute the program. Being written in the Java programming language means BizzJUMP is cross-platform and can run on different operating systems. (BizzJUMP will run on Linux or other operating systems in which the Java programming language is supported, not just on Microsoft Windows.) BizzJUMP is written in the Java programming language, which is powerful, productive and widely adopted. BizzJUMP is not designed as a web application, but to run on your desktop or laptop computer, like your word processor or digital music player. It is a “GIS program”, which means it is made to work with digital maps and other types of “geospatial data”.
Who maintains and develops BizzJUMP?
Landon Blake maintains BizzJUMP as a fork of JUMP as part of his work at Redefined Horizons. He works closely with the OpenJUMP community, sharing as much code between the two (2) programs as possible.
Why is BizzJUMP important?
BizzJUMP provides a viable alternative to expensive proprietary GIS software. This allows small businesses, non-profit organizations, and small government agencies to reap the benefits of GIS when they would not otherwise be able to afford it. Some features that make BizzJUMP and important member of the open source GIS software community include:
- It provides a simple design that makes it easy for programmers to learn.
- It is easy to add functionality to the program using modules known as “plug-ins”.
How is BizzJUMP different from OpenJUMP?
BizzJUMP is different from OpenJUMP in several important ways:
- All new features of the program will be added to BizzJUMP via plug-ins whenever possible. New features will not be added to the core, and plug-ins will not be “embedded” in the core unless it is absolutely necessary to do so. The plug-in system for BizzJUMP has already been modified to make it easier to add new features without tweaking core source code. This includes letting plug-ins take actions as part of the program start-up process (but after all plug-ins have initialized) or as part of the program shutdown process and in letting plug-ins register with the core so they can expose there public interfaces to one another during run time.
- Improvement of all contributions to the core must be accompanied by a comprehensive set of unit tests and good source code comments. External documentation of the source code is also encouraged. Comprehensive Javadoc comments are a must. This applies to all contributions.
- All contributions to the core must make use of the new system testing or integration testing framework that has been built into BizzJUMP, if this is appropriate. This is different from unit testing, but tests the interaction between components and sub-systems in BizzJUMP.
- Landon Blake must be able to understand the source code or modifications from other individual programmers or organizations want to contribute to the BizzJUMP core. This is critical, because if code goes into the core he must be able to maintain it for the long term. Code he can’t understand won’t be maintained, and code that won’t be maintained won’t be getting in. He will be asking contributors to tell him how they are using BizzJUMP and how long they plan on being involved with the project. He will strongly encourage contributions via plug-in and will strongly discourage modifications to the core.
- There will be regular releases of BizzJUMP. Every even month in the year there will be a maintenance release that contains mostly refactoring, reorganization, bug fixes, and improved documentation. Every odd month there will be a release that includes new features for programmers and/or users. Every six months there will be a stable release of BizzJUMP. Smaller minor unstable releases will be made during the month as appropriate.
- BizzJUMP's dependencies on external libraries will be kept to a minimum. When possible, dependencies created for the program will be as small and modular as possible. Utilizing and sharing code with libraries like GeoTools and Jodd will be strongly encouraged.
- Landon Blake will be striving for simplicity and clarity in BizzJUMP source code whenever possible. This means there won't be chaining of method calls, use of inner or anonymous classes, or other various things that can make Java source code hard for newbies to understand. Changes will be implemented in the simplest way possible.
A Brief History of BizzJUMP
BizzJUMP was created in the early winter of 2009 from a fork of JUMP Version 1.2 source code. It was created to address some of the problems Landon Blake identified in the OpenJUMP code base, and to allow for development that wouldn't be appropriate for OpenJUMP or accepted by the OpenJUMP community.
The Future of BizzJUMP
BizzJUMP currently has some limitations. It may not be the desktop GIS program for you or your organization. Some of these current limitations include:
- Very limited support for printing, especially high-quality and precise cartographic printing.
- Its ability to work with extremely large data sets is limited by your computers RAM, or memory.
- It lacks precision geometry creation (drawing) and geometry editing tools that you will find in the typical CAD environment.
Version Number and Release Schedule Information
A stable release of BizzJUMP will be made every six months. The first component of the BizzJUMP version number indicates the stable version number. For example: In the BizzJUMP version number 2.05.12 the stable version number is 2, indicating this is the second stable release of BizzJUMP.
A major unstable release of BizzJUMP will be made every month. Every even month is a maintenance release of BizzJUMP, in which I improve source code documentation, user documentation, or refactor/maintain the source code of the core. Every odd month is a new feature release in which some new user or programmer feature has been added to the BizzJUMP core. The second component of the BizzJUMP version number indicates the major unstable version. . For example: In the BizzJUMP version number 2.05.12 the major unstable version number is 5, indicating this is the fifth major unstable release of BizzJUMP for stable version 2.
A minor unstable release of BizzJUMP will be made whenever a logical chunk of programming is completed. This could be for either maintenance or adding new features to the program. Numbers rounded to the nearest whole 10 indicate a bug fix. The third component of the BizzJUMP version number indicates the major unstable version. For example: In the BizzJUMP version number 2.05.12 the minor unstable version number is 12. If the BizzJUMP version number where 2.05.20, it would indicate a bug fix.
Source Code, Distribution Download, and Javadoc
The latest distribution of BizzJUMP and of BizzJUMP plug-ins can always be downloaded from the files web page at the SurveyOS Project SourceForge site. You can view the source code for BizzJUMP in the SurveyOS Project SVN. The Javadoc for BizzJUMP can also be viewed online.