Page Operations
Browse Space
Ideas for uDig Plugins
Shapefile to PostGIS converter
Create a wizard to open a shapefile and create a new postgis layer from it.
Key Map
Add a view showing the world in lat/long and a polygon (rectangle?) outlining the current map bounds. Moving the polygon causes the map to pan.
Easy Point Symbolization
Provide a simple way to turn a point layer into graphics (users currently have to hack at the SLD document).
Fixed zoom level SLD editor
Would be great if one could easily construct an SLD file for a webmap such as those displayed by openlayers or on top of Google Maps. They work with set zoom levels, so it'd be nice if the SLD editor prompted you at what zoom levels you wanted which rules to show up.
Export to GeoServer/MapServer
Add a button to export the current active layers to GeoServer or MapServer, writing all the configuration files to plug right in.
Export of a workspace
Workspaces should really be exportable as zip archive with all the referred data inside. Another person should be able to import it and see it exactly the same way I saw it.
Georeferencing raster and vectors
To georeference a raster image is one of the common tasks that a GIS user must accomplish working with spatial data. uDIG must give support to this functions.
I didn't intend to show any data in the key map – just the current viewport bounds. Why are we talking in this comment box? we have a wiki page to edit – don't worry about keeping the format above – just hack it into any form you like, perhaps with design pages forking off.
Posted by Why put the effort in building a shape to postgis converter when ogr provides these capabilities?
Sorry if this sounds offending, but I am new to uDig and a frequent user of qGIS that allready uses the GDAL/OGR libraries underneath. Is uDig somehow connected to GDAL/OGR?
Hi, here is an idea for a new plugin: A file manager (sort of a file explorer) in which it can recognize all the files in a PC that are used in udig (*.shp, *.png, etc) to make them more easy to find and manage.
Magna
Shapefile to PostGIS converter
That work should be part of a major rethinking of the catalog system. GIS is first and foremost about Information Systems, i.e. info management. We need to get the catalog system to the point that users can
we could go on along the same lines.
In thinking about this, I realize that I'm not yet sure how one uses the handle to the dataset (its url) to get each piece of the data set: the host, the schema, the location, the data. I'll have to work on that.
The catalog currently presents data in a tree widget. Probably we will want to rethink that in the future so users can get information about the host along with the host UI 'handle' (the drop target for operations, or the click handle for re-configuration). Similarly, users will want info on the data sets. Also, I imagine users really want all the shapefiles in the same directory to be visually bunched together in the catalog view.
So there's lots of work to do along those lines. I'm hoping to start soon. A first step will be a request to re-mix the feature system in uDig so each piece is better isolated but more on that elsewhere.
Key Map
Actually, I would not want any interactivity on this map. It's most useful to find lost data, for example if one layer is corrupted and is all at the origin or is off the map near neptune somehow. The widget would be most useful as an information system. I suspect trying to make it a naviagtion tool as well would only make things harder.
--adrian