Provides additional widgets for PureGWT
Improve the speed of Geomajas by caching results. Cached data is invalidated when needed.The cached data can be tiles, features, bounds, rasterized data (for the rasterizing plug-in).
Automatically invalidates data when needed.
This plug-in contains new widgets for the GWT face that provide a more advanced view of the map. On one hand there is the LegendTree widget, which is a combination of the original LayerTree and Legend, on the other hand there is a widget that adds support for thematic views.
Legend tree widget: This widget combines the current layertree and legend widgets into a single widget. It has some other differences with the current layertree: - Visible/invisible controllers on the tree icons (on folders and single layers) - Support for transparency - Layer tree tools can be attached as buttons on top (like the layertree) but also using a right mouse button context menu.
Thematic views: This functionality would allow the definition (configuration) of pre defined themes, a theme being a combination of a bunch of layers with specific transparencies. For this you must think of an application with lots of layers (10~20).
This plug-in provides extra utility widgets for the Geomajas GWT faces (both SmartGWT and pure GWT). These widgets are not necessarily GIS related. Examples are a Ribbon (office like toolbar), a Wizard, a file upload widget, etc.For the SmartGWT face, this plug-in provides extensions for the default themes (as GWT modules), so that the widgets automatically fit in your applications.
This plugin provides several widgets for advanced querying and filtering, also supporting geographical queries for the GWT face. Where possible the widgets use the default Geomajas communication API, where necessary specific commands have been added. Basically 2 widgets will form the main topic:
Spatial search widget: A spatial search that searches for features based on free drawing, geolocation or current selection. Also a buffer option is included:
Accesses the Geomajas system using REST and GeoJSON.
Widgets for the GWT face that provide more details on feature attributes.
The plugin contains following components:
Feature list table: A multilayer feature list table, that allows search results from different layers to be displayed in a single popup. The multilayer flt has an option to automatically zoom to selected features.
Identification and feature info: Mouse over feature info (show the feature label when you move over it with the mouse)
This plugin also features a list of widgets for displaying Feature Attribute information
This plug-in adds a TMS (Tile Map Service) raster layer to Geomajas. WMS is an open standard developed by OSGeo for providing georeferenced raster layers.
Similar to the other Geomajas layer plug-ins, the TMS layer provides access to external data sources. In other words, this plug-in will not create a TMS server out of your Geomajas application, but if you whish to include your own raster images, set up a TMS server, and use this plug-in to read from it.
Plugin that adds security based upon Spring configuration. Allows for fine-grained tuning of authorisation on layer-level, feature-level and even attribute-level.
This plug-in adds support for OpenStreetMaps (OSM) raster layers. OpenStreetMap is a free and editable map, made by people like you. With OpenStreetMap you can view geographical data from the whole world.
At the moment this plug-in only reads in the OSM raster data. It does not read or edit the OSM vector data. Since the OSM licencing model is far less strict than Google's, this layer can be a perfect alternative for the Google street maps.
This plug-in adds support for incorporating Google Map raster layers. The 3 types of Google raster layers are all available:
More information on how to use these can be found in the documentation pages.
This plug-in adds a WMS (Web Map Service) raster layer to Geomajas. WMS is an open standard from the Open Geospatial Consortium (OGC) for providing georeferenced raster layers. If you whish to include your own raster images as a background layer, set up a WMS server, and use this plug-in to read from it.
Note that, like all the other layers, this is meant as a source of data. This means that this plug-in will not create a WMS server out of your Geomajas application.
This plug-in provides a vector layer implementation that makes use of Hibernate Spatial, which is a GIS extension of the Hibernate Object Relational Mapping (ORM) technology.
This plug-in is essential in streamlining Geomajas with the familiar domain modelling practices of mainstream Java programmers. Using this layer, it is possible to define complex attribute relations, including many-to-one and one-to-many associations.
As with all technologies, in Hibernate you declare Java POJO objects and map them to the underlying database. These mappings can be defined with annotations (java 1.5).
When using this module to define a new layer, simply use the java class of the POJO objects in the XML configuration. Names of the attributes in XML are automatically translated to getters and setters in the java objects. What's more, if a java object contains many-to-one's or one-to-many relationschips (and therefore lists of other mapped java objects), one can simply define these as "associations" in the XML layer configurations, and this module will do the rest.
This plug-in introduces a vector layer based on the GeoTools DataStore. What this means, is that any type of datastore supported by GeoTools, can be accessed using this layer.
Geotools is an open source (LGPL) Java code library which provides standards compliant methods for the manipulation of geospatial data, for example to implement Geographic Information Systems (GIS). The GeoTools library implements Open Geospatial Consortium (OGC) specifications as they are developed, in close collaboration with the GeoAPI project.
Currently GeoTools 2.7.4 is used, through which Geomajas supports for the following formats:
Note that only vectorial formats are supported through the geotools layer model!
GeoTools is a well known Java library which is at the heart of many open source GIS packages (e.g. Geoserver). While GeoTools has done an excellent job in creating a generic datastore interface, we think there are some advantages in using a Hibernate Spatial model when complex domain modelling is involved. On the other hand, GeoTools currently offers support for data services like WFS or ArcSDE and complex feature modelling seems to be on their roadmap.
One thing to be aware of when using GeoTools is the fact that its features have to implement a common Feature interface, which means that general POJO objects are not allowed. This means that, unlike with the Hibernate model, one cannot use domain objects that were made in a different context. Geomajas transparently handles both types of features (GeoTools and Hbernate Spatial) by delegating feature access to a specific implementation of the FeatureModel interface for each case.
This plug-in provides a geenric command and GWT widget for finding map locations based on a free string. You can configure how exactly this conversion is done, using either your own data or some external service like Yahoo! PlaceFinder.
This plug-in adds a simple to use printing functionality to the Geomajas GWT face. On the server it makes use of the iT3xt library for creating PDF files. On the client, it provides widgets for presenting print options, such as format (A1 - A4), DPI and much more.
This plugin is an external plugin. This means that it's source code is maintained outside of the Geomajas repository, and therefore not supported by the Geomajas community. The KML plugin is a proof of concept which creates an overlay on a Geomajas map.
This is the recommended face for the Geomajas technology, for versions 1.6.0 and higher.The GWT face allows you to use Java code for development of your AJAX based GIS web applications. It uses Google Web Toolkit and the SmartGWT widget library to have powerful widgets which look nice.
For the developer, there is the ability to run your applications in development mode. Though this is slower than production mode, it does remove the need for the full compilation before application startup (a big improvement as GWT produces different code per browser and language pair), and what's more, it allows debugging your application in Java.