Hello, and welcome to OSM.

Your edit has been redone.

Here are the reasons.

What you actually did here was… simply adding a name to a building. The map would therefore just just show "a house named KR Easy projects". This is not what you want because the business who pays you would never be shown anywhere.

What you should do instead.
1) Do not modify the properties of the building itself.
2) Create a floating point inside the building.
3) Add a name to this point and, very importantly, a category. For instance, your changeset title mentioned craft=builder. This tag should be added to the point.

Here is the final result.
node/14103382786

If the business owner has a website or a phone number, I think it would be useful to add those.

Hello,

Thanks for adding an arts centre here.

Please observe that the address for nbr 1 on Rue Lambert Crickx - Lambert Crickxstraat *already* exists on the map.

I would be grateful to you that you do not add a duplicate address when you add new items to the map. This damages the quality of our database.

I wrote to you earlier today but it looks like you ignored the recommendation and have created multiple duplicates all through the afternoon. This is another friendly attempt to reach you.

Thanks in advance.

Hello, ZukoDz, and welcome to OSM.

Thanks for adding new places to the map.

However, it looks like you are always typing an *address* on them. This is not a recommended practice nowadays. In Belgium, addresses are preferably mapped separately. Make sure that you only include the business type, name and some details (website, phone number) but please do address. Those are calculated automatically. I am currently taking care of removing the duplicate values from your previous edits; please bear this in mind for your future edits.

Hello,

Does this relation really only exist in one direction? No line from De Panne to Gent at all?

Relations should always start from a stop position node, it looks like it was incorrectly split in Gent. Would you mind having a second look?

Also, network=NMBS/SNCB is a bad value; it is still found in the database because many newbies have blindly clicked on absurd suggestions by the name suggestion index and there aren’t enough people to clean up afterwards. Make sure not to import those errors for new data. AFAIK, network=P for those relations.

Thanks.

Bonjour,

J'ai examiné cette rue après un signalement sur le fait que les magasins avaient été incorrectement dessinés… à la place des bâtiments.

Nous avons rectifié ce matin.

Laissez svp les bâtiments inchangés, les magasins s'ajoutent comme de simples points flottants à l'intérieur du bâtiment.

Avantage supplémentaire : si vous avez fait une erreur de localisation, il est facile de glisser le point vers la bonne maison.

Hello.

This "no comment" changeset looks like an import.

It was probably scripted because latitudes and longitudes have errors, creating this huge bounding box covering half of the world.

The similarities of latitudes and longitudes of those 79 hydrants suggest that you imported a database without realising that the decimal separator was not on the same place, depending on the number of digits.

5.116636 1.404543
51.162426 1.405849
51.189239 14.052914
51.165733 140.460175
5.117839 140.509

Hello,

Is the following value:
"wikimedia_commons=Category:LOFAR in Potsdam"
relevant on a relation that spreads over most of Europe? relation/13218198

This tag should preferably be set on the device(s) in Postdam, not on the whole relation.

Hello,

Would you mind giving this edit a second look?

The tags suggest it is a about a shop in France, whereas the information was added to a small intersection in Ohio, USA. And the POI is missing a main feature tag (presumably shop=* ).

@felixcrux: It looks like you had mapped a church in Toronto with StreetComplete and did not upload your data before you travelled to Sweden and mapped a church there.

As a consequence, we now see an upload containing edits over two continents, bundled as a single upload.

To avoid this in the future: make sure to properly upload all the pending data *before* you travel, and everything will be all right. Alternatively, the StreetComplete app has a setting to upload your answers immediately.

I removed those names + same mistake in other changesets, while keeping the objects themselves.

@Marbled%20Stargazer Here is a pointer to the OSM documentation explaining why we do not name small items like those.
osm.wiki/Names#Names_are_not_for_descriptions

Happy mapping.

Bonjour,

Il y a sûrement une bonne intention derrière ce changement, mais ceci est pour signaler que ça a de nouveau cassé la structure des relations bus ici. Le but n'est pas uniquement que ça soit joli sur la couche transport ; une ligne de bus, ce sont des arrêts et des rues placées dans un ordre bien précis.

