Update Maps documentation for .NET 11 features

[jfversluis]

Description

Updates the Maps control documentation (docs/user-interface/controls/map.md) to cover all new features added in .NET 11 via the Maps epic (dotnet/maui#33787).

New features documented

All new content is gated with >=net-maui-11.0 moniker ranges.

Feature	Source PR
Pin clustering (IsClusteringEnabled, ClusterClicked)	dotnet/maui#33831
Custom pin icons (Pin.ImageSource)	dotnet/maui#33950
MoveToRegion(MapSpan, bool animated) overload	dotnet/maui#33982
MapSpan.FromLocations() for best-fit zoom	dotnet/maui#33982
Pin.ShowInfoWindow() / Pin.HideInfoWindow()	dotnet/maui#33985
MapLongClicked event	dotnet/maui#33792
MapElementClick event for Circle/Polygon/Polyline	dotnet/maui#29101
UserLocationChanged event and LastUserLocation	dotnet/maui#33799
Map.MapStyle for custom JSON styling (Android)	dotnet/maui#33991
MapElement.IsVisible and MapElement.ZIndex	dotnet/maui#33993
XAML TypeConverters (LocationTypeConverter, MapSpanTypeConverter)	dotnet/maui#33995
Map.Region bindable property	dotnet/maui#33995

Structure

All additions are within the existing map.md file, inserted into the relevant existing sections:

• New Map properties added to the properties table
• New Pin properties (ImageSource, ClusteringIdentifier) added to Pin properties
• New sections: Custom pin icons, Pin clustering, Map styling
• Extended sections: Display a specific location (XAML converters), Create a MapSpan (FromLocations), Move the map (animated), Show user location (events), Map clicks (long click, element click), Interact with a pin (ShowInfoWindow), Polygons/polylines/circles (IsVisible, ZIndex)

Closes #3208

---

Internal previews

📄 File	🔗 Preview link
docs/user-interface/controls/map.md	docs/user-interface/controls/map

[learn-build-service-prod]

Learn Build status updates of commit 188f07b:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
docs/user-interface/controls/map.md	❌Error		Details

docs/user-interface/controls/map.md

• Line 159, Column 1: [Error: moniker-range-invalid] Invalid moniker range: '>=net-maui-11.0'. Moniker 'net-maui-11.0' is not defined.
• Line 159, Column 1: [Warning: moniker-zone-empty] No intersection between zone and file level monikers. The result of zone level range string '>=net-maui-11.0' is '', while file level monikers is 'net-maui-10.0', 'net-maui-8.0', 'net-maui-9.0'.
• Line 280, Column 1: [Warning: moniker-zone-empty] No intersection between zone and file level monikers. The result of zone level range string '>=net-maui-11.0' is '', while file level monikers is 'net-maui-10.0', 'net-maui-8.0', 'net-maui-9.0'.
• Line 308, Column 1: [Warning: moniker-zone-empty] No intersection between zone and file level monikers. The result of zone level range string '>=net-maui-11.0' is '', while file level monikers is 'net-maui-10.0', 'net-maui-8.0', 'net-maui-9.0'.
• Line 351, Column 1: [Warning: moniker-zone-empty] No intersection between zone and file level monikers. The result of zone level range string '>=net-maui-11.0' is '', while file level monikers is 'net-maui-10.0', 'net-maui-8.0', 'net-maui-9.0'.
• Line 463, Column 1: [Warning: moniker-zone-empty] No intersection between zone and file level monikers. The result of zone level range string '>=net-maui-11.0' is '', while file level monikers is 'net-maui-10.0', 'net-maui-8.0', 'net-maui-9.0'.
• Line 514, Column 1: [Warning: moniker-zone-empty] No intersection between zone and file level monikers. The result of zone level range string '>=net-maui-11.0' is '', while file level monikers is 'net-maui-10.0', 'net-maui-8.0', 'net-maui-9.0'.
• Line 618, Column 1: [Warning: moniker-zone-empty] No intersection between zone and file level monikers. The result of zone level range string '>=net-maui-11.0' is '', while file level monikers is 'net-maui-10.0', 'net-maui-8.0', 'net-maui-9.0'.
• Line 791, Column 1: [Warning: moniker-zone-empty] No intersection between zone and file level monikers. The result of zone level range string '>=net-maui-11.0' is '', while file level monikers is 'net-maui-10.0', 'net-maui-8.0', 'net-maui-9.0'.
• Line 820, Column 1: [Warning: moniker-zone-empty] No intersection between zone and file level monikers. The result of zone level range string '>=net-maui-11.0' is '', while file level monikers is 'net-maui-10.0', 'net-maui-8.0', 'net-maui-9.0'.
• Line 1000, Column 1: [Warning: moniker-zone-empty] No intersection between zone and file level monikers. The result of zone level range string '>=net-maui-11.0' is '', while file level monikers is 'net-maui-10.0', 'net-maui-8.0', 'net-maui-9.0'.
• Line 1228, Column 1: [Warning: moniker-zone-empty] No intersection between zone and file level monikers. The result of zone level range string '>=net-maui-11.0' is '', while file level monikers is 'net-maui-10.0', 'net-maui-8.0', 'net-maui-9.0'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit 3cc80f4:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/user-interface/controls/map.md	✅Succeeded	View (>=net-maui-8.0)

For more details, please refer to the build report.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit 5c7f63e:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/user-interface/controls/map.md	✅Succeeded	View (>=net-maui-8.0)

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit 117cfab:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/user-interface/controls/map.md	✅Succeeded	View (>=net-maui-8.0)

For more details, please refer to the build report.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.