<div>
Well you have a classic choice:
</div><div><br></div><div>- if you can make a feature store then the udig editing tools will work.</div><div>- If not you can make your own tools</div><div><br></div><div>There are two tutorials on how to make a Datastore / FeatureSource / FeatureStore thing here:</div><div><br></div><div>http://docs.geotools.org/latest/userguide/tutorial/advanced/index.html</div><div><br></div><div>ContentDataStore (uses newer cleaner code so is easier to follow and looks pretty but is not as well tested)</div><div>AbstractDataStore (uses older code and is a better tutorial covering more stuff)</div>
<div><br>-- <br>Jody Garnett<br><br></div>
<p style="color: #a0a0a0;">On Monday, 25 July 2011 at 2:19 AM, Mirco Franzago wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>==Weekly Report==<br><br>Hi all,<br>this week I studied the uDig tutorials and uDig code to learn how to use the renderers. <br>I made some experiments about OSM data import and editing using JOSM and Potlatch2.<br>Now I'm trying to find a way to edit OSM data directly from uDig and a way to commit (save) the data on the neo4j-spatial database<br>
after the editing phase. <br>Regards,<br>Mirco.<br>
</div><div>_______________________________________________<br>SoC mailing list<br><a href="mailto:SoC@lists.osgeo.org">SoC@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/soc">http://lists.osgeo.org/mailman/listinfo/soc</a><br></div></div></span>
</blockquote>
<div>
<br>
</div>