Elk 0.2 Released

I just wanted to let everyone know that there's an update for Elk available. I've added a generic OSM component to allow you to pull any data types from the file that you want. Otherwise it's unchanged from the previous release.

-Tim

Replies to This Discussion

Permalink Reply by Richard Schaffranek on February 23, 2012 at 10:40am

Hello,

create plugin!

Only took a few minutes to generate a complete city map and check what within five minutes of different points.

Just wondering in the .osm files some nodes are marked as an entrance:

but the generic OSM doesn't find these Points.

Does it only search inside the way tags?

Richard

Permalink Reply by m on March 2, 2012 at 1:06pm

Thanks for a great share Tymothy.

I can't get it to work with the data retrieved from the Planet.osm extracts though, as found for example here. The OSM's api limit of 50,000 nodes makes it rather unusable for downloading entire cities. What is the required data structure of the XML file to work with Elk? I figured out the bounds line is missing, adding it manually seems to do the trick just for the OSMData node. However both the way and generic OSM nodes fail to retrieve data...

Permalink Reply by Timothy Logan on March 2, 2012 at 2:23pm

Just scanning through one of the files I don't see anything else that's missing or out of place beyond the bounds node. Maybe it's an exception I'm missing somewhere. I've been working on some other changes, but my free time is almost non-existent for the moment so development is going slower than I'd like. I'll try to take a closer look at it sometime in the next couple of days.

-Tim

Permalink Reply by m on March 3, 2012 at 1:44pm

Ok, the problem seems to occur when a node referenced in the <way /> definition is missing from the osm file. I assume that Elk is set to abort the import of data when it encounters such a mismatch.

Maybe setting the default behaviour to skip the missing node would solve the problem?