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. This is because of past experience with imports.

Have you done this? I couldn't find a posting on the imports@ mailing list. If you haven't, you'll need to stop the import until you consult with the community, including imports@.

Paul Norman
For the Data Working Group

Hi,

When you use a comment like "Test" it makes it hard for others to understand what you were doing. For example, I can't figure out what way/376870750 is supposed to be

It looks like this removed information and din't replace it. Should it be undone?

Sorry, I had missed this reply.

Google's terms for their public services prevent you from using them to build your own map. For example, you can only geocode with them if you're going to be displaying the result on a Google map.

It doesn't look like this import was properly proposed, so should probably be reverted.

There's some odd gas stations in this, like way/61247009

Is this the actual signed name of the trail, or a description of it? In OSM we use the name tag only for names

You've tagged a house as Jackson's House. Is this an actual name of the house, or were you just indicating that someone named Jackson lives there?

Hi,

In OpenStreetMap we don't record private information like this that others won't be able to verify. There are tools like http://umap.openstreetmap.fr/en/ which allow you to overlay points on top of OpenStreetMap, if that's what you want to do.

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.