On Monday 20 March 2017, Andreas Vilén wrote:
>
> It's not up to me to decide if this data is to be deleted or not. If
> you want to do that, raise the question with each respective
> country's mailing list.
I don't want to push the issue - and there is little chance for such a
suggestion without
On Mon, Mar 20, 2017 at 07:15:47AM +0100, Jochen Topf wrote:
> On Mon, Mar 20, 2017 at 06:27:05AM +0100, Andreas Vilén wrote:
> > It's not up to me to decide if this data is to be deleted or not. If
> > you want to do that, raise the question with each respective country's
> > mailing list.
>
> I
On Mon, Mar 20, 2017 at 06:27:05AM +0100, Andreas Vilén wrote:
> It's not up to me to decide if this data is to be deleted or not. If
> you want to do that, raise the question with each respective country's
> mailing list.
I was under the impression that were in contact with the Swedish
community
There is a difference between data errors that the osmi will detect and bad
quality map data. Corine is the latter.
It's not up to me to decide if this data is to be deleted or not. If you want
to do that, raise the question with each respective country's mailing list.
/Andreas
Skickat från mi
On Sunday 19 March 2017, Andreas Vilén wrote:
>
> Also, as has been pointed out earlier, Corine data might be bad, but
> does not contain that many pure data errors as we define them.
That is not quite accurate in my experience. As i explained in
https://lists.openstreetmap.org/pipermail/talk/20
On Sun, Mar 19, 2017 at 12:09 PM, Martin Koppenhoefer <
dieterdre...@gmail.com> wrote:
>
> On 18 Mar 2017, at 21:40, Sandor Seres wrote:
>
> In another style, typical land related names are on the water like here
> http://osm.org/go/0Tt1PZIt-?layers=T .
>
>
> seems like either a bad import or loc
Also if I remember correctly the whole point was to optimize/be able to
process osm data faster by not having to deal with so many errors(each case
can slow down the processing)
On Mar 19, 2017 7:23 AM, "Martin Koppenhoefer"
wrote:
>
>
> sent from a phone
>
> > On 19 Mar 2017, at 10:03, Andreas
sent from a phone
> On 19 Mar 2017, at 10:03, Andreas Vilén wrote:
>
> The main problem with Corine is that oftentimes the landuse data overlaps
> villages (which I found when I mapped mountain villages in southern Spain
> last week as well)
whenever looking closeup at any corine data it w
sent from a phone
> On 18 Mar 2017, at 21:40, Sandor Seres wrote:
>
> In another style, typical land related names are on the water like here
> http://osm.org/go/0Tt1PZIt-?layers=T .
seems like either a bad import or localities on the sea, e.g. here:
http://www.openstreetmap.org/node/25351
To be fair, "the local community" in this case is probably mostly me and my
interpretation of the Swedish community's reaction when someone tried to
remove Corine imagery rather carelessly (introduced a lot of new errors) a
couple of years ago. It's too bad that we're talking about a region when no
Sandor,
if I understand you correctly your basic message is "let's try and
improve osm2pgsql's polygon interpretation rules instead of fixing the
data", or at least "while we wait for the data fixing to be completed".
I think this is not a good idea because, as you remark yourself, those
worki
There has been some discussion on the HOT mailing list that makes things a
bit clearer.
OSM in general has a fair number of things that have been added in a less
than ideal way. It can be difficult to correct some things as we have
guidelines or recommended practises as opposed to hard and fast r
12 matches
Mail list logo