Add TMS (Tile Map Service) support

[ronitjadhav]

Overview

This PR adds support for TMS (Tile Map Service) to the ogc-client library, extending its capabilities beyond WMS, WMTS, WFS, and OGC-API to now include TMS-compliant services according to the Tile Map Service Specification.

Features Added

TMS Endpoint

Implemented TmsEndpoint class with the following methods:

• getEndpointInfo(): Retrieves basic information about the TMS endpoint, including title, abstract, and keywords
• getAllTileMaps(): Fetches available tile maps from the TMS service, filtering to a specific tile map if the endpoint points to one
• getTileMapInfo(href): Retrieves detailed information about a specific tile map by URL

The class handles proper caching of service data through internal methods:

• Private getServiceData(): Fetches and caches TMS service data
• Private getFilteredData(): Applies filtering based on the endpoint URL

Utility Functions

• normalizeUrl(url): Ensures consistent URL formatting with lowercase hostname and trailing slash
• getParentPath(url): Extracts parent path from versioned TMS URLs
• fetchXml(url): Fetches XML content with robust error handling for:
  • Network failures
  • Non-XML responses
  • XML with or without declaration

Implementation Details

The implementation closely follows the TMS specification while maintaining consistency with the API design pattern used throughout ogc-client. This ensures a familiar interface for developers already using the library for other OGC services.

Current Limitations

• Root resource handling as described in the TMS specification is not yet implemented and will be addressed in a future update

Testing

Comprehensive unit tests cover:

• URL normalization with various edge cases
• XML fetching with different response types
• Error handling for network issues and invalid content
• TmsEndpoint class functionality for retrieving endpoint information and tile maps

Usage Example

import { TmsEndpoint } from '@camptocamp/ogc-client';

// Create a TMS endpoint
const endpoint = new TmsEndpoint('https://ahocevar.com/geoserver/gwc/service/tms/1.0.0/');

// Get endpoint information
const info = await endpoint.tileMapServiceInfo;
console.log(info.title, info.abstract);

// Get all available tile maps
const tileMaps = await endpoint.allTileMaps;

// Get detailed information for a specific tile map
const tileMapDetails = await endpoint.getTileMapInfo(tileMaps[0].href);

[ronitjadhav]

@jahow

I made updates as we had discussed. Here's a summary of the changes:

• profile and tileSets are now direct properties for TileMapInfo Structure
• Converted async methods to getters
• Enhanced component reuse in Vue app
• Moved getParentPath to shared module and reused it for TMS
• Improved XML parsing for different server implementations

[jahow]

Thank you, good job! that looks good, I just have a question regarding the bounding box. Please merge when you feel it's ready :)

[jahow]

Is that something that application code would be expected to do? IT sounds like the Bbox should always be an array