On 09/11/12 22:00, RudyWI wrote: > Ben Caradoc-Davies wrote >> Sorry, user-defined geometry types are not supported. GeoServer (and >> GeoTools) relies on compiled Java bindings for all geometry types, and >> as far as I know, cannot encode user-defined geometry types. > I would like to implement Java bindings for my user-defined geometry types.
All Java bindings for GML 3.1.1 and GML 3.2.1 geometry types are in the GeoTools gt-xsd-gml3 module, in modules/extension/xsd/xsd-gml3 Why do you need your own geometries? I have copied Justin Deoliveira, maintainer of the GeoTools module. You will be asking him for help. > Where can I find Application Schema Mapping source code ? All source code for the gt-app-schema module is in modules/extension/app-schema/app-schema in GeoTools. > Do you have any advise to perform this implementation ? Why do you wish to define your own geometry types? My first advice is to not do so. (1) Unless you have niche requirements, I bet that this is the hardest way to solve a problem that can be solved with other patterns. I have previously suggested to you that you should consider modelling your data with has-a geometries (composition, aggregation) rather than is-a geometries (inheritance). Have you considered this approach? (2) GML is for interoperability. By defining your own geometry types you are using the GML at its least popular level (highest complexity), reducing interoperability. You might also have to write a client to consume these types. Kind regards, -- 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
