User-friendly Desktop Internet GIS

This week in uDig - January Week 1

2012-01-07T19:00:00.000-08:00

I may as well take a turn writing one of these posts - Happy New Year from the uDig Team!

This week has a bit of catch up; as several github "pull requests" have been submitted over the break.

1.3.1
We have issued a small uDig 1.3.1 patch release just prior to the holidays. The release notes are up; but it amounts to a couple fixes reported on the user list (zoom out and copying features into the feature table).

Thanks to those who took part in testing over December!

SDK
The bulk of my week was devoted to the construction of a SDK bundle. Panagiotis from udig-devel supplied a patch changing the manner in which "source features" are generated to follow the Eclipse 3.2 standard.

Each feature is responsible for packaging a number of plugins for deployment; the generated source feature is now a single jar (with internal folder structure matching the listed plugins.

The SDK is now available from the uDig download page. Maurcio and Panagiotis report success (although I am not sure if they have updated the SDK instructions).

Native Code Fragments
Frank Gasdorf has been a whirlwind of productive (and indeed hard to keep up with). Frank has been exploring the the use of fragments to package the native code we use in the uDig project. We have several categories of native code; extensions for Java (such as Java Advanced Imaging, ImageIO and ImageIO-Ext); GDAL (for ImageIO-EXT to use); and that native Eclipse code (such as Standard Widget Toolkit).

The native Eclipse code is packaged into platform specific 'fragments' which are wired up when the application launches - accounting for both the java class path and the corresponding native library path.

uDig has been dependent on a combination of a custom JRE (where we place the Java extensions into the ext/lib folder; and their native code into the bin folder) and the "udig.sh" or "udig.bat" script (so we can set the GDAL environmental variables correctly).

When Frank has successfully packaged the native code as fragments we will switch over to using JAI, ImageIO and ImageIO-EXT as jars and no longer be dependent on their presence as java extensions. We trust this will result in a smaller download; and better integration options with projects such as the OSGeo Live DVD.

Eclipse Modelling Framework Code Generation
One of the most impressive changes this week was the work Paul Pfeiffer put into the core Map, Layer and Viewport classes. These classes make use of the Eclipse Modelling Framework; allowing developers to update the model and generate out the changes to the code.

Paul has update the java interfaces ( a couple new zoom methods) and hit the magic code generation button. The net result of this is a simplification to to some of our classes (EMF now provides base classes with many of the boilerplate methods) and an update to use Java Collections with generics.

A new feature of EMF is the inclusion of a UML editor to visually review your model. Here is an example of the rendering system displayed with this tool.

Render Manager

I have copied several of these diagrams into the developers guide. Paul's work will continue next week as we are going to clean up some of the method names in ILayer.

uDig 1.3.0 Released

2011-12-08T02:24:00.000-08:00

The uDig Community is pleased to announce the release of uDig 1.3.0.

This release is made in conjunction with GeoTools 8.0-M4.Thanks to Andrea Amie and Gabriel Roldan for support, encouragement and timely bug fixes.

This point release includes significant usability improvements and new functionality - thanks to thehard work of Levi Putna and Paul Pfeiffer.

For more information on User-friendly Desktop Internet GIS please check out the uDig Overview.

Release Details

Download the package appropriate to your platform, unzip and run:

uDig download page (with archives for Windows, Mac and Linux)
udig-1.3.0 Release Notes
Issue Tracker Change Log

About uDig 1.3

This release features some great usability improvements with a new tool palette and easy to access tool options.

Here are some new features you can look forward to:

Area of Interest support - define your area of interest based on CRS, current screen or a bookmark
Filter the Table view using the current area of interest - a great way to focus on what is on screen
Updated Info and Profile tool for raster data
Teradata support
Spatial Toolbox view allowing access to OMS3 processing; with tutorial!
New import and export formats: CSV and KML.
Check out What is new page for details

Usability Improvements

New Tool Palette with easy to use Tool Options for quick access to preferences (blog)
New "cheatsheet" help system offering guide assistance to new users (blog)
Control Tool interaction with your layers with the ability to mark background layers

Additional documentation:

Updated Walkthrough 1 and Walkthrough 2 for the new Tool Palette and Tool Options
Extensive update to online help including uDig Overview
New step by step Introduction to Spatial Toolbox
Reorganisation of the Tasks section with step by step instructions for using new features

For developers:

Access to the latest GeoTools 8.0-M4 release
Access to the latest JTS 1.12
Access to the latest ImageIO-EXT 1.1.2
Fork me on github
Works with Eclipse 3.7

Adding CheatSheets Interactive Help to uDig

2011-10-04T07:18:00.000-07:00

I have been putting together the release notes for the upcoming uDig 1.2.3 and ran into a really great usability feature that we have not mentioned on our blog feed yet.

The next release of uDig includes the concept of "Cheatsheets"; these act in a manner similar to a wizard (in that the provide a series of steps); but instead are designed to supliment the running application. What is impressive is the "Click to Perform" button which will perform the task it is describing so it can show you the result.

The Quickstart cheatsheet included in uDig 1.2.3 uses this to great effect when showing the differences between the normal Map Perspective (used for working on data) and the Style Perspective (used for working on presentation).

What is even more impressive is this form of help follows you into dialogs and screens offering helpful advice as it shows you how to perform an activity.

The traditional uDig online documentation is of course still available.

This week in udig - Sep - Week 4

2011-10-04T01:55:00.000-07:00

Levi Putna is making progress inthe development of Smart Buffer tool, the following demo shows how it works.

Levi has done a great work with Map Status Bar Tool Options. It can now take a preference page id that will be opened when the tool icon is clicked in the status bar option contribution.

Emily have resolved the following bugs (thanks a lot!):

Jesse, Jody and Mauricio have done the codereview of the issues described above.

Tool Palette and Options

2011-10-03T00:06:00.000-07:00

Tools have gotten a major usability improvement featuring:

ToolPalette - used to quickly explore available tools, configure tool display to show labels, descriptions or large icons for a helpful hand when learning.By default the Palette is displayed along side your Map; you can also Choose Show View > Other and Open the Palette on its own as a tear off View. This is great for users with more than one monitor or when you have multiple maps open side by side. This is the same Palette used during Page printing.
ToolOptions - quick access to common tool preferences from the Map Status Line. This has allowed us to reduce the number of tools while maintaining the same functionality.

These change combine to make uDig even more User-friendly with a presentation of tools similar to a paint program. As an example edit tools can use the area to make options such as "snapping" visible (previously available as a keyboard shortcut!). It is also an efficient use of screen real estate as snapping options do not waste space when they are not needed.

Palette

Here are a couple examples how how the palette looks using the Large Icons preference.

Extension

uDig practices an open development model with a couple Request for Change proposals being closed today.

As part of that the following pages have been updated in the user guide:

Map Editor

For more information about what is new in the uDig 1.2 series see the user guide.

And developer documentation for the new tool option functionality:

Tools

The good bit is covered here:

public class OptionContribtionItem extends ToolOptionContributionItem {
     public IPreferenceStore fillFields( Composite parent ) {
            Button check = new Button(parent,  SWT.CHECK );
            check.setText("Scale");
            addField( NavigationToolPreferencePage.SCALE, check );
         
            Button tiled = new Button(parent,  SWT.CHECK );
            tiled.setText("Tiled");
            addField( NavigationToolPreferencePage.TILED, tiled );
            
            return ToolsPlugin.getDefault().getPreferenceStore();
        }
    };

uDig Source Code Visualisation

2011-09-27T03:09:00.000-07:00

Continuing on to uDig for a great gource visualisation showing the impact of a couple of code sprints in 2010; and a new development team starting up in 2011.

Here is the link: http://www.youtube.com/watch?v=cqxXJ7bOBTg and the video itself is shown below.

Aside: This is a much better visualisation as I have been learning to gource control options (so the video tracks activity for a better view of what is going on).

By popular request (on IRC) here are the command line options used for code.google.com/p/gource project.

I started by using "camera-mode" track to make the action focused; I also really lowered the number of seconds used to represent each day so that we could quickly cover two years of development.

gource -title uDig -1280x720 --camera-mode track --auto-skip-seconds 1 --seconds-per-day 0.05 -o udig.ppm

And then I stitched the result into a movie using ffmpeg:

 ffmpeg -y -b 10000K -r 60 -f image2pipe -vcodec ppm -i udig.ppm -vcodec libx264 -vpre slow -threads 0 -bf 0 udig.x264.mp4

THIS WEEK IN UDIG - SEP - WEEK 3

2011-09-21T04:10:00.000-07:00

Jody has done a geat difusion task in FOSS4G2011 Denver. He leaded the uDig code sprint. It looks like the people have had a good time as is shown in the event's snapshots.

Emily Gouge has been working to fix up some bugs in the uDig paltform.

Mauricio has begun the development of uDig Weather.

THIS WEEK IN UDIG - SEP - WEEK 2

2011-09-11T23:47:00.000-07:00

The community is working to improve the user experience in uDig.

- Levi Putna and Jody Garnett are presented the Map Status Bar Tool Options idea, that will allow a better access to the different tool options.

- uDig will have a new useful tools Smart Buffer, it have been proposed by Levi Putna.

- Jesse and Andrea have provided feedback and good advices to carry out those ideas.

- Jody was cleaning the java 5 compliance from uDig platform code to allow to
use the override annotation with the java 6 semantic (to override interface
signatures).

- Mauricio is advancing in the udig Weather vision. He was analyzing the GUI requirements for the weather desktop.

THIS WEEK IN UDIG - SEP - WEEK 1

2011-09-05T02:08:00.000-07:00

- The University of Trento has ufficialized the next
courses about hydrology, geomorphology, water supply systems and stormwaters, based on uDig and engineering tools developed by HydroloGIS. More info.

- Jesse and Andrea have done the code review of GEF Palette.

- Jody and Scott have improved and updated the "Getting Started". The following pages were updated:

SDK Quickstart
Plugin Tutorial
Custom Application Tutorial
Workbench Tutorial

- John Hudson have update the worktrough 1. The new tool palette is shown in the screenshots.

- Mauricio have tested the udig internal snapshot with the community update site (1.2).

THIS WEEK IN UDIG - AUGUST - WEEK 3

2011-08-22T02:04:00.001-07:00

Our weekly summary:

- Andrea Antonello has nominate Levi for commit access. He has helped review the palette change request.

- Mauricio was checking the status of part of puzzle required for uDig Weather: gt-greb1, gt-netcdf, jgrass plugins. He was done a quickly review of what the meteorolgy communiy has written about standards.

- The LisaSoft team, John Hudson, Scott Henderson and Jody Garnett , has made the integration of the new GEF Palette tool . The following video shows the new look and feel of uDig.It is a great contribution for uDig project, thanks LisaSoft.

THIS WEEK IN UDIG - AUGUST - WEEK 2

2011-08-15T02:21:00.000-07:00

- Kenneth Gulbrandsoy has proposed to migrate uDig project persistance to Common Data Object (CDO). He has evaluated the efforts required and has finished the initial design. The PSC has approved the CDO proposal.

- Andrea has been working in some enhancements in Single band raster styling.

- Jody was improving the icons presentation.

- Jesse and Jody have reviewed the GEF Tool Palette proposed by Levi and Scott. The proposal was approved by the PSC.

- Mauricio has been analyzing the data structures used in the weather domain to share data. A draft of Data Weather Analysis and Forecast document was done. Moreover, he was reading the work done by Andrea Antonelo in the project Netcdf in JGrass.

This week in uDig - August - Week 1

2011-08-06T01:59:00.000-07:00

This week we want to highlight the following activities.

- Jody. He has made a progress in looking how to convert our wiki (which is in textile) into actual source code (now that eclipse supports textile). This would allow us to keep our developers guide github (but would require developer to use the help menu; or someone to run a helpviewer on a webserver).

- Levi. The concept proof of cheet sheet idea is in the main branch of udig-platform. He has committed some cheet sheet examples.

- Jesse has been replying to community questions. He is working in the teradata update site for the latest teradata plugin.

- Andrea is finishing the Java Open Source GIS Development course for the Potsdam University. He was teaching about uDig, Geotools and jGrass Tools.

- Mauricio has updated the Developer Tutorials. He began the inception for uDig Weather.

- The PSC has reviewed the cheat sheet merge request.

This week in uDig

2011-07-30T00:30:00.000-07:00

This post is a summary of what the uDig community has done this week.

- Jody Garnett is currently working on the GeoTools gt-process code. This should allow uDig to make use of some great new operations such as cookie-cutter that are being brought over from the GeoServer project.

- Jody has released an uDig 1.2.2 SDK; users are invited to test.

- Frank Gasdorf has been updating the OSGeo Live DVD content to ensure the latest version of uDig is well represented.

- Andrea Antonello is preparing a training for the university of Potsdam. He will teach how to write models and use them in the uDig Spatial Toolbox. He will afterwards release them
as official docs for geotools/uDig.

- Putna Levi has drafted up the idea of adding cheat sheets to uDig. New users will benefit greatly from there introduction and it will help streamline the initial learning process.

- Mauricio Pazos has improved the CQL parser including the Relate Geooperation which allows to evaluate a pair of geometry taking in to account the intersection matrix (DE-9IM).

- We have formally switched over to Eclipse 3.7; and are looking forward to working with the new GUI designer.

uDig 1.2.2 Released

2011-07-13T03:57:00.001-07:00

The uDig Community is overjoyed to announce the release of uDig 1.2.2.

This release is made in conjunction with GeoTools 8.0-M1and the OSGeoLive DVD projects. We would like to thank these communitiesfor their support. In particular a kind word goes out to Andrea Amie and Micheal Bedward and Daniele Romagnoli for a smooth GeoTools releasein support of our schedule. Aslo a tip of the hat to Frank Gasforf and Cameron Shorter and the OSGeo Live project for setting the schedule(in conjunction with FOSS4G)

We would also like to thank Levi Punta and Nathaniel Keslo for sorting out a patch allowing uDig to use Natural Earth dataset out of the box.

Release Details

Download the package appropriate to your platform, unzip and run:

The uDig download page contains archives for Windows, Mac and Linux
udig-1.2.2 Release Notes
Issue Tracker Change Log

About uDig 1.2.2

The release adds a number of new features and updates the uDig platform to the latest opensource libraries.

Here is what you can look forward to in the desktop application:

Extensive update to online help including uDig Overview
Spatial Toolbox view allowing access to OMS3 processing; with a step by step Introduction to Spatial Toolbox tutorial
Updated Info and Profile tool for raster data
Teradata support
New import and export formats: CSV and KML.
For information on additional new features visit our What is new page

For developers:

Access to the latest GeoTools 8.0-M1
Access to the latest ImageIO-EXT and finally a modern version of GDAL (on supported platforms)
The uDig git repository has moved to github to join the cool kids - and shows a very healthy stream of pull requests.
Works with Eclipse 3.6

Running the Image Georeferencing View. Release 1.0.0 for uDig 1.2.1

2011-06-21T04:46:00.000-07:00

We have released the Image Georeferencing View, versión 1.0.0. It was tested with uDig 1.2.1. The following video shows a typical session.

In this video the user adds the ground control points (GCP) using a road layer as base.

The following video shows as a georeferenced raster can be used to draw a new road layer (vector layer) .

To georeference the raster, the user provides the set of ground control points graved by a GPS device.

Image Georeferencing View RC3 for uDig 1.2.1

2011-05-19T06:18:00.000-07:00

We have released the Image Georeferencing View RC-3. It includes some new user interface features that show the relations between image's marks and the set of gound control points. New tools have been inlcuded in order to manipulate the image and the ground control points.

Finally, the Help (draft) is available too.

To know more about this project, please, go to Axios Community Space.

Image Georeferencing View for uDig 1.2.1

2011-05-04T02:38:00.000-07:00

A month ago, we began the development of Image Georeferencing. Now we want to share the first release in order to test it.

Right now, we are working in some improvements in the usability (zoom, pan, fit, etc). More details and download instructions in the Axios Community Wiki

Comments are welcome

udig development version available for osgeo4w users

2011-03-11T06:34:00.000-08:00

After finally upgrading the Osgeo4w version of uDig to the current 1.2.1, we also decided to add the development version of uDig to the game. It might be a bit unstable from time to time and handle itself like the evil brother of uDig

If you installed it you should feel its presence through its devil red icon in the applications menu.

One good reason to try that out is because it has some nice features that would not be there before an official release. One example is for sure the georeferencing tool that was resurrected from the community repository by moovida and jive. Have a look at some nice screenshot and docs for the module.

What will be next? The line cleaner?
The doors are open...

Spatial Operations Tutorials for Udig 1.2.1

2011-03-11T00:20:00.000-08:00

Hello everyone, recently, we have improved the Spatial Operation Framework in order to do easy its extension with some new operations. Thus, we have updated the following tutorials:

How to add a New Spatial Operation

Reusing Existent Spatial Process. Integrating Sextante

Important, this new feature is compatible with uDig 1.2.1.

To download, visit the section Tutorials and Documents in www.axios.es

Spatial Operations & Editing Tools for uDig 1.2.1

2011-03-08T00:35:00.000-08:00

We have published a new release of our Spatial Operations & Editing Tools for uDig 1.2.1 project.
It includes many fixed bugs and performance improvements.
Now, the product is provided as:

Editing Tools 1.3.3 for uDig 1.2.1
Spatial Operations 1.3.1 for uDig 1.2.1

This features are available in uDig Community Updates Site:
http://udig.refractions.net/update/1.2/community

To download the source and binary distributions, visit our download page in www.axios.es.

uDig 1.2.1 Released

2011-02-02T23:58:00.000-08:00

We have recently released uDig 1.2.1. This is an incremental update with mainly bug fixes but there are a few notable features added as well.

Additional style editor pages; thanks to the JGrass project and Hydrologis
Access to the latest GeoTools renderer with support for hatch patterns
Access to world+image "bmp" files
Experimental - WMS 1.3.0 support
Updated "submit log" in the help menu

Additional documentation:

Updated online help capturing the new style pages style pages
Updated intro documentation for users and developers

For developers:

We have migrated to a new git repository http://gitorious.org/udig
Access to the latest GeoTools 2.7 Release Candidate

The new release can be accessed and downloaded from http://udig.refractions.net/download/

Upcoming uDig Training

2011-01-05T14:56:00.000-08:00

LISAsoft is pleased to announce two uDig training courses in the Australian market:

Sydney Jan 31st to Feb 2nd
Melbourne Feb 7th to 9th

LISAsoft has updated the uDig training course to cover the latest 1.2.1 release including an early preview of GeoTools 2.7.

This is a world renowned course now in its fifth year. The uDig training course is highly recommended for development teams new to uDig, Eclipse RCP or Geospatial development. The courses packs a punch at 5 days, split between the introductory 3-day course and an advanced 2-day course later in the year, covering everything from disk to screen. Material is well paced providing a gradual introduction with advanced exercises to test your knowledge or explore new areas in depth.

For more information or contact information please see:
http://www.lisasoft.com/Registration

Is Australia too far away? Would you prefer an on-site course customised for your development team? The uDig training course is available from supporting organisations in North America, Europe and Australia. Please contact a PMC member in your area for details.

Axios uDig extensions - Releases 1.3.2 and 1.2.9

2010-12-01T00:48:00.000-08:00

We have published the 1.3.2 version for uDig 1.2. This release fixes those bugs present in the last version. Additionally, we have done the backporting to 1.2.9, compatible with uDig 1.1.

These releases are available in uDig Community Updates Site:
http://udig.refractions.net/update/1.2/community
http://udig.refractions.net/update/1.1/community

To download the source and binary distributions, visit our download page in www.axios.es.

Finally, we want to highlight the excellent testing work done by the Municipal Department of Automated Data Processing, Information and Communications Technologies, Vienna City. The have been working hard producing 685 test scenarios for the split tool.

Axios uDig Extensions release 1.3.1 for uDig 1.2.x

2010-10-07T03:57:00.000-07:00

We have published a new release of Axios uDig Extentsions. This version includes fixes and improvements for the Split Tool.

A closed split line can be drown as shown in the screenshot.

The result of split transaction produces:

The split operation is available as a Spatial Operation too. Thus it is possible to split the feature in a layer using lines present in another layer.

This release is available in uDig 1.2 - Community Updates Site:
http://udig.refractions.net/update/1.2/community

To download the source and binary distribution, visit our download page in www.axios.es

UDIG 1.2.0 Release

2010-08-16T07:35:00.000-07:00

The uDig 1.2 release process is complete and we are pleased to offer uDig 1.2.0 for download.
This release is made in conjunction with GeoTools 2.6.5.

The uDig 1.2.0 release is available from the main download page.

Installation

Download the package appropriate to your platform, unzip and run:

Windows
Linux
Mac
SDK: For use with SDK Quickstart instructions

Windows and Linux packages includes a Java Runtime so you really can unzip and run without making any configuration changes to your Machine. On Mac OSX uDig is able to check for Java Advanced Imaging and install if needed. There is also a windows installer.

To get started with uDig:

About uDig 1.2 Series

The uDig 1.2 series highlights a lot really great ideas the developer community has been working on. We have migrated to a modern version of the GeoTools library - bringing in five years of new developments in standard support, and a host of new raster and vector formats. An exciting addition is the use of the ImageIO-ext project allowing the use of raster formats supported by GDAL.

New and capabilities of uDig 1.2 include:

ImageIO-EXT rendering enabling additional raster formats and working with images larger then memory
On select platforms MRSID and ECW raster support
Tiled rendering (as an option in preferences) with a new flicker free panning tool.
Support for GeoWebCache and TileCache via WMS-C
WFS 1.1.0 support (read-only)
Greatly improved ArcSDE support; multithreaded and faster
Advanced Symbology including Hatches and True Type Font support

About uDig 1.2.0

Features and capabilities of this release:

Access to GeoTools DataStores via a generic wizard allowing users to connect to many additional data formats and access all connection parameters.
One long standing difficulty with using large datasets is uDig wanting to know the bounds of the data (so it can efficiently search, zoom). For common spatial file formats this data is known and available; for large databases such as DB2 and PostgreSQL this can take some time to calculate. For the generic GeoTools DataStore wizard above we are experimenting with using bounds based simply on the valid area for coordinate reference system provided by the data.
The valid area of the coordinate reference system is also used when "clipping" WFS requests resolving some long standing issues when editing WFS services that do not update their Capabilities document.
Advanced: Control what features are requested for a layer using a Common Query Language (CQL) expression. The expression builder offers command completion with the full GeoTools function list available as you type
Advanced: Cache support added allowing you to cache Raster layers in memory (please be working with large datasets as this is the first time uDig is allowing users to cache information in memory). Please note that raster file formats on disk are optimised and in may cases perform better than caching in memory. Caching in memory is recommended for formats such as jpeg (where the entire image must be loaded to display even a small section) and when working with data from a slow device such as the network or DVD.
Experimental: Cache support added allowing you to cache WFS layers in memory for increased performance (please be careful when working with large datasets as this is the first time uDig is allowing users to cache data in memory)
Enhanced Vector Editing
Revamped printing support, standard paper sizes are supported when printing
Import multiple layers into the catalog at once
switch between common map scales
Improved Drag and Drop support allowing multiple layers to be manipulated at once
Drag and Drop treats URL as a distinct content type across browser implementations

Notes and documentation for developers:

Service and GeoResource Interceptors Docs
Interceptors Docs
Review of the dependencies used by the uDig SDK with license and build advice
We have transitioned to a modern version of GeoTools allowing for a more productive relationship with the larger community
Support for the "JDBC-NG" rewrite of GeoTools Database access
Uses the latest Eclipse 3.6.0 "Helios" release for an industrial strength plug-in system
Uses the latest "Babel" project translations

Release Notes

The following release notes are applicable to this release:
UDIG 1.2.0 Release Notes, August 9, 2010 (23 Issues)
UDIG 1.2.RC3 Release Notes, May 17th, 2010 (25 Issues)
UDIG 1.2.RC2 Release Notes, March 21, 2010 (7 Issues)
UDIG 1.2.RC1 Release Notes, March 10, 2010 (4 issues)
UDIG 1.2.M9 Release Notes, January 8, 2010 (2 issues)
UDIG 1.2.M8 Release Notes, December 8, 2009 (1 issue)
UDIG 1.2.M7 Release Notes, September 9, 2009 (13 issues)
UDIG 1.2.M6 Release Notes, August 5, 2009 (53 issues)
UDIG 1.2.M5 Release Notes, June 10, 2009 (4 issues)
UDIG 1.2.M4 Release Notes, May 23, 2009 (12 Issues)
UDIG 1.2.M3 Release Notes, March 30, 2009 (74 Issues)
UDIG 1.2.M2 Release Notes, February 5, 2009 (14 Issues)
UDIG 1.2.M1 Release Notes, December 18, 2008 (10 Issues)
UDIG 1.2.M0 Release Notes, August 19, 2008 (19 Issues)

Known problems:

The mac release is unable to support the full range of ImageIO-EXT formats. Please contact udig-devel if you are able to build GDAL on Mac OSX.

Axios uDig Extensions releases 1.2.5 for uDig 1.1 and 1.3.0-m6 for uDig 1.2

2010-07-15T07:21:00.000-07:00

We have published a new releases of Axios uDig Extentsions. The 1.3.0-m6 version for uDig 1.2 includes many fixes for the Split Tool.

Additionaly, we have done the backporting to 1.2.5, compatible with uDig 1.1.

Theses release are available in uDig Community Updates Site:
http://udig.refractions.net/update/1.2/community
http://udig.refractions.net/update/1.1/community

To download the source and binary distribution, visit our download page in www.axios.es

Open Source Blueprint

2010-07-12T18:39:00.000-07:00

Open source has a long standing relationship with academic studies, both as working examples and as something to study in its own right. We are always happy when a student ducks into a project with useful contributions and it is even more rare that the contribution is documentation.

Recently Michelle Ballinger has been writing up an "Blueprint for Creating an Open Source Web Map" which includes a section on uDig. It is nice to see Penn State encouraging students to get out there in the world and make positive contributions; and it makes a change from the endless survey requests open source projects are asked to fill out each year.

If all goes well we will collect these instructions for the uDig online help. Thanks for taking part in open source Michelle.

uDig 1.2 Release Candidate 3

2010-05-19T19:54:00.000-07:00

The uDig 1.2 development is complete and we are pleased to offer uDig 1.2 RC4 for download. This release is made in conjunction with GeoTools 2.6.4.

The uDig 1.2-RC3 is available from the main download page (previous releases are also available).

Installation

Download the package appropriate to your platform, unzip and run:

Windows
Linux:
Mac:
SDK: For use with SDK Quickstart instructions

To get started with uDig:

Help Menu provides a Quickstart
Walkthrough 1
Walkthrough 2

About uDig 1.2 Release Candidate 3

The release adds three amazing new features:

Access to GeoTools DataStores via a generic wizard allowing users to connect to many additional data formats and access all connection parameters.
One long standing difficulty with using large datasets is uDig wanting to know the bounds of the data (so it can efficiently search, zoom etc…). For common spatial file formats this data is known and available; for large databases such as DB2 and PostgreSQL this can take some time to calculate. For the generic GeoTools DataStore wizard above we are experimenting with using bounds based simply on the valid area for coordinate reference system provided by the data.
The valid area of the coordinate reference system is also used when "clipping" WFS requests resolving some long standing issues when editing WFS services that do not update their Capabilities document.
Advanced: Control what features are requested for a layer using a Common Query Language (CQL) expression. The expression builder offers command completion with the full GeoTools function list available as you type
Experimental: Cache support added allowing you to cache WFS layers in memory for increased performance (please be careful when working with large datasets as this is the first time uDig is allowing users to cache data in memory)

Additional documentation for developers:

Service and GeoResource Interceptors
Interceptors
Example code for Feature Panel data entry forms added

Release Notes:

Sub-task

[UDIG-1632] - IFeaturePanel class and Extension Point

Bug

[UDIG-1520] - unable to connect WMS with Udig
[UDIG-1553] - axios plugin edittools
[UDIG-1578] - OracleGeoResource keeps its own IService
[UDIG-1587] - Adding WMS service via wizard fails.
[UDIG-1612] - Bluemarble tif not displayed
[UDIG-1629] - PostGIS next() called before hasNext()
[UDIG-1633] - Cannot resolve PostGIS layer to JDBCDataStore
[UDIG-1638] - Marker size defaults to 6
[UDIG-1639] - Table show selection does nothing
[UDIG-1641] - RenderContextImpl fails when MapViewer not shown yet
[UDIG-1642] - Cant edit PostGIS line feature in 1.2-rc2
[UDIG-1650] - Add transparency support for default Image format image/png8

Improvement

[UDIG-1631] - Move public documentation to public svn
[UDIG-1634] - Break ICatalog up into ISearch and IRepository and check interface boundaries
[UDIG-1647] - Add visual queues to information tool layer list
[UDIG-1648] - Change Coordinate System: Set focus to Search field
[UDIG-1655] - Allow user to change layer filter
[UDIG-1656] - FeatureInterceptor for creation of default values
[UDIG-1657] - Service and GeoResource Interceptors

New Feature

[UDIG-1658] - Generic GeoTools DataStore support
[UDIG-1659] - Relaxing requirement to know bounds
[UDIG-1660] - User control of Feature Caching
[UDIG-1661] - Filter layer content with "query builder"

Known problems:

The mac release is unable to support the full range of ImageIO-EXT formats. Please contact udig-devel if you are able to build GDAL on Mac OSX.
WIn64 download does not include a JRE at this time

About uDig 1.2 Series

New and capabilities of uDig 1.2 include:

ImageIO-EXT rendering enabling additional raster formats and working with images larger then memory
Tiled rendering (as an option in preferences) with a new flicker free panning tool.
Support for GeoWebCache and TileServer via WMS-C
WFS 1.1.0 support
Greatly improved ArcSDE support; multithreaded and faster
Advanced Symbology including Hatches and True Type Font support

Reusing Existent Spatial Operations

2010-05-10T02:36:00.000-07:00

Recently, we have published a tutorial which could be interesting for those developers who want to integrate existent proceses in uDig framework.

This tutorial uses the Spatial Operation Framework, developed under the auspices of Gipuzkoa Provincial Council, Mobility and Land Planning Department, and Sextante, promoted by Spanish autonomous region of Extremadura.

As platform we use uDig 1.2 and Spatial Operations 1.3.

To download, visit our web site www.axios.es and select Tutorials and Documents.

Google Summer of Code 2010

2010-05-08T06:26:00.000-07:00

In two weeks time the Google Summer of Code for 2010 starts, and this year uDig is taking part with an exciting project riding the current NoSQL wave, one of the hottest topics concerning databases in a long time.
Davide Savazzi, a student at the Università degli Studi di Pavia, Italy, and an experienced GIS developer, is doing a project titled 'Adding support for Neo4j graph database in Geotools and uDIG'. We are particularly excited to have Davide involved in this project because he has already made core contributions to the underlying 'Neo4j Spatial' project, which is building GIS capabilities into the graph database itself.

Introduction

Geographic vector data is naturally structured like a graph, network and topological analyses view GIS data as graphs, but so far no-one has tried to make use of a real graph database as the backing store for a GIS.

Neo4j is a new open source database that stores data as a graph, in the mathematical sense of nodes connected by relationships, with both nodes and relationships storing properties as key-value pairs.

The goals of the project are:

extend Neo4j graph database with spatial indexing and query functions.
enable GIS application developers working on either or both Geotools and uDIG to use Neo4j as a true spatial database.
enable GIS users working with uDIG to perform spatial analyses better or faster than normal.

Roadmap

At the highest level, the project will take the following phases:

define the best approach to store spatial data in Neo4j graph database
create spatial indexing and query functions for Neo4j
create a Geotools DataStore that can read and write spatial data contained in Neo4j
add a Catalog to uDIG for this new DataStore
add persistence support to Geotools graph module through Neo4j
prototype a plugin in uDIG for network / routing analyses

uDig 1.2 Release Candidate

2010-03-31T04:42:00.000-07:00

The uDig 1.2 development cycle is near completion on the community is pleased to announce the availability of our second release candidate. This release is made in conjunction with GeoTools 2.6.3, we would like to thank the GeoTools community for their continued support.

uDig 1.2 Release Candidate 2 is available from the uDig main download page (previous releases are also available). Please download the package appropriate to your platform, unzip and run.

To get started with uDig:

About uDig 1.2 Series

New and capabilities of uDig 1.2 include:

ImageIO-EXT rendering enabling additional raster formats and working with images larger then memory
Tiled rendering (as an option in preferences) with a new flicker free panning tool.
Support for GeoWebCache and TileServer via WMS-C
WFS 1.1.0 support
Greatly improved ArcSDE support; multithreaded and faster
Advanced Symbology including Hatches and True Type Font support

About uDig 1.2 Release Candidate 2

This release patches up the jre used for the linux distribution and fixes a couple of issues that were spotted by the community with the first release candidate - including fixing Drag and Drop from the latest firefox on windows.

Resolved:

[UDIG-1506] - Pan and Zoom causes vertexes to be slightly displaced when editing
[UDIG-1529] - Displaying deleted layer feature
[UDIG-1600] - FireFox 3.5 DnD
[UDIG-1615] - Create Polygon Tool Validation Broken
[UDIG-1625] - WFS layer exported as shapefile missing geometry
[UDIG-1626] - Printing NPE

Known problems:

Mac OSX release is a simple zip, we will try and make a proper installer shortly.
The mac release is unable to support the full range of ImageIO-EXT formats. Please contact udig-devel if you are able to build GDAL on Mac OSX.
Linux64 release is not provided at this time. Please contact us on the udig-devel list if you are able to bundle a Linux 64 Java Runtime Environment with ImageIO-EXT support.

Axios uDig Extensions release 1.2.4 for uDig 1.1

2010-02-11T01:43:00.000-08:00

A new Axios uDig Extensions bug fix release is available in the udig update site.

It includes many fixes in the parallel tool.

cheers

uDig 1.2 M9

2010-01-31T00:33:00.000-08:00

Welcome to the January milestone release of uDig. This release is made in conjuction with GeoTools 2.6.1 - with a number of improvements to the jdbc "next generation" plugins.

Installation

Installation Notes: Download the package appropriate to your platform:

Windows: installer (including ECW support) or zip archive avaiable.
Linux
Mac
SDK: For use with SDK Quickstart instructions.

On windows and linux uDig includes a Java Runtime so you really can unzip and run. On mac uDig is able to check for Java Advanced Imaging and install if needed.

About uDig 1.2 Milestone 9

We have focused on the Software Developers Kit this release and have a new SDK Quickstart available. These instrucitons have been completely updated for Eclipse 3.5.1.

We have accomplished our goals for the uDig 1.2 series and will be issuing a release candidate shortly.

This release features:

GeoTools 2.6.1

Known problems:

Mac release unable to support the full range of imageio-ext formats (MRSID, ECW, etc...)
Linux64 release is not provided as we wait for a 64 bit release of ImageIO-EXT
Some repots of the Layers menu not showing up under the SDK release

About uDig 1.2

The uDig 1.2 series highlights a lot really great ideas the developer community has been playing with. We have upgraded the version of the GeoTools library we use - bringing give years of new developments in standard support, and a host of new raster and vector formats. An exciting addition is the use of the ImageIO-ext project allowing the use of raster formats supported by GDAL.

New and experimental capabilities of uDig 1.2 include:

ImageIO-EXT rendering enabling additional raster formats and working with images larger then memory
Tiled rendering (as an option in preferences) with a new flicker free panning tool.
Support for GeoWebCache and TileServer via WMS-C
WFS 1.1.0 support
Greatly improved ArcSDE support; multithreaded and faster.

This tech-preview is made available for your testing pleasure; please contribute bug reports and feedback! This milestone is a suitable baseline for your own development efforts.

Axios uDig Extensions 1.2.3 for uDig 1.1

2009-12-21T03:18:00.000-08:00

Recently, we have published the release 1.2.3. It includes fixes for the Split and Parallel tools and cap styles for the Buffer spatial operations.

This product is available in the udig update site and www.axios.es download page.

Is coverage styling finally coming to uDig?

2009-12-02T04:27:00.000-08:00

Finally we have been able to get paid work on raster styling. Taking the JGrass raster styling gui as a starting point, we have been able to give the coverage styling a go.

To read the whole of it, see here.

How to add a new spatial operation

2009-11-12T03:22:00.000-08:00

Hello everyone, we have published a tutorial which shows how to extend the spatial operations framework with new spatial operations.

We expect this document to be interesting for those developers who want to include existent spatial operations or develop a new spatial operation for uDig, taking advantage of the spatial operations framework.

In this tutorial we develop the spatial operation Centroid. The screenshot shows the user interface idea. In the presented example the centroid operation has created a new layer called Centroid_1 using as source layer the countries layer.

To download visit our web site www.axios.es, "Tutorials and Documents".

cheers

AXIOS UDIG EXTENSIONS 1.2.2

2009-11-06T01:36:00.000-08:00

This release, available for uDig 1.1.x, includes improvements

and bug fixes in the Parallel Tool.

Also, you could have a look in the development branch. The axios suit 1.3.0-m2 was tested with uDig 1.2 M6.

To download this new releases please visit the uDig update-site or our web site www.axios.es download page.

New UDIG3D alpha release!!

2009-10-07T05:52:00.000-07:00

We are delighted to announce the release of uDIG3D alpha version 0.1 with
support for 3D spherical (WGS84) maps and 3D projected maps. A new 3D Map is
integrated within udig to be managed as a simple map but with the advantage of
3D representation.

It makes use of OSGVirtualPlanets(osgVP) version 2.2.0. osgVP is a library
developed in the Instituto de Automática e Informática Industrial(AI2) of the
Universidad Politécnica de Valencia(UPV).

If you want to test this release you can download a complete uDIG with the
necessary plugins and native libraries from here:

Linux Version:
http://www2.ai2.upv.es/difusion/uDIG/udig-linux-i386-alpha-v0.1.tar.gz

Windows Version:
http://www2.ai2.upv.es/difusion/uDIG/udig-win-i386-alpha-v0.1.zip

Some video demonstrations can be found here:
http://www2.ai2.upv.es/difusion/uDIG/demo-uDig1.swf
http://www2.ai2.upv.es/difusion/uDIG/demo-uDig2.swf

User Guide:
https://svn-gis.ai2.upv.es/svn/gis-projects/udig-extensions/trunk/Documentation/UserGuide.pdf

If you are interested in taking a look at the code the svn access is:

uDIG3D Plugin:
svn co https://svn-gis.ai2.upv.es/svn/gis-projects/udig-extensions/trunk udig3d-trunk

osgVP Plugins:
svn co https://svn-gis.ai2.upv.es/svn/gis-projects/osgvp/trunk/ osgvp-plugins-trunk

osgVP:
svn co https://gvsig.org/svn/osgvp/trunk/ osgvp-trunk

NOTES:
There is some known problems with the persistence of the 3D Maps, so we
apologize for possible issues. If anyone is interested in continuing or support
these developments please contact us.

uDig 1.2 M6

2009-08-18T18:45:00.001-07:00

The uDig 1.2 "milestone 6" release is available for download.

This release is the result of an amazing week long code sprint held at Hydrologis in Italy supplimented by developers all over the world. A special thanks to the participating organizations: Axios, Camptocamp, Fraunhofer IAIS, HydroloGIS and LISAsoft.

The milestone release features:

Better support for TIFF and depending on your platform ECW and MrSID with an update to the imageio-ext library
Enhanced vector editing, revamped printing support
Upgrade to the latest Eclipse 3.5 (finally we can offer cocoa support on mac!)

Here are some example of some of the enchancements:

Import multiple layers into catalog at once
Deleting multiple maps only asks for a single confirmation and delete
standard paper sizes are now supported when printing!
Add rectangles, roundrectangles and ellipse when printing
Drag and Drop improvements: drag and drop mixed content in the catalog and map, move several maps at once, multiple services on project at once, handle multiple layers in the layer view
Improved workflow: An Open Map action, switch between common map scales

All in all 41 issues have been addressed for this release - for more information check the release notes.

AXIOS UDIG EXTENSIONS 1.2.0

2009-08-14T05:27:00.000-07:00

This release, available for uDig 1.1.x, includes new features, improvements and bug fixes. We want to highlight the following ones:

NEW FEATURES

Spatial Operation Split splits features from a source layer using a LineString features from a second layer (or reference layer).

Spatial Operation Polygon To Line transforms the Polygon features from a source layer into LineString features.

Spatial Operation Fill creates a new geometry using the reference line and the border of the source polygon as its own border.

Spatial Operation Hole Cut makes a hole inside a polygon feature using a valid lineString that is within the polygon.

IMPROVEMENTS

Merge Tool the usability has been improved in several ways.

New Split algorithm, it allows add vertex to neighbour geometries. Additionally, it solves many reported problems in the old split tool.

Parallel Tool - Improvements ofthe algorithym.

Spatial Operation Dissolve allows to select multiple dissolve property.

The spatial operation framework was factored to provide an easy way to extend with new operations. Thus the control logic was encapsuled in abstract classes to simplify the creation, associations presenters- commands and event handling .

Spatial Operation Extensions Point allows to add new spatial operations in the default set.

To download this new release please visit the uDig update-site or our web site www.axios.es download page.

Finally, we want to thank uDig community for your comments and suggestions to improve this product.

If you want to know more about this project visit the
following page: uDig Axios Community Space - Spatial Operations and Editing Tools

FOSS4G2009 presentations about uDig and friends

2009-08-03T00:46:00.001-07:00

The FOSS4G2009 presentations are defined, so here are some uDig related presentation that you might be interested to attend:

Here is what the HydroloGIS team came up with:

JGrass, present and future
Anatomy of a digital field mapping with BeeGIS
JGrass-uDigs's sense for climate change

A very interesting live demosnstration comes from Potsdam, as suggested by Matthias Lendholt:

Live Demonstration of DEWS (that will show a Tsunami Early Warning System using uDig and GeoTools. If the network connectivity works properly they will show a life scenario instead of a powerpoint presentation)

Are there others around? Please send us an email if you are presenting something related to uDig & friends.

IRC meeting about post code sprint release

2009-07-22T02:56:00.000-07:00

The meeting agenda was as follows:
1) jre's and startup scripts
2) to style or not to style
3) where is my printer
4) editing bugs ade

