For today's IRC meeting I added an image to the following page: http://udig.refractions.net/confluence/display/JGRASS/consoleenginedesign
In the last days me and another developer discussed a bit the issues rerlated to the creation of a console engine that should deal with analysis commands execution. We tried to decouple the whole console block from UDig in order to be able to use the analysis engine also from geoserver. We can shortly (hopefully :)) discuss it in today's meeting. An important issue to discuss will be the fact that we couldn't find a way to not use the JGrass workspace definition for the analyses. The catalog is related to virtually every datatype, projection and even graphics... for analyses we need a container of consistent data to refer to. If it goes like we see it, for analyses a GRASS workspace will have to be defined and external data will have to be imported into it in order to work on them. Grassers are used to it, but udiggers, living in a world with less rules in this sense probably will experience problems. So please think about it and express your opinion about that. Andrea _______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
