<br><br><div class="gmail_quote">On Fri, May 30, 2008 at 3:51 PM, Martin Desruisseaux <<a href="mailto:martin.desruisseaux@geomatys.fr">martin.desruisseaux@geomatys.fr</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Daniele Romagnoli a écrit :<br>
<div class="Ih2E3d">> Row 358 of ISO 19115:2003/Cor.1:2006 provides a role name "verticalCRS"<br>
> which is associated to a "SC_CRS" domain. So, it isn't possible to use a<br>
> SC_CompoundCRS or a SC_EngineeringCRS (both are SC_CRS) for the<br>
> verticalCRS link? I thought that the specification has should explicitly<br>
> state "SC_VerticalCRS" instead of "SC_CRS".<br>
<br>
<br>
</div>I forgot this point since it was a while ago... But it is quite possible that we<br>
made the "verticalCRS" association more restrictive in GeoAPI than it was in ISO<br>
specification. But both the association name and the textual description suggest<br>
strongly that VerticalCRS is expected by ISO specification, even if they didn't<br>
expressed this restriction as a VerticalCRS type for unknown reason. We note<br>
also that the ISO 19115 specification before 2003 correction was explicitly<br>
referencing a VerticalDatum.</blockquote><div> </div><div>Mmm... under this constraint I back to my first question:<br>how can I
expose the extent of the 3rd component of a 3D coverage related to a GeographicCRS if 19115
spatialBoundingBox allows to handle 2D geographic coords (n,s,w,e
boundaries), and verticalExtent allows to handle the vertical component
except the case of ellipsoidal height (3D GeographicCRS)?.<br>
I thought linking VerticalExtent to a general SC_CRS would be able to handle both cases.<br><br>Daniele<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Do we have a use case where a user would be right to associate an other kind of<br>
CRS than VerticalCRS to a VerticalExtent? If we wanted to reference a generic<br>
CRS (including CompoundCRS), maybe it would be better located in the Extent<br>
interface?<br>
<div><div></div><div class="Wj3C7c"><br>
Martin<br>
<br>
-------------------------------------------------------------------------<br>
This SF.net email is sponsored by: Microsoft<br>
Defy all challenges. Microsoft(R) Visual Studio 2008.<br>
<a href="http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/" target="_blank">http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/</a><br>
_______________________________________________<br>
Geotools-devel mailing list<br>
<a href="mailto:Geotools-devel@lists.sourceforge.net">Geotools-devel@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/geotools-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/geotools-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>-------------------------------------------------------<br>Eng. Daniele Romagnoli <br>Software Engineer<br><br>GeoSolutions S.A.S.<br>Via Carignoni 51<br>55041 Camaiore (LU)<br>
Italy<br><br>phone: +39 0584983027<br>fax: +39 0584983027<br>mob: +39 328 0559267<br><br><br><a href="http://www.geo-solutions.it">http://www.geo-solutions.it</a><br><br>-------------------------------------------------------<br>