[Geoserver-users] Problems with CityGML and application schema

[Deen]

Hi everyone,

currently I am trying to map the feature type ‘Building’ of CityGML with geoserver application schema and I came across some problems when i tried to map the generic attributes of the buildings. One of feature types about the generic attributes of the building is “stringAttribute”,which is defined in http://schemas.opengis.net/citygml/generics/2.0/generics.xsd, and what i want is just chaining two feature types “buildng” and “stringAttribute”

Here is the a piece of my mapping file “bldg_Building.xml”

bldg v1_bldg_building bldg:Building ...... core:_GenericApplicationPropertyOfCityObject id gen:stringAttribute FEATURE_LINK gen:StringAttributeType ......

Here is the a piece of my mapping file “gen_stringAttribute.xml”

bldg v1_gen_string_attr gen:stringAttribute

…

FEATURE_LINK cityobject_id ......

Here is What I got from WFS of geoserver :

gml:featureMember
<bldg:Building gml:id=“BLDG_0003000b0009a940”>
core:_GenericApplicationPropertyOfCityObject
[FeatureImpl:stringAttribute=[AttributeImpl:value=09030374]]
gen:stringAttribute
gen:value09030374</gen:value>
</gen:stringAttribute>
</core:_GenericApplicationPropertyOfCityObject>
core:_GenericApplicationPropertyOfCityObject
gen:stringAttribute
gen:value09030374</gen:value>
</gen:stringAttribute>
</core:_GenericApplicationPropertyOfCityObject>
…

My question is if there is any way to link two feature types without “container” attribute “core:_GenericApplicationPropertyOfCityObject”, because the standard GML file is something like

<bldg:Building gml:id=“BLDG_0003000b0009a940”>
gen:stringAttribute
gen:value09030374</gen:value>
</gen:stringAttribute>
gen:stringAttribute
gen:value0903387</gen:value>
</gen:stringAttribute>
…

This problem is bugging me for a while and any help I would really appreciate

Thanks

Deen

gen_stringAttribute.xml (3K) Download Attachment
bldg_Building.xml (6K) Download Attachment

---

View this message in context: Problems with CityGML and application schema
Sent from the GeoServer - User mailing list archive at Nabble.com.

[Andrea_Aime4]

Hi Deen,
I’m not 100% sure (still a novice in app-schema) but it seems to me this XML schema is violating
the “GML striping” rule. From the documentation:

···

On Tue, May 10, 2016 at 5:20 PM, Deen <kensongzhu@anonymised.com> wrote:

Hi everyone,

currently I am trying to map the feature type ‘Building’ of CityGML with geoserver application schema and I came across some problems when i tried to map the generic attributes of the buildings. One of feature types about the generic attributes of the building is “stringAttribute”,which is defined in http://schemas.opengis.net/citygml/generics/2.0/generics.xsd, and what i want is just chaining two feature types “buildng” and “stringAttribute”

Here is the a piece of my mapping file “bldg_Building.xml”

bldg v1_bldg_building bldg:Building ...... core:_GenericApplicationPropertyOfCityObject id gen:stringAttribute FEATURE_LINK gen:StringAttributeType ......

Here is the a piece of my mapping file “gen_stringAttribute.xml”

bldg v1_gen_string_attr gen:stringAttribute

…

FEATURE_LINK cityobject_id ......

Here is What I got from WFS of geoserver :

gml:featureMember
<bldg:Building gml:id=“BLDG_0003000b0009a940”>
core:_GenericApplicationPropertyOfCityObject
[FeatureImpl:stringAttribute=[AttributeImpl:value=09030374]]
gen:stringAttribute
gen:value09030374</gen:value>
</gen:stringAttribute>
</core:_GenericApplicationPropertyOfCityObject>
core:_GenericApplicationPropertyOfCityObject
gen:stringAttribute
gen:value09030374</gen:value>
</gen:stringAttribute>
</core:_GenericApplicationPropertyOfCityObject>
…

My question is if there is any way to link two feature types without “container” attribute “core:_GenericApplicationPropertyOfCityObject”, because the standard GML file is something like

<bldg:Building gml:id=“BLDG_0003000b0009a940”>
gen:stringAttribute
gen:value09030374</gen:value>
</gen:stringAttribute>
gen:stringAttribute
gen:value0903387</gen:value>
</gen:stringAttribute>
…

