Here's the puzzle of the day for the brave (Big Prize: ONE secondhand sardine can, no kidding in pure 15W/50 mineral oil).
Explain this mismatch (85 VS 75):
Moral: life sucks
End of method assumed. (line 90)Error: Comma or ')' expected. (line 90)Warning: Function 'GetFrustumNearPlane' doesn't return a value on all code paths. Are you missing a 'Return' statement? (line 91)…
Added by Adam Chałupski at 11:24pm on September 23, 2012
urs x 365 days ), and with modulus in the screenshot above, i could manage to do for every hour. but sometimes in my definition, i have a range from 1 to 35040, which is 365 x 24 x 4 ( 4 here defines every 15 minutes), on other word, when the number is one, then i have 01:00 O'Clock, when the number is 2 then i have 01:15 O'clock, when the number is 3 then i have 01:30 O'Clock...etc , so when the number is 97, which is the next day ( and after the number 96 which is equal 24 hours x 4), then I should have again 01:00 O'Clock.
I hope my idea is clear, thanks in advance!
Nassif…
to an ngon in plankton.
1. Error (CS1061): 'Plankton.PlanktonMesh' does not contain a definition for 'ToPolylines' and no extension method 'ToPolylines' accepting a first argument of type 'Plankton.PlanktonMesh' could be found (are you missing a using directive or an assembly reference?) (line 91)
thanks very much for your amazing work …
ale dell'intera superficie e non delle superfici in cui è scomposta, ti allego il file puoi indicarmi l'errore?
mi piacerebbe fare un corso a Roma quando sarà il prossimo
grazie federico…
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.…
the map? For example in one list I want curves 5, 20, 21, 22, 23, 60. In another I want curves 1, 37, 40. In another maybe 70-80. And in the last, all curves that aren't specified in those three lists. Is there a way to partition the lists as such?…