There's nothing wrong with improving alignment, but before continuing this large-scale edit, can you communicate with the Japanese community on the talk-ja@ list about what you'd like to do, and seek their feedback?

Paul Norman
For the Data Working Group

Hello, you've used Google as a source. Copyright and Google's terms don't let us take their data or use their products to build a map, including Google Street View. (osm.org/copyright) Did you use Google as a source for any other changes?

I need to redact this change, which will prevent the Google-derived data from being viewed.

Paul Norman

For the Data Working Group

Is this a supermarket?

If it's used by cyclists but doesn't have a lane or other on-road markings, it shouldn't have a cycleway tag. Also, cycleway=yes isn't a normal value for the tag.

ruthmaben, could you please have a look at it and respond in the changeset discussion?

Hi,

I wanted to remind you of the importance of writing good changeset comments (osm.wiki/Good_changeset_comments) to help others understand what you have done and why

Google Street View is covered by the Google Maps terms, and for this as well as other reasons they can't be used. I've gone ahead and "redacted" the data, which stops it from being viewable.

Did you get a chance to document the permission?

Hi,

the "description" field is for a description of the feature, and isn't for advertising or PR text. I also fixed the facebook/g+ tags to be the standard ones

I removed the # from the addr:unit tag, we don't add that in OSM.

It's best to use the changeset comment to describe the changes you made, it's not for marketing information.

I've fixed node/3739908016 to remove the custom tags and what looked like marketing text. In OSM we record information like addresses, business names, and other objective information, but not keywords.

I wanted to move the point to the right part of the building. Do you know where shop is in this building?

It looks like this changeset introduced a bunch of duplicate ways in Larrabee state park. I've had a go at fixing the, but could use another look.

Reverted in changeset/33563681

Hello,

This appears to be an undiscussed import. Imports in OSM need to follow wiki.osm.org/Import/Guidelines, which include consulting with imports@ and the local community.

There appear to be tagging problems with the data, as none of the nodes have normal OSM tags, and the changeset does not have a created_by tag.

Hello,

Ukraine has the country relation relation/60199. OpenStreetMap is not a private data store, and this relation has been causing problems.

Please don't recreate it.

Paul Norman
For the Data Working Group

Could you document the import on the wiki and post the permission there? Also, you need to bring up the import on the lists, even though this is after the fact.

Paul Norman
For the Data Working Group

Imports in OSM need to follow the imprt guidelines at wiki.osm.org/Import/Guidelines, which include discussing the proposed import on talk-ca@ and imports@, which you don't seem to have done here.

Did you get special permission from the City of Ottawa? The data license on their site aren't open or compatible with OSM.

wiki.osm.org/Import/Guidelines requires that you document your import. You also need to have discussed it on the imports@ list

You've indicated Google is the source for this as well as another changeset. Unfortunately, Copyright and Google's terms don't let us take their data or use their products. Did you use Google as a source for any other changes?

Paul Norman
For the Data Working Group

You've indicated Google is the source for this as well as another changeset. Unfortunately, Copyright and Google's terms don't let us take their data or use their products. Did you use Google as a source for any other changes?

Paul Norman
For the Data Working Group

You've indicated Google is the source for this as well as another changeset. Unfortunately, Copyright and Google's terms don't let us take their data or use their products.

Paul Norman
For the Data Working Group