Hi List,
Has anyone seen anything like this when using Hale studio and the application
schema plugin. I'm mapping from two postgres tables to the features
tn-w:MarineWaterway and tn-w:WaterwayLink in the
http://inspire.ec.europa.eu/schemas/tn-w/4.0/WaterTransportNetwork.xsd
application schema.
When uploading my mapping using the direct upload function from Hale Studio,
some of the namespace prefixes are auto generated instead of using the actual
namespaces, specifically these namespace prefixes are not resolved correctly:
xmlns:tn=http://inspire.ec.europa.eu/schemas/tn/4.0
xmlns:net=http://inspire.ec.europa.eu/schemas/net/4.0
They instead become:
xmlns:nns__2=http://inspire.ec.europa.eu/schemas/tn/4.0
xmlns: nns__1=http://inspire.ec.europa.eu/schemas/net/4.0
resulting in the below snippet of my appschema file on the geoserver:
<AttributeMapping>
<targetAttribute>nns__1:beginLifespanVersion</targetAttribute>
<sourceExpression>
<OCQL>beginlifespanversion</OCQL>
</sourceExpression>
<ClientProperty>
<name>xsi:nil</name>
<value>if_then_else(isNull(beginlifespanversion),
'true', Expression.NIL)</value>
</ClientProperty>
</AttributeMapping>
<AttributeMapping>
<targetAttribute>nns__2:geographicalName/gn:GeographicalName/gn:language</targetAttribute>
<sourceExpression>
<OCQL>geographicalnamelanguage</OCQL>
</sourceExpression>
<ClientProperty>
<name>xsi:nil</name>
<value>if_then_else(isNull(geographicalnamelanguage),
'true', Expression.NIL)</value>
</ClientProperty>
</AttributeMapping>
<AttributeMapping>
<targetAttribute>nns__2:geographicalName/gn:GeographicalName/gn:nameStatus</targetAttribute>
<encodeIfEmpty>true</encodeIfEmpty>
<ClientProperty>
<name>nilReason</name>
<value>'other:unpopulated'</value>
</ClientProperty>
<ClientProperty>
<name>xsi:nil</name>
<value>if_then_else(isNull('other:unpopulated'),
Expression.NIL, 'true')</value>
</ClientProperty>
</AttributeMapping>
<AttributeMapping>
<targetAttribute>nns__2:geographicalName/gn:GeographicalName/gn:nativeness</targetAttribute>
<encodeIfEmpty>true</encodeIfEmpty>
<ClientProperty>
<name>nilReason</name>
<value>'other:unpopulated'</value>
</ClientProperty>
<ClientProperty>
<name>xsi:nil</name>
<value>if_then_else(isNull('other:unpopulated'),
Expression.NIL, 'true')</value>
</ClientProperty>
</AttributeMapping>....
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
