Hi, > A long time ago we had a team splitting permanent field polygons into smaller > polygons presenting annual crops inside the fields. We had to fill in some > attributes for each crop polygon from application papers and also some data > based on our own satellite image interpretation. In that kind of work it was > important to make the annual crop polygons ready at once while operator had > the application form available and therefore instant noding was needed. I see, interseting application. Wonder if instant noding (or normal noding) mixed with snapping options of edit tools (snap to nodes and snap to lines) would be sufficient to avoid small undershoots and overshoots.
> The software we used was very clever for that certain purpose. It was > possible to define some line layers like a road layer so that new features > automatically made nodes to field boundaries (base parcels, probably called > ilots in France). Some other layers like power line layer or underground > pipework layer were not noded with fields. > > It looks like OJ does not have a tool for finding intersecting features from > the same layer. All the spatial operations are needing a source layer and a > mask layer. I wonder if it could be possible to make some temporary logical > layer from the selected features to be used as a mask layer? Actually, the new noder plugin works on a single layer. Noding has often to be performed on a single layer, and if not, it is quite easy in OpenJUMP to gather several layers into one, then to separate again the layer into several layer after processing. With this two (three) steps technique, the only restriction is you can't node objects of layer A intersecting objects of layer B but create nodes only on layer A (except if one is a line and the other a polygon). Michaël > > -Jukka Rahkonen- > > > Michaël Michaud wrote: > >> Hi Jukka, all, >> >> Interesting idea. Not an easy task, but now, most of the code exists. >> Not sure what would be the benefit compared to digitizing >> roads noding >> them in one step, then creating your polygons. >> >> One difficulty would be to define options (all options in the >> new noder >> plugin would also make sense in an interactive context) >> Another difficulty is to index features to find candidates to noding >> efficiently, as stefan told >> >> In order to re-use what has been done without duplicating too much, I >> think I would proceed the following way : >> - use existing digitizing tool and extend them (ex. double >> click creates >> the line, double click + key 'n' creates the line and node it) >> - use existing plugin options panel to read the user preference >> (eventually duplicate the panel to have it in the options dialog box) >> - try without indexing >> >> Michaël >> >> PS : I updated the documentation about noder >> https://sourceforge.net/projects/jump-pilot/files/Documentatio > n/PlugIn%20Documentation/Noder%20PlugIn/ >> >> >> Le 02/01/2012 18:13, Stefan Steiniger a écrit : >>>>> but a question.. how do you deal with layers that have >> lots of objects? >>>>> (OJ would be in-responsive) >>>> how is the noder plugin dealing with it? is it capable to >> find overlaying geometries (in a performant manner) or are >> they manually selected beforehand? >>> The noding is done on a whole layer (FeatureCollection). so >> nothing is >>> left out - as far as I know (Michael may know more on Topology >>> operations based on JTS). >>> >>> If one would use an index to speed things up, one would >> have the issue >>> that merging/updating of the dataset needs to appear, which >> will be tricky. >>> stefan >>> >>> >> -------------------------------------------------------------- >> ---------------- >>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't >> need a complex >>> infrastructure or vast IT resources to deliver seamless, >> secure access to >>> virtual desktops. With this all-in-one solution, easily >> deploy virtual >>> desktops for less than the cost of PCs and save 60% on VDI >> infrastructure >>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> Jump-pilot-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >>> >> >> -------------------------------------------------------------- >> ---------------- >> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't >> need a complex >> infrastructure or vast IT resources to deliver seamless, >> secure access to >> virtual desktops. With this all-in-one solution, easily >> deploy virtual >> desktops for less than the cost of PCs and save 60% on VDI >> infrastructure >> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox >> _______________________________________________ >> Jump-pilot-devel mailing list >> Jump-pilot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> > ------------------------------------------------------------------------------ > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
