[Talk-ca] Multipolygon problems
james2432 at gmail.com
Fri Jun 30 14:20:23 UTC 2017
As john has said, we only have a couple hundred mappers for 9.985 million
square kilometers...or 27.93 germanies or 41.17 United kindoms or 15.5
Frances. Europe has hundreds of thousands of mappers, Canada does not. If
you wish to help out you are more than welcome as a NTS Grid tile section
usually takes about 2-3 hours to correct everything(knowing what you are
doing of course). It involves mind numbing clicking of buttons to keep all
relations when merging( I really wish there was an option to automatically
keep everything when merging instead of asking me for each of the 800+
polygons which would cut down the job to maybe 10-15 minutes....)
On Jun 30, 2017 9:46 AM, "john whelan" <jwhelan0112 at gmail.com> wrote:
Doing nothing for the moment looks extremely good to me.
Compared to many other areas of the world such as Germany and the UK we
have many fewer mappers per square kilometer. As James has stated this
sort of clean up requires fairly specialised resources that realistically
we don't have in sufficient quantity to meet your priorities and I think
the Canadian mappers have indicated this is not a high priority for them
and they are happy with the status quo.
The more important areas to the map as far as end users go are being
cleaned up but probably not as fast as you would like to see.
If you are willing to make the corrections then I feel sure that the
Canadian community would be happy to see them made.
On 30 June 2017 at 03:52, Jochen Topf <jochen at remote.org> wrote:
> A week ago I wrote this email and nobody answered it yet. Does that
> mean that nobody feels responsible for the import that created this data
> and nobody here cares for this data?
> I see three ways forward:
> * We do nothing. The broken data stays in OSM. Not a good solution,
> because every user of the data has to work around this or handle the
> * The Canadian community steps up and fixes the data, automatically or
> * We ask the Data Working Group to remove the broken import.
> On Thu, Jun 22, 2017 at 11:38:15AM +0200, Jochen Topf wrote:
> > Date: Thu, 22 Jun 2017 11:38:15 +0200
> > From: Jochen Topf <jochen at remote.org>
> > To: talk-ca at openstreetmap.org
> > Subject: [Talk-ca] Multipolygon problems
> > Hi!
> > In the last days the OpenStreetMap Carto Style 4.0 is being deployed on
> > the OSMF tile servers. This new version of the style doesn't take
> > old-style multipolygons (where the tags are on the outer ways instead of
> > on the relation) into account any more. In a huge effort in the last
> > months we have converted all old-style multipolygons to the modern
> > tagging, so this is a good step!
> > Unfortunately, as a side-effect of this change, many multipolygon
> > relations now appear wrong on the map. This is the case for multipolygon
> > relations that have the same tags on the relation as well as on (some of
> > the) outer or inner ways. This is *wrong* tagging, and needs to be
> > fixed. (Note that this always was wrong tagging, even before we
> > deprecated old-style multipolygons, but the way the software worked with
> > old-style multipolygons, this problem was not visible on the map. But
> > now it is.)
> > Here is an example: http://www.openstreetmap.org/relation/1330741 . As
> > you can see (unless somebody fixes this :-) the clearing in the forest
> > that should just have grass, also has tree symbols on it. In many other
> > cases it is not this obvious, there are just islands in a river missing
> > or so.
> > There are about 50,000 cases like this worldwide, forests, waterways,
> > all sorts of areas. But the worst problem is in Canada. There are about
> > 15,000 affected relations, most from the CanVec imports.
> > First, we have to make sure that there are no further imports of broken
> > data. I hope the people who have done those imports (and might still
> > continue) are here on this mailing list. If not please make them aware
> > of this issue and/or put me in touch with them. Second, somebody needs
> > to clean up the broken data, either automatically or manually. 99% of
> > the data has not been changed since the import, so it might be feasible
> > to do an automatic cleanup, but somebody has to do this. Otherwise we'll
> > have to do a manual cleanup, through tools such as Maproulette and the
> > OSM Inspector. I am currently in the process of creating Maproulette
> > challenges for other areas of the planet, but will not do this for
> > Canada at this time. Lets discuss this here first.
> > I can provide OSM data extracts, statistics, etc. if somebody wants to
> > look at the data.
> > All of this is part of a larger effort to fix areas in OSM. See
> > http://area.jochentopf.com/ for more information. There is also a thread
> > on the talk mailinglist at
> > https://lists.openstreetmap.org/pipermail/talk/2017-June/078203.html
> > and this issue
> > https://github.com/osmlab/fixing-polygons-in-osm/issues/36 .
> > News of the effort are posted regularly to
> > https://github.com/osmlab/fixing-polygons-in-osm/issues/15 .
> > Jochen
> > --
> > Jochen Topf jochen at remote.org https://www.jochentopf.com/
> > _______________________________________________
> > Talk-ca mailing list
> > Talk-ca at openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-ca
> Jochen Topf jochen at remote.org https://www.jochentopf.com/
> Talk-ca mailing list
> Talk-ca at openstreetmap.org
Talk-ca mailing list
Talk-ca at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Talk-ca