Redbex is made for observing the real world. However the objects, that exist out there, are basically limitless. It is obvious that no product can satisfy all the needs out of the box and foresee all possible observations you might need. But a product can build for it. So does Redbex.

Let’s say that your company is building a speedway through a big forest and environmental agency wants you to provide data, how the construction is influencing the wild life. In particular, there is a population of 20 bears, that are under protection. Your workers have successfully attached a GPS-collar to each of the endangered specimen. But how to record this data? Buy a bear watching software? Invent yet another one Excel sheet?

In fact all you will need is a new Redbex feature type. Each bear will become a feature, and it’s position at a certain period of type – an observation. Practically any other data can be added to feature and observation structures. Observed bears do have names after all, right?

We can create any feature type that will serve your most specific needs.

New feature types do not mean new installation

Feature types are distributed from our central server. Once your Redbex installation gets information about a new feature type, it will be immediately available. No new installation of server or client is needed. Client interfaces will automatically adapt to the data in the new feature type.

Limitless feature types are already there

Redbex already comes with big number of predefined feature types, which will suffice for most needs. For minor adaptations you can also create subtypes of already existing feature types. For example there is a feature type “numeric value”, which can record, no pun intended, a single numeric value as its observation. Now you need to record the number of trees cut during your construction works. Just create a subtype of “numeric value”, name it “Tree cutting progress”, provide a nice icon, rename the only property to “Number of cut trees” and you are ready to go.