[OSM-dev] Import OSM (XAPI/.osm) Into Drupal

2012-11-13 Thread Alex Rollin
Hi! I have a site configured and could really use some help with XPATH queries to select nodes for import into my site. I've worked for almost a year now and put over a million changes into OSM.org and it would be super-dee-duper if you could please help me to figure out how to access that data

Re: [OSM-dev] WHODIDIT

2012-11-13 Thread Simon Legner
Hi Pierre, The Age drop-down list as a strange behaviour. The html page seems to be updated properly to reflect the Age option selected. But the content of the Age box is not always updated properly. It is possible to select the seven Age options listed, but only the first three are showed

Re: [OSM-dev] Segmentation fault using Osmium

2012-11-13 Thread Jochen Topf
This looks like you simply run out of memory. Running osmium_mpdump on Berlin takes about 1.3 GByte of RAM. Do you have enought RAM? Jochen On Sun, Nov 11, 2012 at 01:30:05AM +0100, Konstantin Clemens wrote: Date: Sun, 11 Nov 2012 01:30:05 +0100 From: Konstantin Clemens

Re: [OSM-dev] Import OSM (XAPI/.osm) Into Drupal

2012-11-13 Thread Simon Legner
Hi! lat - lat v='name' - title `//node` should give you a list of nodes. For each of these nodes `@lat` would give the latitude, and `tag[@k='name']/@v` would give the name field. If anyone has other ideas for simply converting this to a CSV file that would be nice also, but, at some

Re: [OSM-dev] WHODIDIT

2012-11-13 Thread Pierre Béland
Thanks Simon, It is effectively fixed. A second problem. There are areas whitout any report were I know that there are some edits up to recently. See for example http://simon04.dev.openstreetmap.org/whodidit/?zoom=14lat=45.647lon=-72.56572layers=BTTTage=6%20month

Re: [OSM-dev] WHODIDIT

2012-11-13 Thread Simon Legner
Hi Pierre, On 13/11/12 14:38, Pierre Béland wrote: A second problem. There are areas whitout any report were I know that there are some edits up to recently. See for example http://simon04.dev.openstreetmap.org/whodidit/?zoom=14lat=45.647lon=-72.56572layers=BTTTage=6%20month

[OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Simon Legner
Hi all, I'd like to find out what the current status of the Mapnik stylesheets for www.osm.org is. The most recent changes are from June 2012 [1], and the number of open tickets in TRAC is 400 [2]. Who is responsible for incorporating changes? Is some help needed? How are those changes

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Paweł Paprota
On 11/13/2012 03:48 PM, Simon Legner wrote: Hi all, I'd like to find out what the current status of the Mapnik stylesheets for www.osm.org is. The most recent changes are from June 2012 [1], and the number of open tickets in TRAC is 400 [2]. Indeed... I looked at the same thing 2-3 weeks ago

Re: [OSM-dev] WHODIDIT

2012-11-13 Thread Pierre Béland
Yes, to do efficient monitoring of an area, It is of interest to show edits other then nodes. But I understand the technical challenge. There were nodes edited in the area but they are not reported. The last ones are in december 2011. for example : node id='1452468075'

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Lennard
On 13-11-2012 15:48, Simon Legner wrote: I'd like to find out what the current status of the Mapnik stylesheets for www.osm.org is. The most recent changes are from June 2012 [1], and the number of open tickets in TRAC is 400 [2]. Currently it's in a bit of a holding pattern. Personally, I'm

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Lennard
On 13-11-2012 15:58, Paweł Paprota wrote: I'd say the priority should be bringing the main style onto the pretty side... If you take a look at the amount of open tickets, pretty clashes heavily with I want $feature rendered, where $feature ranges from 'yes, probably, sounds sane enough' to

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Paweł Paprota
On 11/13/2012 09:46 PM, Lennard wrote: On 13-11-2012 15:58, Paweł Paprota wrote: I'd say the priority should be bringing the main style onto the pretty side... If you take a look at the amount of open tickets, pretty clashes heavily with I want $feature rendered, where $feature ranges from

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Paweł Paprota
On 11/13/2012 11:13 PM, Derick Rethans wrote: I would rather see as much useful things rendered that make sense for *mappers*. Pretty tiles should also be made, but as far as I know, the default style that is on openstreetmap.org is for *us* - the people who add data. Well, that's the usual

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread sly (sylvain letuffe)
Le mardi 13 novembre 2012 23:25:44, Paweł Paprota a écrit : On 11/13/2012 11:13 PM, Derick Rethans wrote: I would rather see as much useful things rendered that make sense for *mappers*. Pretty tiles should also be made, but as far as I know, the default style that is on openstreetmap.org

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Paweł Paprota
On 11/13/2012 11:32 PM, sly (sylvain letuffe) wrote: I share Derick's view, but maybe what we need is someone to just do it and split the problem in two maps. http://wiki.openstreetmap.org/wiki/Contributors_functionalities_wishlist#Backgound_map_with_the_most_possible_objects Sure,

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Tom MacWright
The biggest problem with the Mapnik stylesheet right now is that it's in SVN. Not the technology, but the fact that this gives people without commit access to that repository no clear way to contribute. There is no way to 'just do it' until the style is actually maintained in GitHub, actually

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread yvecai
On 11/13/2012 11:23 PM, Tom MacWright wrote: Ideally we can move the osm stylesheet to github, close non-actionable tickets and address those that can be addressed. I pretty much agree here. 400 tickets could turns into 50 pull requests merged in a week, just with a few clicks from the

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread yvecai
On 11/13/2012 09:45 PM, Lennard wrote: This requires a reload of the database to at least get public_transport=* in. Handling role values, like stop, is not supported yet. Could some columns be added live instead of a complete reload? ___ dev

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Simon Legner
Hi! On 13/11/12 23:36, Tom MacWright wrote: The biggest problem with the Mapnik stylesheet right now is that it's in SVN. Not the technology, but the fact that this gives people without commit access to that repository no clear way to contribute. There is no way to 'just do it' until the style

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Tom Hughes
On 13/11/12 22:45, Simon Legner wrote: On 13/11/12 23:36, Tom MacWright wrote: The biggest problem with the Mapnik stylesheet right now is that it's in SVN. Not the technology, but the fact that this gives people without commit access to that repository no clear way to contribute. There is no

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Tom Hughes
On 13/11/12 22:42, yvecai wrote: On 11/13/2012 11:23 PM, Tom MacWright wrote: Ideally we can move the osm stylesheet to github, close non-actionable tickets and address those that can be addressed. I pretty much agree here. 400 tickets could turns into 50 pull requests merged in a week, just

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Tom Hughes
On 13/11/12 22:43, yvecai wrote: On 11/13/2012 09:45 PM, Lennard wrote: This requires a reload of the database to at least get public_transport=* in. Handling role values, like stop, is not supported yet. Could some columns be added live instead of a complete reload? We plan to reload the

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Simon Legner
Btw … is someone trying to collect some mirrors? :-D https://github.com/openstreetmap/mapnik-stylesheets/tree/mirror/mirror/mirror/mirror/mirror/mirror/mirror/mirror/mirror/mirror/mirror/mirror/mirror/master ___ dev mailing list dev@openstreetmap.org

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Martin Koppenhoefer
2012/11/13 Tom Hughes t...@compton.nu: Well maybe not... We don't actually want every random POI icon that a user submits to be merged willy nilly - we want somebody to apply some cartographic thought when choosing what to merge. That is an important point. Developing a map style is not

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Dane Springmeyer
On Nov 13, 2012, at 12:45 PM, Lennard wrote: On 13-11-2012 15:48, Simon Legner wrote: I'd like to find out what the current status of the Mapnik stylesheets for www.osm.org is. The most recent changes are from June 2012 [1], and the number of open tickets in TRAC is 400 [2]. Currently

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Matt Amos
On Tue, Nov 13, 2012 at 10:36 PM, Tom MacWright t...@macwright.org wrote: There is no way to 'just do it' until the style ... has active maintainers. Until then we're just talking. seems like this might be the major hurdle - there do seem to be people willing to contribute on this thread, but

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Kai Krueger
Matt Amos wrote i'd sound a note of caution about having separate clean and detailed styles. we sort-of did that before with mapnik and osmarender respectively and... well, we don't have osmarender any more. I doubt that having to maintain two styles was what killed osmarender. It was a

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Kai Krueger
Dane Springmeyer wrote I'm sorry about not providing Windows binaries yet for Mapnik 2.x. The holdup is that I have a dev environment working that is running Visual Studio 2010, and I need to get a parallel setup running Visual Studio 2008 for support compiling the python bindings. Its a silly

Re: [OSM-dev] Status of the Mapnik stylesheets

2012-11-13 Thread Kai Krueger
Tom MacWright wrote The biggest problem with the Mapnik stylesheet right now is that it's in SVN. Not the technology, but the fact that this gives people without commit access to that repository no clear way to contribute. There is no way to 'just do it' until the style is actually maintained