Closed jaykayone closed 4 years ago
Hi,
I believe this is introduced through GDAL/OGR which is used to create the GML first hand: [1]
I've not found so far a OGR GML driver creation option to change that behavior. According to the W3C XML specification, NULL <> empty [2], so the generated XML is valid according to the specification, but this is probably not very helpful if your validator does not like this.
I think a hook to adapt this might be in [3] where an explicit check for NULL values is done through the plugin. A possible solution might be to set the attribute not to NULL, but to an empty string (in case of string values of course).
Anyway, just my 2c, since I'll need to use the plugin in the foreseeable future a couple of times again
Bonjour,
Doit-on effectuer une correction du plugin alors? Ou le checker sera adapté pour supporter la spécification W3C?
il faut une correction du plugin
Fixed in 081c3d401db1a19e384702bc08e4979f3ac24e91
Le GML exporté contient des tags de type nil=True
Notre checker n'accepte pas cette syntaxe. Dans l'ancien export, ces tags étaient omis