This problem is bugging me for a while and any help I would really appreciate

Thanks

Deen

gen_stringAttribute.xml (3K) Download Attachment
bldg_Building.xml (6K) Download Attachment

---

View this message in context: Problems with CityGML and application schema
Sent from the GeoServer - User mailing list archive at Nabble.com.

---

Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

---

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313

fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

---

[Bart_van_den_Eijnde1]

Andrea,

I think you are right.

Deen, generics.xsd in CityGML does not appear to be a GML application schema because it violates the GML encoding rule. It appears to be a mechanism to encode generic weak types. This schema does not follow the GML property model. For this schema to be supported by app-schema, it would need gen:value to be enclosed by an additional complex type; this extra layer encodes type information in case a subclass is used to create a derived type. For example, something like this:

<bldg:Building gml:id="BLDG_0003000b0009a940">
<gen:stringAttribute>
<gen:StringAttribute>
<gen:value>09030374</gen:value>
</gen:StringAttribute>
</gen:stringAttribute>
</bldg:Building>

Subclasses of StringAttribute might add properties that support, for example, internationalisation. Imagine a type called InternationalisedStringAttribute. Because generics.xsd violates the GML encoding rule and omits this layer, a consumer of such an instance document has no way of determining the type because it cannot know if the element contained in gen:stringAttribute is a subclass.

See section 7.1.1 on page 20-21 (PDF page 30-31) of the GML 3.2.1 standard (OGC 07-036):
http://portal.opengeospatial.org/files/?artifact_id=20509

The rule is the same for (GML 3.1.1).

Kind regards,
Ben.

On 12/05/16 02:19, Andrea Aime wrote:

Hi Deen,
I'm not 100% sure (still a novice in app-schema) but it seems to me this
XML schema is violating
the "GML striping" rule. From the documentation:

-----
Note that the GML encoding rules require that complex types are never the
direct property of another complex type; they are always contained in a
property type to ensure that their type is encoded in a surrounding
element. Encoded GML is always type/property/type/property. This is also
known as the GML “striping” rule.
-----

http://docs.geoserver.org/latest/en/user/data/app-schema/mapping-file.html

If that's the case, app-schema might just not be able to encode it.
Hopefully someone more experienced
will follow up confirming this, or showing a way to do what you want

Cheers
Andrea

On Tue, May 10, 2016 at 5:20 PM, Deen <kensongzhu@anonymised.com> wrote:

Hi everyone,

currently I am trying to map the feature type 'Building' of CityGML with
geoserver application schema and I came across some problems when i tried
to map the generic attributes of the buildings. One of feature types about
the generic attributes of the building is "stringAttribute",which is
defined in http://schemas.opengis.net/citygml/generics/2.0/generics.xsd,
and what i want is just chaining two feature types "buildng" and
"stringAttribute"

Here is the a piece of my mapping file "bldg_Building.xml"

     <typeMappings>
         <FeatureTypeMapping>
             <sourceDataStore>bldg</sourceDataStore>
             <sourceType>v1_bldg_building</sourceType>
             <targetElement>bldg:Building</targetElement>
             ......
             <AttributeMapping>

<targetAttribute>core:_GenericApplicationPropertyOfCityObject</targetAttribute>
                     <sourceExpression>
                         <OCQL>id</OCQL>
                         <linkElement>gen:stringAttribute</linkElement>
                         <linkField>FEATURE_LINK</linkField>
                     </sourceExpression>

<targetAttributeNode>gen:StringAttributeType</targetAttributeNode>
                 </AttributeMapping>
               ......
   <typeMappings>

Here is the a piece of my mapping file "gen_stringAttribute.xml"

  <typeMappings>
         <FeatureTypeMapping>
             <sourceDataStore>bldg</sourceDataStore>
             <sourceType>v1_gen_string_attr</sourceType>
             <targetElement>gen:stringAttribute</targetElement>
              .......
             <AttributeMapping>
                     <targetAttribute>FEATURE_LINK</targetAttribute>
                     <sourceExpression>
                         <OCQL>cityobject_id</OCQL>
                     </sourceExpression>
                 </AttributeMapping>
              ......
  </typeMappings>

Here is What I got from WFS of geoserver :

