OpenStreetMap logo OpenStreetMap

Reinhart Previano's Diary

Mapping Saga Continues at klia2 (Kuala Lumpur International Airport)

Posted by Reinhart Previano on 25 October 2018 in English.
  1. Added Pier P gate numbers
  2. Added Pier Q gate numbers
  3. Added Pier K/L gate numbers

I have discussed those changesets in Part 1 and Part 2. Now it’s time to complete this map.

I recently added the final gates in klia2, which is located at Pier J (Domestic). That’s the main message, however someone have added some lengths of lines connected to the taxiway. Unfortunately, these are not visible in the regular OpenStreetMap layer.

Before changeset Before changeset

Apparently, they are the aeroway:parking_position paths. These paths are self-explanatory, which are the ones followed by an aircraft to safely deliver passengers to the parking spot (and terminal gates). Bing satellite imagery provides a clear view of these lines to be added.

That’s the motivation to complete the Pier K/L parking position lines in Changesets 63867934 and 63868266. Actually, there are some paths that are still unmapped, specifically in the gates K20, L20 and L22. aeroway:parking_position lines will be added in other piers (and hopefully Terminal 1) soon, to make the entire KLIA to be better mapped for the public.

Location: Sepang, Selangor, Malaysia
Email icon Bluesky Icon Facebook Icon LinkedIn Icon Mastodon Icon Telegram Icon X Icon

Discussion

Comment from nickjohnston on 28 October 2018 at 17:23

Great work! I like looking at airports on OpenStreetMap when travelling. Some (such as Munich) are mapped to incredible detail :) Keep up the good work!

Comment from mboeringa on 29 October 2018 at 11:29

Since you seem to go to great detail with this, a couple of remarks to take it to the next level:

  • I noticed the lines and especially curves / bends are digitized quite coarsely. I recommend refining the 90 degree curves by adding and using at least 7 nodes for each curve. This will give a much nicer look when zoomed in on the map.
  • Add surface=asphalt/concrete to both runways and taxiways (surface=*). This will allow distinct rendering for those renderers supporting it (I currently have a personal renderer that does this). This is of course a rough distinction compared to e.g. the list of surface types listed on Wikipedia (https://en.wikipedia.org/wiki/Runway), but these are the standard surface types currently in use in OSM.
  • Add width=x to each runway and taxiway segment. It is highly preferably to use the standard minimal widths as defined by international standards for avation for different runway classifications, instead of approximately “measuring” it in an editor like iD. E.g. most used for runways are 15/18/23/30/36/45/52/60/65/80 meters widths, see for example here (https://www.legislation.gov.au/Details/F2010L02900). For taxiway, it seems usually something like 15/18/23.

Comment from Reinhart Previano on 29 October 2018 at 12:28

I noticed the lines and especially curves / bends are digitized quite coarsely.

Did you mean for the curves on the taxiway?

Comment from mboeringa on 29 October 2018 at 20:30

Yes, sure, except for the curiosity of the Endless Runway project, which is less of a joke than it may seem, I know of no curved runways (yet)… ;-)

https://endlessrunway-project.eu/

Log in to leave a comment