getLegendGraphic becomes getLayerLegend under the nomenclature of method names
This looks like work we should build on for some of our MoSeS portlets.
Abstract specifications from Orchestra are conformant with OGC and ISO.
SLD Extensions
Charts on maps
Orchestra adding SVG support so that any symbol can be added to a map not just a basic symbol with a well known name.
Chloropleth maps
Orchestra adding SVG support so that any type of graphic pattern can be used not just line type patterns.
Bounding Box (BB) input for symbolisation to give regional control for symbolisation.
Not sure why BB and not a geometry in general, maybe that is a further extension to consider or can be achieved with operations prior to SLD parsing.
SOAP messages are more practical than http get due to size of GML
Main implimentation integrated with Quantum GIS (QGIS)
Label placement algorithms in SLD and further advancements being considered
Is there a need for a Portrayal Working Group (that can align with an ISO Portrayal Working Group known to exist) or can these extensions be considered for inclusion in specification by existing Working Groups?
Gerald Creager (Gerry) encryption of data and MoSeS data problems. Gerry might have some solution for MoSeS to use compute on any grid irrespective of confidentiality and data confidentiality concerns.
Talked with Craig Lee who is involved in OGF and plans to suggest to Geoffrey Fox to invite Microsoft to present its Virtual Earth at OGF21
Detailed program of OGF21 not yet available online.
WMS WG
Tiling WMS
WSDL SOAP XSD and SLD
Discussion on getFeatureInfo: Do we need a simple XML schema?
ESRC Research Resources Board may be interested in funding something on geoservices.
Described a Cartogram Use Case:
Cartograms are useful for displaying aggregate region socio-economic data where one variable should be shown proportionally to another and where this has little (or even negative) correlation with the size (usually area) of regions.
Algorthims for constructing cartograms often result in representations that are usually more distorted at the edge of a set of regions in terms of distance and contiguity (although this depends on the algorithm and constraints used).
For any selection of regions (for example a set of UK 2001 Human Population Census Output Areas intersecting a specific health authority area), there are several cartograms that can be generated.
Consider circular style representations then one can base the circle areas on numerous different census variables.
There are other non-circular style representations (e.g. space filling cartograms more continuous in coverage), and volume based surface drape style representations.
For each style of representation the proportions of the geometry can be achieved using different shape and contiguity constraints that grow or distort the spatial region representation iteratively by different amounts each iteration.
A set of different cartograms representing data from different (contiguous) regions can be aggregated together into a single graphic.
This can be useful as it takes some time to learn what the different parts of the cartogram are in respect of the spatial area represented.
There are more cartogram style representations than one would want to pregenerate and store and have readily available for a user of a particular dataset.
Moreover a user might want to play around until a set of cartogram fit for purpose is produced for a specific set of regions and variables.
This demands functionality to generate cartograms on the fly via a user friendly interface.
Some cache or registry of pregenerated cartograms can be kept.
Grid technology can be used on the back end to speed up and facilitate cartogram generation, archiving and reuse.
Cartograms (and general geospatial visualisation and analysis tools) were things I was trying to get James Reid to consider as part of an NCeSS Node bid... I don't know what in the end was submitted but am very keen to work on this.
Martin suggested some tests to compare the performance of different Grids data structures and JAI itself for convolve operations for generating the same results.
![[Validate CSS]](http://www.geog.leeds.ac.uk/people/a.turner/images/vcss.gif "W3C CSS Validation")
![[An image of Andy Turner]](http://www.geog.leeds.ac.uk/people/a.turner/a.turner.png)