OpenStreetMap logo OpenStreetMap

Changeset When Comment
156230159 over 1 year ago

osm.wiki/Russian–Ukrainian_war

156279401 over 1 year ago

osm.wiki/Russian–Ukrainian_war

155364333 over 1 year ago

«Perhaps you could propose a detailed scheme somewhere on the wiki, that we could discuss, and tweak, to come to a consensus? Mind you, it should be universal, not just limited to your own territorium.» osm.wiki/Talk:Tag:aeroway%3Daerodrome#Other_tags,_generic

155364333 over 1 year ago

*https://en.wikipedia.org/wiki/Aeronautical_Fixed_Telecommunication_Network

155364333 over 1 year ago

«Perhaps you could propose a detailed scheme somewhere on the wiki, that we could discuss, and tweak, to come to a consensus? Mind you, it should be universal, not just limited to your own territorium.» This can be done. In what form do you propose to do this? osm.wiki/Proposal_process or in some other? If you are concerned about the general description of ref at wiki and you want to specify the description of this code and you are against the latinized version of this code in "ref" tag, then one of my proposals is to transfer these codes to the another tag: "aftn" or "ref:aftn" (Aeronautical Fixed Telecommunications Network https://en.wikiphedia.org/wiki/aeronautical_fixed_Telecommunication_network because this code is used primarily for this network and for the general identification) and add information about this on wiki ref=* + aeroway=aerodrome. At the moment, I'm observing the only use of "aftn" tag in Croatia near Pula, the use of "ref:aftn" I don't observe. The use of "aftn"/"ref:aftn" tag for latinized version will not be limited to the territories of the former USSR. The use of the AFTN in cyrillic version as "nat_ref" tag value also corresponds to the description on wiki, since this option is used at the national level. I remind you that I am talking exclusively about official identifiers that are appointed state structures of the USSR, the Russian Federation and other states of the former USSR. For amateur identifiers, such as from the site aopa.ru, which aren't included in the official lists and aren't indicated on official airfield schemes, I already proposed using the corresponding tags like ref:aopa:ru & ref:aopa:en (as almost a monopoly source of identifiers amateurs in the Russian Federation). However, if we come to an agreement to use the aftn/ref:aftn tag, then latinized identifiers beginning with U*** but not assigned as an ICAO code should be moved from ref:aopa:en to aftn/ref:aftn, since they are also used in AFTN. It should be noted that the AFTN code, when it contains more than 4 characters, may be used by aerodrome units/departments or aerodrome services

155364333 over 1 year ago

«Any reference that is not global or universal is, by definition, local. » Definition by whom? ref=* int_ref=* - international reference numbers or codes; nat_ref=* - national reference numbers or codes; reg_ref=* - regional reference numbers or codes; loc_ref=* - local reference numbers or codes. XWPR & similar official refs isn't a local reference.

155364333 over 1 year ago

XWPR isn't a IATA / ICAO / FAA code. About Local_ref, you added personally to wiki it is not clear for what reason. You probably saw the data already marked up incorrectly or tried to systematize it this way. But local_ref it's about local reference. XWPR & similar official refs isn't a local reference. It's a national/international rank of codes. Yes, I'm having trouble understanding why after several discussions you're marking non-local refs as local (local_refs) when it's national/international. No, Wiki doesn't prohibit the use of ref, but recommends the use of IATA / ICAO / FAA (iata=*, icao=*, faa=*) codes where they mean and not use ref to specify these codes. No, except for the local (local_ref), there are also national (nat_ref), international (int_ref), regional (reg_ref). Since these codes are used both at the national and limited international level, I believe that this is just "ref" tag.

155364333 over 1 year ago

There are no restrictions for refs at airfields at wiki. XWPR isn't a local reference (local_ref). It's a national (& international between several countries like Russia, Belarus, Armenia, Qazaqstan etc.) reference. Please, don't change the official refs (by Federal Air Transport Service of Russia at «Руководство по авиационной электросвязи» 01.09.1999 & at «Сборник четырехбуквенных указателей (индексов) местоположения аэродромов, полигонов и посадочных площадок») from "ref" to "local_ref" or ref:aopa:*.

155364333 over 1 year ago

«ref= should not be used for aerodromes, cfr. wiki » ref=* "ref" stands for "reference" and is used for reference numbers or codes. Common for roads, highway exits, routes, entrances to big buildings etc. It is also used for shops and amenities that are numbered officially as part of a retail brand or network respectively.

132257255 over 1 year ago

«Even RWY polygons were removed. ((» According to aeroway=runway, it's recommended to mark runway as a way, and not recommended to mark it as an area. Probably, an area can be built based on the way object and the width=* data

132257255 over 1 year ago

aeroway=stopway *

132257255 over 1 year ago

If you want to replace area:aeroway=clearway with area:aeroway=blastpad, it is worth discussing this issue in the community, because on the wiki https://wiki.openstreetmap. org/wiki/Tag:aeroway=stopway states the identity of stopway with blast pads: «These are also known as overrun areas, or blast pads (although, technically, a "blast pad" may not be strong enough to fully support an aeroplane, and merely be a cover to prevent jet blasts from eroding the ground -- but this distinction isn't generally visible on the ground, so we should ignore it).», which the author of the page on wiki @JesseFTW added from the beginning. In my opinion, this statement is incorrect and we need to separate the stopway (SWY) from clearway (CWY) and blast pad in OSM. If you are willing to participate in promoting these new tags and describing them on the wiki — please, let me know

132257255 over 1 year ago

It's certainly not a SWY (area:aeroway=stopway). It is a CWY or part of a CWY. If the pad is smaller than all CWY, then it may be designated as a blast pad. There is no SWY in either Belgorod Airport or Sheremetyevo Airport

132257255 over 1 year ago

http://www.caiga.ru/ANI_Official/Aip/aipsource1/aip/ad/ad2/uuob/1-ad2-rus-uuob-txt.pdf

AD 2.12 RUNWAY PHYSICAL CHARACTERISTICS
SWY dimensions
(M): NIL
CWY dimensions
(M): 300x150.
If I'm still wrong somewhere — please let me know about it

132257255 over 1 year ago

example*

132257255 over 1 year ago

For wxample, https://aip.enaire.es/AIP/contenido_AIP/AD/AD2/LEBZ/LE_AD_2_LEBZ_ADC_1_en.pdf with SWY&CWY with special RESA marking at SWY https://www.icao.int/NACC/Documents/Meetings/2016/ACI/D1-05-RESA.pdf

132257255 over 1 year ago

«For instance: https://vfr-demo-map.s3.eu-west-1.amazonaws.com/mazda.png» it's Belgorod Airport.

http://www.caiga.ru/ANI_Official/Aip/aipsource1/aip/ad/ad2/uuob/1-ad2-rus-uuob-031-031-1.pdf

CWY, not SWY or anything else.

132257255 over 1 year ago

What is your question? Which airport(s) are you talking about? Do you know the differences between stopway (SWY) aeroway=stopway and clearway (CWY)? The changes weren't for rendering, but for more correct marking of objects

152013983 over 1 year ago

osm.wiki/Russian–Ukrainian_war

152013879 over 1 year ago

osm.wiki/Russian–Ukrainian_war