<gml:featureMember>
<bldg:Building gml:id="BLDG_0003000b0009a940">
      <core:_GenericApplicationPropertyOfCityObject>
      [FeatureImpl:stringAttribute<StringAttributeType
id=DENK_ID>=[AttributeImpl:value<string>=09030374]]
         <gen:stringAttribute>
            <gen:value>09030374</gen:value>
        </gen:stringAttribute>
      </core:_GenericApplicationPropertyOfCityObject>
      <core:_GenericApplicationPropertyOfCityObject>
           <gen:stringAttribute>
            <gen:value>09030374</gen:value>
        </gen:stringAttribute>
    </core:_GenericApplicationPropertyOfCityObject>
      .....

My question is if there is any way to link two feature types without
"container" attribute "core:_GenericApplicationPropertyOfCityObject",
because the standard GML file is something like

<bldg:Building gml:id="BLDG_0003000b0009a940">
         <gen:stringAttribute>
            <gen:value>09030374</gen:value>
        </gen:stringAttribute>
               <gen:stringAttribute>
            <gen:value>0903387</gen:value>
        </gen:stringAttribute>
......

This problem is bugging me for a while and any help I would really
appreciate

Thanks
Deen

*gen_stringAttribute.xml* (3K) Download Attachment
<http://osgeo-org.1560.x6.nabble.com/attachment/5265622/0/gen_stringAttribute.xml&gt;
*bldg_Building.xml* (6K) Download Attachment
<http://osgeo-org.1560.x6.nabble.com/attachment/5265622/1/bldg_Building.xml&gt;

------------------------------
View this message in context: Problems with CityGML and application schema
<http://osgeo-org.1560.x6.nabble.com/Problems-with-CityGML-and-application-schema-tp5265622.html&gt;
Sent from the GeoServer - User mailing list archive
<http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html&gt; at
Nabble.com.

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data
untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

[Deen]

Hi Andrea and Ben, thanks for your replies.
Ben, I am still a little bit confused about your suggestion. As far as I
understand,in order to generate your example code via WFS, I will end up
with adding a property called "stringAttribute" to the feature type
"building",which is defined in
http://schemas.opengis.net/citygml/building/2.0/building.xsd, because the
type "building" itself does not have an explicit property called
"stringAttribute". And the property probably looks like:
<xs:element name="stringAttribute" type="gen:StringAttributeType"
minOccurs="0" maxOccurs="unbounded"/>
but what about the namespace of this property, it should be "bldg" not
"gen",isn't it? In addition, I still need to modify the generic.xsd by
adding an element type
<xs:element name="StringAttribute" type="StringAttributeType"
substitutionGroup="_genericAttribute"/>
Am I missing anything?

Kind Regards
Deen

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Problems-with-CityGML-and-application-schema-tp5265622p5266114.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

[Bart_van_den_Eijnde1]

Deen,

I think this is a defect in CityGML that renders it incompatible with app-schema. This is not something that you can fix by yourself because, even if you did by changing the XSD files, your schema would be different to the official CityGML schema and your WFS service would not be interoperable. CityGML clients would not understand your WFS responses.

What are you trying to do? Do you want to deliver information via one service or are you preparing a CityGML change request?

I draw your attention to the annotation on GenericCityObjectType:
http://schemas.opengis.net/citygml/generics/2.0/generics.xsd
"Generic (user defined) city objects may be used to model features which are not covered explicitly by the CityGML schema. Generic objects must be used with care; they shall only be used if there is no appropiate [sic] thematic class available in the overall CityGML schema. Oherwise [sic], problems concerning semantic interoperability may arise."

This is warning you *against* using these types.

Why are you not able to use one of the other types? What are you trying to do? Who will consume the service? What are they trying to do?

Kind regards,
Ben,

On 13/05/16 09:24, Deen wrote:

Hi Andrea and Ben, thanks for your replies.
Ben, I am still a little bit confused about your suggestion. As far as I
understand,in order to generate your example code via WFS, I will end up
with adding a property called "stringAttribute" to the feature type
"building",which is defined in
http://schemas.opengis.net/citygml/building/2.0/building.xsd, because the
type "building" itself does not have an explicit property called
"stringAttribute". And the property probably looks like:
<xs:element name="stringAttribute" type="gen:StringAttributeType"
minOccurs="0" maxOccurs="unbounded"/>
but what about the namespace of this property, it should be "bldg" not
"gen",isn't it? In addition, I still need to modify the generic.xsd by
adding an element type
<xs:element name="StringAttribute" type="StringAttributeType"
substitutionGroup="_genericAttribute"/>
Am I missing anything?

