| Re: [udig-users] vector operations and attribute table management |
G. Allegri wrote:
I will need you to be a bit more specific; we do have support for validation constraints (they are something you can runn to produce issues; rather than enforced during editing). This is an area where we will need to see what developers wish to volunteer for; or what customers wish to fund.TOPOLOGY SUPPORT What is the state of topology support? I mean, topological editing and topoloigcal rules.
If you mean network topology and rout finding you will see that I have added the net.refractions.udig.graph module to trunk which can be used as a starting point.
Review the "Reshape" operation in uDig; the only it cannot do in your list is joins; I need to have a better understanding of what people expect from joins (and the above comment about time/money establishing direction also applys).ATTRIBUTE TABLES / DB At the moment there's support for CQL queries. Are you considering to delegate the other operations to external sw (like, i.e., Excel or OpenCalc) to do field calculation, tables join, table management (add-remove fields, for exemple), or is it in your roadmap?
Right now the state of the art is actually considerably beyond the recent uDig 1.1.0 release; uDig trunk has vastly improved raster support - and an amazing amount of work done on the rendering side (supporting tile servers; caching tiles for smooth panning etc...).Ok this is a short summary of the questions I would have done, but I've seen the longer requests about the same arguments have been sent in the past [1]. It's just to know the state of the art and what I should expect from the future :-)
I am not sure exactly how we can get this work into the hands of the community; something for this weeks uDig meeting.
Jody