Add Realistic Elevation to Simulated Run
add elevation to gpxrealistic elevation profilealtitude data gpselevation gain strava
Learn how to add real elevation data to your GPS activities. We show you how to create altitude profiles that match real terrain. This makes your routes look real.
1
1. Why Elevation Matters
Good elevation data is key to making your activities look real:
Impact on How Real It Looks:
• Strava and other apps use elevation gain to calculate effort
• Flat routes in hilly areas look fake
• Mountain routes with no elevation changes are clear fakes
• Elevation affects pace and how hard a run feels
What Good Elevation Data Includes:
• Gradual changes that match the real ground
• Pace that matches the hill (slower uphill, faster downhill)
• Total elevation gain that is realistic for the distance
• Smooth changes with no sudden jumps
• It should accurately show the local area
Without good elevation, your activity may:
- Look fake to experienced runners
- Have wrong effort scores
- Look wrong on local leaderboards
- Fail automatic detection
Impact on How Real It Looks:
• Strava and other apps use elevation gain to calculate effort
• Flat routes in hilly areas look fake
• Mountain routes with no elevation changes are clear fakes
• Elevation affects pace and how hard a run feels
What Good Elevation Data Includes:
• Gradual changes that match the real ground
• Pace that matches the hill (slower uphill, faster downhill)
• Total elevation gain that is realistic for the distance
• Smooth changes with no sudden jumps
• It should accurately show the local area
Without good elevation, your activity may:
- Look fake to experienced runners
- Have wrong effort scores
- Look wrong on local leaderboards
- Fail automatic detection
[Image: Comparison of realistic vs unrealistic elevation profiles]
2
2. Automatic Elevation From Terrain Data
The easiest and best way is to use real terrain data:
How Easy Jockey Does It:
When you draw a route in Easy Jockey, the tool can:
• Find elevation data for your route
• Add real altitude values to each GPS point
• Make sure the elevation changes are smooth
• Match the real ground in that area
Benefits of Automatic Elevation:
• Matches real-world terrain
• No math needed
• It adds hills, valleys, and mountains for you
• It creates real profiles that match the area
Using Automatic Elevation:
1. Draw or import your route
2. Turn on the "Add Elevation Data" option
3. The system finds the terrain data
4. Elevation is applied to all points
5. Review the elevation profile
Best For:
• Real routes you want to copy
• When you need it to be accurate
• First-time users
• Complex ground with many hills
How Easy Jockey Does It:
When you draw a route in Easy Jockey, the tool can:
• Find elevation data for your route
• Add real altitude values to each GPS point
• Make sure the elevation changes are smooth
• Match the real ground in that area
Benefits of Automatic Elevation:
• Matches real-world terrain
• No math needed
• It adds hills, valleys, and mountains for you
• It creates real profiles that match the area
Using Automatic Elevation:
1. Draw or import your route
2. Turn on the "Add Elevation Data" option
3. The system finds the terrain data
4. Elevation is applied to all points
5. Review the elevation profile
Best For:
• Real routes you want to copy
• When you need it to be accurate
• First-time users
• Complex ground with many hills
[Image: Automatic elevation application process diagram]
3
3. Manual Elevation Adjustments
For special cases or small changes, manual control gives you options:
When to Use Manual Adjustment:
• Creating fictional routes
• Making hills bigger for a training simulation
• Flattening routes for a specific reason
• GPS art that needs a specific profile
Techniques for Manual Elevation:
Gradual Hills:
Start at a base elevation (e.g., 100m). Gradually increase to a peak (e.g., 200m). Then decrease. Avoid sudden jumps.
Natural Variation:
Even "flat" ground has 2-5 meter changes. Add small ups and downs.
Hill Symmetry:
What goes up must come down. The end elevation should match the start (unless it's a one-way mountain climb).
Pace and Hill Matching:
• Uphill sections: reduce pace by 20-40%
• Downhill sections: increase pace by 10-20%
• Flat sections: maintain a steady pace
Elevation Rate:
• Gradual hills: 2-5% grade (2-5m per 100m)
• Moderate hills: 5-10% grade
• Steep hills: 10-15% grade
• Extreme hills: 15%+ (rare, use with care)
When to Use Manual Adjustment:
• Creating fictional routes
• Making hills bigger for a training simulation
• Flattening routes for a specific reason
• GPS art that needs a specific profile
Techniques for Manual Elevation:
Gradual Hills:
Start at a base elevation (e.g., 100m). Gradually increase to a peak (e.g., 200m). Then decrease. Avoid sudden jumps.
Natural Variation:
Even "flat" ground has 2-5 meter changes. Add small ups and downs.
Hill Symmetry:
What goes up must come down. The end elevation should match the start (unless it's a one-way mountain climb).
Pace and Hill Matching:
• Uphill sections: reduce pace by 20-40%
• Downhill sections: increase pace by 10-20%
• Flat sections: maintain a steady pace
Elevation Rate:
• Gradual hills: 2-5% grade (2-5m per 100m)
• Moderate hills: 5-10% grade
• Steep hills: 10-15% grade
• Extreme hills: 15%+ (rare, use with care)
[Image: Manual elevation adjustment interface]
4
4. Region-Appropriate Elevation
Different places have different types of terrain:
Flat Regions (Netherlands, Florida, Denmark):
• Total elevation gain: 0-50m per 10km
• Very small hills
• Mostly constant altitude
• Small changes from bridges
Moderate Hills (UK, Eastern US):
• Total elevation gain: 50-200m per 10km
• Rolling hills with easy slopes
• A mix of flat and hilly parts
• A few steep climbs
Mountainous Regions (Alps, Rockies, Pyrenees):
• Total elevation gain: 200-1000m+ per 10km
• Long climbs and long downhills
• Steep hills are common
• Big altitude changes
Urban Areas:
• Varies by city
• Include bridge elevations
• Include city hills
• Parking garages and underpasses
Research Your Location:
Before creating elevation:
• Look at real runs in that area on Strava
• Use topographic maps
• Find typical elevation gains for the region
• Match what local runners see
Flat Regions (Netherlands, Florida, Denmark):
• Total elevation gain: 0-50m per 10km
• Very small hills
• Mostly constant altitude
• Small changes from bridges
Moderate Hills (UK, Eastern US):
• Total elevation gain: 50-200m per 10km
• Rolling hills with easy slopes
• A mix of flat and hilly parts
• A few steep climbs
Mountainous Regions (Alps, Rockies, Pyrenees):
• Total elevation gain: 200-1000m+ per 10km
• Long climbs and long downhills
• Steep hills are common
• Big altitude changes
Urban Areas:
• Varies by city
• Include bridge elevations
• Include city hills
• Parking garages and underpasses
Research Your Location:
Before creating elevation:
• Look at real runs in that area on Strava
• Use topographic maps
• Find typical elevation gains for the region
• Match what local runners see
[Image: World elevation profile examples by region]
5
5. Common Elevation Mistakes
Avoid these errors that make elevation data look fake:
❌ Mistake 1: Perfectly Flat
Issue: Real ground is never perfectly flat
Solution: Add 2-5m changes even in flat areas
❌ Mistake 2: Sudden Jumps
Issue: Elevation jumps 20m in one point
Solution: Spread the change over many points
❌ Mistake 3: Unrealistic Total Gain
Issue: 500m gain in a flat area
Solution: Find typical values for that area
❌ Mistake 4: Hills Don't Match Pace
Issue: Same pace on flat ground and hills
Solution: Change your pace to match the hill
❌ Mistake 5: No Return to Start Elevation
Issue: Starting at 50m, ending at 150m on a loop
Solution: Make sure loops end near the start elevation
❌ Mistake 6: Too Smooth
Issue: Elevation changes are perfectly gradual
Solution: Add small, random changes
❌ Mistake 7: Wrong Scale
Issue: Making a small hill seem huge
Solution: Find real elevation values
❌ Mistake 8: Ignoring Geography
Issue: Big hills in a flat town
Solution: Match the local ground
❌ Mistake 1: Perfectly Flat
Issue: Real ground is never perfectly flat
Solution: Add 2-5m changes even in flat areas
❌ Mistake 2: Sudden Jumps
Issue: Elevation jumps 20m in one point
Solution: Spread the change over many points
❌ Mistake 3: Unrealistic Total Gain
Issue: 500m gain in a flat area
Solution: Find typical values for that area
❌ Mistake 4: Hills Don't Match Pace
Issue: Same pace on flat ground and hills
Solution: Change your pace to match the hill
❌ Mistake 5: No Return to Start Elevation
Issue: Starting at 50m, ending at 150m on a loop
Solution: Make sure loops end near the start elevation
❌ Mistake 6: Too Smooth
Issue: Elevation changes are perfectly gradual
Solution: Add small, random changes
❌ Mistake 7: Wrong Scale
Issue: Making a small hill seem huge
Solution: Find real elevation values
❌ Mistake 8: Ignoring Geography
Issue: Big hills in a flat town
Solution: Match the local ground
[Image: Common elevation mistakes illustrated]
6
6. Advanced Techniques
Use these tips for even better profiles:
Simulating Real Climbs:
Copy famous climbs:
• Alpe d'Huez: ~1100m gain over 13.8km
• Mount Ventoux: ~1600m gain over 21km
• Hawk Hill, San Francisco: ~250m gain over 2km
Seasonal Considerations:
It is best to keep profiles consistent. Real elevation does not change much with the seasons.
Matching Strava Segments:
If your route covers a real Strava segment:
• Check the segment's elevation profile
• Match the expected elevation gain
• Align with other times on the leaderboard
Creating Training-Specific Profiles:
• Hill repeats: many up-and-down spikes
• Tempo runs: moderate, steady elevation
• Recovery runs: very little elevation change
• Interval training: varied elevation
Quality Check:
✓ Elevation matches the location
✓ Total gain is realistic for the distance
✓ Pace matches elevation changes
✓ No sudden jumps or drops
✓ Smooth changes between points
✓ Loops return to start elevation
✓ The profile looks real in a graph
Simulating Real Climbs:
Copy famous climbs:
• Alpe d'Huez: ~1100m gain over 13.8km
• Mount Ventoux: ~1600m gain over 21km
• Hawk Hill, San Francisco: ~250m gain over 2km
Seasonal Considerations:
It is best to keep profiles consistent. Real elevation does not change much with the seasons.
Matching Strava Segments:
If your route covers a real Strava segment:
• Check the segment's elevation profile
• Match the expected elevation gain
• Align with other times on the leaderboard
Creating Training-Specific Profiles:
• Hill repeats: many up-and-down spikes
• Tempo runs: moderate, steady elevation
• Recovery runs: very little elevation change
• Interval training: varied elevation
Quality Check:
✓ Elevation matches the location
✓ Total gain is realistic for the distance
✓ Pace matches elevation changes
✓ No sudden jumps or drops
✓ Smooth changes between points
✓ Loops return to start elevation
✓ The profile looks real in a graph
7
7. Tools and Resources
Resources for creating better elevation profiles:
Easy Jockey Features:
• Automatic elevation from terrain
• Manual elevation tools
• Elevation profile preview
• Pace and elevation matching
• Pre-set hill profiles for training
External Resources:
• OpenTopoMap: free terrain maps
• Google Earth: see terrain in 3D
• Strava Heat Map: see popular routes and their profiles
• Local running clubs: find data for your area
Verification Tools:
Before you upload your activity:
• Preview the elevation graph
• Check total elevation gain
• Compare with real runs in the area
• Verify pace matches the hills
• Test on different platforms if possible
Learning from Real Data:
Get GPX files from real runs:
• Study their elevation patterns
• Understand natural changes
• Learn regional differences
• Compare your fake runs to real ones
Easy Jockey Features:
• Automatic elevation from terrain
• Manual elevation tools
• Elevation profile preview
• Pace and elevation matching
• Pre-set hill profiles for training
External Resources:
• OpenTopoMap: free terrain maps
• Google Earth: see terrain in 3D
• Strava Heat Map: see popular routes and their profiles
• Local running clubs: find data for your area
Verification Tools:
Before you upload your activity:
• Preview the elevation graph
• Check total elevation gain
• Compare with real runs in the area
• Verify pace matches the hills
• Test on different platforms if possible
Learning from Real Data:
Get GPX files from real runs:
• Study their elevation patterns
• Understand natural changes
• Learn regional differences
• Compare your fake runs to real ones
Conclusion
Adding realistic elevation makes your fake runs look real. You can use Easy Jockey's automatic tool or build a profile by hand. The key is to understand how real elevation works. Match your elevation to the local area. Match your pace to the hills. Avoid common mistakes like sudden jumps or flat lines. With practice, your elevation profiles will make your activities look authentic. They will pass any careful check.