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

Basemap “spatial reference isn't compatible.”

CeBe

With the ArcGIS Field Maps 25.2.0 release, all basemap services are showing “spatial reference isn't compatible.” They work normally in the web portal, but no longer in Field Maps. Several users have reported this issue on Reddit. This is an extremely critical error; everything worked fine before the update.

Find more posts tagged with

Accepted answers

All comments

JHolmes

I'm experiencing the same thing - sideloaded TPKs basemaps that worked before the 9/30 update that now don't work.

ChrisDunn1

Hi @TuolumneRiver ,

We do not have a timeframe at the moment as we are assessing possible solutions, getting it fixed is a high priority. We are hoping to include a fix in an upcoming release but we don't yet know if that will be feasible. I'm sorry that I don't have a better answer right now.

ChrisDunn1

Hi @CeBe - thank you for the clarification, it didn't register with me in your original post that you said basemap services and not basemap packages. While that may be related to the work that was done with basemaps, it is certainly unexpected. Have you opened a case with support? That will be the best way to get someone looking into it quickly as they are already familiar with these issues that have come up with the new Field Maps release.

CeBe

It's not about packing the basemap; the online map in Field Maps no longer works! Our map and online background map in Field Maps have the same spatial reference. Our pre-calculated tcpkgs also use the same spatial reference. The pre-calculated tcpkgs can be used, but the Online background map does not work when you are online. The following message appears: “spatial reference isn't compatible.” The background maps work normally in the web browser. It's the online map in Field Maps.

All our data is in UTM33N; we don't use different references!

TuolumneRiver

@ChrisDunn1 Is there any timeline for an update that will fix this issue? I need to know whether I can wait this out or if I need to prioritize rebuilding and deploying sideloaded tiles to my users

paleo999

I have noticed this issue myself with some of our field users for the last week since the 9/30 update. We had multiple base maps and all of a sudden we are getting a spatial reference error some base maps for some of my users. Never had this issue before and nothing has been changed on our end. It should be noted this applies to sideloaded TPK base maps.

base_map_error.png

MaxMolello

Why would you block something that previously worked? You can't take away features that a ton of people already built everything on. Then tell them the workaround is rebuild everything a different way.

ChrisDunn1

Hi @CeBe ,

There is a limitation with the current release where we are blocking switching to a basemap if it is not in the same spatial reference as the map. This will be fixed in a future release.

If your basemap and your map are in the same spatial reference and therefore switching should not be blocked, we have seen an issue with packaging the basemap (tpk/tpkx) where you need to ensure the "Extent Sptial Reference" setting in the packaging tool (it should be near the bottom of the tool UI) is also using the same spatial reference as your tiles and your map.

We're sorry for the issues this is causing but hopefully that helps get you unstuck for now.

Chris

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.