Fine, that makes sense. Thanks for explaining that.<div><br></div><div>Martin<br><br><div class="gmail_quote">On Tue, Aug 16, 2011 at 9:21 AM, Martin Desruisseaux <span dir="ltr"><<a href="mailto:martin.desruisseaux@geomatys.fr">martin.desruisseaux@geomatys.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello Martin<br>
<br>
Le 16/08/11 17:32, Martin Davis a écrit :<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Even better, why not provide these tests in the MetaCRS Test format? That way they are declarative, platform and API-independent, and hence more easily usable by all the various CRS projects.<br>
</blockquote></div>
Because there is many programmatic tests performed through the API, in addition of testing the actual transformed point values: axis order, units, prime meridian, transform consistency, area of validity, etc. This test suite does not just tests if the transformed points are correct; it actually tests if the CoordinateReferenceSystem and CoordinateOperation objects are ISO 19111 compliant.<br>
<br>
This is complementary with the MetaCRS test format. Actually once this MetaCRS file will be available, I plan to add a JUnit test using it straight into the "geoapi-conformance" module, so GeoAPI implementations (including Proj.4 through the JNI wrappers) will get this test case automatically without any coding on their side.<div>
<div></div><div class="h5"><br>
<br>
Regards,<br>
<br>
Martin<br>
<br>
______________________________<u></u>_________________<br>
MetaCRS mailing list<br>
<a href="mailto:MetaCRS@lists.osgeo.org" target="_blank">MetaCRS@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/metacrs" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/metacrs</a><br>
</div></div></blockquote></div><br></div>