bxl-forever's Comments
| Changeset | When | Comment |
|---|---|---|
| 165023989 | 8 months ago | Thanks for adding new places. We fixed your edits, in particular: addresses should not be repeated multiple times in the databases, city names and post codes are not repeated on individual objects in Belgium, and much more. |
| 164997190 | 8 months ago | Nice… but if there is already a vacant shop, it is advised to re-use the existing node instead of creating a new node next to it.
We fixed your edit. |
| 164982022 | 8 months ago | Hello. You created a pedestrian area inside… an existing pedestrian area. I understand that non-local mappers may be confused in our car-free area but despite it looks like there are roads, those are only used by delivery vehicles and residents. Also, the surface of the area in the centre of the square looks like setts, not flat paving stones.
I will fix your edit. |
| 164982928 | 8 months ago | Please do not repeat addresses on shops/restaurants/etc., we don’t do this anymore. We fixed your edit. |
| 164923427 | 8 months ago | Also on this changeset
I see the problem now.
My request to you (and your other team members) is the following.
Apart from that, thanks for the good work you are doing. |
| 164923427 | 8 months ago | Hello, Pardon my asking but it looks like something weird happened with this changeset: Version 1 included a valid phone number. You replaced it with "+32 00000000" which is obviously a non-number. It looks like an automated change made by your software. Either Foodmaker does not have a phone number anymore—and in that case the key should be removed entirely—or there is something wrong with the software you use to import data into OSM. This comment also applies to those two other changesets of yours
Can you please have a look. |
| 164914066 | 8 months ago | Gateau was already on the map here
Organic Maps does not show all the existing/current data, please always check against live data first. |
| 164887676 | 8 months ago | Hello, Thanks for adding a cafe.
1) There is already a building with an address here: way/705257473 Adding a cafe as a floating node inside it is correct… but please do not add the address on the cafe itself, because now we have two places (the building and the cafe) that are defined for the same address. It is not necessary (and not wanted) to repeat addresses on places. 2) Phone numbers always in the international format (+32 10… instead of 010…) We will fix it. Hope this helps. |
| 164844471 | 8 months ago | We had to fix a lot of stuff here. Please make sure not to create duplicate address points, do not duplicate the same information on buildings and nodes, and if a car dealer sells multiple brands, there is only *one* node on OSM and not one per brand. Use the "brand" tag correctly to store the list of brands (not in the public name). You will find a corrected version here:
|
| 164846922 | 8 months ago | Hello, Nous n'avons aucune trace d'une résidence nommée Willendyck à Forest. Ça semble être une maison d'habitation.
Pourquoi donner un nom à ce bâtiment ? |
| 164831279 | 9 months ago | Hello, This changeset seems to be much more than just changing a Colruyt. I see you spend a lot of time mapping but could you use a few more seconds to start typing real changeset descriptions for your changes. Just asking: i see you are using the landuse category to map… individual plots as landuse=residential like here: way/1376863124 Wouldn’t place=plot be a more appropriate choice? place=plot |
| 164809234 | 9 months ago | Hello, This is not useful and not wanted. Post codes and town names should *not* be repeated on every object in OSM. This information is automatically calculated from existing zones. For instance, every object within this zone is automatically recognised as having post code 1620
|
| 164771768 | 9 months ago | Hello, and welcome to OSM. Nice work but please make sure to *not* type free text in phone numbers or opening hours. The database expects that a phone number is just a phone number (international format), e.g. "phone=+32 2 477 41 41"
|
| 164724995 | 9 months ago | No promotional content in changeset descriptions on OSM, please. The description is only there to indicate what was added/changed, not to advertise your business. We also fixed your edit because you incorrectly changed the building instead of adding a node inside it and failed to select a proper category, therefore it would be useless for anyone looking for an estate agent. The place will be now correctly referred as an estate agent office.
|
| 164726722 | 9 months ago | Hello, I must inform you that we reverted this edit. You already uploaded this "attraction" earlier today and I left a message explaining that it was already on the map. Please be kind and do not repeatedly upload the same items, especially when they are already correctly tagged. See discussion here: changeset/164704591 |
| 164704591 | 9 months ago | Hello, Experience Europe was already on the map, here: node/12541780057 It had been added earlier this year, so perhaps you missed it in case you are using an old local copy of data (Organic Maps does not show you live OSM data). You may want to refresh data prior to mapping a territory. Don’t worry, we fixed your edit and re-used some relevant data you added (e.g. the opening hours) to merge them into the existing node. |
| 163710736 | 9 months ago | Hello and sorry for the delay about this. I finally found some time to inspect the situation here.
|
| 164626571 | 9 months ago | Hello, and welcome to OSM. Some tips for your next contributions: 1) Please write meaningful title when you upload data, e.g. "I added a pharmacy" instead of a vague statement that something was missing 2) Do not change building types. The building is not a giant pharmacy, it is a normal residential building with Multipharma on the ground floor. We redid your edit and mapped the pharmacy as a single node instead of merging it with the building itself. Happy mapping. |
| 164394384 | 9 months ago | Hello, I checked and it looks fine now, thanks for your latest changes. I just fixed some permissions to make sure they produce the same access conditions as before even if they are tagged as paths. |
| 164566640 | 9 months ago | Can you please check the coherence of route relations, they seem to have been broken e.g. L26 here relation/57641 is currently discontinuous and contains parts of the alleged L26B/1, which should probably have its own relation. Feel free to request help if you cannot do it yourself. |