The good news is a release being organized for Friday.

Code Grind 09 wrap up

2009-07-21T01:44:00.000-07:00

The world-wide code sprint/grind has now wrapped up and with very good results. uDig trunk is very functional with an incredible number of bugs and usability issues addressed. Many (although not all) have been listed in other blog postings. We will be combing through the logs and getting a complete list of the issues addressed very soon.

There is only one more task to complete the sprint: make a new Milestone release.

The new release will be trimmed down to the plug-ins that we think work very well and all other plug-ins will be moved to a unstable feature that will be avalaible from the update site (once the final, non-milestone, release is made).

The unstable feature will also be available to developers in the SDK (that is the current plan but is up for debate).

We hope to finish up the release this week and get it on-line.

Good work to all the developers who helped out and the organizations who sponsered them:

uDig Code Grind Day 4 Australia

2009-07-16T19:03:00.000-07:00

An interesting day ... John Hudson returns with a partner in crime by name of Jim Groffen and proceed to keep pace verifying all the bugs being fixed. They also identified the instructions for setting up a development environment as in need of fixing (due to the recent arrival of Eclispe 3.5).

Mark started hooking his user interface up to the StyleBlackBoard (and then want off on the town all dressed up - perhaps he had a date? Ugo Taddei is not the only good looking guy around here).

