+1 for guerda. Though, don't expect a response from iWowik, he ignores such requests due to (as he's stated in a previous discussion) feeling justified in using enormous (in both bbox area & element-count) changesets.

Sigh. 3 changes, yet still an enormous bbox.

Thankyou! 🙂

Much smaller changeset areas, please: osm.wiki/Changeset#Geographical_size_of_changesets

Thankyou! 🙂

Having been reading documentation & GH issues, this whole station needs much more work.

See discussion of changeset/11863662

Re node/1783532818

It's definitely gone. Had a good look this morning. Seems that the surface may have been repaved, since, and bins now occupy the same location. No wonder I had trouble seeing the outline.

Repositioned the node, updated the tags. Just another 35 to go.

Also, what makes for osm.wiki/Good_changeset_comments

Much smaller changeset areas, please: osm.wiki/Changeset#Geographical_size_of_changesets

Simply commenting on changeset/115984698 would've been sufficient, rather than another change.

See changeset/115991882

source=* = ?

Definitely not Google (try http://mymemory.translated.net/ which returns multiple matches (transliteration isn't deterministic) & features a no-BS API (don't even need an API key), with the possibility of supplying QA feedback and suggesting improved phrasing), nor machine-translation.

I meant in comparison to how we have
* name:en=*
* name:de=*
for the name of an element in different languages (human-input, rather than from an algorithm).

Similar concept for changesets, to input the same comment in different languages (i.e. both a contributor's native language and any other languages he knows for the benefit of a wider audience).

A link to some (non-proprietary) auto-translate web-service wouldn't be objectionable, though. However, that should really be a browser-feature (lest every website have to implement it). I recall there being add-ons for Firefox to do exactly this.

I was jesting about a pseudo-bug-report (actually a feature-request: “Request For Enhancement”) that there needs to be a mechanism for changeset comments in different languages.

Perhaps
* comment:en=*
* comment:de=*
and so on.

🙂.

Howdy.

Looks mostly good for a first edit.

Some pointers, though:
* should include a source=* with your changeset (where did the data come from? There are standardised values)
* the name=* key isn't for labels, but only the proper name of a feature (in this case, buildings). You already input the addr:* tags, so name=* is clearly duplicated. osm.wiki/Tagging_for_the_renderer is to be avoided (like with name=*, here).
* if buildings aren't actually rectangular, then OK, but if they are there is a squaring tool in most editors (try the Q keyboard key)
* for way/1019462929 the layer=-1 was surprising; the building is underground?
* looks like you made way/1019462927 share a node with Byron Lane. The way marking the road is for the centre-line. Thus, the building shouldn't share any nodes with it, but be offset to the side. Keep in mind that imagery isn't perfectly aligned (we don't have enough GNSS traces, yet); notice that different imagery sources disagree with each other re alignment. Read the wiki for more.
* sharing nodes between buildings is good, if they're actually touching; avoids redundant nodes, keeps the database tidier, and keeps things clearer for future contributors (to avoid leaving empty gaps on the map by moving one element without its associated elements also moving)
* tagging an entire building (e.g. as shop=*) is fine so long as that PoI concerns the entire building. If not, then a separate outline (way) marking which area is relevant, or if unknown just place a node near the main entrance.

I think those were the main points.

Thanks for your contribution.

+1 for _RM-mapper

Since when did Spain extend that far north?

RFE: multi-lingual comments?

🙂👍