Kind Regards
Deen

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

[Deen]

Hello Ben,
sorry that late to reply, actually we are preparing for a CityGML change
request. In the project we are using our python code for clients to import
and export CityGML data from 3d CityDB, but right now we want to upgrade our
project and provide WFS for the clients. 3d CityDB offers also the WFS
interface, howerver, it is Simple WFS (free version), which is not enough to
satisfy our need. Since we do have Geoserver running on our server, I was
asked to run some tests with app-schema to see if it can serve the CityGML
with a standard format via Geoserver WFS, before we buy the commercial one
or start coding the WFS by ourselves. Two weeks ago, mapping the surface
geometry such as "WallSurface" and "GroundSurface" to the "Building" ran
quite well for me, I thought that mapping generic attributes and appearance
would do the same tricks. As
you suggested, the "generic.xsd" violates the GML encoding rule and these
types should be carefully used, but somehow this piece of information is
needed for us. it seems to me now, the app-schema is probably not the
solution we are looking for. But anyway, big thanks for your help!

Kind Regards
Deen

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Problems-with-CityGML-and-application-schema-tp5265622p5267076.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

[Bart_van_den_Eijnde1]

Deen,

have you considered creating a thin wrapper application schema that defines new types that extend CityGML types by adding the properties you need? Some other application schemas also support simple extensibility by adding properties of xs:anyType with minOccurs="0". One of these approaches may suffice for your needs; extending types is more robust.

The underlying problem is that clients will need to understand the XML. While generics.xsd will let you encode arbitrary XML, it does not say what these properties mean.

Kind regards,
Ben.

On 19/05/16 08:04, Deen wrote:

Hello Ben,
sorry that late to reply, actually we are preparing for a CityGML change
request. In the project we are using our python code for clients to import
and export CityGML data from 3d CityDB, but right now we want to upgrade our
project and provide WFS for the clients. 3d CityDB offers also the WFS
interface, howerver, it is Simple WFS (free version), which is not enough to
satisfy our need. Since we do have Geoserver running on our server, I was
asked to run some tests with app-schema to see if it can serve the CityGML
with a standard format via Geoserver WFS, before we buy the commercial one
or start coding the WFS by ourselves. Two weeks ago, mapping the surface
geometry such as "WallSurface" and "GroundSurface" to the "Building" ran
quite well for me, I thought that mapping generic attributes and appearance
would do the same tricks. As
you suggested, the "generic.xsd" violates the GML encoding rule and these
types should be carefully used, but somehow this piece of information is
needed for us. it seems to me now, the app-schema is probably not the
solution we are looking for. But anyway, big thanks for your help!

Kind Regards
Deen

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

[Andrea_Aime4]

Hi Ben,
just thinking out loud here, so bear with me for a second but… wondering if app-schema
encoding machinery could be relaxed to allow non GML compliant schemas.
I’m trying to understand if we are against a veritable design wall, that would require deep
changes, if the code is trying to play cop and enforce the GML rules, or something in the middle
(e.g., may be hard but not impossible to get generic elements to be encoded).

If the alternative is looking for a licenced product, then some funds could be directed at
relaxing/“improving” the app-schema store instead

Cheers
Andrea

···

On Thu, May 19, 2016 at 12:18 AM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Deen,

have you considered creating a thin wrapper application schema that
defines new types that extend CityGML types by adding the properties you
need? Some other application schemas also support simple extensibility
by adding properties of xs:anyType with minOccurs=“0”. One of these
approaches may suffice for your needs; extending types is more robust.

The underlying problem is that clients will need to understand the XML.
While generics.xsd will let you encode arbitrary XML, it does not say
what these properties mean.

Kind regards,
Ben.

On 19/05/16 08:04, Deen wrote:

