This changeset is faulty.

This bus stop is run by De Lijn and you changed some tags inherited from TEC, which is another company operating here, creating a mess, for instance assigning zone numbers from one operator to the other, or creating a mismatch between network and network:wikidata.

Belgium is a complicated country, that is why local mappers spend a lot of time carefully maintaining proper tags, especially like hear near internal borders where many stops are shared by two or more operators. We are quite saddened to see people without any local knowledge adding wrong data.

Bonjour. Est-ce que vous pouvez regarder ce qui se passe avec les lignes de bus de Flixbus ici ?

Il y a 12 relations bus qui sont brisées actuellement. Elles utilisaient cette voie-ci que vous avez supprimée.
way/626660000/history

Ce que je comprends est que ces bus sont sur l'avenue de la Libération et doivent aller desservir cet arrêt : node/1289085603

Je n'ai pas de connaissance locale de votre ville. Si vous connaissez l'itinéraire, pouvez-vous reconstruire les relations bus svp, ou nous pouvons le faire pour vous si vous nous dites où passent les bus maintenant.

Thanks.
Merci.

Hi!

Most stops here are operated by both TEC and De Lijn. This is one of the cases where naming bus stops properly is difficult when each operator has a different name for it.
To make it even more challenging, this part is Wallonia but it is one on the Belgian municipalities with facilities, making it a de facto bilingual area (fr - nl).

The French name is obtained by TEC, even though we scraped the Dutch translation in the town name, while the Dutch name is obtained by De Lijn.

Apps can alternatively rely on "name:TEC" and "name:De_Lijn", which use the exact same spelling used by each operator. Those tags were properly added here: node/2675919337

Bonjour,

Pas une bonne idée de suivre un peu aveuglément les recommandations d’Osmose, c'est un outil avec énormément de faux positifs, surtout hors de France.

Par exemple : vous avez renommé plusieurs arrêts de bus du TEC (Belgique) pour avoir la belle graphie « n° » dans les noms. Même si nous déplorons que l’exploitant fait parfois des fautes de syntaxe dans les noms officiels… ce sont les noms officiels qui correspondent aux fichiers des horaires et à l’information aux arrêts et ça ne doit pas être changé.
node/3075692283/history

Autre exemple : node/10583998138/history
L’arrêt de bus s’appelle "Panaderia Rayo". Osmose vous a convaincu de transformer cet arrêt de bus en boulangerie à cause de son nom. C'est clairement une erreur.

Beste,

Wat is de rol van deze relatie "uitbreiding Madonna"?

Als een aparte relatie in OSM is het fout. Ik kan die koppelen aan een bestaande relatie van lijn 30. Weet u hoe dit stuk uitgebaat wordt? Rijzen vanuit Diksmuide naar Madonna, of vanuit Roeselare? Eindpunt Madonna of in en uit in dezelfe rit?

Groeten.

No problem, the solution was not too difficult and now it will show beautifully on the map.

Is it a true roundabout with D7 signs (osm.wiki/File:Belgian_road_sign_D05.svg)?
If yes, we can put junction=roundabout instead of oneway=yes.

This comment is a duplicate of changeset/130543728

Don't worry, the name has not been deleted from the database, it belongs to the relation here: relation/57639 The relation is okay.

Ordinary railway tracks do not have names. If you see "L161" on the list of ways on this changeset page, it is only because osm.org uses the ref to show the objects when the name tag is empty. Click on any of those ways and you will see how it is tagged.

.

We fixed it.

@Matus1978: sorry but your change was not good, we had set a timer to execute this today at midnight, to ensure smooth operation of apps.

Hi.

stop_area_group relations are mostly a deprecated scheme. Apart from very specific mobility hubs such as interchange stations between two subway lines no-one uses them anymore.

In case somebody wants to use them (properly), they must contain all the stop_area relations of multiple stops. It contained two members that proved to be duplicates for the same stop. I removed one duplicate and now we had this problem with "1-member relation" shown by Osmose.

I’ve just removed the stop_area_group here, no need to worry anymore.

Ja, bedankt voor de steun. 👍️
Het is inderdaad de bedoeling om alle buslijnen langs de Misiabrug te tekenen.
Een taak voor de komende dagen, hopelijk.

Hallo

Deze opmerking is niet verbonden aan mijn changeset (121140820) mbt. de buslijnen.

De naam komt van changeset/116977402: way/1027477066/history

1582 is the normal stop towards Bordet Station. The OpenData GTFS does not give a real image of the network, only the stops that are operated during a 14-day period, and those lists will change often.
In STIB/MIVB internal carto the stop is set as 1582TMP for the moment because the buses are diverted, that is why you won't find it in the GTFS.

Hi there: what do you mean? Are you suggesting the service stop on the boulevard is no longer there? This is the stop where buses are parked between trips. Is the terminus operated differently now?

Hi there: There was a mistake in the data import here, Bon Air/Schone Lucht and Pommier/Appelboom were mixed. I spotted the mistake too and fixed it yesterday.

Apologies to everyone about this unusually large bounding box.
It wasn’t intended: I inadvertently re-used an existing object instead of duplicating it, as I thought I did.

Ja, u hebt gelijk, die groot gebied met amenity=bus_station is fout, omdat way/757851076 reeds bestaat en is correct.

Ik heb het probleem opgelost.

Ik begrijp maar "Oostende Station" is de naam die de reizigers willen/moeten zien op de tramlijn. Die twee nodes zijn de twee perrons, één per richting.
Idealiter zou men de perrons als `ways` moeten tekenen, zoals in Berlijn of Brussel, om dit volledig op te lossen.
Hebt u suggesties, misschien?

Hi!
Most stop_area_group relations in this city were gone already, or were outdated. We couldn’t find any use that couldn’t be covered with established stop_area relations.
Do you really need that? How can we help?