Heights in task waypoint property box - request Imperial measurements
Heights in task waypoint property box - request Imperial measurements
If Imperial or Australian units are selected, the heights in the property box - elevation, min and max altitudes - should be in feet, or alternately, metres and feet. We shouldn't be banging away on a calculator creating tasks for online.
NEW ADDITION: Heights in Penalty Zones are only in metres. They should also be in feet, reflecting Imperial or Australian unit settings. Please...
Thanks in advance.
Dan Daly
2D Canada
Edited for clarity and addition of a new find - Penalty zones
NEW ADDITION: Heights in Penalty Zones are only in metres. They should also be in feet, reflecting Imperial or Australian unit settings. Please...
Thanks in advance.
Dan Daly
2D Canada
Edited for clarity and addition of a new find - Penalty zones
Last edited by DanD on Sun Feb 14, 2021 4:22 pm, edited 2 times in total.
-
- Posts: 19
- Joined: Wed Feb 27, 2019 3:43 pm
- Location: Ottawa, Canada
Re: Heights in task waypoint property box - request Imperial measurements
The min-max altitudes are displayed in 100xfeet on the task map, isn't that enough for the metrically challenged ?
CN: MPT — CondorUTill webpage: https://condorutill.fr/
Re: Heights in task waypoint property box - request Imperial measurements
Which 'task map'? On mine, in the Task tab in the Flight Planning dialog box, when I move the cursor over the start/finish area, it gives me the height of terrain, which is not start or finish height. It is not documented in the Condor Manual, that I can find.
I flew - in feet and nautical miles - professionally for 35 years. I have 800 glider hours. I have only been in one aircraft with an altimeter in metres - a Fouga Magister at Ecole de l'Air. I have tasked about a hundred flight plans for my club weekly soaring, in C1 and now C2. It is an ongoing irritant to have to do the m to ft conversion and appreciably slows process. Since online competition makes Condor more appealing, surely pissing off the people who run contests in North America and having them consider quitting doing so is not optimal.
For those who run Imperial or Australian units on anything else, why metres?
Could you please provide a screen shot of the 'task map' showing this?
I flew - in feet and nautical miles - professionally for 35 years. I have 800 glider hours. I have only been in one aircraft with an altimeter in metres - a Fouga Magister at Ecole de l'Air. I have tasked about a hundred flight plans for my club weekly soaring, in C1 and now C2. It is an ongoing irritant to have to do the m to ft conversion and appreciably slows process. Since online competition makes Condor more appealing, surely pissing off the people who run contests in North America and having them consider quitting doing so is not optimal.
For those who run Imperial or Australian units on anything else, why metres?
Could you please provide a screen shot of the 'task map' showing this?
Re: Heights in task waypoint property box - request Imperial measurements
Sorry, didn't mean to offend anyone
Pics below (same FPL, different units options)
My feeling was that, now that the DDH is set to aim towards the minimum altitude of a turn point or the finish line, +/- 100ft was precise enough (that's just a wee bit more than 2 times the wingspan of a standard class sailplane)
Metric (altitude limits in 100m) Imperial (altitude limits in 100ft) Aussie (same) Flight plan
Pics below (same FPL, different units options)
My feeling was that, now that the DDH is set to aim towards the minimum altitude of a turn point or the finish line, +/- 100ft was precise enough (that's just a wee bit more than 2 times the wingspan of a standard class sailplane)
Metric (altitude limits in 100m) Imperial (altitude limits in 100ft) Aussie (same) Flight plan
Code: Select all
[Version]
Condor version=2090
[Task]
Landscape=Slovenia2
Count=5
TPName0=LESCE-BLED
TPPosX0=179594.578125
TPPosY0=93454.2109375
TPPosZ0=502
TPAirport0=1
TPSectorType0=0
TPRadius0=3000
TPAngle0=90
TPAltitude0=1500
TPWidth0=0
TPHeight0=10000
TPAzimuth0=0
TPName1=NewTP
TPPosX1=179640
TPPosY1=96072.8125
TPPosZ1=525
TPAirport1=0
TPSectorType1=0
TPRadius1=3000
TPAngle1=180
TPAltitude1=1500
TPWidth1=0
TPHeight1=1500
TPAzimuth1=0
TPName2=KOSUTA
TPPosX2=159941.171875
TPPosY2=103356.1875
TPPosZ2=2028
TPAirport2=0
TPSectorType2=0
TPRadius2=3000
TPAngle2=90
TPAltitude2=2100
TPWidth2=2000
TPHeight2=3000
TPAzimuth2=0
TPName3=NewTP
TPPosX3=167130
TPPosY3=88242.8125
TPPosZ3=455
TPAirport3=0
TPSectorType3=0
TPRadius3=3000
TPAngle3=90
TPAltitude3=1500
TPWidth3=2400
TPHeight3=2600
TPAzimuth3=0
TPName4=NewTP
TPPosX4=179730
TPPosY4=90132.8125
TPPosZ4=532
TPAirport4=0
TPSectorType4=0
TPRadius4=3000
TPAngle4=180
TPAltitude4=1500
TPWidth4=800
TPHeight4=10000
TPAzimuth4=0
PZCount=0
[Weather]
WindDir=134.090621948242
WindSpeed=5.32164859771729
WindUpperSpeed=13.8888893127441
WindDirVariation=3
WindSpeedVariation=2
WindTurbulence=1
ThermalsTemp=22.53125
ThermalsTempVariation=2
ThermalsDew=6.296875
ThermalsStrength=2
ThermalsStrengthVariation=4
ThermalsInversionheight=2387.5
ThermalsWidth=3
ThermalsWidthVariation=3
ThermalsActivity=3
ThermalsTurbulence=1
ThermalsFlatsActivity=2
ThermalsStreeting=3
WavesStability=8
WavesMoisture=6
HighCloudsCoverage=0
Pressure=1016.85992431641
WeatherPreset=0
RandomizeWeatherOnEachFlight=0
[Plane]
Class=Club
Name=StdCirrus
Skin=Default
Water=0
FixedMass=0
CGBias=0
[GameOptions]
StartTime=12
StartTimeWindow=0
RaceStartDelay=0.16666667163372
TaskDate=44003
IconsVisibleRange=12
ThermalHelpersRange=0
TurnpointHelpersRange=3
AllowPDA=1
AllowRealtimeScoring=1
AllowExternalView=1
AllowPadlockView=1
AllowSmoke=1
AllowPlaneRecovery=0
AllowHeightRecovery=0
AllowMidairCollisionRecovery=1
PenaltyCloudFlying=190
PenaltyPlaneRecovery=200
PenaltyHeightRecovery=200
PenaltyWrongWindowEnterance=0
PenaltyWindowCollision=0
PenaltyPenaltyZoneEnterance=0
PenaltyThermalHelpers=200
RandSeed=276911529
StartType=0
StartHeight=700
BreakProb=0
RopeLength=50
MaxTeams=0
AcroFlight=0
[Description]
Text=
You do not have the required permissions to view the files attached to this post.
CN: MPT — CondorUTill webpage: https://condorutill.fr/
Re: Heights in task waypoint property box - request Imperial measurements
OK, I've learned something and will pass that on. Thank you!
My first point - that the properties box which has to be used to get the heights - start height, minimum finish, noting field elevation - are always in metres, even when Imperial or Australian units are selected - is still valid.
Dan
My first point - that the properties box which has to be used to get the heights - start height, minimum finish, noting field elevation - are always in metres, even when Imperial or Australian units are selected - is still valid.
Dan
-
- Posts: 1
- Joined: Thu May 09, 2013 8:29 pm
Re: Heights in task waypoint property box - request Imperial measurements
This would certainly be a helpful feature! +1
Re: Heights in task waypoint property box - request Imperial measurements
I think it would be a good idea as well for consistency, that when a 'Unit' is selected, that all status and selection items in Condor would follow this unit and not just some. Of course there needs to be a reference Unit, and metric is obviously the unit to use, and conversion from/to feet can be to the nearest metre.
I fly in gliders with altimeters in feet, and tried to fly with an altimeter in metres at a World Contest, and ended up trying to convert in my head all the time. I quickly changed to an altimeter in feet, and although it seems trivial, it takes a significant amount of time to get used to a different unit. Flying a real glider with an altimeter in feet and flying Condor in meters presents the same challenge.
I fly in gliders with altimeters in feet, and tried to fly with an altimeter in metres at a World Contest, and ended up trying to convert in my head all the time. I quickly changed to an altimeter in feet, and although it seems trivial, it takes a significant amount of time to get used to a different unit. Flying a real glider with an altimeter in feet and flying Condor in meters presents the same challenge.
Re: Heights in task waypoint property box - request Imperial measurements
Agree. The task entries should use the same unit as the option selected. I hope the developer will put them in a fix.
Re: Heights in task waypoint property box - request Imperial measurements
Agreed. As discussed by Dan and Nick, Imperial/Australina units are the better choice for our applications. My glider also has instruments in feet and knot.
Regards,
Jacques
Regards,
Jacques
-
- Posts: 4
- Joined: Mon Dec 02, 2013 12:27 pm
Re: Heights in task waypoint property box - request Imperial measurements
I agree--I fly with instruments in imperial units. +1
Re: Heights in task waypoint property box - request Imperial measurements
Imperial measurements would be good
Re: Heights in task waypoint property box - request Imperial measurements
As discussed by Dan and Nick, Imperial/Australian units are the better choice to be consistent with our "real life" operations in North America. I concur with the suggestion that task planning units (or wherever else units appear) be consistent with the unit selection in setup.