[postgis-users] PostGIS and X3D - Adding a optionnal parameter for value -1

[Pedro Doria Meunier]

In all my humbleness...
Please **full** beta-test things before committing anything...
Pedro.

-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of TECHER
David
Sent: quinta-feira, 12 de Abril de 2007 0:08
To: PostGIS Users Discussion; PostGIS Development Discussion
Subject: Re: [postgis-users] PostGIS and X3D - Adding a optionnal parameter
for value -1

Hi Oliver,

First of all, sorry for my  being late to answer you.

I think this kind of function is very, very interesting! :)

Since you understand French as you can see in the following link - 
that's only for the fun -
http://www.davidgis.fr/blog/index.php?2007/04/09/207-un-petit-importateur-x3
dtopgsql-made-by-myself 

my wish is that asx3d() could be implement in the futur in PostGIS!

As you mentionned for the specification, SFS 1.2 TIN and POLYHEDRON so 
why not implement your function (you and David)???

Let's go for a first 3d function in PostGIS!  A first functon  for 
viewing our data in 3d!

Win, GNU/Linux, Mac OS X have good player for x3d data: octagaplayer, 
freewrl,and so on!


I hope ;)

Olivier Courtin a écrit :
> Quoting TECHER David <davidtecher at yahoo.fr>:
>
> Hi David,
>
> First please to me that this new kind of feature seem interresting :)
>
>> I ask for that because parsing the coordIndex from a x3d file is not 
>> possible. PostgreSQL reports to me the following error
>>
>> multidimensional arrays must have array expressions with matching 
>> dimensions
>>
>> for example something like array[[1,2,3][1,3,4][4,7,12,13]]
>> That's the only solution I've found!
>
> Well with the last week code, you should be able to import with 
> something like
> that:
> array[[1,2,3,-1][1,3,4,-1][4,7,12,13]]
>
> So a -1 in the initial array structure could be used to 'complete' an 
> array
> with ignorable value.
> Of course it's still such an hack because imagine you have only one 
> face with 10
> nodes, and quite a few with only 3, you will have a lot of useless 
> values...
>
> Our first implementation (David and i) was initially designed to 
> handle right
> TIN structure (so it's always triangle), but as X3D also support variable
> structures like square and so on... well it's was a quick and dirty 
> way (i.e -1
> useless value) to handle this feature...
>
> For the moment the only 'clean' way to handle 3D structure storage in 
> Postgis
> seem to implement SFS 1.2 TIN and POLYHEDRON as said last week.
>
> I don't have yet reaction for Paul or Sandro, if this new types could 
> be add
> in Postgis SVN, if such a patch provided.
>
> My 2 cents,
>
> -- 
> Olivier
>



	

	
		
___________________________________________________________________________ 
Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son
interface révolutionnaire.
http://fr.mail.yahoo.com
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users