Thank you to the volunteers who helped out, and the support of the OSM
community.
In this regard, we wish to call on your feedback/inputs regarding how the
community can clearly communicate whether data sources are compatible (or
incompatible) with OpenStreetMap.
I have drafted an FAQ [1] that i
Hi everyone,
This work is finished. It took a while due to the complexity of the revert.
What this means right now is that place geocoding (via nominatim ) is
less accurate and the visual map for boundaries has less details.
However, our map is much better without incompatible licensed data!
Than
After reviewing initial results of the automated rollback [0] we
decided to do a manual process involving a couple of mappers [1].
Please check the workflow linked and let us know if anyone wants to help.
[0] https://github.com/OSMPH/papercut_fix/issues/67#issuecomment-653891322
[1] https://github
FYI, we are starting the rollback, I advise that we don't touch any of
the related changesets until the rollback is done.
https://github.com/OSMPH/papercut_fix/issues/67#issuecomment-653737739
On Tue, Jun 30, 2020 at 3:18 PM maning sambale
wrote:
>
> Hi Everyone,
>
> After reviewing the edits and
On 30/06/2020 08:15, maning sambale wrote:
After reviewing the edits and communicating with the mapper, we
decided to roll-back all edits related to this issue due to
incompatible source.
We plan to do this as a local community. Please see the plane here
for comments and suggestions:
https://git
Hi Everyone,
After reviewing the edits and communicating with the mapper, we
decided to roll-back all edits related to this issue due to
incompatible source.
We plan to do this as a local community. Please see the plane here
for comments and suggestions:
https://github.com/OSMPH/papercut_fix/issu