"There's no units or scale to the OSM data. Everything in the file is just latitude and longitude coordinates, so when you import it with Elk it converts the latitude and longitude to whatever units your project contain at a 1 to 1 scale.
"The problem is the OSM file you're providing is missing some information that Elk is expecting, particularly the <bounds></bounds> tag that's typically found near the beginning of the file. In a typical OSM file downloaded…"
"I expect it's not anything you're doing wrong so much as something is wrong in how Elk is handling the GeoTiff. All of the samples I used for testing were from what I had available, and they were all very standard 1°x1° tiles.…"
"I no longer work for the LMN where I developed Lyrebird, so there's not really much of an official distribution any longer that's even remotely up to date. I have continued to make edits to it and have contributed to it's github…"
"Any information found in tags should appear in the Feature Key (K) output of the OSM Data component. It's up to you to filter out the data based on the key you want. Here's an example of me looking for any highway data that has a tag…"
"It's likely a problem in Elk. I looked through the OSM file a bit for the ATM's and the hits when I searched for the text 'atm' in the file and found 17 hits, though 2 represented the same object because one of it's…"
I was looking at your great HKS blogpost on the Emotiv interface and grasshopper and have a few questions: (a) why didn't you simply use OSCs and link them back through something like ghowl? (b) have you looked into using emotion states…"
"I've had some people mention they can't get it installed, but I haven't been able to determine exactly why. I can tell you that you'll need to make sure all of the 26 files included in the ZIP file are all unblocked, the…"
"I'm running into two problems that I don't recall seeing before. First, when you have the "Show Individual Outputs" checked from the sub-feature selection window, the OSM Data component isn't outputting any data. …"
"If there's no error it's going to be difficult to help. From Elk 2 onward you do need to use 64bit Rhino 5 because the GDAL library it's using is 64bit. If you're running a 32bit version of Rhino then it won't…"
"Looks like a wonky filter in the Grasshopper component. It has a check to make sure the closed planar curves are planar in the XY plane, but was set to break apart the curve if it was passed, when it should only break it apart when it fails…"
I was looking at your great HKS blogpost on the Emotiv interface and grasshopper and have a few questions: (a) why didn't you simply use OSCs and link them back through something like ghowl? (b) have you looked into using emotion states (focus, excitement etc.) as input to the components rather than commands like blink etc? Thanks!
I am looking for the Topography file of Boston from USGS site,,,
The Lon and Lat of map I am working on is that Longitude is -71.086 to -71.0486, and the Latitude is 42.351 to 42.3716. So I download N42W071.hgt, but it does not match my map at all, then I was also trying to use N42W072.hgt, and eventually it matched. I wondering how this works, it was kinda weird.