Atlas Output alignment

I am attempting to use an atlas to produce a 3 panel map that will be printed to separate pages and then aligned together, similar to a ‘triptych’ but vertically.

I created a single rectangle over the map output area, then split it into 3 polygons (using a plugin).

This is working well.

What I am having trouble with and need advice on, is that the features/lines of the map on the bottom of one page do not match the precise location/coordinate of the same feature on the top of the next page. It appears that the scale differs between each atlas page. I attempted to set the scale equal, but it resets to a close/similar value. I am wondering first, how to get the atlas output to align and if there are more resource or topics I need to look into to help figure this out.

Is it necessary to create 3 separate maps, as opposed to one single map across a single custom page size?

On Fri, Dec 26, 2025, 5:24 PM Stephen via OSGeo Discourse <noreply@discourse.osgeo.org> wrote:

scetron
December 26

I am attempting to use an atlas to produce a 3 panel map that will be printed to separate pages and then aligned together, similar to a ‘triptych’ but vertically.

I created a single rectangle over the map output area, then split it into 3 polygons (using a plugin).

This is working well.

What I am having trouble with and need advice on, is that the features/lines of the map on the bottom of one page do not match the precise location/coordinate of the same feature on the top of the next page. It appears that the scale differs between each atlas page. I attempted to set the scale equal, but it resets to a close/similar value. I am wondering first, how to get the atlas output to align and if there are more resource or topics I need to look into to help figure this out.


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

Yes, the output will be used/printed separately but should align. I suppose I can cut the output from a single page export myself, but I would have thought this would be a part of the atlas. It seems like from documentation I should be able to place my own extents that I’ve calculated, which is also not working.

I would also ask, is this part of using the atlas? Or could this be something I am not familiar with how mapping crs to flat output files slightly distort things?

After sleeping on it last night, I did have a couple of questions related to projection.

What projection is the dataset ?

How large are your polygons in that projection?

Doug

On Sun, Dec 28, 2025 at 8:45 PM Stephen via OSGeo Discourse <noreply@discourse.osgeo.org> wrote:

scetron
December 29

Yes, the output will be used/printed separately but should align. I suppose I can cut the output from a single page export myself, but I would have thought this would be a part of the atlas. It seems like from documentation I should be able to place my own extents that I’ve calculated, which is also not working.

I would also ask, is this part of using the atlas? Or could this be something I am not familiar with how mapping crs to flat output files slightly distort things?


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

The project projection is 26918 and the polygons are around 1285596223 in area (not sure of the unit there, I think derived from that projection?). I just noticed that the polygons have slightly different area, I am thinking due to the projection? Perhaps this is making a little more sense now why each map doesn’t have the same scale/size and that I would likely need a more trapezoid shape to get equal area and for the atlas to line up better.

You may want to review https://www.usgs.gov/faqs/how-are-utm-coordinates-measured-usgs-topographic-maps or related UTM zone descriptions

This is the epsg code for utm zone 18N. The middle of each zone has an easting of 500,000, so the placement of your polygons in the zone may account for the differences.

Doug

On Wed, Dec 31, 2025, 3:47 PM Stephen via OSGeo Discourse <noreply@discourse.osgeo.org> wrote:

scetron
December 31

The project projection is 26918 and the polygons are around 1285596223 in area (not sure of the unit there, I think derived from that projection?). I just noticed that the polygons have slightly different area, I am thinking due to the projection? Perhaps this is making a little more sense now why each map doesn’t have the same scale/size and that I would likely need a more trapezoid shape to get equal area and for the atlas to line up better.


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

It sounds like each polygon is about 36 km on a side, if square. What latitude are the polygons at?

More utm fun, https://www.e-education.psu.edu/natureofgeoinfo/book/export/html/1695#:~:text=In%20every%20case%2C%20distortion%20is,%2B%20or%20%2D%201%20meter%20off.

https://www.e-education.psu.edu/natureofgeoinfo/c2_p23.html#:~:text=UTM%20eastings%20range%20from%20167%2C000,10%2C000%2C000%20meters%20in%20South%20zones.

On Wed, Dec 31, 2025, 6:20 PM Doug Newcomb <gistinker@gmail.com> wrote:

You may want to review https://www.usgs.gov/faqs/how-are-utm-coordinates-measured-usgs-topographic-maps or related UTM zone descriptions

This is the epsg code for utm zone 18N. The middle of each zone has an easting of 500,000, so the placement of your polygons in the zone may account for the differences.

Doug

On Wed, Dec 31, 2025, 3:47 PM Stephen via OSGeo Discourse <noreply@discourse.osgeo.org> wrote:

scetron
December 31

The project projection is 26918 and the polygons are around 1285596223 in area (not sure of the unit there, I think derived from that projection?). I just noticed that the polygons have slightly different area, I am thinking due to the projection? Perhaps this is making a little more sense now why each map doesn’t have the same scale/size and that I would likely need a more trapezoid shape to get equal area and for the atlas to line up better.


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.