Hello Ben,
sorry that late to reply, actually we are preparing for a CityGML change
request. In the project we are using our python code for clients to import
and export CityGML data from 3d CityDB, but right now we want to upgrade our
project and provide WFS for the clients. 3d CityDB offers also the WFS
interface, howerver, it is Simple WFS (free version), which is not enough to
satisfy our need. Since we do have Geoserver running on our server, I was
asked to run some tests with app-schema to see if it can serve the CityGML
with a standard format via Geoserver WFS, before we buy the commercial one
or start coding the WFS by ourselves. Two weeks ago, mapping the surface
geometry such as “WallSurface” and “GroundSurface” to the “Building” ran
quite well for me, I thought that mapping generic attributes and appearance
would do the same tricks. As
you suggested, the “generic.xsd” violates the GML encoding rule and these
types should be carefully used, but somehow this piece of information is
needed for us. it seems to me now, the app-schema is probably not the
solution we are looking for. But anyway, big thanks for your help!

Kind Regards
Deen

–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

---

Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

---

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313

fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

---

[Bart_van_den_Eijnde1]

Andrea,

I think that support for generic elements is possible but would require substantial changes both in the way mapping paths are resolved in the app-schema feature type cache and also changes in the GeoTools XML Encoder. We could continue to use GeoAPI, but the encoder would need some way of knowing that it should omit certain type information elements. Similar information is already smuggled in the UserData map, so that is an obvious route. Reverse mappings also need to be handled so that filter queries work. Supporting generic non-GML-compliant properties might be similar in problem scale to support for xs:anyType, although instance documents using xs:anyType still encode type information.

Kind regards,
Ben.

On 19/05/16 19:57, Andrea Aime wrote:

Hi Ben,
just thinking out loud here, so bear with me for a second but... wondering
if app-schema
encoding machinery could be relaxed to allow non GML compliant schemas.
I'm trying to understand if we are against a veritable design wall, that
would require deep
changes, if the code is trying to play cop and enforce the GML rules, or
something in the middle
(e.g., may be hard but not impossible to get generic elements to be
encoded).

If the alternative is looking for a licenced product, then some funds could
be directed at
relaxing/"improving" the app-schema store instead

Cheers
Andrea

On Thu, May 19, 2016 at 12:18 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Deen,

have you considered creating a thin wrapper application schema that
defines new types that extend CityGML types by adding the properties you
need? Some other application schemas also support simple extensibility
by adding properties of xs:anyType with minOccurs="0". One of these
approaches may suffice for your needs; extending types is more robust.

The underlying problem is that clients will need to understand the XML.
While generics.xsd will let you encode arbitrary XML, it does not say
what these properties mean.

Kind regards,
Ben.

On 19/05/16 08:04, Deen wrote:

Hello Ben,
sorry that late to reply, actually we are preparing for a CityGML change
request. In the project we are using our python code for clients to

import

and export CityGML data from 3d CityDB, but right now we want to upgrade

our

project and provide WFS for the clients. 3d CityDB offers also the WFS
interface, howerver, it is Simple WFS (free version), which is not

enough to

satisfy our need. Since we do have Geoserver running on our server, I was
asked to run some tests with app-schema to see if it can serve the

CityGML

with a standard format via Geoserver WFS, before we buy the commercial

one

or start coding the WFS by ourselves. Two weeks ago, mapping the surface
geometry such as "WallSurface" and "GroundSurface" to the "Building" ran
quite well for me, I thought that mapping generic attributes and

appearance

would do the same tricks. As
you suggested, the "generic.xsd" violates the GML encoding rule and these
types should be carefully used, but somehow this piece of information is
needed for us. it seems to me now, the app-schema is probably not the
solution we are looking for. But anyway, big thanks for your help!

Kind Regards
Deen

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data
untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

[Deen]

Hi all,
one of my colleagues spoke with the contributors of CityGML last week,
according to them, the generic objects model of CityGML will be modified in
the coming version 3.0 to match GML encode, it would be probally released in
next year. Just provide some information for those, who are currently doing
or will do something similar like I used to do.

Kind Regards
Deen

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Problems-with-CityGML-and-application-schema-tp5265622p5270200.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

[Bart_van_den_Eijnde1]

Thanks very much Deen. Please let us know if you encounter any difficulties delivering CityGML 3.0 with GeoServer app-schema.

Kind regards,
Ben.

On 07/06/16 06:05, Deen wrote:

Hi all,
one of my colleagues spoke with the contributors of CityGML last week,
according to them, the generic objects model of CityGML will be modified in
the coming version 3.0 to match GML encode, it would be probally released in
next year. Just provide some information for those, who are currently doing
or will do something similar like I used to do.

Kind Regards
Deen

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Problems-with-CityGML-and-application-schema-tp5265622p5270200.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand