> El 4 mar 2016, a las 10:37, Janko Mihelić escribió:
>
> I think existing mappers are not the biggest problem. If mapping starts being
> paid, there may be an influx of new mappers who do it only for the money.
>
> They will, of course, map a lot because that's how you get more money. They
>
Ar...
>
>> For info just in case you haven't seen it, this previous thread on the
> "dev" list explains why coastline updates stopped temporarily:
>
>
> https://lists.openstreetmap.org/pipermail/dev/2016-February/thread.html#29068
>
> Ok,
In fact actually there is not lake with coastline beca
I think existing mappers are not the biggest problem. If mapping starts
being paid, there may be an influx of new mappers who do it only for the
money.
They will, of course, map a lot because that's how you get more money. They
will introduce skewed mapping practices at best, and outright wrong ma
On 03/03/2016, Richard wrote:
>> Even without talking about nefarious schemes, even well-meaning users
>> will tend to change their mapping behavior because of this. In this
>> case it's about uploading more often, potentially making changes
>> harder to follow.
>
> imho it would be good if people
On 04/03/2016 10:55, Jérôme Seigneuret wrote:
...
It is possible to refresh the base water layer if it is the unique
solution?
For info just in case you haven't seen it, this previous thread on the
"dev" list explains why coastline updates stopped temporarily:
https://lists.openstreetmap
On Friday 04 March 2016, Jérôme Seigneuret wrote:
>
> There is no consensus about this matter? I am not aware of war
> tagging... I thought that it was the solution because multipolygon
> exist and costline isn't really needed.
No - multipolygon and coastline mapping of lakes in parallel has exist
>
> z<=12 is re-rendered monthly or after style updates or based on manual
> tile expiry. But this won't do you any good since any change in
> coastline tagging of larger lakes will stall coastline processing and
> the data won't be updated even if you re-render the tiles.
>
OK. I understand.
So
On 04/03/16 11:06, Janko Mihelić wrote:
> Paying mappers should have a very intricate web of defined jobs and
> reviewers. Ideally, OSM Tasking Manager should be used. "Map all forests
> and roads in this square, I review, and you get 0.1 bitcoins". Anything
> less strict is prone to misuse.
A mec
On Friday 04 March 2016, Jérôme Seigneuret wrote:
>
> You can compare results between 13 and 12 level. (what is refresh
> delay for level <=12?)
z<=12 is re-rendered monthly or after style updates or based on manual
tile expiry. But this won't do you any good since any change in
coastline taggi
Paying mappers should have a very intricate web of defined jobs and
reviewers. Ideally, OSM Tasking Manager should be used. "Map all forests
and roads in this square, I review, and you get 0.1 bitcoins". Anything
less strict is prone to misuse.
Janko
pet, 4. ožu 2016. u 10:36 Lester Caine napisa
Hi,
I use OSM Inspector to check coastlines. In european block, I fixed lakes
because outer and inner ways of multipolygons also contains tags with
natural=coastlines...
I removed natural=coastlines but it cause graphics problems on rendering
for inner part of multipolygons.
exemple Lake Ladoga
pet, 4. ožu 2016. u 02:48 Hans De Kryger
napisao je:
>
> My guess is yes, i just checked it and the website is using data from at
> least 2013 or newer so i'm assuming they'd have to accept osm's license
> since that's years after the change. Hopefully that's what you meant Janko?
>
What I mean
On 03/03/16 11:17, Marc Gemis wrote:
> If I understand the discussion on [1] correctly OsmAnd will reward
> mappers with bitcoins. The bitcoins seem to be paid via a formula
> based on the number of changesets you upload.
>
> I think this is a bad idea, (just like Jack Burke illustrates with the
>
13 matches
Mail list logo
