[OSM-talk] osmapi 0.5.0 for python supports changeset discussion

2015-01-03 Thread Stefan Oderbolz
Hi there, the python wrapper for the OSM API now finally supports changeset discussions, the new feature introduced in November: https://pypi.python.org/pypi/osmapi In the course of this update, I also added the new calls to the API wiki page: http://wiki.openstreetmap.org/wiki/API_v0.6. Cheers

[OSM-talk] MEP - pipelines

2015-01-03 Thread Rainer Fügenstein
in accordance to the mechanical edit policy, I'd like to open the discussion on this list: a recently approved proposal introduced new tags for pipelines and marker [1] and changed an established tag: type=* was changed to substance=* the main reason for this change was a (possible) conflict wi

Re: [OSM-talk] MEP - pipelines

2015-01-03 Thread François Lacombe
I don't see any objection to do as Rainer suggested. Maybe someone can give us examples of conflict with any other data ? All the best *François Lacombe* fl dot infosreseaux At gmail dot com www.infos-reseaux.com @InfosReseaux 2015-01-03 17:50 GMT+01:00 R

Re: [OSM-talk] MEP - pipelines

2015-01-03 Thread Chris Hill
On 03/01/15 16:50, Rainer Fügenstein wrote: in accordance to the mechanical edit policy, I'd like to open the discussion on this list: a recently approved proposal introduced new tags for pipelines and marker [1] and changed an established tag: type=* was changed to substance=* The values may

Re: [OSM-talk] MEP - pipelines

2015-01-03 Thread François Lacombe
2015-01-03 18:22 GMT+01:00 Chris Hill : > > The values may need changing, e.g. type=sewer become substance=sewage > +1 indeed > > > What about the maps I produce for my client? You're not likely to know > about it as it is a private project. If you make a mechanical edit that > breaks my render

Re: [OSM-talk] MEP - pipelines

2015-01-03 Thread Rainer Fügenstein
CH> No, just because a handful of wiki 'votes' does not mandate a mechanical CH> edit. OK, then we'll have split data. CH> What about the maps I produce for my client? You're not likely to know what about changing the rendering rules after the mechanical edit? the purpose of this discussion i

Re: [OSM-talk] MEP - pipelines

2015-01-03 Thread Werner Hoch
Hi, Am Samstag, den 03.01.2015, 17:50 +0100 schrieb Rainer Fügenstein: > in accordance to the mechanical edit policy, I'd like to open the > discussion on this list: > > a recently approved proposal introduced new tags for pipelines and > marker [1] and changed an established tag: > > type=* was

Re: [OSM-talk] 176k Wikidata tags to add to OSM

2015-01-03 Thread Morray
Hi Edward, any updates on your project? As said before, I would love to see some test imports. Am 24.11.2014 um 12:28 schrieb Edward Betts: > It has been suggested that I shouldn't be using Wikipedia at all, instead I > should be looking at the 'instance of' property in Wikidata. Using English > W

Re: [OSM-talk] MEP - pipelines

2015-01-03 Thread Chris Hill
On 03/01/15 17:46, François Lacombe wrote: 2015-01-03 18:22 GMT+01:00 Chris Hill >: What about the maps I produce for my client? You're not likely to know about it as it is a private project. If you make a mechanical edit that breaks my render, should I

Re: [OSM-talk] MEP - pipelines

2015-01-03 Thread François Lacombe
2015-01-03 21:18 GMT+01:00 Chris Hill : > > I include some mechanical edits as vandalism, other than that, vandalism > has not caused me any problems at all. > I was too. And I don't understand why a static snapshot can't help you regarding changes that don't suit your needs. > > If you must ad