Jukka, Thanks for the PDF. I didn't know about the image manager tool. I'm going to see if I can make time to find out more.
Landon On Wed, Feb 29, 2012 at 5:05 AM, Rahkonen Jukka <jukka.rahko...@mmmtike.fi> wrote: > Hi, > > I would like to make the document a bit better before putting it into wiki. > But if it goes as it tends to go, there probably will not be any extra time > for fixing it and after some lag period I will let it go as it is. > > When our governments will supply us with masses of fine raster maps and > aerial/satellite images the image index layer will be very valuable. OpenJUMP > can handle at least 50 image files in ECW or JPEG2000 format in one virtual > layer even without scale limits. > > I was hoping that a dedicated file name extension would help OpenJUMP to > understand that it should not show the JUMP GML file as vectors. Sometimes it > might still be good to be able to edit it as a normal vector layer. For sure > there will be cases when the drive letter of USB-drive changes and index file > would come useless, or images are moved to new locations for some other > reason. But perhaps it could be handled better by adding a new Open Image > Index entry into Open File dialogue. > > > -Jukka- > >> -----Alkuperäinen viesti----- >> Lähettäjä: Michaël Michaud [mailto:michael.mich...@free.fr] >> Lähetetty: 29. helmikuuta 2012 14:44 >> Vastaanottaja: OpenJump develop and use >> Aihe: Re: [JPP-Devel] Improving and renaming the Image Layer >> Manager tool >> >> Hi Jukka, >> >> Thanks for sharing your knowledge and ideas about this tool. >> >> I think your document could be put in the wiki (just see that >> entry for >> this tool is actually missing in >> https://sourceforge.net/apps/mediawiki/jump-pilot/index.php?ti > tle=Layer_Menu) >> >> You can create a link from this wiki page to a new page entirely >> dedicated to this tool. >> If you prefer, I can also upload your doc to sourceforge files >> documentation section >> (in this case, it would be useful to have your name and a date in the >> document I think) >> >> I have not a clear idea about how your proposal would improve >> OpenJUMP >> as I don't >> use images very often (and will have no much time for that in a near >> future). >> By the way, I'm curious about what problem creating another file >> extension for images >> index files would solve. >> Just as a side note, I think that internally, image layer >> management is >> the same as >> vector's in that rendering pipeline displays in-memory features which >> envelope >> intersects the viewport. >> Difference is in the "style", which is in charge of the image >> display in >> the case of a >> image layer. In this case disk accesses to read images are only >> performed for images >> to be displayed. >> >> Michaël >> >> >> >> > >> > Hi, >> > >> > I wrote a short document about the OpenJUMP Image Layer >> Manager tool. I have a feeling that it is not much used so I >> took a bunch of screen captures for showing what is does and >> how it is used. In the end of the document there are a few >> suggestions for making this fine tool better. In few words I >> recommend to rename the tool to something that describes the >> tool better, like Image Index Manager, and to make it >> possible to save and open OJ image index files more >> conveniently than now. >> > >> > http://latuviitta.org/documents/OpenJUMP_image_layer_tool.pdf >> > >> > I have a slight feeling that OpenJUMP could sometimes >> benefit also from analogous vector file index system. For >> example, we have a dataset that contains thousands of >> shapefiles, each one covering a 10 by 10 kilometer rectangle. >> With a vector index file and properly set layer scale limits >> OpenJUMP might be able to handle the whole dataset as a one >> seamless layer even it is a few gigabytes all together. I >> guess it would be much easier to make it work as read-only >> than to make is support also editing. >> > >> > -Jukka Rahkonen- >> > >> -------------------------------------------------------------- >> ---------------- >> > Virtualization& Cloud Management Using Capacity Planning >> > Cloud computing makes use of virtualization - but cloud computing >> > also focuses on allowing computing to be delivered as a service. >> > http://www.accelacomm.com/jaw/sfnl/114/51521223/ >> > _______________________________________________ >> > Jump-pilot-devel mailing list >> > Jump-pilot-devel@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> > >> > >> >> >> -------------------------------------------------------------- >> ---------------- >> Virtualization & Cloud Management Using Capacity Planning >> Cloud computing makes use of virtualization - but cloud computing >> also focuses on allowing computing to be delivered as a service. >> http://www.accelacomm.com/jaw/sfnl/114/51521223/ >> _______________________________________________ >> Jump-pilot-devel mailing list >> Jump-pilot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
