• Sns.Admin
  • /docs/spatial/providers
  • Docs
    • Overview
      • Approach
      • Vision
    • Concepts
      • Communities
      • Places
      • Structures
      • Spaces
      • Assets
    • Platform
      • Architecture
      • Sns.Framework
      • Sns.Spatial
      • Data Model
    • UX Patterns
      • Entity Icons
      • Editors
      • Layouts
      • Navigation
    • Workflows
      • Place Onboarding
      • Asset Uploads
      • Requests
      • Projects
    • Spatial
      • Maps
      • Providers
      • Geo DTOs
      • Digital Twins
    • Data
      • Places
      • Assets
      • NavItems
      • Scoring
    • AI / Automation
      • AI Assistants
      • Completeness
      • Confidence
      • Monitoring
    • Developer Guide
      • Getting Started
      • Repo Map
      • State Patterns
      • Coding Standards

New Page

docs/spatial/providers

Providers

Spatial providers are external map or visualization systems such as Google Maps. SnS keeps provider concerns isolated so the rest of the platform can work with stable spatial concepts.

Provider Folder Pattern

Provider-specific DTOs belong under provider DTO folders, and provider JavaScript interop belongs under provider interop folders. This keeps translation code close to the provider while protecting domain workflows from provider-specific details.

  • Providers/<Provider>/Dto for provider DTOs.
  • Providers/<Provider>/Interop for .NET interop wrappers.
  • wwwroot/js/<provider> for provider JavaScript modules.

Current Direction

Google is the most developed provider today. Other provider areas should be treated as extension points until implementation details are present and documented.

More info goes here.
  • Home
  • Finder
  • This Place
  • Explore
  • Database
  • Solutions
  • Ready
  • : 1
  • Enterprise: 13
  • Application: 1046
  • NavItem:
  • Theme: 1