[postgis-devel] Status of X3D
lr at pcorp.us
Sat May 9 14:26:35 PDT 2015
I haven't committed my work yet, but I think I have working geocoordinate
support at least for "GD" "WE" (both longitude_first and latitude_first
flavors) which I'll commit once I've done some more testing in x3dom and
updated the docs and tests. To use geocoordinate, data needs to be in 4326
(the only SRID I'll probably be supporting out of the gate).
One question I had is how much demand is there for the other spatial
reference frames. I didn't go down the path of supporting UTM and GC
flavors since that requires mapping to our spatial_ref_sys to derive those
values from the SRID passed in and reject if it can't be mapped.
From: postgis-devel-bounces at lists.osgeo.org
[mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Tom van Tilburg
Sent: Friday, May 01, 2015 3:44 AM
To: postgis-devel at lists.osgeo.org
Subject: Re: [postgis-devel] Status of X3D
I'm using it solely to work with X3Dom, and that works very nice but I had
troubles getting it from x3dom to other viewers. For sure there's some
problem with capitalization is well there.
For a working example of the output:
It's based on a combination of pgpointcloud and 2D vectordata where the 3D
result is extracted purely by using SQL.
Query is hypercomplex (and slightly dirty), I can sent on request.
@Regina: for the 2.2 release would be amazing! Looking forward :)
On 30-4-2015 23:44, Rémi Cura wrote:
I recently had a lot of trouble with x3D.
I couldn't use it with several geom in one file ( N Multipolygon in one
and a classic viewer (like MeshLab or CloudCompare in my case).
I resorted to use .PLY files, for which I feel shameful.
Any real world example (more complex than the PostGIS doc, and outputting
real x3D files)?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the postgis-devel