Hello TomesLaw,

I hope you don't mind me asking about an edit from 9 years ago. On this changeset you added a "source=Google" tag on node/2232000240 here. We can't actually use that as a source in OSM because the Google's licence doesn't allow it to be used here - it would cause real problems for the project if we were found to be using Google Maps as a source.
As this is your business, "source=local_knowledge" would be perfectly OK.

Best Regards
Andy Townsend, on behalf of OSM's Data Working Group

Sorry, that should be "Hello thalyaface" - copy and paste error from a previous message!

Hello deldred,

I hope you don't mind me asking about an edit from 10 years ago. On this changeset you added a "source=Google" tag on node/1622836795 here. We can't actually use that as a source in OSM because the Google's licence doesn't allow it to be used here - it would cause real problems for the project if we were found to be using Google Maps as a source.
If this is somewhere that you are familiar with, then "source=local_knowledge" would be perfectly OK.

Best Regards
Andy Townsend, on behalf of OSM's Data Working Group

Hello deldred,

I hope you don't mind me asking about an edit from 8 years ago. On this changeset you added a "source=Google" tag on node/2320263113 here. We can't actually use that as a source in OSM because the Google's licence doesn't allow it to be used here - it would cause real problems for the project if we were found to be using Google Maps as a source.
If this is somewhere that you are familiar with, then "source=local_knowledge" would be perfectly OK.

Best Regards
Andy Townsend, on behalf of OSM's Data Working Group

Hello Nadeau,

I hope you don't mind me asking about an edit from 8 years ago. On this changeset you added a "source=Google" tag on node/2561302571 here. We can't actually use that as a source in OSM because the Google's licence doesn't allow it to be used here - it would cause real problems for the project if we were found to be using Google Maps as a source.
If this is somewhere that you are familiar with, then "source=local_knowledge" would be perfectly OK.

Best Regards
Andy Townsend, on behalf of OSM's Data Working Group

你好霍華德cc1，
請不要將測試數據添加到 OpenStreetMap。 如果你想測試一下，請使用開發服務器。 有關更多詳細信息，請參閱 osm.wiki/Sandbox_for_editing#Experiment_with_the_API_(advanced)。
此致，
安迪

Hello howardcc1,
Please don't add test data to OpenStreetMap. If you want to test things out, please use the development server. See osm.wiki/Sandbox_for_editing#Experiment_with_the_API_(advanced) for more details.
Best Regards,
Andy

Hello,
I've remapped the gap in changeset/123395426 and added a bit more detail to the immediate area in changeset/123395629 .
There's lots more that can be done, including the "large not all grass fixme".
Best Regards,
Andy

Hello,
I've remapped this in changeset/123395426 and added a bit more detail to the immediate area in changeset/123395629 .
There's lots more that can be done.
Best Regards,
Andy

If you are an organisation that has customers, you probably need to follow https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines .

Hello,
Who are you if you have "customers"?
Best Regards,
Andy

Hello - I've filled in a gap in NCN422 here in osm.org/history - hope this is OK. Bother sides either side of it are route relation members, so I've assuming that this bit is too.
Best Regards,
Andy

Hello,
Just to let you know that I've connected up a gap in NCN1 here relation/9579#map=18/56.19986/-3.41796 in changeset/123333039 . The previous layout https://overpass-api.de/achavi/?changeset=123247480 had a bit of a "convenience link" across the (old?) car park that didn't match the recent imagery. Hopefully my link around the service roads is OK.
Best Regards,
Andy

As requested earlier, please use changeset comments that explain to other mappers what you have done. "675" does not do this.

Hello,
What change was actually made here? "a few tweaks" doesn't really help :)
For info, changeset/123170512 (the changeset before yours here) deleted a bit of the Jubilee Way. See https://nrenner.github.io/achavi/?changeset=123170512 for info.
Best Regards,
Andy

Hello,
In this changeset you created a gap in the Jubilee Way. Before:
https://overpass-turbo.eu/s/1jVd
After:
https://overpass-turbo.eu/s/1jVe
Looking at the imagery, it looks like there is a path through.
Turn on GPS traces, and you can see that a bit of GPS traces matches the OS OpenData StreetView. Of the other imagery Bing isn't much help but Esri and Maxar do show something a little to the west of the GPS trace.
Best Regards,
Andy

Hi Dudley,
Just wondered - is way/973303758/history really a castle wall?
I don't think I've ever got that close to it, but it seems a bit unlikely?
Best Regards,
Andy

According to https://lists.openstreetmap.org/pipermail/talk-gb/2022-July/029121.html , it appears that the mapping in this changeset is based on out-of-date information.

Hello R66_Mapper,

On this changeset it looks like you've used Google Maps when editing here. We can't actually use that as a source in OSM because the Google's licence doesn't allow it to be used - it would cause real problems for the project if we were found to be using Google Maps as a source.
If this is somewhere that you are familiar with, then "source=local_knowledge" would be perfectly OK.

Best Regards
Andy Townsend, on behalf of OSM's Data Working Group

Hello SHARCRASH,
I'm not going to have a discussion about "how to map farmland". As I said above, neither approach is wrong.
The question is really about "please leave room for other mappers in Luxembourg". You say "I'm not forbidding anyone to map" but that literally has been the effect of your actions. Please do not always assume that your approach is correct and other people's approaches are wrong.
If it came down to it and we had to choose between keeping you as a contributor in Luxembourg but losing everyone else, or keeping everyone else and losing you, we'd choose the second option instantly. However, we don't want to make that choice. Please be respectful of what other people have already edited.
Best Regards,
Andy (from the DWG)