Jody stayed up till oh dark early with the following (admittedly cool) screen snaps emerging. The first one is command completion with the entire function list avaialble as you type. And it is generated on the fly so it is always current!

Next one is also interesting - field decorators that can provide feedback (warnings; errors; if the field is erquired etc...).

Yes the warning tool tip on the decorator is a really horrible message from the Extrended Common Query Language Parser - I am going to see if we can get row,col information out so we can highlight where the problem is exactly and save the message as a "more details" kind of thing.

uDig Code Grind 2009 Europe Day 3

2009-07-15T23:54:00.000-07:00

Day 3 of the code sprint has come and gone and Day 4 has now begun. Another fantastic day of work.

Here's a quick summary:

Andrea Antonello (HydroloGIS)

Compiled ImageIO ext for Mr.Sid and Geotiff on Mac
Reviewed printing framework
Added z-ordering actions for the Page layout

Jesse Eichar (Camptocamp)

Some low level work to make more of uDig use the ID objects to identify Services and GeoResources
Refactored Raster plugins to share more code
Added type of raster to the titles of raster layers. This is required because multiple plugins can handle geotiff (for example) and there needs to be a way to distinguish between them.
Windows still had a problem persisting services in the catalog. This was fixed.
Improved displayed title for rasters in layers view

Silvia Franceschi (HydroloGIS)

Saving our life with testing

Mauricio and Aritz (Axios)

Set up environment for Aritz
Finished fixing a very challenging bug with hole tool

The uDig Code Grind Team

2009-07-15T23:50:00.000-07:00

You might be asking yourself who is on this sprint. Here we go with nice pics, so at the next Foss4g conference you can recognize them and ask them to solve your problems for free. :)

In random order:

1) Lisasoft Adelaide team: Jim Groffen and John Hudson

2) Lisasoft Sydney: Mark Leslie

3) ...and Jody Garnett

4) Camp2camp and HydroloGIS Bolzano based team: Jesse Eicher and Andrea Antonello

5) HydroloGIS Bolzano: Silvia Franceschi

6) Axios Spain: Mauricio Pazos and Aritz Dávila

7) Fraunhofer-Institut Germany: Ugo Taddei (for the ladies we should mention he is Brazilian and has Italian blood)

All around the world!!!

uDig code grind day 2

2009-07-14T22:44:00.000-07:00

Another very long day of bug fixing has just wrapped up. The day progressed more or less the same as yesterday.

Andrea Antonello (HydroloGIS)

Andrea has gotten the image-io-ext working on linux 32 and 64 and windows.
Andrea has Mr Sid and geotiff in image-io-ext compiling on Macosx and is now in a grand battle with ECW to get it to compile.

Jesse Eichar (Camptocamp)

