While most software vendors require training, certification, and a fee, our approach is a bit different. We require any organization wanting to be a value added reseller (VAR) and provide first-tier support to stand up a custom instance of the OpenGeo Suite. This not only proves that the organization is adept at using our software and able to help others but also provides the concrete value of a demonstration that shows what is possible.
Background
Part of the OpenGeo Suite approach is to build web applications that speak to a particular domain. Building accessible user interfaces that leverage the power of GIS is a preferable alternative to buying complicated desktop GIS packages and the training needed to perform the same five operations over and over again. Our potential partners can best demonstrate that message to their clients by building a compelling web application that speaks to a particular problem common to your clients and potential clients and illustrates how the OpenGeo Suite can address their challenges. It should be a showcase of how the Suite is a flexible solution that has real relevance to them.
We realize this can take a decent amount of time but see it as a preferable alternative to expecting an upfront fee of thousands of dollars and requiring certification tests to become a partner. A demo not only helps us evaluate how well you will be able to support OpenGeo Suite clients but also provides both of us with a concrete example of our capabilities.
The Task
Potential VAR partners must take the OpenGeo Suite and build a territory specific application. This requires building a demo that highlights the particular geographic region and/or domain of the potential partner that utilizes some unique data sets that are not commonly seen in demos and interacting with them in specific ways. Some examples include a widget that does a parcel search against a cadastral layer or a site that lets users browse biological classification by taxonomy. Most potential clients who are not GIS experts will much more easily understand the power of the OpenGeo Suite when presented with something they know about.
The demo should use the entire stack of OpenGeo software—PostGIS, GeoServer, GeoWebCache, OpenLayers and GeoExt— as anyone providing support on the OpenGeo Suite should be adept with all components. Each should be optimized for production: tuned, cached, minified and configured for performance.
The demo must be on a public site that we can link to from our Partner page and Demo page and needs to be available 99% of the time. Those who cannot keep their service running risk losing their VAR status.
Evaluation
After the demo is complete it should be submitted to OpenGeo for evaluation against a number of criteria, including:
- Performance: The demo should be a responsive application, quick to load the JavaScript and the map tiles behind it. We recommend caching static layers (with GeoWebCache) and optimizing SLD's to quickly load dynamic layers.
- Stability: It must be able to handle a significant load. We will run The Grinder or similar tests to make sure that the server stays up.
- Cartography: Maps must look good with nice details and colors. They may use other tile sets as base layers but overlays should look good on them. Rendering custom base layers with GeoServer is always appreciated.
- Interactivity: Users should be able to do something more than just browse—it should be more than just a static online map.
- Uniqueness: It must be specific to a domain and/or area and should speak to a particular client or solve a problem that your clients often experience. Examples include searching/browsing particular kinds of layers, performing common tasks faced in the domain, making analysis easy for anyone to do, etc.
- Extras: While not required, we are excited to see demos that incorporate real-time data, editing, nice KML produced by GeoServer, time visualizations, or anything that enhances core software or provides new capabilities.