This is most likely the reason you are interested in the GeoTools library - this module finally lets you draw a map using all that data you set up. 01 StreamingRenderer 04 Styling 05 Style 06 Style Layer Descriptor Document 07 Symbolizers 08 StyleVisitor use with DuplicatingStyleVisitor and RescaleStyleVisitor 10 SLD Utility Class Style Examples GeoTools rendering is based around the Style Layer Descriptor standard, for details please see the API module. We are working with GeoAPI in order to support the latest SLD 1.1 specification, but right now we are only using SLD 1.0. Congratulations! You made it to the end of the GeoTools library. There is a little more - plugins exist to supplement this core library with different formats, coordinate reference system authorities and so on. Extensions exist that build additional ideas and services on top of this base.

You are here << >>

MapContext

This module actually defines a new data structure - MapContext. A MapContext is made up of a series of MapLayers which are drawn in order.

This is not part of the formal GeoTools API module because it is not considered finished, done, or complete. The GeoTools community is actively looking to collaborate with other projects (such as OpenJUMP, uDig and DeeGree) in order to collaborate on these ideas. If open source collaboration fails we will look to traditional collaboration with a standards body in the form of the the OGC working group on "Open Web Context" documents.

What about the Widget?

This module only draws into a Graphics2D context (so printer or image buffer). You can use this functionality in your own Swing widget in order to draw something on screen.

The GeoTools user community is really interested in doing this, but right now we do not have sufficient volunteers signed up on the dotted line to make this a reality for you.

Here are some options:

• in development : module widgets-swing-pending provide a growing set of swing widgets. still there is not much feedback on those and the structure is not definitive, so if you are searching for something supported in the futur, dont use it.
• unsupported/mappane module has defined a sample JMapPane - please use this as a starting point only, and be kind to the volunteer. This could be folded into the library, but only if enough people are helpful with bug reports, patches and documentation.
• http://net.refractions.udig This is an application and SDK built around the Eclipse platform, please consider this a real world solution suitable for desktop applications. It makes use of the SWT toolkit so while you can use it as an example of how to do really fast rendering you will not be able to directly use the code in a swing application.
• http://puzzle-gis.codehaus.org This is a second application and SDK build around NetBeans platform. At the contrary of Udig, this solution is based only on SWING widgets and is not ready for real world. This application uses all the swing widgets of geotools and some mores. If you are a swing developer, we suggest to use udig until puzzle is ready.
• Google Summer of Code students are working on 3D rendering pipelines