[osmosis-dev] new plugin-api for Osmosis

[marcus.wolschon at googlemail.com]

On Thu, 22 Jan 2009 11:44:38 +0100, Jochen Topf <jochen.topf at geofabrik.de>
wrote:
> On Fri, Jan 16, 2009 at 09:02:12AM +0100, Marcus Wolschon wrote:
>> I have a working JavaPluginFramework -based new plugin-api
>> for osmosis and a change to  TravelingSalesman/libOSM to
>> have plugins for writing the OsmBin -format.
>> The new plugin-api automatically searches 
>> ./plugins
>> ~/.openstreetmap/osmosis/plugins
>>  and under windows 
>> /userprofiles/(username)/(env:APPDATA)/openstreetmap/osmosis/plugins/
> 
> Sounds like a great idea. I could make good use of such a plugin scheme.
> One request though: Can be add a search path for the plugins to the
> command line? I'd rather give an explicit search path for cases like
> automatic runs called from cronjobs etc.

Brett just submittet my code to osmosis:HEAD and I have no write-access
there.
So you have to ask him to add a parameter to add an arbitrary path to
the list of directories in TaskRegistrag.java .
functionally it should be no problem.

I will submit the code for Traveling Salesman soon to build osmosis-plugins
for
* reading, writing and rebuilding indice for the osmbin-1.0 format (current
status: debugging)
later
* repairing broken osmbin-1.0 -maps (like an fsck.osmbin)
and later preprocessing-tasks like
* build 3 additional levels of simplified detail from a given map
* for every type=street -relation combine all ways, simplify them and add
the result
  in a special role. (e.g. have simplified polylines of cross-cotinent
motorways
  for interactive rendering)
* add the wayid of the associated street to house-number
-nodes/interpolation-ways
* relate ways to their circumscribing place-polygons (zip-code, village,
city, ...)
* ...

for applications using osm-data for more then pretty map-rendering.

Marcus