Taz,
in the image you posted, this is what happens:
The Keys input of the Sort component operates on numbers. You are
providing a list of points. There is no data-translation defined
internally for {Point->Number}, but there are translations for {Point-
>Vector} and {Vector->Number}. The first simply copies over the x, y
and z values from a point into a vector, and the latter measures the
length of the vector. So, in effect, when you feed points into a
number parameter, what you actually end up with is a list of numbers
(one for each point) that represent the distance from that point to
the world origin (0,0,0). That is why your points have to be far away
from the origin for this to work. If the point grid was near the
origin, the points would have been sorted in concentric circles. If
you're far away enough, these circles start to straighten out and
their curvature will become smaller than the grid cell dimensions:
http://grasshopper3d.googlegroups.com/web/ConcentricSortCircles.png?gsc=BneQ9xYAAABgmkrzSTv_bJnBXWuCuy5MsJrAtjd9Fq-fV8M8HcFQDQ
It would be technically possible to get a set of unordered points, a
reference plane/surface and reverse engineer the grid from the
projected {uv} coordinates. this is way more complicated that just
linear sorting though. I'll have a look to see if I can some up with a
reasonably watertight algorithm for this.
--
David Rutten
Robert McNeel & Associates
On Oct 10, 2:17 am, taz <[EMAIL PROTECTED]> wrote:
> This is the easiest thing I could think to do.
>
> I referenced the 144 points in by windowing all of them at once. And
> then I let Grasshopper sort them.
>
> The list of points (looking at the sorted output of the key values) is
> sorted based on the distance from the origin to the point (or perhaps
> the magnitude of a vector...).
>
> To get a valid surface I had to shift all the points into the positive
> quadrant and move them far enough away from the origin. The U value
> is 12.
>
> There must be a smarter way to sort points referenced points, but
> David may have to chime in about that.
>
> http://groups.google.com/group/grasshopper3d/web/srfgrid_pts.png
>
> taz
>
> On Oct 9, 5:59 pm, oompa_l <[EMAIL PROTECTED]> wrote:
>
> > Hi Taz
>
> > I just uploaded a file with some points
> > :http://groups.google.com/group/grasshopper3d/web/some-points-01.3dm
>
> > there's nothing particularly meaningful about them - I constrructed
> > them for the purposes of this discussion. I was trying to tackle
> > another problem and I had wanted to go parametric with my surface....
>
> > thanks for the advice
> > Gabe
>
> > On Oct 8, 8:30 pm, taz <[EMAIL PROTECTED]> wrote:
>
> > > Well, that's the simplest example but look at the order of the points
> > > in the final list.
>
> > > You'll have to wrangle (sort) your referenced points into something
> > > similar (i.e. sort by x-coordinate, then y, z)
>
> > > Post your points, or an example, if you want.
>
> > > On Oct 8, 7:45 pm, oompa_l <[EMAIL PROTECTED]> wrote:
>
> > > > yes, i guess that does help. I had hoped there was a way to use points
> > > > that were already baked into the real model space as opposed to points
> > > > assembled into a rectangular grid. You basically answered my question
> > > > my suggesting that what I wanted to do is not possible, or should be
> > > > done in a different way.
>
> > > > thanks, sorry for the need to be hand-held...
>
> > > > On Oct 8, 7:29 pm, taz <[EMAIL PROTECTED]> wrote:
>
> > > > > oompa,
>
> > > > > See if this helps:
>
> > > > >http://groups.google.com/group/grasshopper3d/web/srfgrid_demo.png
>
> > > > > taz
>
> > > > > On Oct 8, 11:22 am, oompa_l <[EMAIL PROTECTED]> wrote:
>
> > > > > > once I have my points, one for each uv position how do I do the
> > > > > > "sorting"...and can they be sent to the SrfGrid component by a Pt
> > > > > > component (which represents a list of points)? I know this seems
> > > > > > elementary, but I'm not getting it...nor the surface.
>
> > > > > > thanks- Hide quoted text -
>
> > > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -
