I do not understand why you are extending GeometryPropertyType. How is
your new type conceptually a specialisation of GeometryPropertyType?
Why not create a type that has a gml:GeometryPropertyType property and
other properties? This pattern allows reuse of the existing types and is
known to work with GeoServer's special treatment of geometries. This is
the pattern used in all GML application schemas I have seen (GeoSciML,
EarthresourceML WaterML, ...):
<element name="MyFeature" type="myNs:MyFeatureType">
<complexType name="myNs:MyFeatureType">
<complexContent>
<extension base="gml:AbstractFeatureType">
<sequence>
<element name="shape" type="gml:GeometryPropertyType">
<element name="myElem" type="string"/>
</sequence>
</extension>
</complexContent>
</complexType>
You instance document would then become:
<myNs:MyFeature>
<gml:shape>
<gml:Point>
<gml:pos>...</gml:pos>
</gml:Point>
</gml:shape>
<myNs:myElem>...</myNs:myElem>
</myNs:MyFeature>
Conceptually, your feature has-a shape and it has-a myElem, while it
is-a feature.
Kind regards,
Ben.
On 09/11/12 23:56, RudyWI wrote:
> I'm confused.
>
> If I define the following schema :
>
> <element name="MyPoint" type="myNs:myType" />
> <complexType name="myNs:myType">
> <complexContent>
> <extension base="gml:GeometryPropertyType">
> <sequence>
> <element name="myElem" type="string"></element>
> </sequence>
> </extension>
> </complexContent>
> </complexType>
>
> To produce the following XML :
>
> <myNs:MyPoint srsName="...">
> <gml:pos>...</gml:pos>
> <myNs:myElem>...</myNs:myElem>
> </myNs:MyPoint>
>
> Is it just incompatible with Geoserver because "myNs:myType" inherit from
> "gml:GeometryPropertyType" ?
> Or is it also forbidden by GML recommendation ?
>
> In my point of view, "myNs:MyPoint" is correct :
> - it inherits from "gml:GeometryPropertyType", so it can have "gml:pos"
> property.
> - it can also have its own property "myNs:myElem"
> So, I don't understand why it's not incompatible with GML Specification
> (part 7.1.3).
>
> Kind regards
>
>
>
> --
> View this message in context:
> http://osgeo-org.1560.n6.nabble.com/App-schema-How-to-map-Oracle-Geometry-into-GML-tp4984781p5015201.html
> Sent from the GeoServer - User mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Geoserver-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
--
Ben Caradoc-Davies <[email protected]>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