I spent another day fixing bugs. Some of which include:
Updated features and files so that we can export uDig on Eclipse 3.5
Fixed a bug when selecting several features using shift select
An important editing bug related to the selection
Fixed an issue when a new layer is created that has the same name as an existing layer
Fix an exception that is thrown when writing wgs84 into the CRS Selection dialog
Improved performance (but worse for memory) for JPEG and other simple world+image formats. Hopefully more to come.
Working on problem importing a tiff that is both a geotiff and a world+image

Sylvia (HydroloGIS)

Lots of testing
Writing a workflow as an end user
Bug fix verification

Mauricio (Axios)

He is in Spain right now so I don't have the details of his work but I am aware that he has been doing work on the more advanced features of the edit tools. He is working on fixing bugs with the hole cutter I believe.

uDig Bug Crunch Day 3 Australia

2009-07-14T22:30:00.000-07:00

Bug crunching is in full swing today with almost all the bugs to be marked as FIXED on the Code Sprint Road Map verified and closed.

Moving onto the "to be verified" list, I started to see a trend for "Catalog Improvements" issues. After a short discussion on the uDig IRC channel, Jody and I came to the conclusion we should make a single Feature Request and close all the other issues, check it out here. Looks like this has been something wanted for quite sometime, I closed five separate feature requests.

For the interested, Jody as been working on a new Catalog View Proposal which outlines a improvements, check it out here, its pretty cool!

uDig Code Grind Day 2 Australia

2009-07-14T03:35:00.001-07:00

Today we are branching out across Australia with LSIAsoft developers from Sydney and Adelaide.

First up is John Hudson, drawing on earlier motivation, has focused on chewing the bugs listed on the Road Map and verifying and/or closing bugs.

Back in Sydney Mark has started putting together the new Point Symbolizer page (see below).

Jody was mostly decorative and has been working on a reuseable ExpressionViewer to use for each of the fields above. He promisses to be useful tomorrow.

uDig Code Grind 2009 Europe Day 1

2009-07-13T13:30:00.000-07:00

An exciting day 1 is wrapping up here in Europe. The fine coalition (Axios, Camptocamp, HydroloGIS) have been hard at work knocking down bugs. A quick list of the tasks we have been working on for today:

Jesse Eichar(Camptocamp) - Many miscellaneous workflow bugs:

Drag and drop bugs
Import data bugs
Selection bugs
Map and Catalog persistence bugs

Andrea(HydroloGIS) - Image IO

Working on getting the GDAL/ImageIO plugins working on Linux 32/64 and windows

Mauricio (and co) (Axios) - Editing Bugs

Hole tool bug

As a team we are focusing on addressing as many bugs that affect the core functionality of uDig.

See you tomorrow!

Have a look at the Italian sprint headquarter:

Can you guess on how many systems udig is tested?

Code Grind Sprint Day 1 Kickoff

2009-07-12T18:18:00.001-07:00

It is our please to kick off the code grind sprint. We will add to this news post over the course of the day as each team around the world starts up.

LISAsoft Team

Myles is starting in on the tutorials and was very happy with the result.

Mark and Jody are going to be going over the Style Editor (design notes here).

Update: We reviewed the three style extension points; StyleEditorPage (very good but specific to SLD); StyleConfigurator (general purpose the content will go in the StyleEditor using an adapter or be present in the Style view); and the StyleEditorPart (while we can see implementations I am not sure where they are used from?).

We decided to go with StyleEditorPage and expect to add a few methods as time goes on this week. Here is our initially empty "Point" page.

Eclispe 3.5

For those joining the hands on experience here are some instructions for getting your Eclipse 3.5 game on:

Download Galileo " Eclipse for RCP/Plug-in Developers" for and unzip

Fire it up and add EMF SDK and GEF SDK into the mix using the help menu "Install New Software"

Download extras-3.5.0.zip and unzip into your "drop-ins" folder. We are operating with a really reduced set of "extras" this time around since we have had some trouble with the Eclipse 3.5 delta pack.

Proceeed remaining instructions...

RoadMap and Testing

Silvia has done a nice job updating the road map to focus on uDig 1.2 M6 bugs - this will be a large part of the QA focus of the code spint.
For more information please check out Road map; we also would welcome any volunteers to help out with testing this week - there are already a long list of "resolved" issues that need a sanity check before we mark them closed.

New Server

2009-06-16T06:17:00.000-07:00

Refractions is kindly hooking us up with a new server; there may be some transition pains as the website, mailing list and wiki are moved across.

In order to facilitate the global nature of uDig development Jesse Eichar from our project steering committee is also experimenting with a GIT repository located in Europe. For more information please join the developer list and say hi.

AXIOS UDIG EXTENSIONS 1.2.0-RC01 (Testing)

2009-06-15T03:13:00.000-07:00

This release, available for uDig 1.1.x, includes new improvements and bug fixes. We want to highlight the following:

– Split Operation. We have fixed the split behaviour to split a geometry properly using complex split line like it's shown in the following figures.

– Split Operation. Fixed the split behaviour to split geometries properly when splitting several neighbour features.

– The Spatial Operations framework was refactored to provide an extension point that could be used by other developers to add new operations.

To test this new release please visit the uDig update-site or our web site www.axios.es download page. Here you can find the latest stable release Axios uDig Extensions 1.1.4, as well as the latest under development release Axios uDig Extensions 1.2.0-RC01 for uDig 1.1.x.

If you want to know more about this project visit the
following page: Spatial Operations and Editing Tools

uDig Code Grind 2009 coming up!

2009-06-02T23:59:00.000-07:00

We are embarking on a week long code sprint from July 13 to 17. The main goals are to focus on the core features and functionality of uDig 1.2 and ensure that they are release ready.

This will be a world-wide event with several members Australia as well as others from Europe and North America. We will maintain a strong presence on IRC but will supplement it with frequent skype calls and video conferences.

Everone is welcome to join. Documentation, testing or coding: all contributions are welcome.

Our many thanks to the sponsers of this sprint:

Axios,
CamptoCamp,
LisaSoft,
Hydrologis.

WireframeSketcher

2009-05-29T23:26:00.000-07:00

One of the eclipse plug-ins I ran into recently is really pretty impressive. I have used Viso to do user interface mock-ups before - but there are kind of two problems with this approach:

the result looks like a real application; so if you show it to a customer they want to stop talking to you and run the application
the Viso templates only provide a Windows XP appearance which is pretty lame these days

It turns out that the Viso templates were "removed" from the latest copy of Viso (along with a bunch of other useful things) and held ransom as part of a Professional Edition.

So I went off to look .... and found something better :-)

WireframeSketcher - http://wireframesketcher.com/

This is an eclipse plug-in, it is beautifully written, and very fast to quickly slam together a ui mock up.

And even better the result looks like a ui mock up; allowing every one to stay focused on the workflow; the trade offs; and how the user interface functions rather than get distracted by the font used or the icons.

Perfect.

Here is an example mock-ups done for the uDig style editor.

Stay tuned (or jump on the mailing list) for styling plans.

I have added a page on WireframeSketcher to the udig list of recommended tools in our wiki.

We keep a list of good design ideas on our wiki; in order to refine the ideas before implementation, this tool should be helpful in those discussions.

Google Summer of Code 2009

2009-05-27T00:09:00.001-07:00

This is the first week of the Google Summer of Code - an event uDig is once again pleased to take part in. This year we have two fascinating projects:

Web Map Tiles for uDig - Tobias Sauerwein is going to go beyond the WMS-C support uDig currently enjoys and branch out to tile server implementations. Check the above link for details.

netCDF - Andrea Antonell is tackling one of the most expressive raster formats known. This project should produce both wonderful visuals; and some interesting user interface design challenges.

Check back weekly for updates on both these projects.

uDIg 1.2-M4 Released

2009-05-25T23:54:00.001-07:00

Another 1.2 milestone release for your testing pleasure. This release includes lots of fixes for WMS-C support. WMS and WFS support has been heavily tested against the Australian SLIP data services.

This release of uDig can be found in the usual location:
Unstable Downloads

The SLIP portal has been featured on our data wiki page for some time. Once you have signed up you are sent a user name and password which you can enter when connecting to their data services.

I would also like to thank OpenGeo for the excellent WMS-C tile server "sigma". Sigma is listed in the "Web" view of the main uDig application if you would like to try it out.

Here is what the two data services look like together:

UDIG 1.2-M3 Released

2009-03-26T05:30:00.000-07:00

Normally I would tell you what great new thing is in a release - this time I would like to ask you to look at the release notes! An amazing 60 bugs closed (and 13 more waiting for testers to verify).

This is the result of the "10 minuet code sprint" where the development community got together and fixed as many bugs as they could over the course of a couple of days.

The UDIG 1.2-M3 release is available here:
- http://udig.refractions.net/download/unstable/

AXIOS UDIG EXTENSIONS 1.1.2

2009-03-24T01:40:00.000-07:00

This release, available for uDig 1.1.1, includes new improvements and bug fixes. We want to highlight the following main improvement:

– Split Operation. We have improved the split behavior by allowing the tool to add one or more vertexes to the neighbor geometries (whose boundaries are intersected by the split line) of the one that has been split.

To test this new release please visit the uDig update-site or our web site www.axios.es download page. Here you can find the latest stable release Axios uDig Extensions 1.1.2, as well as the latest under development release Axios uDig Extensions 1.2-M3 for uDig 1.1.1.

If you want to know more about this project visit the following page: Spatial Operations and Editing Tools

We want to thank Rudolf Hochmeister from the Municipal Department of Automated Data Processing, Information and Communications Technologies, Vienna City, for his contribution to improve this project.

udigLite: An OSGi-friendly subset of uDig

2009-03-20T04:30:00.000-07:00

Depending on your environment, you may find it hard to integrate other OSGi bundles or Eclipse plug-ins with uDig. My team and I have tried for some time to build a viewer application for a proprietary car navigation database format on top of uDig 1.1 releases or uDig 1.2 trunk snapshots, fighting with version conflicts and class loader issues caused by the "grab all you need" plug-in net.refractions.udig.libs.

The root of these problems is Geotools and its dependency on the META-INF/services mechanism, which requires some trickery to be made compatible with OSGi.

We have now succeeded in creating a minimal subset of uDig and Geotools which solves these conflicts by turning all Geotools and third-party libraries into separate bundles. For technical reasons, we had to work with cloned repositories, which should simply be regarded as a uDig working branch.

More details about udigLite can be found in the uDig wiki. Have a look at my blog to get an idea of what we are using uDig for.

Finally, thanks for all the support from the uDig community so far - we very much hope to join forces to bring the results of this activity back into uDig trunk.

TileSync

2009-03-10T21:29:00.000-07:00

TileSync, based on uDig, developed by LISAsoft in conjunction with Landgate and ExaMin, allows a user to select any feature (Polygon) and add it as a Region Of Interest to a Region Of Interest View. The View allows the User to locally cache a any WMS-C Layer in the Catalog within the bounds of the Region Of Interest. The plugin also allows the local cache to be exported with TAB (MapInfo) header files and a seamless XML file.

Also included is a MapGraphic which outlines the Region of Interest on the Map View when it is selected in the Region of Interest View.

A bundled version is available for download here, and a copy of the plugin can be checked out of the uDig community SVN here.

I have made up some flash videos on usage available online:

The 10 minutes bug code sprint

2009-03-06T13:08:00.000-08:00

What is the 10 minutes code sprint?

A code sprint in which bugs and feature requests will be fixed that are supposed to take only 10 minutes to the involved developer (in a perfect world).

Further info at the Osgeo wiki.

IRC Logs March 6th

2009-03-05T12:46:00.000-08:00

