Hi,<div><br></div><div>Thanks everyone for the nice greetings, I'm very impressed with how polite and helpful the GRASS community is.</div><div><br></div><div>There is a wiki [1] and source code repository [2] for the Image Segmentation - Google Summer of Code project. </div>
<div><br></div><div>The mentors for the project have already provided a lot of advice, if there is anyone else with an interest in segmentation you are welcome to add to the Specifications or other areas of the wiki.</div>
<div><br></div><div>For the "code" I have started an outline, but I think there are still too many questions to call it pseudocode yet!. Many of the questions are for myself to research and answer. Of course, I welcome input and suggestions for all of it, but some of the bigger questions are:</div>
<div><br></div><div>1. How to best deal with images that are larger then available memory. (I assume too much disk I/O would be slow, but simple tiling could lead to poor segmentation at the tile borders.)</div><div><br>
</div><div>2. How to find neighbors. (Is this already available somewhere in GRASS?)</div><div><br></div><div>3. Would any functions would be useful as a general library function.</div><div><br></div><div>4. If library functions are already available for any steps.</div>
<div><br></div><div><br></div><div>I saw GSoC is on the agenda for the Sprint, if it would be helpful (and isn't too early in the day!) I can join by Google video / IRC / etc.</div><div><br></div><div>Regards,</div><div>
Eric</div><div><br></div><div><div>
[1] <a href="http://grass.osgeo.org/wiki/GRASS_GSoC_2012_Image_Segmentation" target="_blank">http://grass.osgeo.org/wiki/GRASS_GSoC_2012_Image_Segmentation</a></div><br></div><div><div>[2] <a href="https://trac.osgeo.org/grass/browser/grass-addons/grass7/imagery/i.segment" target="_blank">https://trac.osgeo.org/grass/browser/grass-addons/grass7/imagery/i.segment</a></div>
</div>