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; } } }

Map Viewer- Issues with imagery layers and Map Viewer flagging as incompatible

Amanda.Huber@threeriversparks.org_trpd

Hello,

We recently saw that Hennepin County updated their imagery service, upon trying to add to our existing Web Map that consumes these county services we ran into an issue. It appears two layers are not playing nice together, but we're unclear why since they're both in the same coordinate system as they were before and worked properly:

Basemap we're using- https://trpd.maps.arcgis.com/apps/mapviewer/index.html?webmap=5505ebdfdb3a49ea87ccbe469d1bc93f

2024 Hennepin County Service-
https://gis.hennepin.us/arcgis/rest/services/Imagery/UTM_Aerial_2024/MapServer

New 2025 Hennepin County service we're trying to add (and replace the respective 2024 one)- https://gis.hennepin.us/arcgis/rest/services/Imagery/UTM_Aerial_2025/MapServer

When adding the 2025 layer we see this error message:

This is a curious thing, because the 2024 layer is in the exact same coordinate system and has had no issues in this map over the last year:

2025: 26915 (26915) LatestVCSWkid(0)
2024: 26915 (26915) LatestVCSWkid(0)

Upon narrowing it down further, it appears the 2025 Hennepin imagery is not playing nice with the Scott County layer-

Since nothing has changed between the 2024 and 22025 Hennepin County Imagery, can someone explain why all of a sudden these are being flagged as incompatible?

Thanks so much,

Amanda Huber

Find more posts tagged with

Accepted answers

All comments

Neal_t_k

Not sure on that front, I thought maybe visibility thing, but that isn't it...

Amanda.Huber@threeriversparks.org_trpd

...WILD.
That seemed to work perfectly. You are amazing, thank you sooo much!

So next question, why would that be a limitation by Esri?

Neal_t_k

@Amanda__Huber Try adding it as a layer and then moving it to the basemap

Neal_t_k

@Amanda__Huber Yes, Let me try to replicate what I did.

Amanda.Huber@threeriversparks.org_trpd

Hi @Neal_t_k ,

Thanks for your help! I just tried that and unfortunately I'm still seeing that error. I tried your workflow of adding it first, moving all items from basemap, then back in= error

Then tried adding the layer after removing items from the basemap = error

You were able to get this workflow to work?

Thanks again!

Amanda Huber

Neal_t_k

If you add the new one, and then move all the old ones out and then back into the basemap it appears to work

Also there is visibility range set on your new aerial you may need to update.

RPGIS

I have a few thoughts but it could potentially be related to one of the following:

1. UTM_Aerial_2024 - Supported Query Formats: JSON, geoJSON, PBF
2. UTM_Aerial_2025 - Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP
Layer:
1. Layer: HennepinCounty_MN_Nearmap_Sp24_6in.sid (ID: 0)
  Imagery/UTM_Aerial_2024 (MapServer)
Format: MIXED - UTM_Aerial_2024///MapServer/0
Compression Quality: 75.0
Origin: X: -1.190968E8
Y: 1.407315E8

Supported Operations:

Generate Renderer, Return Updates,Iteminfo, Thumbnail Metadata

Supported Operations:

Query, Query Attachments, Query Analytic, Generate Renderer, Return Updates,

Iteminfo, Thumbnail, Metadata

Any number of these could be the issue. Try asking for a differently formatted aerial image with similar specifications and see if that is the issue or pulling in the actual imagery layer using the same direct layer

This could also be it below

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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