Diana - roadmap

Projections

Diana are now using proj4 to handle projection, but there are some issues left:

Remove all reference to the old projection-library milib

There are still some problems when plotting spherical earth data on a map with spheroidal reference surface

Field interface

Use The fimex library to read field data

Read Felt-format, NetCDF (including ncml), Grib(1&2), and [[https://wdb.wiki.met.no|Wdb]

FieldFunctions will use standard_names (cf)

Definitions will be moved from the setupfile to gui

reference time

plot type (contour, wind arrows, values etc)

All fields from a data source should be available as 1-dimensional plots without any setupfile definitions

Plot definitions in the setupfile will be used to define: plotname, default options, multi-dimensional plots etc

Web Map Services

producing WMS-layers

bdiana can produce maps for WMS servers, but this functionality needs improvment

displaying WMS-layers

Diana should be able to display maps from WMS-servers

Vertical cross-sections

New option: Min/max value

Find min/max value in the current cross-section

Mark the min/max positions at the plot

Write max value and position below the plot

Write min value and position below the plot

QuickMenu

Include Vertical cross-section plots in QuickMenus

Polygons, points etc

Data from shape, ascii, qsocket

Time dependent/independent

Datatypes

polygons(coordinates, text, colour etc)

points (coordinates, text, url, colour, marker etc)

Texts available on the map or in separate textbox

Editable

Priority levels, just plot the most important info (?)

Raster images

Use the field interface

Select channel mixing in the gui

Observations

Read observations from url

More general plotting, all parameters available

Move parameter definitions to the setupfile

Possible to mix data from different sources (metadata + data)

misc

All information available from ascii files should also be available from http

setupfile, ascii-obs, maps, product definitions

Qt - The Graphics View Framework

Should diana use Qt's Graphics View Framework?

Use Qt's Graphics View Framework when editing maps (draw polygons, points, etc)?

Use Qt's Graphics View Framework for all plotting?

Questions:

Is it fast enough?

Can the Graphics View plot all layers available i diana today?

What about bdiana?

Advantages

Advanced polygon drawing

Possible to write directly on map

Advanced GraphicsItem handeling

Might solve PostScrips issues?

Might solve bdiana X-display issues?