Enterprise Integration

Real geometry.
Through the systems you already use.

Carry locations, areas and routes through your front-, middle- and back-office systems as compact Spatial Reference Locators (SRLs). Give records, documents and workflows a shared spatial reference that carries its geometry.

For storage and transport, systems can handle an SRL like a location ID in a text field. No fundamental architectural changes or native geometry support are needed to store and pass it on. Integrate decoding, visualization and spatial processing where those capabilities are needed.

One reference across systems

Encode the geometry.
Carry the reference through.

1. Source geometryExisting coordinates, supported shapes or user selection
2. EncodeCreate a full SRL with the appropriate type and precision
3. Carry the SRL stringBusiness records, CRM, ERP, APIs and documents
4. Decode where neededRecover the represented geometry for maps and spatial processing

An SRL can travel with a record or document across internal systems, partner portals and field applications. Each system forwards the same SRL string alongside the relevant business identifiers. Applications decode it where the geometry is needed for display or spatial processing.

Each business object keeps its own identity. An SRL identifies represented geometry; it does not replace business identifiers or access permissions. Field lengths, validation and interfaces must preserve the complete string.

Connect at the right points

Your existing data.
Your users’ spatial selections.

The current API and embed are pre-release integrations. Access is provisioned individually with a paid entitlement. Scope, expected workload, usage limits and support are agreed for the integration.

Encoding a reference does not perform spatial analysis. Receiving applications supply their processing or integrate an appropriate service. Planned platform services and deployment options are discussed separately from currently available functionality.

Start with your data

Validate the fit.
Then scale the integration.

1. Choose a representative sample

   Identify source formats, coordinate references, geometry types and the precision your workflow needs. Include difficult cases as well as typical records.

2. Measure the result

   Compare supported SRL representations with the source geometry. Measure reconstruction differences, serialized payload sizes and the changes needed in the receiving systems.

3. Plan the initial conversion and ongoing flow

   Agree on the volume, validation, throughput and handling of unsupported records for the initial conversion. Define how new and changed geometry will be encoded during ongoing operation.

SRLs use supported parameterized geometry families with defined precision and size limits. Suitability for complex source polygons must be evaluated; compact references do not imply lossless encoding of arbitrary geometry. Initial large-volume conversion is scoped individually, rather than offered here as an existing self-service batch service.

Your integration

Bring a real workflow.
Define a measurable evaluation.

Discuss a technical evaluation using a representative dataset and a clearly bounded path through your systems. Agree on success criteria for geometry fidelity, payload size, integration effort and operating volume before expanding the scope.

Tell us which systems exchange the data, which geometry they need to carry, your initial data volume and expected ongoing workload. We can then discuss evaluation scope, commercial terms and the requirements for production use.

Use the contact form to describe the workflow and data requirements. Arrange a suitable transfer method before sharing confidential customer data.