# Height Map

**URL:** <https://discourse.agopengps.com/t/height-map/13324>\
**Category:** Feature requests\
**Created:** [16 June 2023 13:57 UTC](https://discourse.agopengps.com/t/height-map/13324 "2023-06-16T13:57:46Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![BGunics](https://discourse.agopengps.com/user_avatar/discourse.agopengps.com/bgunics/32/20565_2.png) [@BGunics](https://discourse.agopengps.com/u/BGunics)\
**Post date:** [16 June 2023 13:57 UTC](https://discourse.agopengps.com/t/height-map/13324/1 "2023-06-16T13:57:46Z")

</div>

We were discussing about height maps, it looks we’d need the following data:  
heighmap.txt  
epoch, Lat, Lon, Height, Heading, Roll, antenna height, workswitch

I think it could be stored similarly how we do sections.txt  
Then using post process (or perhaps even during operation? ) we could enhance the data for higher resolution.  
10Hz / per line and +2 extra lines based on roll?

cm precision? 😃

Here’s what Trimble can do:

 ![image](https://discourse.agopengps.com/uploads/default/original/2X/c/cc3fc143fd8a654bee84e7ddedbfc78041c12f73.jpeg)

---

<div class="post-metadata">

**Author:** ![ahevesi](https://discourse.agopengps.com/letter_avatar_proxy/v4/letter/a/d6d6ee/32.png) [@ahevesi](https://discourse.agopengps.com/u/ahevesi)\
**Post date:** [16 June 2023 19:16 UTC](https://discourse.agopengps.com/t/height-map/13324/2 "2023-06-16T19:16:54Z")

</div>

Good idea!  
With the help of this feature, the drainage routes can be easily designed on my waterlogged areas. In my opinion, collecting data every 20-30 square meters (relative to the width of the implement) should be sufficient for the purpose I would use it for.

---

<div class="post-metadata">

**Author:** ![Dylan1](https://discourse.agopengps.com/letter_avatar_proxy/v4/letter/d/898d66/32.png) [@Dylan1](https://discourse.agopengps.com/u/Dylan1)\
**Post date:** [30 June 2023 03:54 UTC](https://discourse.agopengps.com/t/height-map/13324/3 "2023-06-30T03:54:21Z")

</div>

sounds like an awesome idea. collect your field elevations while seeding etc. then go back and design your drains with opengrade

---

<div class="post-metadata">

**Author:** ![kcm01](https://discourse.agopengps.com/letter_avatar_proxy/v4/letter/k/258eb7/32.png) [@kcm01](https://discourse.agopengps.com/u/kcm01)\
**Post date:** [30 June 2023 04:09 UTC](https://discourse.agopengps.com/t/height-map/13324/4 "2023-06-30T04:09:24Z")

</div>

Make sure you use orthometric heights for drainage design. Orthometric height datums are normally related to mean sea level and take into account the effect of gravity.

---

<div class="post-metadata">

**Author:** ![Boerher](https://discourse.agopengps.com/letter_avatar_proxy/v4/letter/b/bc8723/32.png) [@Boerher](https://discourse.agopengps.com/u/Boerher)\
**Post date:** [12 September 2023 21:18 UTC](https://discourse.agopengps.com/t/height-map/13324/5 "2023-09-12T21:18:44Z")

</div>

Is there any progress? I’m also interested.

---

<div class="post-metadata">

**Author:** ![Kevin](https://discourse.agopengps.com/letter_avatar_proxy/v4/letter/k/2acd7d/32.png) [@Kevin](https://discourse.agopengps.com/u/Kevin)\
**Post date:** [13 September 2023 15:23 UTC](https://discourse.agopengps.com/t/height-map/13324/6 "2023-09-13T15:23:08Z")

</div>

Wow I’ve been installing drain tile a long time and have never even thought about that. It looks like roughly 8in / mile according to google. It’s minimal but can add up. Thanks for knowledge!

---

<div class="post-metadata">

**Author:** ![NorthernFarmer](https://discourse.agopengps.com/letter_avatar_proxy/v4/letter/n/c0e974/32.png) [@NorthernFarmer](https://discourse.agopengps.com/u/NorthernFarmer)\
**Post date:** [14 September 2023 19:06 UTC](https://discourse.agopengps.com/t/height-map/13324/7 "2023-09-14T19:06:57Z")

</div>

8 inch per mile sounds a lot to me, is that on a rare spot or a relatively common figure?

Aren’t drainage machines usually using laser or old systems just visual control, neither one considering gravity changes (within the worked area).

---

<div class="post-metadata">

**Author:** ![WildBuckwheat](https://discourse.agopengps.com/letter_avatar_proxy/v4/letter/w/46a35a/32.png) [@WildBuckwheat](https://discourse.agopengps.com/u/WildBuckwheat)\
**Post date:** [14 September 2023 21:14 UTC](https://discourse.agopengps.com/t/height-map/13324/8 "2023-09-14T21:14:53Z")

</div>

> [@NorthernFarmer](#):
>
> 8 inch per mile sounds a lot to me, is that on a rare spot or a relatively common figure?

That’s a straight line (laser) sitting tangent (level) to the diameter of the Earth (round).

If you put the laser at the highest part of the field then all the errors just lead to extra slope.

---

<div class="post-metadata">

**Author:** ![Kevin](https://discourse.agopengps.com/letter_avatar_proxy/v4/letter/k/2acd7d/32.png) [@Kevin](https://discourse.agopengps.com/u/Kevin)\
**Post date:** [15 September 2023 12:36 UTC](https://discourse.agopengps.com/t/height-map/13324/9 "2023-09-15T12:36:01Z")

</div>

[Quora](https://www.quora.com/How-many-feet-per-mile-does-the-earth-curve-down-from-where-you-stand)  
That is some math from Quora. Average drop. Basically at sea. 8" per mile is .0126% slope. It’s squared so shorter distance would be much less slope. More distance much greater slope. I would say hardly noticable within laser range.

---

<div class="post-metadata">

**Author:** ![NorthernFarmer](https://discourse.agopengps.com/letter_avatar_proxy/v4/letter/n/c0e974/32.png) [@NorthernFarmer](https://discourse.agopengps.com/u/NorthernFarmer)\
**Post date:** [15 September 2023 12:45 UTC](https://discourse.agopengps.com/t/height-map/13324/10 "2023-09-15T12:45:40Z")

</div>

So the main thing is the curvature of the face of the earth, not that much from the local variation of gravity. Would be nice to see example figures for the latter but already the simple curvature surprised me. Should I say we luckily do not have 15 mile long fields as in the Quora example. 😀

---

<div class="post-metadata">

**Author:** ![BGunics](https://discourse.agopengps.com/user_avatar/discourse.agopengps.com/bgunics/32/20565_2.png) [@BGunics](https://discourse.agopengps.com/u/BGunics)\
**Post date:** [15 October 2023 12:47 UTC](https://discourse.agopengps.com/t/height-map/13324/11 "2023-10-15T12:47:40Z")

</div>

I’ve seen a demo with John Deere where they mentioned that to set up AB curve they had to manually drive on the AB to have it in the program. Meh…  
Video here (it’s in Hungarian but the drone shot is cool)

[![](https://discourse.agopengps.com/uploads/default/original/3X/f/b/fbfe88b71cea55a47415f272b7f2f57120618853.jpeg "Hatékony módszerek talajerózió ellen: gépek, erózióvédelmi sávok, szintvonalas művelés 12%-os lejtőn") ](https://www.youtube.com/watch?v=4n8xgbQsKxg)

So I tried to reproduce it in AOG 🙂  
First we need contour lines, that I created with this tool: [https://contourmapcreator.urgr8.ch/](https://contourmapcreator.urgr8.ch/)

Here’s on google earth:

 ![image](https://discourse.agopengps.com/uploads/default/original/3X/8/2/829224115fd3f9436d4bfd7bb6e25ff0ac278d68.jpeg)  
Then I draw:

- BROWN: field outer boundary
- RED: some trees + 2 big electrical poles that we’d like to avoid.
- GREEN: the 2 areas based on which we can create 4 contour lines.

How to add these in AOG?  
Issue #1: for some reason KMZ doesn’t work.  
Issue #2: for some reason we can only define AB curve on the outer boundary…

Workaround for #2:  
I start by adding the GREEN areas and then use the overview button / function to draw my AB curve. (We’ll name / smooth them later.)

So for each green area:

1. load the KML as outer boundary
2. do 1-2 AB curve
3. Then I delete the outer boundary (curve stays)
4. then I name / smoothen the curve

Then I add the brown / red boundaries.

Here it is in AgOpenGPS:

 ![image](https://discourse.agopengps.com/uploads/default/original/3X/4/4/446dcfd0c2258bdd1f1825bbaa42c5d3a03e8297.png)

However when I try to use K-turn I get this error: (latest v5.7.3.1 )  
 ![image](https://discourse.agopengps.com/uploads/default/original/3X/0/c/0c7febe30a65daefdd87d8d614af71c115ac9239.png)  
(U-turn does work nicely, but sometimes the K turn is displayed as U turn, although I set my radius 5.00m and implement was 10.00m so probably that’s why)

Am I doing something wrong by defining AB curve from boundaries that no longer exists or I found a bug?  
Files to reproduce:  
[hektarpodcast.zip](https://discourse.agopengps.com/uploads/short-url/shM2voU6nox7LV5r3zAqnTSRnxw.zip) (113.9 KB)

---

<div class="post-metadata">

**Author:** ![Larsvest](https://discourse.agopengps.com/letter_avatar_proxy/v4/letter/l/50afbb/32.png) [@Larsvest](https://discourse.agopengps.com/u/Larsvest)\
**Post date:** [15 October 2023 14:17 UTC](https://discourse.agopengps.com/t/height-map/13324/12 "2023-10-15T14:17:41Z")

</div>

> [@BGunics](#):
>
> 5.00m and implement was 10.00m so probably that’s why)

I believe the old fault with AOG making 8 shape turns is fixed, but to rule out that issue, set radius to 4,95 m or 5,05 ( old fix for 8 shape issue doing u turn at half implement width)

---

<div class="post-metadata">

**Author:** ![BGunics](https://discourse.agopengps.com/user_avatar/discourse.agopengps.com/bgunics/32/20565_2.png) [@BGunics](https://discourse.agopengps.com/u/BGunics)\
**Post date:** [15 October 2023 19:41 UTC](https://discourse.agopengps.com/t/height-map/13324/13 "2023-10-15T19:41:25Z")

</div>

Countours.txt seem to have the height map:

> <https://github.com/farmerbriantee/AgOpenGPS/blob/81bea9e8380162eba35c574c65967c893e62192d/SourceCode/GPS/Forms/SaveOpen.Designer.cs#L1219C1-L1224C1>