Airport Parking Charts recommendations for next work-up
-
As per Ironman’s new charts, that would be called 33L. So that change was my question.
-
@jayb said in Airport Parking Charts recommendations for next work-up:
As per Ironman’s new charts, that would be called 33L. So that change was my question.
Understood. For sure a mistake.
@Ironman53rd Lets crosscheck here -
it is indeed a mistake … but I did send them out as a concept document and these have not been quality checked.
Apologies for any confusion caused.
Ironman
-
Out of curiosity, are you creating an automated process (similar to that used by @Falcas in WDP); a template for manual production (thinking about the consistency for theatre makers); or bespoke per chart?
I created a Photoshop template system (of sorts) for airport charts, for personal use (and before the WDP automated feature). I’ve previously made these charts available on the forum (Balkans, EMF and Israel).
And another question: what is the RL workflow? Do you land and park at the end of that runway or taxi to the take-off end, in prep for a quick turnaround? I’m sure the answer is “it depends”. Of course, it might also be based on the Squadron’s “home” area.
-
@CriticalMass said in Airport Parking Charts recommendations for next work-up:
Out of curiosity, are you creating an automated process (similar to that used by @Falcas in WDP); a template for manual production (thinking about the consistency for theatre makers); or bespoke per chart?
I created a Photoshop template system (of sorts) for airport charts, for personal use (and before the WDP automated feature). I’ve previously made these charts available on the forum (Balkans, EMF and Israel).
And another question: what is the RL workflow? Do you land and park at the end of that runway or taxi to the take-off end, in prep for a quick turnaround? I’m sure the answer is “it depends”. Of course, it might also be based on the Squadron’s “home” area.
For the APC charts, it was a mixture of MC and photoshop.
For the rest, photoshop.In the future we will avoid having this crazy amount of work again and try using more modern technologies with the use of open source platforms connected with BMS database.
Since we have to recreate ALL charts new for 4.38 (NT, different coordinates, etc.), theres no way to do it again old style.
We have it done in the past 3 years for Balkans/KTO/ITO. It was a nightmare of work and not healthy for the brain.About your “flow” question: it depends indeed.
For ITO: where do you posted those charts? I’m interested to see them.
-
@Micro_440th said in Airport Parking Charts recommendations for next work-up:
@jayb said in Airport Parking Charts recommendations for next work-up:
As per Ironman’s new charts, that would be called 33L. So that change was my question.
Understood. For sure a mistake.
@Ironman53rd Lets crosscheck hereChaps,
Having just reviewed the parking charts for SUWON my charts are correctly labelled - if you land on RWY 33L you will be directed to the parking area shown as AP 33L. (top left hand corner of the AB)
Remember these are post mission parking charts NOT pre mission spawning charts.
-
Thanks for the comments and understanding
@Dee-Jay
for SID, STAR, Airport (if individual charts are available, absolutely!) I was speaking more specifically of the Airport Parking Chart. (I am a hobbyist and fan but not an aviator or in the aviation business)
@Ironman53rd @Micro_440th
I am sorry if I missed the discussion in the forums somewhere.
Charts are not a priority for u4 or 4.38. Only so many resources available. I get it. If you are moving to a new navigraph style system, and spending resources to fix is not in the game plan, please state this. (I looked but didn’t find anything… see above for me missing it )Does the charting team have specific information they want to cut from the new style charts?
Is there a mock-up of what the team really wants as an end goal so maybe community sourced charts could be created within the Docs Team design requirements.Couple of points:
I have made a start on the 4.37 charts, just to establish a format for charts going forward in conjunction with Micro, an example are shown below - any constructive comments would be welcome.
Thank you for putting the time in! In the manuals it states that BMS Docs is moving to new charts like Incheon/Seoul. Ironman links to the older style charts. Ironman please don’t take this as criticism, just a single point that needs clarification.
I think using paint as a start for quick mockups from what is existing is a good starting point, but would lack the detail needed for higher res png. Vector graphics like inkscape or adobe illustrator or some other graphics (I am not a graphics person either) would be a better long term solution.Ironman if you want to connect privately, I would be glad to take this out of the forums @Bugler on discord.
If this topic has been beaten to death already and I am neither in the know nor wise enough, just ask me to back-out and I’ll go on my merry way
Thanks to all that move the ball forward!
Find joy and pass it along!
Bugler
-
@Bugler said in Airport Parking Charts recommendations for next work-up:
If you are moving to a new navigraph style system
I only just found out about this … I have looked at their web site and not sure how this will produce charts and especially parking charts for BMS?
Is there a BMS mock up using “Navigraph” ?
My work was in response to my own dissatisfaction with the “raw” parking charts produced straight from MC - they are very confusing and contain a great deal of information you DONT need to park the jet in the assigned slot as well as the RWY numbering being labelled up as spawning positions not parking positions.
I will just keep this work for myself in 4.37 and produce AB parking charts as I move to a particular AB in BMS 4.37.
In light of your updates on this subject it might be worth closing down this thread ?
Ironman
-
Thank you Ironman! If I find anything else I will tag you.
Yes regarding this topic. I’ll consider it closed.
-
@Bugler said in Airport Parking Charts recommendations for next work-up:
Thank you Ironman! If I find anything else I will tag you.
Yes regarding this topic. I’ll consider it closed.
discord friend request sent
-
The docs team didnt decided yet how we will proceed. So sending a mock up is not possible for now.
Navigraph was just a reference to an idea for an interactive app approach.
If you are interested in this topic, please contact ironman and me.
-
@Ironman53rd - Per your request for suggestions:
For filename consistency and clarity with your documents, rename
SuwonRWY33L.png as SuwonRWYpark33L.png
and
SuwonRWY33R.png as SuwonRWYpark33R.pngto be consistent with the existing filenames of the other two parking charts:
SuwonRWYpark15L and
SuwonRWYpark15R.png -
@SoBad They should name the files the same as chart title.
APC is perfectly fine (Apron Chart).
What is maybe missing on the APC chart are a north reference.
Best would be to have all chart oriented relative to north (mag or true … true would be probably easier)
And when this is not possible, well we will have the north reference drawn on the chart for proper orientation. -
Since the parking charts have dual use (spawn and landing) how about naming them something like “APC 15R / LPC 33L” ? So that would be LPC for Landing Parking Chart.
-
APC does mean Airport Parking Chart (or maybe Apron Parking Chart)
@jayb Not a bad idea, but in that case use the right aero wordings: Departure/Arrival
And to avoir confusion or APC(A) for arrival / APC(D) for departure.
-
This post is deleted! -
@CriticalMass Yep that is what I meant. I wrote “does” but for some reasons my phone corrected it for “doesn’t” (!?) I’ve edited the post.
-
@Dee-Jay My post deleted
So, the current airport charts are called
<name>_Airport.png
, this will change to<name>_AGC[(A|D)].png
in the future? I manually changed mine (to keep aligned to the WDP database). -
@Dee-Jay said in Airport Parking Charts recommendations for next work-up:
@jayb Not a bad idea, but in that case use the right aero wordings: Departure/Arrival
And to avoir confusion or APC(A) for arrival / APC(D) for departure.
Even better, thanks
-
@jayb
I am not the one working on that area.
Our friends Micro and Ironman are in charge.