La ligne termine à "Valenciennes – Gare", d'accord ?

Alors pourquoi avoir placé les arrêts Maubeuge Pôle Gare Quai 10 et Maubeuge Lycée Pierre Forest Quai B après les arrêts Valenciennes Gare ? Ces arrêts sont *avant* Valenciennes sur le parcours, pas après.

Et pourquoi placer la boucle qui commence ici way/23614166 à la fin de la liste ?

Il n’y aucune volonté d’être désagréable ici mais on aimerait vraiment que vous lisiez les commentaires faits sous vos changements depuis plusieurs années. Pour ne pas vous décourager, je ne laisse pas une note à chaque faute, mais je pense que toutes vos éditions concernant des relations de bus nécessitent que quelqu’un repasse derrière.

Bonjour,

Retirer les arrêts node/3836403754 des relations mais en laissant node/11537991759 avec role=stop dans les relations n'est pas une bonne correction, ça crée encore plus d'erreurs dans la DB.

In case you are not familiar with phone numbers in Belgium, here are some hints.

Businesses often write down phone numbers in the traditional style (which worked well on old wired phones, and which also works on mobile phones if people are in Belgium when making the call).

They write `02 XXX XX XX`.

On OSM, we drop the "0" because this only works from Belgium, and add "+32" for Belgium. It will become `contact:phone=+32 2 XXX XX XX` This makes sure that the phone will be clickable in apps and work from any phone.

Mobile phone numbers are usually written like this on websites and shop doors: `04XX XX XX XX`, which we will map as `contact:mobile=+32 4XX XX XX XX`

Hello,

Thanks for spotting missing places on the map. But we might have a couple of issues.

1. When you add shops, please just add the shops and do *not* make the shop be an address point on its own. I know that CoMaps does strange things but you should really make sure not to mess with the addressing system, duplicating them is really annoying.

2. I often spot invalid phone numbers, like here. +322653763 is obviously lacking one digit. From your previous contribution, it looks like you always omit the regional prefix, so perhaps it would be +32 2 653 37 63. Did you take notes or pictures of what you saw here, so that we can check?

Hello,

Prince Optical has been on the map for 4 years.
node/10031838476

It looks like you are mass-importing businesses to OSM without checking first.

Thanks, and welcome to OSM.

One small detail: "floor" is not a common tag, I presume you meant level=*

I am not sure that MapRoulette recommandations are advisable either.

For instance, here is a bus shelter with a JCDecaux advertising screen attached to one of the sides. Your edit merely… detached the screen and added a useless new node in the middle of one of the edges.
way/485304557
Why???

Hello,

Please use correct changeset descriptions for your changes on the OSM database.

It looks like you are re-using an auto-generated title from a MapRoulette gaming action, despite you are doing much more stuff than fixing intersecting objects.

A brief analysis of your latest changes suggest that you are automatically pushing all the automatic suggestions from the name-suggestion-index, but I need to alert you that plenty of those suggestions are either useless or plainly incorrect. Mappers are expected to be very careful about those suggestions.

Smaller changesets would be appreciated instead of those large collections of unrelated changes.

Thanks.

Hello,

Thanks for the extra information here.

Just one thing: Only use the name field when objects have a real name. It looks like "gas pumping station" is a description and not really a name.

way/1547408389 has been redone, with the following tags:
* man_made=pumping_station
* substance=gas

Hello, and welcome to OSM.

Your previous edit changeset/186929551 was fine, you had added two benches that were missing.

But here… you are adding a third bench in the middle. That makes no sense. I checked against pictures we have of this area and that third bench does not exist.

You may be interested to know that "Organic Maps" does not show live OSM data, it takes a snapshot of past data. The information you added earlier today will not be visible in Organic Maps until the next data update, probably in a few weeks time.
This is one of the reasons why we recommend that people avoid editing the map with that app.

I fixed your edit and removed the extra bench here.