Location Field in the templates causes error on applying template

[kkopiec]

Steps to reproduce:

1. Create content type based library
2. Add Location field to either one or all of the content types (through the list view add column)
3. Grab provisioning template
4. Apply provisioning template to another site collection

Result:
Following error message:
Apply-PnPProvisioningTemplate : Column Limit Exceeded. There are too many columns of the specified data type. Please delete some other columns first. Note that some column types like numbers and currency use the same data type.

initial investigation revealed that Location column adds all its sub fields (i.e. City, street, postcode etc.) to the data type and this create abundance of single line of text type fields.
This breaks deployment with the Message above.
The only solution is to delete Location fields entirely from the template and then reapply them manually to each content type (post deployment).
As the location field is really popular and useful for the customers this renders PnP templating not fully useful in the best case (single large deployment), unfeasible at all in case of dynamic deployments.

[sathya-bhat]

Any update or workaround for this issue? I am running into this in Document library list column with Location.
PnP trace shows
[OfficeDevPnP.Core] [0] [Error] ExecuteQuery threw following exception: Microsoft.SharePoint.Client.ServerException: Column Limit Exceeded.

[BenLinktech]

This error is still occurring in 2022 -almost 3 years ago - and still not resolved!
However, my quick test of deleting all of the reference/secondary fields - just leave the main "Location" field reference and it provisions correctly - the other fields seem to be created-on-demand when using the provisioned template.
So just delete ALL FIELDS that have a colon in the DisplayName property. E.g.
<Field Type="Text" DisplayName="Destination: Country/Region"