geotoolbox

Convert MKMapItem to PlaceDescriptor and geocode addresses with MapKit.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/mazicimert/RunDom --skill geotoolbox-mazicimert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: geotoolbox
Source: https://github.com/mazicimert/RunDom/tree/main/.claude/skills/mapkit/geotoolbox
Command: npx skills add https://github.com/mazicimert/RunDom --skill geotoolbox-mazicimert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GeoToolbox PlaceDescriptor patterns streamline portable location data across apps by unifying coordinate, address, and service identifiers, with MapKit for geocoding.

Core Features & Use Cases

  • Represent a place with coordinates, addresses, or common names via PlaceDescriptor.
  • Perform forward geocoding (address to coordinates) and reverse geocoding (coordinates to an address) using MKGeocodingRequest and MKReverseGeocodingRequest.
  • Convert MKMapItem to PlaceDescriptor and attach multi-service identifiers for cross-service interop.
  • Read and inspect PlaceDescriptor properties such as coordinate, address, commonName, and service identifiers.

Quick Start

Create a PlaceDescriptor from an MKMapItem and read back its coordinate, address, and common name.

Frequently Asked Questions about geotoolbox

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

FAQPage Schema
How do I convert an MKMapItem to a portable location representation?

You convert an MKMapItem to a PlaceDescriptor to create a portable location representation. This unifies the coordinate, address, and common name properties into a single data structure for cross-app usage.

What is the best way to perform forward and reverse geocoding with MapKit?

Forward and reverse geocoding with MapKit is handled using MKGeocodingRequest and MKReverseGeocodingRequest. These APIs convert addresses to coordinates and coordinates back to addresses within the PlaceDescriptor structure.

How do I attach multi-service identifiers for cross-service location interop?

You attach multi-service identifiers by mapping them into the PlaceDescriptor. This manages service identifiers alongside coordinates and addresses to ensure cross-service interoperability for location data.

Can I inspect PlaceDescriptor properties like coordinates and common names?

Yes, you can read and inspect PlaceDescriptor properties. The structure exposes coordinate, address, commonName, and service identifiers, allowing you to extract specific location data from the unified representation.

Does GeoToolbox require MapKit APIs for geocoding and location data management?

Yes, GeoToolbox requires MapKit APIs for geocoding and location data management. It relies on PlaceDescriptor, MKGeocodingRequest, and MKReverseGeocodingRequest to execute its core location unification tasks.

Why unify coordinates, addresses, and service identifiers into a single PlaceDescriptor?

Unifying coordinates, addresses, and service identifiers into a PlaceDescriptor streamlines portable location data across apps. It solves the problem of fragmented location representations by providing a consistent structure for cross-service interop.