OpenStreetMap logo OpenStreetMap

Changeset When Comment
88846178 over 5 years ago

Hello,
Please add "access=private" on those objects.
Otherwise, people who do a search for a nearby swimming pool will be misled into amenities that are not open to the general public.
Thanks.

88736835 over 5 years ago

Fine, thanks.

88770818 over 5 years ago

Hello,
Adding gardens is nice and useful.
Just one piece of advice: do not forget to add "access=private" and "garden:type=residential".
Otherwise, plenty of apps will treat them just like public gardens and will mislead people looking for a green area to have some rest. :-(

88736835 over 5 years ago

Hello,
This changeset is causing problems. People looking for a swimming pool will now see many private pools in people’s gardens.
Please use "access=private" on private pools you create.
Can you please update your changeset?

88690403 over 5 years ago

Hello,

Just one improvement here: adding crossing=unmarked for a node where a footway intersects a road with no marks on the ground.
node/7766394532/history

88798287 over 5 years ago

Hello,

Thanks for this. I had some clean-up to do after your changes. Just a few things:
* associatedStreet relations only contain objects with addr:* tags. For instance: numbers 72 and 72A are nodes inside a building, the nodes go into the relation, the building doesn’t.
* It’s better to sort housenumbers within associatedStreet relation—but I’m afraid it’s not possible with the simple online editor.
* If you fix addresses, make sure they match the official street name, e.g. "Rue De Wand - De Wandstraat"; it uses both official languages.

Otherwise, I like the improvements you are doing on the map, it’s nice work! :-)

88701748 over 5 years ago

Good idea.
I think I may have removed the wikidata/wikipedia links from some of those murals in the past—precisely because they were not specific to the POI—I’ll try to find them and add them to the relation.

81142199 over 5 years ago

Hello,
No need to fill name:fr and name:nl tags here. We only use language tags when they have a different value from the main tag. Not here.

86621293 over 5 years ago

Hello,
Indeed, my fixes were for the building outlines, because the balconies are there if we map an area with building:part, for instance, but not for the main building structure—expected to match official UrbIS numerical imagery.
Your indoor mapping was preserved. This is nice work—and something usually particularly difficult—congrats.
Just one thing, check out this page: building:levels=* because I’m not sure it should count as 11 levels (rather 10, because floor –1 does not count unless it is not really an underground floor).

88389737 over 5 years ago

OK, thanks.

88292596 over 5 years ago

Hello,
Are you sure of the location of this device.
A bicycle repair station in front of an iconic building on Grand-Place/Grote Markt, really?

88491870 over 5 years ago

Hello,
I think the result will be achieved in a better way by using the "operator" tag. I suggest naming it "FOD Financiën - SPF Finances - FOD Finanzen", so that you collect everything with one single query for the whole of Belgium.
Otherwise, two problems might occur:
1) Querying all buildings having government=tax will give you unwanted results, such as regional or local tax offices.
2) Other mappers might want to remove government=tax altogether because, as I said, this tag is aimed for places where people are expected to show up and pay their taxes in person (a tax-collection office, commonly found in Commonwealth countries and in the US). AFAIK, Belgium SPF buildings are not open to the public and only contain civil servants doing administrative work related to taxes, right?

88491870 over 5 years ago

Hello,
Good edit. Yes, there were incorrect tags here, thanks for spotting this.
(Incidently, I reverted government=tax; a "tax office" is essentially a UK standard, on the continent we use government=ministry for such buildings.)

86429741 over 5 years ago

Bonjour,
Il y avait quelques petites erreurs, j’ai essayé de corriger.
Pour la longueur des véhicules, la bonne valeur à utiliser c’est "maxlength=10".
La signalisation pour les camions est étrange : un camion ne va découvrir la limite de 10 m que quand il arrive au milieu de la rue Vandenbroek, c’est ça ? Ce n’est pas posté à l’entrée de la rue ?

86428701 over 5 years ago

Hello,
Do you know whether cycling is now allowed in both directions?
During my last survey there were no M2 signs ("excepté/uitgezonderd" + bicycle logo). But that was before the street was changed.

88389737 over 5 years ago

Hello,
It seems that "according to the picture" means you are mapping from aerial imagery, aren’t you?
This is a good idea. We have excellent imagery for the Brussels Region.
Sadly, the editor always opens with default AGIV imagery (low-res and sometimes distorted, causing users to move objects that they shouldn’t move).
When you are editing the map, go to the menu bar on the right : "Backgrounds", and select "UrbIS-Ortho 2019".
Happy mapping.

58191975 over 5 years ago

Hello,
Not sure emergency=yes is correct for Rue d’Argent/Zilverstraat (way/369853232). I believe fire trucks or emergency vehicles will be unable to pass through.

88206842 over 5 years ago

service:bicycle:retail=no, indeed! My mistake.
Thanks.

70133475 over 5 years ago

Hello,
I think there is a small mistake here: I found maxspeed=50 tags on the edges of ways 8083239 and 17173274 (bridge of the A12 above Romeinsesteenweg).
Do you know where the new speed limit starts?

72013664 over 5 years ago

Thanks for this, it was missing on the map.
Next time, please write a more accurate description for your changeset ("update" is not enough to understand what you have wanted to do). Possibly also using both FR and NL names for official buildings.
Don’t worry, I fixed this one.