skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

migrating-system-spatial

Migrate spatial data types from System.Spatial to Microsoft.Spatial for OData v4.

19|2|Updated May 13, 2026
Search Tags:#API compatibility#spatial data migration#Microsoft.Spatial#OData v4#namespace replacement
One-click install
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-system-spatial
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrating-system-spatial
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/libraries/migrating-system-spatial
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-system-spatial

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the migration of spatial data types from the obsolete System.Spatial library to the updated Microsoft.Spatial library for OData v4, streamlining the upgrade process and ensuring compatibility.

Core Features & Use Cases

  • Namespace Replacement: Automatically updates all using directives from System.Spatial to Microsoft.Spatial.
  • API Compatibility: Ensures spatial type APIs (GeographyPoint, GeometryPoint, etc.) remain largely compatible.
  • Workflow Automation: Provides a step-by-step workflow for a successful migration, including detecting usage, updating project files, and verifying results.

Quick Start

Migrate your spatial data types from System.Spatial to Microsoft.Spatial by running the provided script.

Frequently Asked Questions about migrating-system-spatial

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from System.Spatial to Microsoft.Spatial for OData v4?▼

To migrate from System.Spatial to Microsoft.Spatial, run the provided script to automatically detect usage, update project references, and verify migration results for OData v4 compatibility.

Is Microsoft.Spatial API compatible with System.Spatial spatial types?▼

Yes, Microsoft.Spatial ensures API compatibility for spatial types, meaning spatial type APIs like GeographyPoint and GeometryPoint remain largely compatible after replacing the System.Spatial namespace.

How do I automatically update System.Spatial using directives in my project?▼

You can automatically update System.Spatial using directives by running the migration script, which handles namespace replacement to Microsoft.Spatial across your project files.

When do I need to migrate spatial data types to Microsoft.Spatial?▼

You need to migrate spatial data types to Microsoft.Spatial when upgrading from the obsolete System.Spatial library to ensure compatibility and streamline spatial data processing in OData v4.

What is the workflow for replacing the System.Spatial namespace in OData v4 projects?▼

The workflow for namespace replacement involves detecting System.Spatial usage, updating project references to Microsoft.Spatial, and verifying the migration results to ensure OData v4 compatibility.

Related Skills

Explore More Software Engineering Skills→
microsoftmicrosoft
19

migrating-cryptography-namespaces

Migrate System.Security.Cryptography namespace usage from .NET Framework to modern .NET.

Official
Intermediate
microsoftmicrosoft
19

migrating-data-odata-to-odata-core

Automate .NET project migration from Microsoft.Data.OData to Microsoft.OData.Core.

Official
Advanced
microsoftmicrosoft
19

migrating-data-edm-to-odata

Migrate OData v1–v3 EDM types to OData v4 in .NET projects.

Official
Intermediate
OpenAEC-FoundationOpenAEC-Foundation
30

blender-agents-version-migrator

Migrate Blender Python code across major version updates with API mappings.

Official
Advanced