migrating-system-spatial

Name: migrating-system-spatial
Availability: InStock
Author: Microsoft

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

Ready to run

npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-system-spatial

💬 Prompt for ChatGPT / Claude Chat▼

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.