[07:06am] jgarnett: morning
[07:07am] jgarnett: emily_g ping? were you able to sort out where layer.refresh() goes?
[07:07am] emily_g: hello jody
[07:07am] emily_g: no
[07:07am] emily_g: I wasn't
[07:07am] emily_g: layer.refresh() doesn't fire any events
[07:09am] jgarnett: um it does something though right?
[07:10am] jgarnett: somehow it adds a bounding box to an area that needs to be repained for a layer
[07:10am] jgarnett: and queues up a RenderJob to handle it right?
[07:11am] emily_g: yes that sounds about right
[07:11am] emily_g: but there are no events there that I can listen for
[07:12am] jgarnett: um from the ui I can listen to the layer state changes; rendering, etc... I think I can listen for layer refresh as well
[07:12am] jgarnett: (I am sorry I am at home on funny mac thing and do not have the source code in front of me)
[07:13am] emily_g: funny mac thing eh? sounds like fun
[07:13am] jgarnett: so if there were no events RenderJob would of been called directly via layer.refresh?
[07:13am] emily_g: LayerImpl.refresh calls getRenderManager.refresh()
[07:14am] emily_g: now that I think somehow calls RenderJob
[07:14am] emily_g: but I guess I need to walk further into the code
[07:14am] emily_g: I kind of stopped there thinking I hit the wall
[07:14am] emily_g: but you have a point; I may need to go further and look at layer state events or render events
[07:15am] emily_g: I have a couple questions about the current udig graph module
[07:15am] jgarnett: sure
[07:15am] emily_g: 1 - it has very few to no comments; this really isn't cool if you are trying to understand what's going on
[07:16am] emily_g: 2 - it looks to me like you can only route on one dataset at a time
[07:16am] jgarnett: (although the news here is that if you need to change how graph works you can - it is not used much yet and has not seen public release)
[07:16am] emily_g: (the waypoints are stored on the map blackboard)
[07:16am] jgarnett: thinking ....
[07:16am] jgarnett: 1. you are correct about the comments; mostly that is because the graph functionality is document well on the geotools wiki
[07:17am] jgarnett: I should go through and add at least class level commens (ie meet the udig requirements for comments)
[07:17am] emily_g: ya; I think that would help
[07:17am] jgarnett: 2. this is something that can be changed I guess
[07:17am] emily_g: I'm not sure we need to change it
[07:17am] jgarnett: it depends on where you store the graph data structure
[07:17am] emily_g: I'm just trying to understand what is happening now
[07:17am] jgarnett: is routing actually making sense on more than one data set?
[07:17am] jgarnett: I could see a public transit one and a car one
[07:18am] emily_g: or trasit; car; walk & bike
[07:18am] emily_g: or maybe you want to test different dataset
[07:18am] jgarnett: but not both at the same time; you would set up what you need and then ask it to generate a route
[07:18am] emily_g: and see how the attributes give you different routes
[07:18am] jgarnett: yeah okay fair enough
[07:18am] emily_g: i'm sorry i'm making up use cases ... I don't actually have that use case ... yet
[07:19am] jgarnett: so the workflow for that package right now places a graph on the map blackboard; we would need it to change and place a graph on a layer blackboard; and make a single renderer to show way points and the route calcualted against that graph.
[07:19am] jgarnett: you guys are using pgRouting; and I am mostly interested in assuring you make use of the catalog api correctly
[07:20am] emily_g: I'm sure we are not
[07:20am] jgarnett: (ie it would be bad form to start doing data access connection stuff at the layer level)
[07:20am] jgarnett: did you get my origional message to Tim?
[07:20am] emily_g: yes I did
[07:20am] emily_g: but I'm still working on understanding it
[07:20am] jgarnett: I tried to think it through ... but I may of missed something. I assume he had gone through Service / Renderer / Style tutorials.
[07:20am] emily_g: You said somewhere that we should just use the postgis connection in the catalog - I don't think we can guarentee this is already a connection in the catalog
[07:21am] emily_g: our client also has some "weird" requirements that they want the connection stuff as a different bundle; so what we do for them will probably be a bit different from what we do for udig
[07:22am] jgarnett: um the requirements are fine
[07:22am] jgarnett: you can add functionality to the udig postgis from a different bundle
[07:22am] jgarnett: backing up to the larger picture
[07:22am] jgarnett: we want to make sure the postgis connection pool is managed stupidly well
[07:23am] jgarnett: and it would be good to share the connection between the postgis datastore and the pgRouting api
[07:23am] jgarnett: is that okay / understandable?
[07:23am] emily_g: yes - you want one connection
[07:23am] emily_g: makes sense to me
[07:24am] jgarnett: well one connection pool
[07:24am] jgarnett: so for your customer do you have access to the udig catalog?
[07:24am] emily_g: aren't connection pools managed by geotools datastores?
[07:25am] jgarnett: (this conversation kind of has two parts; one about how to manage the connection pool and another about how to intergrate with the graph tools)
[07:25am] jgarnett: not really; when you construct a geotools datastore you can hand in a connection pool
[07:25am] jgarnett: (or you can specifiy a bunch of optional parameters and ask it to create you one)
[07:26am] jgarnett: either way will work here; we need to get access to the connection pool for the PostGISserviceImpl
[07:26am] jgarnett: (I think there may already be a resolve target - for ConnectionPool or Connection)
[07:26am] jgarnett: I am not too worried about that ...
[07:26am] jgarnett: mostly about defining an API to access pgRouting; and then making sure you can get the connection pool in behind that api
[07:26am] emily_g: the thing is in the end our client may not want a direct connection to postgis anyways
[07:27am] emily_g: they may want it go to through some middleware connection
[07:27am] jgarnett: Do you have an API for pgRouting yet?
[07:27am] jgarnett: ah right - fair enough.
[07:27am] jgarnett: even more important to make an API then
[07:27am] jgarnett: (and consider spring remoting when implementing the api for your client - in order to reduce the cost of setting up the middleware)
[07:27am] emily_g: yes and no; I'm not really ready to answer that question
[07:27am] jgarnett: okay np
[07:27am] emily_g: i'm still working on it
[07:28am] jgarnett: at somepoint here will be some methods right?
[07:28am] jgarnett: hand in a start and end point and get back a route; or whatever other services pgrouting offers (I have only read about it)
[07:29am] emily_g: yes it is basically that
[07:29am] emily_g: pass in some points & route type and get back geometry
[07:29am] jgarnett: thinking
[07:30am] jgarnett: sorry for the distraction on the postgis front; going through some middleware thing is a bit different
[07:30am] jgarnett: I would probably handle it by defining that API
[07:30am] jgarnett: and sticking that object on the map or layer blackboard
[07:30am] jgarnett: and defining the graph tools against that object (or graph wizard or whatever)
[07:31am] jgarnett: and then I would implement using geotools graph
[07:31am] jgarnett: and implement using the middleware
[07:31am] jgarnett: and if we have call to talk to postgis directly I would go off and play that game.
[07:31am] emily_g: that's sort of what we are doing I think
[07:31am] jgarnett: in some sense that makes defining the api easier; since it comes down to what you need the tools to be able to call.
[07:31am] emily_g: without the geotools graph stuff because that is already handled for us by pg routing
[07:32am] emily_g: the problem I was having was want to do with our pgRouting API implementation; but you are correct - we can put it on the map blackboard
[07:32am] jgarnett: in anycase feel free to manipulate the graph module into that shape; it may even be a helpful move for your project since it would allow you to test prior to the create of the middleware bit
[07:33am] jgarnett: ah right - putting custom components on the map (or layer blackboard) is the way to go.
[07:33am] jgarnett: you may find that you need a bit more lifecucle control;
[07:33am] jgarnett: ie if the layer was deleted you may want to be told about it?
[07:33am] jgarnett: if that is the case we may need to look at making the blackboard a little smarter (ie more into a container)
[07:34am] jgarnett: but no sense causing trouble unless you have the need I figure.
[07:34am] jgarnett: um you did this approach for the birds demo; so I thought it would be fresh in your mind
[07:34am] jgarnett: (still want to write that demo up for others)
[07:34am] emily_g: ya; and I've used it for the mapgraphic rendering problem;
[07:34am] emily_g: just didn't clue into it; too many other things going on
[07:35am] emily_g: i have a meeting shortly and I need to eat so I'm going to run away
[07:35am] emily_g: thanks for the help
[07:35am] emily_g: is there an official irc meeting tommorrow?
[07:35am] jgarnett: okay; I will post these logs; and spend the rest of the meeting timeslot here on sorting jira bugs.
[07:35am] jgarnett: Today is friday for me; and this is the meeting timeslot.
[07:36am] emily_g: okay I'm confused between what day it is
[07:36am] jgarnett: Andrea wanted to go over Jira bugs (in prep for a code sprint) tomorrow
[07:36am] jgarnett: np
[07:36am] jgarnett: that is what weekends are for; to help you organize what day is where (or when?)
[07:36am] jgarnett:
[07:42am] jgarnett: thanks for the chat emily

FOSS4G 2009: One week extension to Workshops and Tutorial submissions

2009-03-01T15:53:00.000-08:00

Sydney, Australia. 2 March 2009.

In response to requests from presenters, the deadline for the FOSS4G 2009 workshop and tutorial abstract submissions has been extended by one week, to Monday 9 March 2009. If you are considering submitting a workshop, please notify your intent by emailing the Workshop/Tutorial coordinator, Mark Leslie m a r k . l e s l i e AT l i s a s o f t . c o m

About FOSS4G

FOSS4G, held 20-23 October 2009 in Sydney, Australia, is the international "gathering of tribes" for open source geospatial communities. The theme for the FOSS4G 2009 conference will be "User Driven". Users and developers are encouraged present their latest projects and software to demonstrate the power of Open Source for system integration through a series of workshop sessions and tutorial presentations. Session participants should expect to see presentations on both geospatial open source and propriety software integration along with pure open source solutions.

Workshops

Workshops are expected to be a hands-on experience with participants following along with the instructor, working directly with the application under discussion. All workshop rooms will be equipped with computers (two students sharing one system) to support this vision. Workshop computers will pre-installed with a basic image containing standard packages running in a Windows XP environment. A projector will be provided for each computer room for use within a workshop. Instructors will need to discuss pre-installation requirements with the Conference Organising Committee if required.

Workshops are expected to require considerable effort to create, with past experience showing that three days of preparation per hour of presentation are required to produce a high quality workshop. Additionally you will be expected to develop material for attendees to take home with them, such as handouts, workbook, CD-ROMs etc. Due to the effort involved in producing and presenting a workshop, instructors will receive a single complementary registration to the conference for delivering a workshop.

All workshop submissions will be considered, but particular interest will be shown in the following topics:

Practical Introduction to ____
Integrating Open Source
Spatial Data Privacy and Security

Tutorials

Tutorial rooms will not be equipped with computers, however presenters may optionally make use of delegate laptops and the FOSS4G LiveDVD.

At least 80% of delegates are expected to be carrying a laptop and FOSS4G LiveDVDs will be given to all delegates.

Preference will be given to hands-on tutorials.

Any hands-on aspects to a tutorial will be the responsibility of the presenter and needs to be described in the tutorial description. Presenters making use of the Live DVD or Climate Change Integration Plugfest (CCIP) will be expected to contribute to testing pre-releases to ensure material and software is properly installed. To discuss your requirements for LiveDVD, please contact the organising committee: http://2009.foss4g.org/contacts/.

All tutorial submissions will be considered, but particular interest will be shown in the following topics:

Practical introductions
Interoperability
Spatial data accuracy
Spatial data privacy
Spatial data security
System implementation
Data migration

Submission instructions and templates are available at http://2009.foss4g.org/workshops/and http://2009.foss4g.org/tutorials/.

The deadline for workshop / tutorial submissions is March 9, 2009

IRC Logs Feb 27th

2009-02-26T12:51:00.000-08:00

uDig IRC meeting:

(7:09:51 AM) jgarnett: morning!
(7:10:00 AM) jgarnett: I am getting better at this (and getting better)
(7:10:10 AM) emily_g: good afternoon :P
(7:10:19 AM) jgarnett: this should be my last week of coming into the office early to attend these things
(7:11:06 AM) jgarnett: (finally ordered internet for my house)
(7:11:19 AM) jgarnett: I am going to send a quick email to the list and see if we can scare up more people
(7:11:21 AM) emily_g: how exciting
(7:11:35 AM) jgarnett: but there is some interesting things going on SoC, FOSS4G workshop deadline etc
(7:12:32 AM) jgarnett: how is your hacking going emily?
(7:13:12 AM) emily_g: good for now I think I'm mostly done what I need to do
(7:13:30 AM) emily_g: I'm still now sure how to deal with udig community module relying on the unsupported geotools module
(7:13:57 AM) emily_g: I've been committing a jar file which I know is a very bad thing :)
(7:14:03 AM) jgarnett: gak!
(7:14:07 AM) jgarnett: well there are two ways
(7:14:50 AM) jgarnett: 1. make the geotools module supported; we really should not be selling our customers less (the supported mechansim exists mostly as a measure of quality). The process work gdavis did is in a similar bind I am afraid
(7:15:12 AM) jgarnett: 2. do not make it supported; and make udig libs suck up the dependency
(7:15:29 AM) jgarnett: Question - is this just a code dependency? Or is does it need to hook into the geotools factory finder thing?
(7:16:14 AM) jgarnett: Finally you could have a refresh.xml script fetch the jar (copy the one out of libs); or we can modify the refresh.xml script in libs to copy the jar into your module (so there is still a single refresh.xml script to run)
(7:16:21 AM) jgarnett: but these are all good questions
(7:16:34 AM) emily_g: I'm not sure I understand what that means - the geotools factory finder thing ?
(7:18:41 AM) jgarnett: geotools has a plugin system
(7:18:53 AM) jgarnett: (ie not the plugin system eclipse uses; but one called FactorySPI that comes with java)
(7:19:18 AM) jgarnett: it depends on looking up a magic file in the jar MANIFEST
(7:19:35 AM) emily_g: Well my udig module doesn't make direct use of factory finders, but I think the geotools caching module may
(7:19:42 AM) jgarnett: actuall a magical folder called services/ that has text files listing all the "factory service provider interfaces"
(7:20:01 AM) jgarnett: the question is does your geotools caching modules have ones of these services/ folder
(7:20:16 AM) emily_g: no I don't think so
(7:20:18 AM) jgarnett: (you can see an example in geotools main; where the services directory is used to list all the function implementations for example)
(7:20:40 AM) jgarnett: okay; if it did have a services/ folder it would *have* to go into net.refractions.udig.libs or it would not work
(7:21:16 AM) jgarnett: what is your module that uses the caching?
(7:21:31 AM) jgarnett: is it your own community module; or did you need to work on the udig wfs module?
(7:22:00 AM) emily_g: it's my own community module
(7:22:06 AM) jgarnett: (aside here is the geotools documentation on factory spi - http://docs.codehaus.org/display/GEOTDOC/05+How+to+write+a+Plugin+-+from+Interface+to+Factory)
(7:22:22 AM) jgarnett: okay; since it is your own work everything is up to you
(7:22:42 AM) jgarnett: if you were intergrating this into core udig I would get all frumpy and do a code review
(7:22:43 AM) emily_g: community/emily/net.refractions.udig.catalog.wfs.cache
(7:22:53 AM) jgarnett: as a community module we can treat it as a proof of concept.
(7:22:57 AM) emily_g: well quiet frankly that's the boring code;
(7:23:04 AM) emily_g: the caching code in geotools is much more exciting
(7:23:35 AM) jgarnett: when/if you did want this in udig we would seriously look at cleaning up the geotools module and making it supported (either adding the functionality into core geotools or signing up as a module maintainer for the thing)
(7:24:08 AM) jgarnett: if I was your customer I would be asking for this of course :-) Perhaps you can suggest it as a phase 2 (now that you know the approach is worth following)
(7:24:29 AM) emily_g: hmm okay good advice
(7:24:30 AM) jgarnett: aside: Andrea was thinking of another code sprint; either based on a bug fix run or on a new functionality run
(7:24:41 AM) jgarnett: adding caching would be cool idea
(7:24:43 AM) emily_g: I'll put it on my list
(7:25:11 AM) jgarnett: (and would provide symetry with the TileCache work; uDig 1.2 would then feature caching for both wfs and wms resources)
(7:25:17 AM) emily_g: it would be nice to try to clean up some of the bugs in "core" functionality of udig
(7:25:36 AM) jgarnett: agreed; the code sprint format seemed productive.
(7:25:46 AM) jgarnett: I may as well ask if there is any good time slot for you this month?
(7:25:53 AM) jgarnett: perhaps we can set an initial time...
(7:26:04 AM) emily_g: no good time; jan-mar is usually bad time here
(7:26:13 AM) emily_g: april/may might be better but further off
(7:26:47 AM) emily_g: I would be willing to pick a bug or two and try to fix them in my spare time; but the problem I had with that
(7:26:55 AM) emily_g: is that I went and look a jira and got confused and scared
(7:27:59 AM) emily_g: I couldn't really easily figure out what bugs were current; what were fixed or what I could do that was useful
(7:28:08 AM) emily_g: I suspect that stems partly from my inexperience
(7:28:36 AM) jgarnett: it is partly from Jira bugs being automatically assigned to people who are not around anymore like Richard :-P
(7:29:03 AM) sidlon: basic question: if i have an image, like a satellite photo of an area... do you know if there's any way in uDig to display that along with shapefile data? would that be a raster layer?
(7:29:04 AM) jgarnett: I understand that year end is a bad time for you
(7:29:18 AM) jgarnett: yes that would be a raster layer.
(7:29:35 AM) jgarnett: many stellite photos have the information inside them about where they should be displayed.
(7:29:43 AM) jgarnett: if it is a simple png or jpg they will not
(7:29:51 AM) jgarnett: and you need a seperate text file to say where it should be on the world
(7:30:00 AM) sidlon: so if i have a jpeg, are there tools i can use to add the geo info to them?
(7:30:03 AM) jgarnett: (this is called the "world + image" format and is documented in the udig help menu)
(7:30:31 AM) jgarnett: you can actually just do it yourself with a text editor like notepad
(7:30:49 AM) jgarnett: a couple people have made tools for you to position the image on the screen; but I am not aware of any of them going public
(7:31:00 AM) jgarnett: let me find you a link to one that was written around udig (but not folded in)
(7:31:32 AM) jgarnett: http://udig.refractions.net/files/downloads/flightline/
(7:31:57 AM) jgarnett: here is documentation on the world plus image format
(7:31:58 AM) jgarnett: http://udig.refractions.net/confluence/display/EN/World+Plus+Image
(7:32:08 AM) jgarnett: hopefully that is enough to get you going?
(7:32:31 AM) jgarnett: as I said most satillite images will be in TIFF format; and when they fold the location information into the file it is called "GeoTiff"
(7:32:38 AM) jgarnett: where are you getting your photo from?
(7:32:49 AM) jgarnett: (it may already just work)
(7:32:50 AM) sidlon: i think this will definitely help. thanks!
(7:33:43 AM) sidlon: i'm looking to create an application that can accept satellite imagery & shapefiles (for roads etc) and display them together
(7:34:11 AM) jgarnett: well you found one
(7:34:30 AM) jgarnett: and if you go through the tutorials you will see how to create your own custom application (using udig as a base)
(7:34:44 AM) sidlon: then maybe write a plugin to generate an xml describing the combined scene
(7:35:05 AM) jgarnett: I hope you find the documentation in order; we have made some of the high quality intro documentation public on the website - but much of the advanced stuff is part of our commercial training course
(7:35:07 AM) jgarnett: ah!
(7:35:13 AM) jgarnett: there is already a plugin to do that
(7:35:19 AM) jgarnett: but I have not had a chance to make it work recently
(7:35:24 AM) jgarnett: perhaps you would like to work on it
(7:35:30 AM) jgarnett: a scene is called a "context"
(7:35:42 AM) jgarnett: so the plugin writes an "OWS Context" file
(7:36:09 AM) jgarnett: "ows" = open web service - but the actually do more than that now allowing people to document shapefiles; and google maps and stuff for the web programs.
(7:36:43 AM) jgarnett: At the very least the plugin can show you how to write you a description of a scene; and how to create a map when reading the description back in
(7:37:02 AM) jgarnett: http://www.ogcnetwork.net/context is the formal docs
(7:37:15 AM) sidlon: so far i'm definitely impressed w/ everything uDig can do... i really appreciate this help
(7:38:00 AM) sidlon: one last question... is there currently, or would it be possible for me to right, code to merge layers?
(7:38:08 AM) sidlon: (write)
(7:40:39 AM) sidlon: basically i'd like to make it possible for the user to load a number of shapefiles covering different areas and save them to a single shapefile
(7:40:54 AM) jgarnett: I would like to say yes
(7:40:58 AM) jgarnett: since you can do almost anything in code
(7:41:05 AM) jgarnett: but the shapefile format is limited to a single kind of feature at a time
(7:41:13 AM) jgarnett: (ie all points, or all lines, or all polygons)
(7:41:30 AM) jgarnett: also it only stores one kind of feature; so all the featues would need a single set of attributes
(7:41:38 AM) sidlon: gotcha... so if i had 2 polygon shapefiles, they could be merged maybe?
(7:41:43 AM) jgarnett: right now you can do that
(7:41:57 AM) jgarnett: load up one shapefile; select all, copy, and paste into your new layer
(7:42:01 AM) jgarnett: and repeate for the other layer
(7:42:10 AM) jgarnett: but understand that the attributes will not be merged or anything
(7:42:27 AM) jgarnett: look at the reshape operations for an example of how to manipulate attributes (rename; recalculate, etc...)
(7:42:27 AM) sidlon: ok. i think i understand. thanks again!
(7:42:42 AM) jgarnett: you would need to make both layers have the same attributes in order to merge them
(7:49:55 AM) jgarnett: okay I think we are winded down - thanks for the chat guys
(7:50:11 AM) emily_g: thanks jody
(7:50:13 AM) emily_g: have a great day

