Bonjour, bonne idée que d'indiquer les amphithéâtres. Le wiki suggère (faute d'un schéma approuvé) d'utiliser les combinaisons amenity=theatre et theatre:type=amphi (615 usages à ce jour). Avez-vous suffisamment de connaissance des lieux pour ajouter plus d'amphi et compléter l'amphi Lacoste ? De même vue les bâtiments je suggère de préciser les étages (level=0 pour RdC par exemple ou level=0-1 pour un amphi prenant deux étages). Par avance merci et n'hésitez pas en cas de question.

Bonjour,

Il y a une voie qui contient juste name="à pied" dans ce changeset. L'intention est-elle d'indiquer un itinéraire piéton pour circuler dans l'école militaire ? Si oui, il serait mieux de retirer name et de mettre highway=footway ainsi que de marquer comme tel les portions passant sous bati (tunnel=building_passage) ou en intérieur (indoor=yes). Voulez-vous vous en occuper ?

Bonjour, je trouve plusieurs passages piétons dans vos modifications qui ne sont pas connectés aux rues qu'ils croisent. Quand deux routes se croisent il convient de leur faire partager un noeud au niveau de cette intersection. Dans le cas d'un passage piéton il s'agit d'un noeud avec highway=crossing. J'en ai corrigé deux mais pouvez-vous svp corriger les autres ?

Super merci !

Bonjour Simon, tu as retiré le tag highway=unclassified de la way/232204758, du coup ce n'est plus une route empruntable pour les voitures alors qu'elle l'est. Erreur à réparer ?

Hi Mateusz, considering the existing installations and the official website (https://www.andoyaspace.no/sounding-rockets-balloons/), I consider this no more a project. I don't know in which language you read Wikipedia, but it might not be up-to-date?

Reguarding your proposal I think it makes sense and take it into account.

Hi,

node/5475841622 looks like an advertising, which is not allowed in OSM. Can you please explain why you created it?

Moreover languages are not respected in both features: 'name:pt' shall contains Portuguese, not another language. And 'name' should preferably be the common default name, i.e. usually in local language.

I opened a request to render aeroway=landingpad: https://github.com/gravitystorm/openstreetmap-carto/issues/3112

Ok, then you are ignoring two things.

First we shall not map for the renderer. OSM is there to build a database, not to display maps (even if I would like it to change). The map displayed in the website is a thirdparty among many others which can easily be modified in order to render launchpads, landingpads, runways and helipads the same way (just open a ticket, i'm sure it will be approved). Then the feature will no longer be invisible. Also, there are plenty of tools which render or use OSM data, and assuming that the map in OSM website is the only one is ignoring all the ecosystem around OSM (some may already differentiate landingpads from runways). In fact this is how I discovered your changesets: landingpads have disappeared from my tool.

Then aeroway=landingpad is a new feature which has been discussed between the community and validated recently. Ignoring this work is ignoring the fact we are a community working together and that a vote has been made. See aeroway=landingpad

For those two reasons, I have to set back again the landingpads tags. Please follow the tags and the documentation (wiki) and not the renderer (again, rendering is only a way of displaying data). If you disagree with the tag added by a user, then contact him to understand/discuss before erasing his work.

Reguarding the aeroway word... I agree with you, I also don't understand where it came from (I work in the aerospace business and never heard about it), but it has been used since a long time, too old to be changed. So as soon as it is documented, I don't care if it is one word or the other: the point is to all use the same language even if we create a new word.

One last comment reguarding your runway definition: Be carefull, an airplane is an aircraft but an aircraft can be more than an airplane: it can also be an helicopter, a ballon, even a rocket depending of the definition you use. So we have to pick the right landing type feature for each type of aircraft. To be transparent with you, I changed a little bit the runway wiki page to reflect this fact and the new landingpad tag.

Yours

Hi tychoanomaly and welcome onboard OSM!

You changed the landing zone 1 and 2 from landingpad to runway. What is the rationale? Those features are not runways and the aeroway=landingpad tag had been approved for this kind of feature (see aeroway=spaceport).

I strongly think that it should be set back to landingpad. Thank you for your feedback on this one.

Ok, thank you! I've seen you put layer=3 but I replaced to level=3 which is more suitable to indicate floor levels (whereas layer is only for rendering purposes)

Hi km2bp, I was recently in St Peter's basilica (Vatican) and where not able to localize the amenities you've mapped there (drinking point, post box...). Do you remind at which level they were ? Assuming level=0 is the basilica, -1 the pope's tombs and -2 the necropole

Bonjour, la rue des Barres et la rue du Grenier sur l'Eau sont pavées et non pas goudronnées. Est-ce donc volontairement qu'elles aient été marquées comme goudronnées ? J'ai fait la correction mais j'ignore du coup si les autres rues sont bien taggées. Cordialement.

Bonjour, je vois que les passages piétons et chemins piétons ont été indiqués comme rue piétonnes (highway=pedestrian). Je trouve personnellement highway=footway plus approprié, le wiki tendant à confirmer cela. Je ne parle pas des terres pleins mais des chemins reliant/traversant les terres pleins (ex : way/383788599). De plus une rue piétonne traversant une rue piétonne n'a que peux de sens. Qu'en pensez-vous ?

Modified to access=private in changeset/47007664

Hi, you used access=permissive but according to the wiki access=private would better fit as soon as the airport is not open to general traffic. What do you think?

Ok merci, cf. changeset/46031362

Bonjour, je comprend que l'emprunte soit bien des immeubles (d'où le correctif), mais les immeubles sont-ils complétement des boutiques ? Tous les étages ? Il me parait plus juste de conserver les bâtiments actuels (mais remplacer building=retail par building=yes) et mettre chaque boutique sur un node à part (ou à la rigueur faire du indoor mapping). EN profiter pour remplacer les shop=yes par ce qui va bien. Qu'en pensez-vous ?

Done, all previously tagged shops have been redefined as shop. See changeset/45980978

Yes I agree with your second sentence to better answer your first point: "30 mph" is different from "30mph" exactly because parsing (and regular expressions) can't save everyone, everywhere and everytime. This is why this is relevant at the end. Having a consistent data set helps improving quality and good habits while reducing opportunities for future errors.
Saying that I'm not happy if I make work harder for others... Data are evolving everyday so I hope you have already considered that other maxspeeds are adopting/leaving/changing the "space notation" daily without my help even if I've drastically (and suddenly... thus aggressively) fixed the landscape for this speed limit.
(PS: I don't forget your request on real estates)