[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [udig-devel] today's IRC meeting: console design
|
[...]
> I would like to know more about the JGrass workspace definition - is
> their javadocs I can review?
Not really, there is nothing right now well documented in java. We
follow the GRASS folder structure concept, which holds all the
informations needed about projection, region and whatever needed to have
one safe place in which to process stuff.
> The catalog is more used to manage known resources (the local catalog is
> used to manage
> connections to resources).
>
> Individual GIS activities are free to provide their own grouping of
> *data* (rather then connections):
> - MapEditor - works with the concept of projects, maps and pages
> - Analysis - apparently works with a "workspace" as defined by JGrass
>
> That sounds good to me ... am I missing something?
No, it sounds great to me also :)
>> 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.
>>
> I really am not understanding something here in terms of workflow - if
> it helps you could define
> a "scratch" workspace to use is when analysis is performed in an ad hoc
> fashion?
I don't get exactly what you mean here, we can talk in the IRC meeting.
Andrea