AXIOS UDIG EXTENSIONS 1.2-M2 (UNDER DEVELOPMENT)

2009-02-13T00:39:00.000-08:00

This release, available for uDig 1.1.1, include the following new operations:
- Fill Spatial Operation. It creates new geometries

using the reference lines, present in other layer, and the borders of the source polygons as their own borders.

- Hole Spatial Operation. It makes holes inside a polygon feature using valid LineStrings that are present in another layer, used as reference.

To test this new release please visit our web site www.axios.es download page. Here you can found the latest stable release Axios uDig Extensions 1.1.1 for uDig 1.1.1.

If you want to know more about this project visit the
following page: Spatial Operations and Editing Tools

IRC Logs February 14th

2009-02-12T13:10:00.000-08:00

(7:10:58 AM) emily_g: morning jody

(7:12:14 AM) silli: morning all!
(7:12:27 AM) silli: unfortunately moovida is sick
(7:12:36 AM) silli: and can not join the IRC
(7:15:34 AM) emily_g: I have a question about udig libs & building udig (I'm getting a bunch of errors)
(7:15:50 AM) jgarnett: okay cool; lets set an agenda ...
(7:16:12 AM) jgarnett has changed the topic to: 0) what is up 1) udig and building
(7:16:45 AM) jgarnett: I was thinking of talking to moovida about the table view problem I fixed; and seeing if anyone wanted to back port it to 1.1.x.
(7:17:08 AM) jgarnett: anything else worth talking about? We should be doing something with SoC I guess.
(7:17:28 AM) jgarnett: Right now the best thing we can do is make sure we have time to act as sponsors
(7:17:45 AM) jgarnett: sorry mentors
(7:17:55 AM) jgarnett: emily_g are you interested in mentoring this year?
(7:18:25 AM) emily_g: I have no idea what is involved in mentoring ...
(7:18:58 AM) jgarnett: there is a nice page on it somewhere; but the actual work kind of depends on how dialed in the student you get is
(7:19:39 AM) jgarnett: I have gotten away with code reviews and email before; others have had failure even with spending lots of time
(7:19:47 AM) jgarnett: Suppose I will send it to the email list ...
(7:19:49 AM) jgarnett: 0) what is up
(7:20:02 AM) emily_g: I will do some reading and think about it
(7:20:21 AM) jgarnett: jgarnett - fixed table view; not sure if anyone wants that backported to 1.1.x. May get some time to hack this weekend.
(7:20:50 AM) emily_g: emily - still poking away at feature caching
(7:22:37 AM) jgarnett: 1) udig and building
(7:22:47 AM) emily_g: so I updated udig this morning
(7:23:00 AM) jgarnett: so where are you at emily? there was some issue with imageio-ext jars not being deployed to the osgeo repo; but that is fixed now?
(7:23:01 AM) emily_g: and libs gives me errors
(7:23:08 AM) jgarnett: (I have not done that yet; let me try now)
(7:23:12 AM) emily_g: package org.geotools.arcsde.gce.band does not exist in this plug-in
(7:23:29 AM) jgarnett: ah
(7:23:30 AM) emily_g: same for org.geotools.arcsde.gce.imageio & org.geotools.arcsde.gce.producter
(7:23:41 AM) jgarnett: gabriel has been hacking away at arcsde hard these last couple of days
(7:23:50 AM) jgarnett: and some of the package names may of changed
(7:24:00 AM) jgarnett: so here are the two ways it could break us
(7:24:23 AM) jgarnett: - gabriel may be testing in udig; and updating udig as he goes; but if he has not deployed his geotools changes we will have trouble
(7:24:38 AM) jgarnett: - or he may of deployed his geotools changes; and nobody has updated udig libs yet
(7:24:58 AM) emily_g: I think it may be the second
(7:25:19 AM) jgarnett: There is a single button "update" you can do; called organized manifests ... I tend to do it by hand so I can hide a few projects that we
(7:25:22 AM) emily_g: as I don't see any commits related to sde in the last few days
(7:25:50 AM) jgarnett: I am going to duck over to the geotools list and ask
(7:26:30 AM) groldan [n=groldan@host179.201-253-34.telecom.net.ar] entered the room.
(7:26:35 AM) groldan: hello
(7:26:35 AM) jgarnett: hi gabriel
(7:26:46 AM) groldan: hi there
(7:26:53 AM) jgarnett: emily_g reports our udig build broken; something about package changes in arcsde
(7:27:04 AM) jgarnett: did you deploy your changes?
(7:27:16 AM) jgarnett: (if so we need to update udig libs)
(7:27:17 AM) emily_g: package org.geotools.arcsde.gce.band does not exist in this plug-in
(7:27:23 AM) groldan: hum, I only changed package names in the gce stuff
(7:27:28 AM) emily_g: same for org.geotools.arcsde.gce.imageio & org.geotools.arcsde.gce.producer
(7:27:38 AM) groldan: ok, so its just a matter of removing those packages from the manifest
(7:27:55 AM) groldan: yup, there's a single org.geotools.arcsde.gce package now
(7:28:00 AM) groldan: (we're doing more with less code)
(7:28:27 AM) emily_g: sounds good; I will remove them from the udig manifest and commit the fix
(7:28:29 AM) emily_g: thanks
(7:28:31 AM) groldan: so please just remove those packages from the manifest, I don't have a udig dev env at hand
(7:28:38 AM) groldan: thanks emily_g
(7:29:15 AM) groldan: FYI all this fuss is to have something like this: http://arcy.opengeo.org:8080/geoserver/wms?bbox=33001.0,774001.0,333001.0,961999.0&styles=&Format=application/openlayers&request=GetMap&version=1.1.1&layers=massgis:SDE.IMG_USGSQUADM&width=800&height=470&srs=EPSG:26986
(7:29:17 AM) groldan: :)
(7:29:49 AM) emily_g: nice :)
(7:30:17 AM) jgarnett: fun; performance seems good too
(7:31:06 AM) groldan: yup, thanks to JAI :)
(7:31:09 AM) jgarnett: gabriel your email on this subject was so dense I have not made it through yet
(7:31:20 AM) jgarnett: I trust Saul is giving you most of the feedback you need
(7:31:27 AM) groldan: ouch, I liked the rant
(7:31:29 AM) groldan: :/
(7:31:42 AM) jgarnett: is there anything else fun that you would like to talk about?
(7:31:46 AM) groldan: still, most of it shall go end up to the wiky though
(7:32:01 AM) jgarnett: (not a rant; you do not send email - and then you send one big one)
(7:32:16 AM) groldan: he, bad groldan
(7:32:45 AM) jgarnett: does arcsde support nD grids?
(7:33:07 AM) groldan: hum, supports N-band ones
(7:33:17 AM) jgarnett: yeah
(7:33:21 AM) dassouki [n=a_d@fctnnbsc15w-156034075039.pppoe-dynamic.nb.aliant.net] entered the room.
(7:33:24 AM) groldan: but I don't think it matches the nD concept
(7:33:47 AM) groldan: they're _rasters_, 2D
(7:34:00 AM) jgarnett: It kind of can; if you make your own color model based on the number of bands etc...
(7:34:02 AM) jgarnett: oh okay
(7:34:06 AM) jgarnett: that is fine; just asking
(7:34:19 AM) groldan: and yeah, I'm having a lot of fun to support raster catalogs now
(7:34:37 AM) jgarnett: reading your email about "fail if there is no support for the raster's format and number of bands" - I think you do not need to fail is all
(7:34:41 AM) groldan: see my previous chat with simboss at #geoserver
(7:34:54 AM) jgarnett: thinking
(7:35:02 AM) jgarnett: so what do you need to hook this up in uDig?
(7:35:13 AM) groldan: a little bit of time
(7:35:18 AM) groldan: (the spare one)
(7:35:19 AM) jgarnett: we need to be able to discover what grid coverages are available; how is that handled on the arcsde side?
(7:35:31 AM) groldan: but its something I really want to do
(7:35:41 AM) groldan: raster_columns table
(7:36:00 AM) emily_g: jgarentt - i removed those packages and now I get another error - libs is missing library lib/beam-1.0.jar; does this mean anything to you?
(7:36:08 AM) jgarnett: cool
(7:36:11 AM) jgarnett: thinking
(7:36:48 AM) groldan: yeah I can add an ArcSDERasterFormat.getAvaliableRasters():List method with ease
(7:36:52 AM) groldan: or such
(7:37:05 AM) silli left the room.
(7:37:17 AM) jgarnett: I have it in mine emily_g; but I can run again. What it would mean (if it is not there and you did your libs from scratch) is that beam is no longer a dependency
(7:37:33 AM) jgarnett: (we get random jars dropped on us via maven dependency; sometimes they go away as well)
(7:37:56 AM) jgarnett: groldan++ if you have a method like that we can make a list of raster children
(7:38:04 AM) jgarnett: um but are we likely to have a list of thousands?
(7:38:15 AM) jgarnett: like more than the number of tables
(7:38:38 AM) jgarnett: do they have any kind of organization to the raster? Or perhaps the rasters can be very big ... not really sure of the arcsde model
(7:40:52 AM) groldan: catching up...
(7:41:24 AM) groldan: list of thousands: you'll have a list as big as the number of rasters are registered, just like for FeatureTypes
(7:41:35 AM) jgarnett: fair enough
(7:41:41 AM) groldan: I don't quite get why you say more than the number of tables?
(7:41:56 AM) jgarnett: hopefully we can get some good descriptive information out of them as well; so users can find what they want
(7:42:11 AM) groldan: hehe, I'm your friend here
(7:42:21 AM) jgarnett: I have seen rasters represented as values in a database table before
(7:42:26 AM) jgarnett: a big old blob
(7:42:30 AM) groldan: check out http://arcy.opengeo.org:8080/geoserver/ows?service=WCS&request=GetCapabilities
(7:42:59 AM) groldan: look at the abstract info for the ones in the massgis namespace
(7:43:11 AM) groldan: I'm building quite a nice ResourceInfo here
(7:43:21 AM) jgarnett: SDE.IMG_COQ2001_CLIP_BOS_1 is an ArcSDE Raster
(7:43:25 AM) groldan: and made the geoserver config to get the default description from ResourceInfo
(7:43:32 AM) jgarnett: really? SDE.IMG_COQ2001.....
(7:43:38 AM) jgarnett: for the title :-)
(7:43:47 AM) groldan: uh?
(7:44:24 AM) groldan: what tile?
(7:44:27 AM) jgarnett: this looks like the ID has been turned into a tilte
(7:44:52 AM) jgarnett: for massgis:SDE.IMG_BWORTHOS_CLIP_BOS the title is SDE.IMG_COQ2001_CLIP_BOS_1 is an ArcSDE Raster
(7:45:24 AM) jgarnett: a lot of the titles have the " is an ArcSDE Raster"
(7:45:41 AM) groldan: agreed, bad
(7:46:00 AM) groldan: just the old geoserver way "XXX is a YYY Raster"
(7:46:34 AM) groldan: I can get something more useful from the table metadata but found they hardly set it
(7:47:01 AM) groldan: still, fallbacking to the table name seems like the only solution as for what ResourceInfo concerns?
(7:47:22 AM) jgarnett: agreed
(7:47:36 AM) jgarnett: I should check if ResourceInfo is allowed to have a null title
(7:47:46 AM) jgarnett: we are allowed to point out to users when their title is bad :-)
(7:47:46 AM) groldan: I realize you're thinking in udig where there's not an admin setting nice titles for you like in geoserver
(7:48:13 AM) groldan: we are
(7:48:21 AM) jgarnett: well if you give me the API
(7:48:33 AM) jgarnett: we can let users update the metadata from udig
(7:49:03 AM) jgarnett: aside: our idea of introducing "info" to geotools has kind of failed
(7:49:17 AM) jgarnett: we did not push it through the other datastore implemntations and thus it has not been picked up
(7:49:50 AM) jgarnett: emily_g how goes the build? still stuck on beam?
(7:50:05 AM) emily_g: I deleted it from the class path and everything works fine for me
(7:50:26 AM) emily_g: should I commit that change?
(7:51:07 AM) groldan: ok, deal: http://jira.codehaus.org/browse/GEOT-2337
(7:51:20 AM) jgarnett: yep
(7:51:38 AM) jgarnett: I am doing a fresh build here to make sure beam does not get dragged in from refresh.xml
(7:51:46 AM) groldan: I gotta go back trying to figure out the JAI Mosaic operation
(7:51:54 AM) jgarnett: it could be that beam is new; and the dependency has not been deployed to the repo yet
(7:51:57 AM) groldan: thanks for the chat, see you
(7:52:00 AM) jgarnett: ciao
(7:52:51 AM) CIA-8: UDig: egouge * r31109 udig/plugins/net.refractions.udig.libs/ (.classpath META-INF/MANIFEST.MF): fixes for updates to sde geotools jars & removal of beam from classpath
(7:53:10 AM) emily_g: I have another more geotools related question for you - I would like to add a bit of documentation about this caching stuff I've done.
(7:54:20 AM) emily_g: I think this is the original page - http://docs.codehaus.org/display/GEOTOOLS/SoC+2007+Caching+data
(7:54:41 AM) emily_g: should I modify this page , add a new one, or ask the geotools list?
(7:55:57 AM) jgarnett: question
(7:56:01 AM) jgarnett: is this thing its own module?
(7:56:23 AM) emily_g: ya it's an unsupported module
(7:56:25 AM) jgarnett: make a page here (http://docs.codehaus.org/display/GEOTOOLS/Module+Matrix) and link back to the SOC page
(7:56:25 AM) emily_g: gt-caching
(7:56:34 AM) jgarnett: we try and have just one developer notes page
(7:56:49 AM) jgarnett: this SOC page was kind of project notes; most students used it to report on their timeline and what they were doing
(7:57:26 AM) jgarnett: does that help?
(7:57:39 AM) jgarnett: Hopefully your hard work will leave this thing in a state it can be used
(7:57:46 AM) jgarnett: I never even asked for user documentation for this one
(7:58:43 AM) emily_g: i hope so too but I"m not use; I read through aaime list of requirements of a cache and this cache isn't that sophisticated
(7:59:10 AM) jgarnett: aaime has been talking about a cache
(7:59:16 AM) jgarnett: for 4 years
(7:59:20 AM) jgarnett: there are two good ways to do it
(7:59:28 AM) jgarnett: and nobody really knows which is great
(7:59:32 AM) jgarnett: until we build and profile
(7:59:39 AM) emily_g: So I'll add a link from the modules matrix page to the soc page and update the soc page with the modifications I've made
(7:59:41 AM) jgarnett: so I would not worry; it is faster then remote WFS access :-)
(7:59:53 AM) emily_g: yup :)
(7:59:55 AM) jgarnett: um
(8:00:05 AM) jgarnett: I would rather see you update the model matrics page
(8:00:10 AM) jgarnett: talk about the code
(8:00:51 AM) jgarnett: the SoC 2007 is over right?
(8:00:57 AM) jgarnett: what you are doing now is about the module
(8:00:59 AM) emily_g: yup
(8:01:07 AM) jgarnett: yup
(8:01:13 AM) emily_g: okay I'll make a new page for the module
(8:01:52 AM) jgarnett: I am running refresh.libs now
(8:02:12 AM) emily_g: what do the different colored stars mean?
(8:02:13 AM) jgarnett: if beam is not around then I you can commit your change. If not we have a mystery to solve first
(8:02:35 AM) jgarnett: At the bottom of the module matrics page it tells you
(8:02:46 AM) jgarnett: http://docs.codehaus.org/display/GEOT/Gold+Star+Quality+Assurance+Check
(8:03:01 AM) jgarnett: really primitive metric to report to users the state of maturity of the module
(8:03:09 AM) emily_g: umm I already committed my change to remove beam ...
(8:03:12 AM) jgarnett: idea stolen from the maven plugin system
(8:03:22 AM) jgarnett: ha ha; okay
(8:03:30 AM) emily_g: ya I got that; I was wondering what the difference was between red and yellow
(8:04:44 AM) kartben [n=kartben@pur31-3-82-240-189-250.fbx.proxad.net] entered the room.
(8:04:58 AM) jgarnett: yellow is good
(8:05:00 AM) jgarnett: red is bad
(8:05:07 AM) jgarnett: pass or fail
(8:05:28 AM) jgarnett: I would of just listed the number of stars but that is me
(8:05:34 AM) emily_g: ok I though no star meant fail -
(8:05:42 AM) emily_g: thanks
(8:06:19 AM) jgarnett: yeah I did as well
(8:09:46 AM) jgarnett: okay thanks for the meeting

