Hi Ben, Thanks for the reply. I've been working with an old app schema configuration that uses GeoSciML Portrayal 2.0, for which there are a couple of mandatory elements in the BoreholeView feature type other than positionalAccuracy that are breaking validation when null (namely specification_uri and metadata_uri). The positionalAccuracy element was a poor example to use in my original post.
Going to GeoSciML Portrayal 4.0 has solved the problem. All elements in the BoreholeView feature type have minOccurs="0" (except identifier and shape which will never be null in our database), and as such there's now no need to use encodeIfEmpty. Thanks again for your help. Regards, Aaron. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/app-schema-encodeIfEmpty-with-null-values-SEC-UNCLASSIFIED-tp5273475p5273667.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
