precisely: you can't have read the name from Maxar. while Kaart performed a survey. the name of the road still comes from that survey. maybe replace `source` with `source:name`?

Hola. Gracias Milton por quitar la cláusula SA de vuestra licencia. Sin embargo podrían considerar una excepción explícita? Así como lo mencioné en el foro.

Aha, I see... But what is the added value of removing the reference to the Kaart survey?

hola, disculpa si te comento a un mes de distancia, vi que editabas con "StreetComplete" y no me fijé en el contenido del conjunto de cambios. Le pusiste dirección al edificio de la estación? "addr:housenumber" sería el número cívico (identificativo de una puerta) y tiene sentido en combinación con los otros elementos "namespace" addr (el prefijo). quizás era otra cosa que querías hacer?

changeset:113820114

It's a bit more difficult than that, because you reused existing nodes, moving them, and you created objects that need to be split before we can add them to relations. I'll restore the previous administrative border, saving your fixes. please do contact the community for help when you don't know how to proceed, as in this case.

I see what happened: you corrected the mouthing of the stream, but did not notice that the stream was being used as a border for the two relations. without knowing whether the river should be used as border or the border should run where the river had been incorrectly placed, I would not know which would be the correct fix. the easiest one would be to retrieve the nodes you deleted, forming the segment of the river you removed, and put it back as border but not as river. easiest, if you used JOSM.

… you added a segment to the Quebrada Chiriquicito (why did you need that?) and you did not add it to the two now broken relations.
… the segment 12451026, "outer" for Rambalá, should end at the mouthing of Quebrada Chiriquicito.
… the segment 255435819, "outer" for Chiriquí Grande, should end at that same point.
(is this enough explanation? do you want someone to fix it for you? would you prefer experimenting a bit further? I suggest make use of chat groups if you want assistance while editing.)

it is very possible that the source of your mistake was joining segments. an object that we were using as "outer" for the relation now ends somewhere else.

oops: I added all the trees in the Viento Solar collection, and not only didn't I ever complete the genus/species work, I also forgot to add the 'natural=tree' tag!

ah, la Panamericana! también me ha pasado que al editar intersecciones me han salido cambios hasta Alaska. :-)

oops, qué conjuntos de cambios más gigantesco! que pasó? abarca de Patagonia a Guatemala.

I'm adding two tags to mark it as a sea wreck. I'm removing the descriptive name. if you can have a look at the wiki page and complete the tagging?
changeset:113810456

I'm glad if you can use my comment. "in general", I can't recall noticing your team in my current land of residence. if you do go map Panama, please make use of the forum to alert the tiny local community, of your intentions, and do also inquire about the needs that people feel regarding the OSM database.
https://forum.openstreetmap.org/viewforum.php?id=61

I had a look at the 301863751 road and yes it does look bad. :-D
in Panama we recently had contributions by the #adt, adding a huge amount of nodes to specify coastlines that aren't correctly defined (so their work is incredibly precise, but not correct).
I don't know if your focus is on maximising metric precision, or on improving connectivity. I assumed the latter. I'm sorry it sounded like "complaining", it was an attempt to alert you about the issue.
(it was this post: https://shtosm-ru.translate.goog/all/milliard/?_x_tr_sch=http&_x_tr_sl=auto&_x_tr_tl=EN&_x_tr_hl=es-419&_x_tr_pto=nui)

oh, as usual I assume things are obvious. these two roads are respectively 542m and 632m long, using respectively 58 and 82 nodes. that's more than one node every 10m. if your organization is concerned with connecting places, not only you don't need this, but you are also putting a strain on the OSM database (incidentally, the last OSM-weekly has links regarding the finite numberspace in our database).
if you use JOSM-simplify way, set at 0.3m, they become respectively 40 and 59 nodes.
for your needs you probably want to set the property to 0.5, or more.
it's the `simplify-way.max-error` setting in JOSM.

an informal place for finding help is the Telegram group https://t.me/OpenStreetMapOrg
or you can try the forum site https://forum.openstreetmap.org/

not first hand, but I've heard good things about Organic Maps. just make sure it works on the live data, not from a snapshot, or you're back with maps.me sync problem.

"not straight away", he said!
osm.wiki/Apple_iOS
osm.wiki/Go_Map!!
(I have no experience with them obviously)

thanks for the feedback you know! it's uncommon of maps.me mappers. :-)