I really garbled the first paragraph of that last post. Let me try again: It turns out you set the Geometry for a feature in the AbstractBasicFeature class, not in the BasicFeature class. This meant the geometry modification was not being counted as an attribute modification. (I'm still not sure why two edits to a geometry were counted by my modification to the AbstractBasicFeature class, but not a single edit. This is odd.)
The Sunburned Surveyor On Mon, Jan 11, 2010 at 2:26 PM, Sunburned Surveyor <sunburned.surve...@gmail.com> wrote: > Turns you set the Geometry for a feature in the AbstractBasicFeature > class, not the BasicFeature class. This meant the geometry > modification was not being counted as a modification. (I'm still not > sure why two edits were counted, but not a single edit. This is odd.) > > At any rate, I was able to override the setGeometry method in > BasicFeature to fix the problem. The Select Modified Features plug-in > now detects when a single node has been moved, added to, or deleted > from a feature geometry. > > I'll have the plug-in out in my next BizzJUMP release. Maybe this week > if I get time. Wouldn't take much to port it to OJ if someone needs > it. > > The Sunburned Surveyor > > On Fri, Jan 8, 2010 at 3:08 PM, Sunburned Surveyor > <sunburned.surve...@gmail.com> wrote: >> A while back we had a pretty intense discussion about creating a >> mechanism to track modified features. I think we then decided to >> modify the the BasicFeature class to track attribute modifications and >> also whipped up a plug-in to track modified features. I didn't see >> this plug-in included by default in the OpenJUMP 1.3.1. >> >> I'm trying to implement the same tracking mechanism in BizzJUMP. It >> seems I'm having trouble getting this system to recognize a feature as >> modified when I just move a single node. The same feature is modifed >> if I move more than one node, or if I move the same node twice. As far >> as I can tell, this problem doesn't seem to be in the plug-in. I also >> can't see an obvious problem with the logic to track moficiations in >> the BasicFeature class. >> >> I almost wonder if the problem is with the way JTS compares geometries >> for equality. (When an attribute is set in BasicFeature it is tested >> for equality. If the attribute values are equal, the change isn't >> marked as a modification.) >> >> I'm still troubleshooting this, but I appreciate suggestions on what >> might be tripping me up. If I can get this bug fixed, and there is >> interest, I can create a plug-in for OpenJUMP that will select >> modified features. >> >> Thanks for the help. >> >> The Sunburned Surveyor >> > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
