The tags added indicate these edits might be based on a tool like scanaerial which would mean this might not actually be a mechanical edit.

However this should still be discussed before widespread use because (a) the quality of the geometries is poor indicating a rather crude algorithm behind it and (b) this seems to be based on poor and outdated lowzoom Bing images which differ a lot from the current reality - see for example here: https://mc.bbbike.org/mc/?lon=-152.654172&lat=70.015963&zoom=13&num=2&mt0=bing-satellite&mt1=mapnik

Bonjour abdeldjalil,

i am sorry for missing the existing mountain region polygon.

However the tagging is still quite wrong since in the area covered exposed bedrock is not the dominating surface type. Most of this area is covered by loose material - mostly either scree or alluvial deposits - like here: https://mc.bbbike.org/mc/?lon=8.069623&lat=25.976448&zoom=14&num=3&mt0=bing-satellite&mt1=mapnik&mt2=google-satellite

Exposed bedrock is mostly limited to steep parts where relief prevents accumulation of loose material.

Having such a big polygon covering a very heterogeneous area makes it difficult for mappers to correctly map details more specifically on a local level.

Merci,

Christoph

Hello Andre68,

this edit is factually incorrect and creates a several thousand square kilometer error in the coastline. Could you please restore correct tagging placing the coastline where the coastline actually is an tagging the bay with the established tag for bays (natural=bay - osm.wiki/Tag:natural%3Dbay)?

Hello tasauf1980,

i am not sure what you are trying to do here but it is not working. You have added five new revisions to osm.org/way/100827142 and the end result is both geometrically (due to self intersections) and semantically incorrect.

If a large and complex multipolygon relation is difficult to handle for you you can split the water area into smaller simple polygons - as it has been done before you created the multipolygon in osm.org/changeset/51275200

And please use meaningful changeset comments so others can understand what you are doing - see osm.wiki/Good_changeset_comments

Hello palimpadum,
not sure if you are aware that you are refining glacier mapping here based on images which are probably older than the ones these were originally mapped from three years ago and which are partly off by more than 100m.

Who is 'we' here?

Keep in mind that planning and organizing of mapping activities and development of mapping conventions should be public.

Although there is not yet a formal policy on organized mapping activities it is good practice to document such activities and reference this in changeset comments/tags. If you develop a mapping system for woodlands in Nepal for others to take cue from this needs to be documented and open for scrutiny, critique and modification by other mappers.

I would like to add that what bdiscoe did here was not in any way destroying a detailed map. He removed nodes which had a very little influence on the overall geometry because they were almost exactly in the middle between the next and the previous node. See http://nrenner.github.io/achavi/?changeset=49549696

Since the original mapping here contains a mixture of too few and too many nodes (too few in the sense that there are many sharp corners in the mapping which do not actually exist in reality, too many in the sense that the influence they have on the shape is small compared to the level of detail of mapping) this is a sensible step. If it is worth the trouble is a different question of course.

Regarding the mechanical nature of your edits please read the 'Scope' section on osm.wiki/Automated_Edits_code_of_conduct

When you add dozens of name tag in different languages in minutes intervals there is no way you can verify this information so this is a mechanical edit even if done with an interactive tool.

Regarding semantic issues - there are a lot of errors in wikipedia and wikidata - wrong names, wrong classifications of objects, interwiki links not representing identical objects etc. We do not want these errors in OSM. You are clearly not familiar with many of the regions you make edits in so you are not able to recognize many of these errors.

Regarding legal issues - while using wikidata as a source of information for manual mapping is not critical (although you should never use it as an only source) using it as a bulk data source is. Wikidata has no strict policies regarding sources of the information, many of the things there have been copied from Google Maps and other restricted sources. Such data should not be entered in bulk into OSM and which is part of the reason why imports need to go through a review process (osm.wiki/Import/Guidelines). See also https://forum.openstreetmap.org/viewtopic.php?pid=618536#p618536

So once more: please do not continue with your edits before discussing them in a broader scope (due to the international scope best would be the talk mailing list).

Hello radek-drlicka,

you continue making mechanical additions of names as well as new features without following the automated edits policy (osm.wiki/Automated_Edits_code_of_conduct) despite having been asked not to in osm.org/changeset/47907976

Please stop making those edits and document and discuss what you do before continuing. There are various both legal and semantic issues with mass addition of information from wikipedia/wikidata.

I mentioned this primarily in

https://lists.openstreetmap.org/pipermail/imports/2013-October/002300.html

and in subsequent discussion (continuing in June 2014)

I was referring to the "No point editing stuff in this area." remark which is pretty unfriendly to someone manually mapping stuff in the area.

As far as the "semantic nonsense" is concerned - i pointed out some of the problems in the import discussion - in particular regarding waterways and wetlands - and could point you to a lot of cases where the imported data is factually wrong because of that. But this is not really the point here.

The point is you should value and respect manual contributions at any time - even if they are untimely for your import - and even if you consider the data you import to be better or more valuable in some way.

So you want to ban manual mapping from Norway to make it easier to create and maintain a map based on 'official' data there? That would be an extremely short sighted attitude.

If you want to address problems with the alignment of images (which are indeed severe in some parts of Norway) a good way would be to provide a rendering of the 'official' map data mappers can then use to align images.

But just because 'official' map data has better positional accuracy does not necessarily mean it is more accurate than what is manually mapped otherwise. The Kartverket imports are full of semantic nonsense and geometry errors.

Hello radek-drlicka,

this changeset creates an untagged node and one mapping a feature that is already mapped in OSM otherwise using incorrect tagging.

Please correct this and please be more careful when editing and do not make mechanical additions based on external data without following the mechanical edits policy.

Kotelny Island is far beyond the polar tree growth limit, as you can see on https://ru.wikipedia.org/wiki/ru:Котельный average temperature in July is only 2.9 degrees.

I am sorry for not being able to reply in Russian.

Hello freeExec,

you might want to check your tagging here - natural=wood is fairly unlikely in this area.

Hello Jenny,

why do you think 4rch drew the coastline you tried to 'align' here the way he did in

osm.org/changeset/35508175

If you think that mapping was faulty it would be a good idea to actually talk the mapper who did this first, especially if - like here - this is an experienced mapper who has drawn hundreds of kilometers of coastline in the area.

Hint: if you'd actually look at the image sources JOSM offers you for the area you map in you might also find images that are a decent depiction of reality.

Hello Philip,

despite having been told not to combine several unrelated edits far apart in a single changeset by manoharuss in

osm.org/changeset/47404357

you continue to do so. Stop doing that! This kind of edits are extremely annoying for your fellow mappers.

Hello Sandro,

your edits to Остров Кверини are factually incorrect, please revert them.

If you do not have reliable data or are not able to reliably interpret the data you have you cannot edit in this area.

Also note you have unnecessarily created five new versions of this island within a few hours:

osm.org/way/240306213/history

but at the same time combine several unrelated edits far apart in this changeset and others. Stop doing that, you are causing a lot of trouble and unnecessary work for your fellow mappers.

Hello Ashley,

this edit and other edits in similar setting are factually incorrect, you are 'improving' existing mapping based on fairly accurate 2-3 year old imagery by 4rch using exceptionally poor, snow impaired 15 year old images in Bing. Please don't do that and revert your past edits in such areas.

Hello Eva,

your edits claims to be based on Bing imagery but Bing apparently has no coverage in this area. Could you explain the basis of this edit?