nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Spatial map series that crosses the antimeridian / 180 degrees

magenta744

Hi all, I'm currently pulling my hair out as I've got a map series in which some of the maps cross the antimeridian. This causes the map extent to go haywire and show the entire world.

My map extents are generated in FME - FME supports "LL360" which allows wrapping around the antimeridian, but it doesn't seem like Arc does. The map series index layer can be in any projection, but the maps themselves are generally in EPSG 3857 / Web Mercator (it does differ on some maps though).

The map which the series is based on has wrapping enabled.

Could I, say, use a particular ArcGIS-supported projection for the map series index and/or for the map itself, that would allow crossing the antimeridian? The weird thing is, I'm pretty sure I've had a map series cross the antimeridian before without issues like this.

Running 3.6.

Encuentra más publicaciones etiquetadas con

Desktop

Accepted answers

magenta744

Hi Renato, thanks for your response. An update on this - I set the spatial reference for the problematic map pages in question to PDC Mercator / 3832 and this is a workaround to the problem, with the extent drawing correctly. Should it work with 3857 as well?

All comments

BarryNorthey

There is a checkbox at the bottom of the Map Properties -> Coordinate Systems window that might need to be checked on if the projection allows wrapping.

magenta744

Hi, I didn't make it clear enough but I already have wrapping enabled for the projection

TomBole

Hi @magenta744

When you say map extents are generated in FME I'm assuming that this process is creating features that are used in a Spatial Map Series. If so, what extent do you get if you select one of the features (map series pages) that is problematic and use zoom to selection command? If you get the same unwanted extent then the issue is not with the Layout/Map Series. The problem is deeper in the code stack, perhaps with how Pro handles these extents or it could be an issue with how the data is created. If the problem is only reproducible with a Map Series then it likely a Layout-related bug.

I'm not familiar with any existing issues of this nature. Can you contact Esri Support? They are better equipped to handle troubleshooting steps and gather bug data. They can be contacted at https://support.esri.com/en/contact-tech-support.

Hope this helps,

Tom

magenta744

Thanks for your response - actually the problem seems to be simpler (well maybe). You're correct about FME. When I go to the extent of the created polygon, it actually shows the whole world, so it does seem to be an issue there and not necessarily with the map series. I would have thought that with wrapping on, this would happen...

magenta744

I'll speak to Esri anyway, but let me know if you think I've missed something obvious

RenatoSalvaleon3

@magenta744 please ask ESRI support to tag the issue with Data Interoperability product. They will ask for your data so we could try to repro the behavior to determine if its a bug or we coud provide a workaround through the Workbench app.

magenta744

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Iniciar Sesión
Registrarse

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.