> -----Original Message----- > From: Ryan Moody [mailto:[email protected]] > Sent: 23 October 2013 14:02
> As you can see, the featureData element can have multiple values – what ... > Can you also please advise if this scenario requires my tables to be > denormalised prior to the App-Schema mapping, and what the performance > implications of this might be, i.e: Yes, I think the only way to get multiple _simple_ property values is to use a denormalised table (or view joining your two tables) with multiple rows for each parent feature. GeoServer will coalesce these into one feature following http://docs.geoserver.org/stable/en/user/data/app-schema/mapping-file.html#denormalised-sources and setting the isMultiple setting to true on your simple multiple-valued property http://docs.geoserver.org/stable/en/user/data/app-schema/mapping-file.html#ismultiple-optional. I would be interested myself in finding out if there is any other way. Marcus Sen This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
