# Sloppy frame when using -Bxafg

**URL:** <https://forum.generic-mapping-tools.org/t/sloppy-frame-when-using-bxafg/1010>\
**Category:** Q&A\
**Created:** [November 4, 2020, 9:23pm UTC](https://forum.generic-mapping-tools.org/t/sloppy-frame-when-using-bxafg/1010 "2020-11-04T21:23:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andreas](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@Andreas](https://forum.generic-mapping-tools.org/u/Andreas)\
**Post date:** [November 4, 2020, 9:23pm UTC](https://forum.generic-mapping-tools.org/t/sloppy-frame-when-using-bxafg/1010/1 "2020-11-04T21:23:58Z")

</div>

The frame is very sloppy when using this one liner:

```auto
$ gmt pscoast -RNO -JS0/90/20c -Gblue -Sgray -pdf test -Bxafg

```

I dont think it’s supposed to look that way.

Looks fine if you add a `MAP_FRAME_TYPE=PLAIN` or `-Byafg`.

---

<div class="post-metadata">

**Author:** ![pwessel](https://yyz1.discourse-cdn.com/flex047/user_avatar/forum.generic-mapping-tools.org/pwessel/32/30_2.png) [@pwessel](https://forum.generic-mapping-tools.org/u/pwessel)\
**Post date:** [November 4, 2020, 10:17pm UTC](https://forum.generic-mapping-tools.org/t/sloppy-frame-when-using-bxafg/1010/2 "2020-11-04T22:17:51Z")

</div>

I agree it does not look good, but you requested it, no? By only deciding to get the longitude (x) axes and annotations you end up with this due to the finite width of fancy frames. Now, I imagine what you would like is to **not** plot those extensions since there is no N-S frames to catch them and that is a valid point. I will see what can be done.

---

<div class="post-metadata">

**Author:** ![Andreas](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@Andreas](https://forum.generic-mapping-tools.org/u/Andreas)\
**Post date:** [November 4, 2020, 10:39pm UTC](https://forum.generic-mapping-tools.org/t/sloppy-frame-when-using-bxafg/1010/3 "2020-11-04T22:39:47Z")

</div>

Ah, of course. The apparently ‘too long’ frames are meant to match up with the W-E frames I did not plot.

This map was an accident, but I thought it looked very weird. But your explanation makes sense, and I dont know if anything should be done with it.

Thanks Paul.

---

<div class="post-metadata">

**Author:** ![pwessel](https://yyz1.discourse-cdn.com/flex047/user_avatar/forum.generic-mapping-tools.org/pwessel/32/30_2.png) [@pwessel](https://forum.generic-mapping-tools.org/u/pwessel)\
**Post date:** [November 5, 2020, 2:52am UTC](https://forum.generic-mapping-tools.org/t/sloppy-frame-when-using-bxafg/1010/4 "2020-11-05T02:52:58Z")

</div>

Thanks for pointing this out; I now have a PR on [GitHub](https://github.com/GenericMappingTools/gmt/pull/4420) that improves this situation.

---

<div class="post-metadata">

**Author:** ![Andreas](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@Andreas](https://forum.generic-mapping-tools.org/u/Andreas)\
**Post date:** [November 5, 2020, 8:21am UTC](https://forum.generic-mapping-tools.org/t/sloppy-frame-when-using-bxafg/1010/5 "2020-11-05T08:21:58Z")

</div>

Great Paul.

NB The example on the github issue page looks good, but I dont see any effect on the figure produced by the command I gave in my original post (`gmt pscoast -RNO -JS0/90/20c -Gblue -Sgray -pdf test -Bxafg`). The N-S frame still protrude.

---

<div class="post-metadata">

**Author:** ![pwessel](https://yyz1.discourse-cdn.com/flex047/user_avatar/forum.generic-mapping-tools.org/pwessel/32/30_2.png) [@pwessel](https://forum.generic-mapping-tools.org/u/pwessel)\
**Post date:** [November 5, 2020, 6:30pm UTC](https://forum.generic-mapping-tools.org/t/sloppy-frame-when-using-bxafg/1010/6 "2020-11-05T18:30:12Z")

</div>

Right. We will have to decide if your implicit -BWESN shall be reduced because you only gave -Bx.