Who bought the uDig blog a sparkling new dress?

2009-02-05T13:48:00.000-08:00

Coming from a very small scientific community as it is the one of JGrass, I must honestly say that I am not very used to people helping to make things better. Usually the do it yourself rule applies best.

Which is why I am glad when I see community members answer to other's community members questions in mailinglist.

And which is why I am even very glad when I am able to "force" a community member to add a small page of documentation.

But my goodness!!! What happened to this blog is amazing, I am almost choked up!

Paul, thank you so much on behalf of the uDig community for the elegant work done to bring this blog to the cadillac of blogs...

IRC Logs Feb 6th

2009-02-05T13:22:00.000-08:00

Agenda:

0) common love for udig 1.2

1) CQL bug in 1.1.x

2) SoC 2009

3) FOSS4G 2009

4) bug hunt with emily_g

(7:16:41 AM) jgarnett: well lets start; moovida i responded to your email asking what we could talk about
(7:16:52 AM) jgarnett: but really I do not mind what we talk about; what is important today
(7:17:14 AM) ***moovida notices that Jody thinks andrea borruso and me are the same person
(7:17:20 AM) jgarnett: (I have a report of a mistake in the CQL parser on uDig 1.1.x; if we fix this in GeoTools 2.2.x are their any plans to release a uDig 1.1.2?)
(7:17:28 AM) jgarnett: ...grr...
(7:17:30 AM) moovida: :) I noticed because of the nice extention point for import/export
(7:17:34 AM) jgarnett: are we up to three Andrea's now
(7:17:48 AM) moovida: there can be only ONE!!!
(7:17:51 AM) moovida: :)
(7:17:54 AM) jgarnett: I got in trouble with duplicate names on the deegree list as well
(7:17:56 AM) moovida: ok, or 10 or 100
(7:18:12 AM) moovida: the Germans are on Markus, right?
(7:18:33 AM) jgarnett: syep
(7:18:34 AM) mauricio: hi
(7:18:34 AM) moovida: Italians like Andrea
(7:18:35 AM) jgarnett: yep
(7:18:44 AM) jgarnett: okay lets make the most of what time we have
(7:18:51 AM) jgarnett: agenda topics
(7:18:53 AM) moovida: yep
(7:19:11 AM) moovida: planning of next sprint
(7:19:13 AM) moovida: :)
(7:19:22 AM) ***moovida thinks udig needs common love
(7:20:51 AM) jgarnett has changed the topic to: 0) common love 1) 1.2-M2 SDK 2) CQL bug in 1.1.x
(7:20:52 AM) moovida: for me nothing in particular, wanted to ask a bit about foss4g 2009, since some of the important ones are here :)
(7:21:06 AM) jgarnett has changed the topic to: 0) common love 1) 1.2-M2 SDK 2) CQL bug in 1.1.x 3) SoC 4) FOSS4G
(7:21:16 AM) jgarnett: 0) common love
(7:21:43 AM) moovida: what is the state of udig 1.2 now?
(7:21:54 AM) moovida: mauricio: were you able to fix that editing bug?
(7:22:05 AM) moovida: just asking
(7:22:13 AM) moovida: I guess time is short usually
(7:22:15 AM) mauricio: :(
(7:22:20 AM) mauricio: no
(7:22:24 AM) moovida: which is why i would propose a new common efforth
(7:22:31 AM) mauricio: I cannot work in it
(7:22:36 AM) moovida: don't worry
(7:22:39 AM) moovida: I understand
(7:22:43 AM) jgarnett: what editing bug?
(7:23:05 AM) moovida: but we need to boost udig 1.2,I have enough to keep 2 versios of JGrass uptodate :)
(7:23:15 AM) moovida: one we had at the code sprint
(7:23:22 AM) moovida: perhaps silli remembers?
(7:23:31 AM) moovida: I don't know exactly any more
(7:23:36 AM) moovida: mauricio?
(7:23:40 AM) mauricio: yes editing features
(7:23:53 AM) silli: it was the an editing bug
(7:24:09 AM) mauricio: the old geometry
(7:24:18 AM) silli: when editing a feature and commit the changes
(7:24:27 AM) silli: then you can not edit an other layer again
(7:24:50 AM) silli: and still there were some problems rendering the edited feature
(7:25:04 AM) jgarnett: okay I must of missed that part of the discussion
(7:25:09 AM) jgarnett: emily_g ping?
(7:25:21 AM) emily_g: yo
(7:25:28 AM) jgarnett: (Emily did some testing of the udig 1.2-M2 release against the walkthroughs and came up with an email)
(7:25:38 AM) jgarnett: we were talking about udig 1.2
(7:25:38 AM) emily_g: right - I only tested walkthough1
(7:25:45 AM) emily_g: none of the editing stuff - sorry
(7:26:08 AM) jgarnett: np; you did have some problems (like DnD from firefox)
(7:26:39 AM) emily_g: yes that is a bit of an intermittent problem; sometimes it works sometimes it doesn't
(7:29:18 AM) silli: moovida: could you please send us the spreadsheet link of the code sprint? all the unresolved bugs where written there
(7:29:19 AM) jgarnett: hrm
(7:29:34 AM) jgarnett: moovida I am not sure what else you would like out of this agenda topic at this time
(7:30:04 AM) jgarnett: I have some plans for udig 1.2 on the API side; I am slowly rolling out an ID class; and I owe you an extension point for stype handling.
(7:30:07 AM) moovida: :) a date Jody, a date, and people willing and happy to hack again a couple of days
(7:30:26 AM) jgarnett: ah
(7:30:33 AM) ***moovida the spreadsheet link: http://www.editgrid.com/user/aborruso/uDig_code_Sprint_2009
(7:30:48 AM) moovida: that is all, I would like to know
(7:30:51 AM) jgarnett: I do not have any plans right now; so I will be happy with whatever date you propose on the mailing list.
(7:31:19 AM) moovida: what about the others? opinions?
(7:31:35 AM) moovida: I would like to know if there is interest right now
(7:31:51 AM) moovida: so I can also plan for myself
(7:32:17 AM) jgarnett: There is interesting; I am just thinking of timing.
(7:32:43 AM) jgarnett: LISAsoft's own project using uDig (which jhudson was working on) is comming to an end.
(7:32:51 AM) moovida: Jody, we are interested, but to do some decent bugfixing
(7:32:55 AM) jgarnett: moovida it would be good to roll out the uDig 1.2-M2 SDK
(7:33:00 AM) moovida: we need some more then us two
(7:33:06 AM) moovida: some more coders and some testers
(7:33:16 AM) moovida: else it won't be worth it
(7:33:21 AM) moovida: in my opinion
(7:33:31 AM) jgarnett: you are correct
(7:33:33 AM) moovida: jgarnett: yes, you are absolutwely right
(7:33:42 AM) jgarnett: now the last code sprint did a lot of good
(7:33:57 AM) jgarnett: but if we have a code sprint too often they will not be a special event of fun and happiness
(7:34:02 AM) emily_g: I may be able to commit some time; but at the moment I'm rather focused on my wfs caching so now is not the best time
(7:34:24 AM) moovida: great emily_g
(7:34:26 AM) emily_g: I'm inclined to agree with jody that we should wait a bit
(7:34:26 AM) jgarnett: so I would like to roll out udig 1.2-M2 SDK and see the response; and we can ask people about another code sprint over the course of the week.
(7:34:32 AM) moovida: and I agree jgarnett
(7:34:38 AM) jgarnett: thinking
(7:34:41 AM) jgarnett: ha ha
(7:34:42 AM) jgarnett: evil idea
(7:34:43 AM) emily_g: I think people are still getting up to speed after the last code sprint that was done
(7:34:46 AM) moovida: it doesn't have to be now
(7:35:07 AM) moovida: what are you thinking about
(7:35:11 AM) jgarnett: perhaps if we have a code sprint on new features; or pet projects it would be fun. emily_g could work on feature caching; I could work on ID
(7:35:13 AM) jgarnett: etc...
(7:35:36 AM) moovida: that would be great fun... but...
(7:35:52 AM) moovida: don't you think that would add unstability to the base?
(7:35:55 AM) jgarnett: last time I said no to new features; I bet we could get a turn out if we offered to help people create new features.
(7:36:01 AM) jgarnett: yeah you are right :-P
(7:36:06 AM) jgarnett: we can keep that idea for later.
(7:36:15 AM) emily_g: i agree; that fixing the base functionality should be more important
(7:36:21 AM) moovida: hmmm, but the idea turns me on :)
(7:36:27 AM) jgarnett: think about it
(7:36:33 AM) jgarnett: and we can ask on the email list this week
(7:36:33 AM) moovida: we should mix a bit
(7:36:36 AM) moovida: probably
(7:36:45 AM) moovida: yes, lets see the response
(7:36:53 AM) jgarnett: 2) CQL bug in 1.1.x
(7:37:04 AM) mauricio: yes
(7:37:05 AM) jgarnett: I have a report of a bug in the CQL parser; which I ported to GeoTools 2.2.x
(7:37:21 AM) jgarnett: if I go and fix it; is there any plans to release a uDig 1.1.2?
(7:37:36 AM) jgarnett: Jesse put up a "teaser" of 1.1.2 but it never went anywhere
(7:38:31 AM) mauricio: I could have a look in 2.2x branch
(7:39:24 AM) mauricio: or you are working in it?
(7:40:09 AM) mauricio: I found problems with all spatial relations
(7:40:27 AM) mauricio: intersect, dwithin, etc
(7:41:00 AM) jgarnett: I do not even have 2.2.x checked out
(7:41:15 AM) jgarnett: indeed I ported CQL in a matter of days; and have not really got a code review from anyone.
(7:41:30 AM) jgarnett: I just found it so much fun on trunk; and the reshape operation is fun
(7:42:17 AM) mauricio: yes trunk is ok
(7:42:18 AM) ***moovida thinks reshape is very imprtant fun
(7:42:24 AM) jgarnett: okay well if there is a will to look at this problem; I will match the community by trying to make a 1.1.2 release - however I am really not in a good position to do so. So if we can hunt down jeichar it would be a better move all around.
(7:42:49 AM) jgarnett: (I am not confident my eclipse set up will let me make a good 1.1.2 release; and we would like to have an installer and stuff)
(7:43:25 AM) jgarnett: mauricio we can take this one to email?
(7:43:33 AM) mauricio: ok
(7:45:08 AM) jgarnett: 3) SoC
(7:45:22 AM) jgarnett: Who is on the SoC email list for osgeo?
(7:45:32 AM) moovida: i am
(7:45:39 AM) jgarnett: I am; and I saw Jesse
(7:45:55 AM) jgarnett: it looks like they are trying to get organized faster this year; due to the SoC program having less scope.
(7:46:17 AM) moovida: yes, same feeling
(7:46:48 AM) jgarnett: So far all I can think to do to prepair is work on the Ideas page; and try and be more specific - and clear out things that were done last time around.
(7:47:11 AM) jgarnett: I also think we should change our expectations for participation on email lists etc...
(7:47:17 AM) moovida: you said that students contacted you?
(7:47:30 AM) moovida: yes, last year was soooo disappointing
(7:47:38 AM) jgarnett: so far the successful students have been very outgoing and chatted on the email list themselves; the others I have had to hunt down their moderator and ask what is going on.
(7:48:21 AM) jgarnett: so I would be happy stating that we will only consider students that have introduced themselves to udig-devel before :-)
(7:48:30 AM) jgarnett: it is a low bar to pass; but I think it would get the point across
(7:48:35 AM) moovida: that is a great idea
(7:48:39 AM) moovida: absolutely
(7:49:57 AM) jgarnett: so I was only reading the SoC list for January; yesterday :-)
(7:50:08 AM) jgarnett: who is actually paying attention; do we have any deadlines or schedules to meet?
(7:50:34 AM) mauricio: I am here
(7:50:39 AM) moovida: :) no idea, I didn't see anything pass... but I am rather blind these s=days
(7:50:48 AM) moovida: we could ask Wolf
(7:50:52 AM) moovida: he is really helpful
(7:52:30 AM) moovida: anyone already some people?
(7:52:38 AM) moovida: jgarnett: did you talk about students?
(7:53:31 AM) jgarnett: one of the students from last year asked me if it was still on; that is what had me check the osgeo list
(7:54:00 AM) jgarnett: (mauricio I was trying to ask who was paying attention to the SOC list)
(7:54:05 AM) moovida: jgarnett: btw, I am a Phd right now and would be allowed to partecipate as student
(7:54:17 AM) moovida: somebody here to mentor me? :)
(7:54:19 AM) jgarnett: really; that is cool. Can you sponsor yourself?
(7:54:22 AM) mauricio: I am not in the soc
(7:54:37 AM) mauricio: but i am thinking tha it is interesting
(7:54:45 AM) moovida: jgarnett: what do you mean?
(7:55:00 AM) jgarnett: I was joking
(7:55:03 AM) moovida: if I would be willing to partecipate?
(7:55:04 AM) moovida: :)
(7:55:07 AM) mauricio: I could work with spanish students
(7:55:19 AM) moovida: ok, even if I talked to Wolf about this
(7:55:32 AM) moovida: I am very tempted
(7:55:35 AM) jgarnett: so in general we are keen here; we need to talk to wolf and work on the ideas page
(7:55:45 AM) moovida: after seeing Martin Landa from GRASS do the same and
(7:55:52 AM) moovida: achieve big things for GRASS
(7:56:05 AM) moovida: ok
(7:56:10 AM) pramsey left the room (quit: ).
(7:56:12 AM) moovida: let's go on
(7:56:44 AM) moovida: 4) FOSS4G
(7:56:52 AM) moovida: jgarnett: what is your feeling here?
(7:57:02 AM) moovida: you should be quite in it, right?
(7:57:09 AM) jgarnett: I am helping organize
(7:57:23 AM) jgarnett: right now my focus is on getting a machine for the "intergration showcase"
(7:57:30 AM) jgarnett: it has been tossed out of the foss4g team
(7:57:35 AM) jgarnett: and give to the OGC as a formal project
(7:57:45 AM) jgarnett: and called the "Climate Change Intergration Plugfest"
(7:58:05 AM) jgarnett: still the short term goal for me is a server to install postGIS/ geoserver/ mapserver on
(7:58:13 AM) jgarnett: with a bunch of climate change data
(7:58:28 AM) jgarnett: we will add servers as sponsors show up; and hopefully have a nice big shoot out
(7:58:42 AM) jgarnett: with large datasets and see who is standing and who fell at the end of the day
(7:58:55 AM) jgarnett: mark issues the call for workshops ... earlier this week
(7:59:04 AM) jgarnett: There is a *very* limited number of 3 hour slots
(7:59:04 AM) moovida: is there a scientific committee or is that all just for showing?
(7:59:12 AM) jgarnett: and no 90 mins slots this time out
(7:59:18 AM) moovida: i.e. is there some analisis and statistic on those data?
(7:59:34 AM) jgarnett: JGrass could showcase data anlaysis against that data set
(7:59:44 AM) jgarnett: indeed this is the point; for workshop people to use the data and serves
(7:59:54 AM) jgarnett: (since data access to europe or north america will be crap)
(7:59:56 AM) moovida: ahhh, now I understand, sounds really cool
(8:00:09 AM) jgarnett: so if we want to do a workshop; we need to put in a strong bid
(8:00:14 AM) jgarnett: and even then it will be tough.
(8:00:19 AM) moovida: silli: sounds to be something for you :)
(8:00:33 AM) jgarnett: they will also have small 90 min BYO laptop things during the conference
(8:00:35 AM) silli: are you thinking just on manage these data (db and show the raw data or some statistical interpretation) or also have some models?
(8:00:44 AM) jgarnett: but having a class bring their own laptop sounds crazy hard to me
(8:01:22 AM) jeichar left the room (quit: Read error: 110 (Connection timed out)).
(8:01:24 AM) jgarnett: um we will have vector and raster data; it is scientific groups in australia giving us the data - I have not sceen it yet so I do not know much.
(8:01:26 AM) jgarnett: thinking
(8:01:41 AM) jgarnett: maybe we could do a combined udig / jgrass workshop?
(8:02:00 AM) moovida: hui hui, now that would be fun
(8:02:03 AM) jgarnett: 90 min intro to open source software stack using uDig as the driver (like what we did in 2007)
(8:02:10 AM) jgarnett: and roll over to installing jgrass plugins
(8:02:16 AM) jgarnett: and attacking the climate change data?
(8:02:31 AM) jgarnett: in anycase this is something for the email list
(8:02:36 AM) moovida: yes, that sounds like big power
(8:02:37 AM) moovida: :D
(8:02:45 AM) moovida: ok, agreed, can you keep us up to date?
(8:02:56 AM) jgarnett: but at least this year; please have no hard feelings if we do not get a workshop - there are only like 16 slots or 12 slots or something
(8:02:56 AM) silli: :D
(8:03:04 AM) jgarnett: the presentations are like normal
(8:03:23 AM) jgarnett: the BYO laptop thing can be hands on; or maybe just show and tell; I do not really understand.
(8:03:34 AM) jgarnett: And there will be a code sprint :-)
(8:03:51 AM) moovida: not after the last night of party please
(8:04:00 AM) jgarnett: looks like google is going to offer us digs; and they are 2 blocks away from lisasoft offices if you guys want to go longer.
(8:04:26 AM) jgarnett: and I will try and do pancakes again :-)
(8:04:35 AM) moovida: mauricio: are you going to attend?
(8:04:42 AM) mauricio: yes
(8:04:43 AM) moovida: you have to taste Jody's pancakes :)
(8:04:47 AM) jgarnett: (if you liked the big truck rental in Canada; here they have muscle cars)
(8:04:54 AM) mauricio: ;)
(8:05:04 AM) moovida: silli: did you hear that!! :D
(8:05:44 AM) silli: yes!!!!
(8:05:55 AM) jgarnett: yep it is like the 50s in north america; they still make v8 monsters; the scary ones are not a car but a car/trunk called a ute
(8:05:58 AM) silli: moovida: we should do everything to partecipate...
(8:06:06 AM) jgarnett: where they have a truck bed for the back; which is lighter so they can go faster
(8:06:24 AM) moovida: :D
(8:06:30 AM) silli: :D
(8:06:51 AM) silli: absolutely fantastic!!!
(8:06:54 AM) jgarnett: well as time goes on I would love help organizing the code sprint; reminding people to be organized; etc... if the conference starts making profit the code sprint may get food service as well
(8:07:05 AM) jgarnett: (not sure how much of this I am supposed to be saying)
(8:07:20 AM) jgarnett: and this climate change thing is going to be fun
(8:07:22 AM) moovida: remove it from the logs
(8:07:28 AM) jgarnett: but it will be really hard to get the open source communities to notice
(8:07:29 AM) moovida: we won't tell anyone :)
(8:07:40 AM) jgarnett: (or even understand that their fav datasets are too far away to be useful)
(8:08:06 AM) jgarnett: so as Mark Leslie and I start standing up servers; maybe we can make some blog posts or flash videos
(8:08:11 AM) jgarnett: showing how to abuse the data
(8:08:21 AM) jgarnett: I worry a bit with this as an OGC thing
(8:08:22 AM) moovida: yes, do that, I really hope we will be able to produce something usefull
(8:08:29 AM) jgarnett: the open source community will not feel as invoved
(8:08:35 AM) jgarnett: (sorry involved)
(8:09:03 AM) jgarnett: finally I have a funny story
(8:09:22 AM) moovida: ?
(8:09:38 AM) jgarnett: One of the cool helpful geotools developers
(8:09:47 AM) jgarnett: (Michael Bedward)
(8:09:49 AM) jgarnett: and I
(8:09:54 AM) jgarnett: finally noticed we were in the same city.
(8:10:02 AM) moovida: lol
(8:10:06 AM) silli: lol
(8:10:08 AM) moovida: he told me last week
(8:10:12 AM) jgarnett: so I am not complete stranded over here; it took us three months to notice
(8:10:14 AM) moovida: Ididn't figure out
(8:10:53 AM) jgarnett: In anycase we are coming up on an hour here; I am glad we are all having fun; and foss4g is going to rock out :-)
(8:11:09 AM) moovida: great
(8:11:14 AM) moovida: thanks for the chat guys
(8:11:40 AM) jgarnett: I will try and upload a 1.2-M2 sdk; but I will need testing (to see of the source code for geotools got in etc...)
(8:11:45 AM) emily_g: jody - before you run away I have a question about the image support on trunk & the problems graham was having yesterday
(8:11:49 AM) jgarnett: it is supposed to be building now; I was hoping to anounce it this meeting.
(8:11:53 AM) jgarnett: ah
(8:11:56 AM) jgarnett: sure
(8:12:13 AM) jgarnett: gdavis did not have his log on; so he did not notice the strack tace
(8:12:17 AM) emily_g: basically I did a clean/refresh/clean/build/restart and I still can't view mr.side files
(8:12:19 AM) moovida: gdavis_: is it possible to try out your sperimental plugins?
(8:12:22 AM) jgarnett: I forgot a null check and was killing it
(8:12:36 AM) emily_g: it's working for graham so its just my comptuer
(8:12:44 AM) emily_g: I was wondering whether you have any ideas for debugging?
(8:12:44 AM) jgarnett: gdavis also was using the wrong imageioext jars
(8:12:47 AM) jgarnett: he had 1.0.0
(8:12:49 AM) jgarnett: not 1.0.1
(8:13:22 AM) jgarnett: can you check what you have emily? before we start ... you may need to smack refresh.xml pretty hard (ie clean out the libs directory and then run)
(8:13:23 AM) emily_g: min all say 1.0.1
(8:13:39 AM) jgarnett: okay that is the first thing; you also have a JRE with all the imageio-ext stuff?
(8:13:57 AM) jgarnett: (note we still do not have a good JRE for the windows platform; we need to make a new one that can do ecw as well)
(8:14:07 AM) emily_g: yes - I'm using the same one as graham
(8:14:30 AM) jgarnett: okay; what is next ... what is your error? We have two debugging techniques
(8:14:38 AM) jgarnett: - consol log and look for strack trace
(8:14:51 AM) jgarnett: - place a breakpoint in the service extension and watch it process the URL
(8:15:18 AM) emily_g: okay ; I'll try those
(8:15:21 AM) emily_g: i'm not getting any error
(8:15:27 AM) emily_g: when I drag and drop a file it doesn't nothing
(8:15:40 AM) jgarnett: all that means is that it did not find any service extension that "recognized it"
(8:15:43 AM) emily_g: and when I open the file using the file menu it just hangs on the loading resource dialog box
(8:15:45 AM) jgarnett: so we need to put that break point in
(8:16:02 AM) jgarnett: so to debug this we will use debugging technique number 2
(8:16:15 AM) silli left the room (quit: Remote closed the connection).
(8:16:38 AM) jgarnett: suppose I should post the logs
(8:16:41 AM) emily_g: okay jody I'll try it out when I get the chance; at the moment I'm a bit sidetracked
(8:16:45 AM) emily_g: thanks for the ideas
(8:16:54 AM) jgarnett: okay; I will be on IRC on and off
(8:17:00 AM) jgarnett: so ping me when you get to the debugging part
(8:17:00 AM) emily_g: if I find anything major I'll post it to the list; most likely I'm just doing something stupid
(8:17:18 AM) jgarnett: (not gdavis also had problems with the code tripping up over spaces in the path)
(8:17:26 AM) jgarnett: heh - not you
(8:17:31 AM) jgarnett: blame the computer :-)
(8:17:41 AM) jgarnett: for extra fun "svn blame" will tell you who committed the error
(8:21:01 AM) emily_g: :)

