Hi all
I can't resist any longer to give my feeling on the subject.
Firstly, I think the mail title should be "suggestion by Paolo" instead
of Pedro :-)
I have made some tests with kosmo rc1 and I am quite impressed by the work.
Not only because they added some capabilities which we have missed for a
long time in openjump, but also because IMHO, kosmo suceeded in adding
new capabilities AND keeping JUMP's philosophy : a simple and clean user
interface for a powerful tool. This is my user point of view. I had no
time to see the code and the many libraries kosmo depends on.
I'm not trying to say OpenJUMP has to switch to kosmo because I agree
with erwan, SS and pedro's remarks. We must make sure that kosmo is
stable enough (my feeling is rc1 is less stable than OJ now, but it is
already quite stable), and we must keep OJ as light and extensible as
possible. I also agree with you when you mention that saig develop kosmo
for particular clients and that OJ must stay a kind of "universal" and
"open" platform. But I did not find particular functions in kosmo which
are uncompatible with OJ's goal. Only useful additions fitting well with
the goal of OJ.
So what ? Many questions in front of us, and even more work. Maybe we'll
have to switch to kosmo in a near future just because kosmo progresses
much faster than OJ (and than JUMP). Before that, I think it is our
interest to get a better collaboration with saig team, and start
studying how the best of both projects could be merged (I think kosmo
did not benefit the developments made the last two years on JUMP and OJ)
: what are the differences in the feature model, what are the
differences in the rendering engine, what has to be done to make a OJ
plugin work with Kosmo ? This last question is important because there
are many important plugins developped by JUMP (conflation suite,
roadmatcher...), by Larry's team, Stefan, Ugo, Pirol university, R1...
and nobody like to loose one's work. I think Kosmo team could help on
these subjects.
Finally, i'd like to thank Kosmo team to have open their code and given
some explanations about their plans. I hope a good collaboration will go
on and benefit to everybody.
I attach a small file with remarks issued from the few tests I have made
with kosmo since yesterday.
Michaël
****************
Packaging
****************
-- Only one very big bundle (75 837 ko) : I'd like a lighter bundle for people
having a jre on their machine (many people I guess)
++ On the other hand : no problem to install kosmo on my windows machine, no
problem to launch it, no error message
****************
First impression
****************
++ Interface is much like OpenJUMP interface : clear enough to understand what
I should do to start working without reading a hundred pages manual. I
appreciate that saig has added several important functionnalities without
adding complexity to the menus (in fact, there are more buttons in the ToolBar,
but buttons which are not usable for a task are grayed, and the interface looks
simple)
-- Internationalization is far from being complete, even for english language
-- I did not start to work (I did not load any data), but there is already 38
Mo of committed memory. OpenJUMP uses less than 8 Mo when it has just been
started.
****************
Coordinate System
****************
++ Coordinate System Mangement is well integrated. First time I tried to create
a project, I was asked for a coord ref system. After that, the coord ref sys
name appeared in the project title. The second time, kosmo remembered what is
my favorite system to work and proposed to me to keep it. Thanks.
-- I did not find our new french reference system (RGF93 / Lambert 93) but I'm
sure we'll be able to add it (take care, the precise transformation from the
old french ref system to the new RGF93 system is not based on a simple 7 param
transformation...)
I did not check if kosmo can do transformation and if it does it well
****************
Using services (wms) : not tested
****************
****************
Loading data from file
****************
++ shapefile is loaded very quicly and with low memory consomption (less than
10 Mo for 22 000 features). Memory consumption climb from 10 to 70 Mo when I
check the "load into memory" checkbox. This is nearly twice the size of the
layer in OpenJUMP !
-- I did not find gml import/export option
++ DXF / DWG / DGN formats are supported : I did not test them yet
++ can load attribute data files (mdb or dbf)
-- I could not read the geometry coordinates from the "View/Edit attribute" or
the "Feature info" panel. This is possible (and useful) in OpenJUMP. No way to
check if z coordinates of a shapefile 3D is correctly read.
-- in the "load table" panel, the cancel button (on the right side of the
panel) has no effect
****************
Loading table
****************
-- one can load a table in mdb or dbf format, and save a layer as excel
(without geometry). It should be useful to have the same format for input and
output. It should also be useful to propose a csv input. csv is proposed as a
plugin, but only for data with point geometry ==> IMHO, formats available for
geographic data I/O and for attribute data I/O is not very clear.
****************
Loading file from database : not tested yet
****************
****************
Loading images
****************
-- it is strange that the core can't read images but JAI library is necessary
for kosmo's installation.
++ the image extension is very simple to add and works fine :
no problem to read tiff, jpg2000, ecw, jpg
-- graphic display is a bit slow for some formats (especialy jpg 2000 - ecw is
fast)
****************
Editing data
****************
++ kosmo is able to modify a onDemandDataSource layer with a "Commit Changes"
system which is quite simple and clear
-- if I want to remove a modified layer from the project, I am asked if I want
to save the changes : yes / no / cancel. If cancel is choosen, the layer is
removed without being saved, which is an unexpected behaviour !!!
-- no way to create a layer with mixed geometries (points, lines polygons)
-- no way to create a layer with 3D geometries
-- a new layer can only be saved as a shapefile (or excel but without geometry)
****************
MISCELLANEOUS REMARKS
****************
Feature model : it seems that a layer may have only one geometry type (point /
line / polygon). I found no information about the z coordinate management.
There are two attribute types different from OJ : long and float. Is float
really useful ? why not boolean ? Do you think it may be useful to add
constraints on AttributeType for compatibility with databases and shapefile/dbf
(ex field width, number of decimal) ?
when I measure an area, a layer "Area" is created. The bb of this layer doest
not correspond to its content, as shown by the zoom to layer command
STYLES
labels should not be revered (the head down)
the capability to display vertex does not exist (it exists in JUMP)
styles can be saved in independant file : is sls file format a standard ? why
not use sld ?
no possibility to synchronize label zoom with map zoom
the "sorting rows" function is very slow : it is much more slow than OpenJUMP
equivalent function, even when the layer is loaded in memory (after I have
check the load into memory checkbox)
-- WARNING : after few manipulations, yesterday, I have broken a valid
shapefile which is no more readable with kosmo. Message is
java.lang.NullPointerException
at
org.saig.core.dao.datasource.filedatasource.shape.geometry.RuleStyle.<init>(RuleStyle.java:109)
at
org.saig.core.renderer.ShapeRenderer.getRulesInScale(ShapeRenderer.java:667)
at org.saig.core.renderer.ShapeRenderer.render(ShapeRenderer.java:172)
Sorry, I don't know how to reproduce the error.
I wanted to try the "relation" capability, but my first try ended with a NPE
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
