Finish up X3D implementation for all types

[robe]

When I created ST_AsX3D I was only focused on 3D bojects — TINS and Polyhedral Surfaces. So there are a lot of loose ends left. Now that I have my Minimalist X3D viewer HTML/JQuery/X3DomJS for I can now easily test out all the deficiencies. Like right now to see a 2D polygon I have to extrude it. It also doesn't handle collections of Polyhedral surfaces and TINS. I hope to clear up all these loose ends before 2.2.0 rolls out and perhaps backport to 2.1 because it is buggy for these in that it tries to handle them and errors out or does the wrong thing.

[robe]

collections of tins should now behandled at r12825. Now I can try out complicated tesselations Still need to fix up handling of polyhedral in collections and then will backport to 2.1 since it was invalid markup so was a bug.

[robe]

actually collections aren't quite handled. I'm just outputting them by recursing, but technically each should be wrapped in a shape and then grouped. That deviates from the model I have for the others. I'm thinking of using the switch (which currently is 0) to denote if x3d should output with shape / grouping tags or just always output collections that way. Other options will include whether to use regular coordinates or X3D geocoordinates.

[robe]

r12847 added shape tags around each geometry in a collection. Haven't documented the behavior yet since not sure I will keep it.

[robe]

To add to this X3D supports curves, so it will be really nice to handle curves as well and since there are few viewers for curved geometries, this will be especially nice to be a able to see curves in the browser with x3dom/html5 power and a smartering of some SQL magic.

[robe]

Milestone renamed