Re: [udig-devel] Heap space error adding/removing graphical layers

[Jesse Eichar <jeichar@xxxxxxxxxxxxxxx>]

Hi

There are 2 main possibilities that I can think of.

1.  Make sure that you are passing in a heap space parameter to your  
X-BeenThere: udig-devel@xxxxxxxxxxxxxxxxxxxxx
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: User-friendly Desktop Internet GIS <udig-devel@xxxxxxxxxxxxxxxxxxxxx>
List-Id: User-friendly Desktop Internet GIS <udig-devel.lists.refractions.net>
List-Unsubscribe: <http://lists.refractions.net/mailman/listinfo/udig-devel>, 
	<mailto:udig-devel-request@xxxxxxxxxxxxxxxxxxxxx?subject=unsubscribe>
List-Archive: <http://lists.refractions.net/pipermail/udig-devel>
List-Post: <mailto:udig-devel@xxxxxxxxxxxxxxxxxxxxx>
List-Help: <mailto:udig-devel-request@xxxxxxxxxxxxxxxxxxxxx?subject=help>
List-Subscribe: <http://lists.refractions.net/mailman/listinfo/udig-devel>,
	<mailto:udig-devel-request@xxxxxxxxxxxxxxxxxxxxx?subject=subscribe>
X-List-Received-Date: Tue, 05 Dec 2006 21:48:53 -0000

Sort of...

"Merge" takes a selection in the layer and merges just those feature.
"Union" take two input layers and makes a new one.

They really are quite different operations... I think you might 
distinguish between "tools" which work on layers in place and 
"operations" which process inputs to create outputs?

I wonder what Adrian thinks?

P

Victor Mauricio Pazos wrote:
> thanks Paul for your reply.
>
> Some products, as ArcMap, have two operation Merge and Union. 
>
> In Merge source layer and target layer must be the same (this operation 
> deletes source features).
> In Union source layer and target layer must be not equals (this does not 
> delete source).
>
> We are thinking about if is needed two operations, Merge and Union, because 
> the tool can distinguish one or other situation detecting if the user has 
> selected a different layer as target (source != target ).
>
> If you agree with "option 2" then, Can we infer that only one operation is 
> required?
>
> Regards
>
> On Tuesday 05 December 2006 20:19, Paul Ramsey wrote:
> > Option 2, clearly. If you are running operations that create new
> > data, the source data should be left unchanged.
> > P
> >
> > On 5-Dec-06, at 11:17 AM, Victor Mauricio Pazos wrote:
> > > Hi, we are defining the merge operation, the team has the follow
> > > question:
> > >
> > > Transaction Merge "FA merge FB =?"
> > >
> > > 1) First option:
> > > - deletes FA and FB from source layer
> > > - creates new  FMerge on target layer
> > >
> > > 2) Second option:
> > >
> > > - if target layer is equal to source layer then "deletes FA and FB"
> > > from
> > > source layer; else no action.
> > > - creates new  FMerge on target layer
> > >
> > > As you can see the first option always delete the source features.
> > >
> > > The following link has the first idea for Merge operation.
> > >  http://udig.refractions.net/confluence/display/COM/Axios
> > >
> > > What do you think that is the best approach for Merge Transaction?
> > >
> > > Thanks in advance
> > > --
> > > Mauricio Pazos
> > >
> > > Axios Engineering
> > > www.axios.es
> > > e-mail: maurcio.pazos@xxxxxxxx
> > > tel-:+34 94 441 63 84
> > > fax: +34-94 441 64 90
> > > _______________________________________________
> > > User-friendly Desktop Internet GIS (uDig)
> > > http://udig.refractions.net
> > > http://lists.refractions.net/mailman/listinfo/udig-devel
> > _______________________________________________
> > User-friendly Desktop Internet GIS (uDig)
> > http://udig.refractions.net
> > http://lists.refractions.net/mailman/listinfo/udig-devel