(8:21:36 AM) jgarnett: aside: did you guys see the blog site now
(8:21:40 AM) jgarnett: pramsey made it look pretty
(8:22:21 AM) moovida: WOW!!!
(8:22:48 AM) moovida: that is better than the official JGrass homepage
(8:22:50 AM) moovida: :D
(8:22:58 AM) moovida: good Paul
(8:25:44 AM) jgarnett: well next time you see him online; be sure to thank him

uDig 1.2-M2

2009-01-29T19:00:00.000-08:00

We are pleased to make a milestone release of uDig 1.2 available for testing.

This release gathers up all the great work accomplished during the January 18th code spint. This is the first release of uDig 1.2 that has gone through QA testing; a big thank you to all the testers who helped out during the code sprint.

Milestone releases are available here:

http://udig.refractions.net/download/unstable/

In addition we would like to thank Geo Solutions for their assistance in integrating the imageio-ext library earlier this week.

User-friendly Desktop Internet GIS

This week in uDig - January Week 1

uDig 1.3.0 Released

Release Details

About uDig 1.3

Adding CheatSheets Interactive Help to uDig

This week in udig - Sep - Week 4

Tool Palette and Options

Palette

Extension

uDig Source Code Visualisation

THIS WEEK IN UDIG - SEP - WEEK 3

THIS WEEK IN UDIG - SEP - WEEK 2

THIS WEEK IN UDIG - SEP - WEEK 1

THIS WEEK IN UDIG - AUGUST - WEEK 3

THIS WEEK IN UDIG - AUGUST - WEEK 2

This week in uDig - August - Week 1

This week in uDig

uDig 1.2.2 Released

Release Details

About uDig 1.2.2

Running the Image Georeferencing View. Release 1.0.0 for uDig 1.2.1

Image Georeferencing View RC3 for uDig 1.2.1

Image Georeferencing View for uDig 1.2.1

udig development version available for osgeo4w users

Spatial Operations Tutorials for Udig 1.2.1

Spatial Operations & Editing Tools for uDig 1.2.1

uDig 1.2.1 Released

Upcoming uDig Training

Axios uDig extensions - Releases 1.3.2 and 1.2.9

Axios uDig Extensions release 1.3.1 for uDig 1.2.x

UDIG 1.2.0 Release

Installation

About uDig 1.2 Series

About uDig 1.2.0

Release Notes

Known problems:

Axios uDig Extensions releases 1.2.5 for uDig 1.1 and 1.3.0-m6 for uDig 1.2

Open Source Blueprint

uDig 1.2 Release Candidate 3

Reusing Existent Spatial Operations

Google Summer of Code 2010

Introduction

Roadmap

Further reading

uDig 1.2 Release Candidate

About uDig 1.2 Release Candidate 2

Axios uDig Extensions release 1.2.4 for uDig 1.1

uDig 1.2 M9

Installation

About uDig 1.2 Milestone 9

About uDig 1.2

Axios uDig Extensions 1.2.3 for uDig 1.1

Is coverage styling finally coming to uDig?

How to add a new spatial operation

AXIOS UDIG EXTENSIONS 1.2.2

New UDIG3D alpha release!!

uDig 1.2 M6

AXIOS UDIG EXTENSIONS 1.2.0

FOSS4G2009 presentations about uDig and friends

IRC meeting about post code sprint release

Code Grind 09 wrap up

uDig Code Grind Day 4 Australia

uDig Code Grind 2009 Europe Day 3

The uDig Code Grind Team

uDig code grind day 2

uDig Bug Crunch Day 3 Australia

uDig Code Grind Day 2 Australia

uDig Code Grind 2009 Europe Day 1

Code Grind Sprint Day 1 Kickoff

LISAsoft Team

Eclispe 3.5

RoadMap and Testing

New Server

AXIOS UDIG EXTENSIONS 1.2.0-RC01 (Testing)

uDig Code Grind 2009 coming up!

WireframeSketcher

Google Summer of Code 2009

uDIg 1.2-M4 Released

UDIG 1.2-M3 Released