t it is rounded to 25, 100, 75. I've figured out the rounding portion, but when I plug the resulting list back into the custom preview, it doesn't recognize the data. I'm guessing it is because my rounded list is in curly brackets, whereas the unrounded data straight from the image sampler is not. How can I process this to remove the curly brackets?
Thanks,
Ryan
…
Added by Ryan Dirks at 5:20pm on September 18, 2014
, a1200)}) Is there any way I can make this list into {a1, a2, a3, a4, -a5, -a6, -a7, -a8, a9, a10, a11, a12, -a13, ..... , a1200} ? ( 4 positive signs then 4 negative signs and so on) - alternating every nth in general.
or
2. Is there any way (workaround) to get negative angle value from 2 vectors? I know 'ANGLE (of 2 vectors)' component by itself doesn't work and I know why too. I have feeling that the reflex angle output might be useful but again, matter of list manipulation.
Any help would be greatly appreciated. Thanks in advance.
Hyo
…
): 'Rhino.Geometry.TextEntity' does not contain a definition for 'FontIndex' and no extension method 'FontIndex' accepting a first argument of type 'Rhino.Geometry.TextEntity' could be found (are you missing a using directive or an assembly reference?) (line 92) 2. Error (CS1061): 'Rhino.Geometry.TextEntity' does not contain a definition for 'AnnotativeScalingEnabled' and no extension method 'AnnotativeScalingEnabled' accepting a first argument of type 'Rhino.Geometry.TextEntity' could be found (are you missing a using directive or an assembly reference?) (line 94)…
nologically label them (there are currently 65 points and this is labelled as in the file i've attached). However, what i'm actually after is to reformat these points into an x and y style grid.(a1, a2, a3, a4, a5)(b1, b2, b3, b4, b5)(c1, c2, c3, c4, c5)(d1, d2, d3, d4, d5) etc.Any ideas/help how this can be made possible would be great.Thanks in advance…
rees west to 1 degree west). Changing the latitudinal domain from, say, 0:1 (the equator to 1 degree north) to 88:89 (88 degrees north to 89 degrees north), has zero effect on the x,y shape of the topography map generated. However, in reality, the map should be far, far thinner in the latter case, because longitudinal lines get closer together toward the north and south poles. In actuality, the shape should be close to a trapezoid in both cases, but this is probably not a necessary detail for most people producing maps, since, at an urban or smaller scale, the latitudinal lines bounding the north and south of the map will probably not be that significantly different in length. But the maps should at least stretch from close-to-square for a 1 degree x 1 degree map near the equator to an extremely thin rectangle for a 1 degree x 1 degree map near the north pole.
As an example, I'm looking at a location in Sheffield, UK. The relevant SRTM HGT file spans from 53 N to 54 N, and 2 W to 1 W. The length of the map in the north-south direction should be approximately 111 km, as is the case with the topo map generated by Elk (and a near-standard for 1 degree latitude anywhere in the world). The length of the map in the east-west direction, however, should be somewhere in the range of 67 km, since the 2 W and 1 W longitudinal lines are much closer together at this latitude than they are at the equator. Thus the map should be nearly twice as long in the North-South direction as it is wide in the East-West direction.
If this were to be sorted out, I think it would be really nice to then have the SRTM topo map be positioned automatically in relation to the OSM map being brought in. I think it's good that the OSM map is positioned at 0,0, rather than it's world coordinates, but maybe the SRTM topo map could be aligned with it based on the latitude and longitude domains we input to the SRTM grasshopper module.…
I don't think I know what you mean. If it is that you want the curve numbers written out as text tags, use the reworked example below and adjust it to your needs.
/Ola
old version that has been fixed by now. I'd ask you to test this on the Rhino6 beta (which I am using to test this), but it looks like you're using a cracked version of Rhino so you probably don't have access to that.…