Hi Igor,
Thanks for sending that through. Firstly for cocities:providername your mapping
should have user providername instead of just name
<targetAttribute>cocities:provider/cocities: providername </targetAttribute>
Instead of
<targetAttribute>cocities:provider/cocities:name</targetAttribute>
Secondly,
Your feature chaining for cocities:TransitStop should be something like.
Without access to your schema file I am unable to test run it but looking
through your mapping this is something I picked up. Let me know the outcome
<AttributeMapping>
<targetAttribute>
cocities:provider
</targetAttribute>
<sourceExpression>
<OCQL>provider_id</OCQL> (link
this table(oip_transit_stop) providerid)
<linkElement> cocities:provider
</linkElement> (link to this feature)
<linkField>FEATURE_LINK</linkField> (using what has been defined by
feature_link)
</sourceExpression>
</AttributeMapping>
And on your chained feature,
<AttributeMapping>
<targetAttribute>
FEATURE_LINK[1](myproviderid
will be used as FEATURE_LINK[1])
</targetAttribute>
<sourceExpression>
<OCQL>myproviderid</OCQL>(myproviderid in cocitiesds)
</sourceExpression>
</AttributeMapping>
<AttributeMapping>
<targetAttribute>cocities:provider/cocities:providerid</targetAttribute>
<sourceExpression>
<OCQL>provider_id</OCQL>
<linkElement>cocities:providername</linkElement>
<linkField>providerid</linkField>
</sourceExpression>
</AttributeMapping>
<AttributeMapping>
<targetAttribute>cocities:provider/cocities:name</targetAttribute>
<sourceExpression>
<linkElement>cocities:providerid</linkElement>
<linkField>name</linkField>
</sourceExpression>
</AttributeMapping>
Victor Tey
Software Engineer
ASRDC
CSIRO Earth Science and Resource Engineering
Phone: +61 8 6436 8944
[email protected] | www.csiro.au |
Address: Australian Resources Research Centre, 26 Dick Perry Avenue, Kensington
WA 6151
PLEASE NOTE
The information contained in this email may be confidential or privileged. Any
unauthorised use or disclosure is prohibited. If you have received this email
in error, please delete it immediately and notify the sender by return email.
Thank you. To the extent permitted by law, CSIRO does not represent, warrant
and/or guarantee that the integrity of this communication has been maintained
or that the communication is free of errors, virus, interception or
interference.
Please consider the environment before printing this email.
-----Original Message-----
From: igor.erdoiza [mailto:[email protected]]
Sent: Thursday, 25 October 2012 2:39 PM
To: [email protected]
Subject: Re: [Geoserver-users] GEOServer: app-schema & Feature Chaining
Good Morning Victor:
I'm working on the Geoserver 2.2 version
I have attached the complete folder cocities.zip
<http://osgeo-org.1560.n6.nabble.com/file/n5011072/cocities.zip> in a zip
file that contains, among other stuff, a mapping file with two FeatureMapping
,where each FeatureMapping points to a database table and a xsd that defines
the desired output.
Thank you very much for your help. I owe you many coffees :-)
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/GEOServer-app-schema-Feature-Chaining-tp5010210p5011072.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_sfd2d_oct
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
------------------------------------------------------------------------------
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_sfd2d_oct
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
