<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello Dieter<br>
<br>
<div class="moz-cite-prefix">Le 05/02/14 18:08, Dieter Stüken a
écrit :<br>
</div>
<blockquote
cite="mid:18C8C3682054CB48990864C67A009E123C2D1919@hydra.esri-de.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>I
found Puzzle-gis which looks very similar to our tool (even if the
development currently seems to stall).</blockquote>
The developer is Johan Sorel, who is on this list. Maybe he can
comment.<br>
<br>
<blockquote
cite="mid:18C8C3682054CB48990864C67A009E123C2D1919@hydra.esri-de.com"
type="cite">Playing around I got a problem with jsr-275 Unit for
EPSG 9003[ft]:<font face="Calibri" size="2"><span
style="font-size:11pt;">
<div>Unit.toString() raises an IllegalArgumentException: Only
integer factors are supported in UCUM</div>
<div> </div>
<div>Wrong version of jsr-275-0.9.3.jar? Will jsr-275 remain
or will it be replaced some day?</div>
</span></font></blockquote>
JSR-275 has been rejected by the JCP, so this project is
theoretically dead. However its former leader, Werner Keil, is
considering to start a new JSR attempt. That would be the third! But
he got support from various communities. I do not yet have a clear
picture about the future, but the choices are:<br>
<br>
<ul>
<li>Werner succeed in starting a new JSR, in which case I would
keep the JSR-275 dependency unchanged until the new JSR has some
prototype, in order to reduce compatibility break (assuming that
the new JSR keep the <tt>javax.measure.unit</tt> package name).</li>
<li>We get confirmation that no JSR will be restarted, in which
case I will replace all current JSR-275 dependency by a <tt>org.unitsofmeasurement</tt>
interface with a custom implementation.<br>
</li>
</ul>
<br>
Wermer's effort is ongoing right now, so I plan to wait a few months
to see what come out. In the main time, we are forced to deal with
current <tt>Unit</tt> using special cases like <tt>if (unit ==
NonSI.FOOT) symbol = "ft";</tt> Of course this is not very
convenient, but hopefully will be resolved some day.<br>
<br>
<br>
<blockquote
cite="mid:18C8C3682054CB48990864C67A009E123C2D1919@hydra.esri-de.com"
type="cite"><font face="Calibri" size="2"><span
style="font-size:11pt;">
<div>Is there some roadmap about what is going on with
geotoolkit, geotoolkit-pending and sis?</div>
</span></font></blockquote>
We have an issue with Apache's wiki lately, so I was not able to
edit the Apache SIS wiki page. But the roadmap is:<br>
<br>
<ul>
<li>Apache SIS 0.4 release candidate as soon as I have completed
the two following tasks:</li>
<ul>
<li>Support of WKT 2 (a.k.a. ISO 19162) formatting - this work
is in progress right now</li>
<li>Review of the Shapefile datastore base started by an other
contributor.</li>
</ul>
<li>Release of Geotk 4.0-M1 milestone right after SIS 0.4 release.</li>
<li>Removal of deprecated Geotk classes that moved to Apache SIS.</li>
<li>New "port Geotk classes to SIS, then deprecate the ported
Geotk classes" cycle. The next cycle toward Apache SIS 0.5 will
include:</li>
<ul>
<li>Map projections</li>
<li>EPSG database</li>
</ul>
<li>At some point in the future (timeline not yet determined),
Geotk and Geotk-pending will be merged in a single project.<br>
</li>
</ul>
<br>
<blockquote
cite="mid:18C8C3682054CB48990864C67A009E123C2D1919@hydra.esri-de.com"
type="cite"><font face="Calibri" size="2"><span
style="font-size:11pt;">
<div>SIS looks very promising. Moving towards immutable
objects and using Java7/JaxB is exactly what we did too last
year.</div>
<div>(We even entered Java8 recently, Lambda is pure fun…)</div>
</span></font></blockquote>
Thanks for the feedback :-). I also wish to start a JDK8 branch on
SIS soon, hopefully after SIS 0.4 release.<br>
<br>
Regards,<br>
<br>
Martin<br>
<br>
</body>
</html>