OSMBrasil / validador-josm

Brazilian-specific validator rules for JOSM
10 stars 3 forks source link

Name of the rivers as boundaries #120

Open angoca opened 1 year ago

angoca commented 1 year ago

I see the Brazilian validator checks the river's name to see if it starts with "Rio" as in Portuguese. However, we have a similar validator in Colombia to check if the name starts with "Río" (with the accent), which is the correct spelling in Spanish.

/* https://overpass-turbo.eu/s/sZz */
way[waterway =~ /^(river|stream)$/][name][name !~ /^(?U)(Água|Arroio|Cabeceira|Córrego|Furo|Grota|Igarapé|Lajeado|Paraná|Restinga|Riacho|Ribeirão|Rio|Sanga)\b/][inside("BR")],
way[waterway =~ /^(river|stream)$/][alt_name][alt_name !~ /^(?U)(Água|Arroio|Cabeceira|Córrego|Furo|Grota|Igarapé|Lajeado|Paraná|Restinga|Riacho|Ribeirão|Rio|Sanga)\b/][inside("BR")] {
    throwWarning: tr("{0} com possível nome errado/incompleto", tag(waterway));
    group: tr("Brasil - Verificar");
}

I suppose you have this issue in all countries with rivers as boundaries.

We (LatAm) should define a name rule for rivers and adjust our validators to comply with this, preventing the changes of our rivers multiple times. I start proposing something like: Rio Apaporis - Río Apaporis (Portuguese before Spanish, because alphabetically it is P before S), with space-dash-space. What do you think?

Examples of this issue:

angoca commented 1 year ago

Another idea could be 'Río Apaporis - Rio Apaporis' because the rivers begins in Colombia, and then it goes to Brasil.

angoca commented 1 year ago

I see a similar issue in the name tag, in Switzerland: https://www.openstreetmap.org/relation/51701 It has the name in its 4 local languages (but I don't know why this order): Schweiz/Suisse/Svizzera/Svizra