[osmosis-dev] Informations about osmosis
johann.sorel at geomatys.fr
Wed Jan 27 11:43:09 GMT 2010
The main reason I see to split osmosis in modules is to achieve a
separation of tasks for
a better integration in third party application/library.
My current work is to write the code to read/write osm files and
communicate with the server in geotoolkit.
I see osmosis has most of the functional code for thoses purposes so it
would be a waste of effort
to duplicate everything.
Actualy osmosis is the only java library that we can potentialy rely on,
in fact the geotoolkit library is under LGPL
and JOSM or the salesman-traveler application dont have a compatible
license (GPL) nor a functional maven build.
Our objective is to be able to acces OSM datas with normalized data
models like ISO 19109 (Feature), ISO 19107 (Geometry)
GML, WFS, WMS and so on ... we already have all this, reprojection,
rendering engines, styling (SLD / SE) ...
We just lack the "connection" part to OSM datas :).
I believe there are plenty of stuff usefull in geotoolkit that could be
used in osmosis, some exemple would be
exporting to shapefile, gml or dynamicly generate image tiles, swing map
viewer and editor and all stuff related to reprojection capabilities.
Back to the main subject :
I hope to be able to reuse osmosis code without importing unnecessary
code like pipelines, database exporter, command line parser
and so one.
By the way I can't find any java code exemples anywhere, reading/writing
osm and so on ?
I can only find command line exemples.
Brett Henderson wrote:
> On Tue, Jan 26, 2010 at 3:33 AM, sorel <johann.sorel at geomatys.fr
> <mailto:johann.sorel at geomatys.fr>> wrote:
> I am a developer on several GIS Java projects like GeoAPI, GeotoolKit,
> Constellation, Puzzle-GIS ... and so on.
> Currently I am exploring existing java solutions to work with Open
> Street Map and seen only OSMOSIS and JSOM free.
> If you have a few minutes to answer my questions that would be a
> real help.
> I explored your project and it's well made, great work.
> I was wondering if it could be possible to split this unique maven
> module in smaller modules to organize it ?
> something like : api, model, utils, osmbin, gpx, mysql, postgresql ...
> (you know the project better than me).
> It's certainly possible. It's currently in one single jar file
> because that was quicker and easier. So far there's been no need to
> split it. I've often thought about splitting it up, but never found
> the time or inclination to do it.
> What are you trying to do with it? Is there any reason to split it
> other than size?
> One complication that would make it difficult to split is cross
> dependencies between java packages. There hasn't been a serious
> effort made to avoid circular dependencies. I suspect some
> refactoring would be required in order to find logical points to make
> it work.
> thank you for your answers, I hope my english wasn't too bad.
> Your English is just fine ;-)
More information about the osmosis-dev