# US 2026/0311429 A1 · Map visualization translation tool

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0311429 A1
- Document ID: US20260311429A1
- Status: Published application
- Kind: A1
- Application number: 19/196,059
- Filed: 2025-05-01
- Published: 2026-10-08
- Earliest claimed: 2025-04-07
- Assignees: Palantir Technologies Inc.
- Applicants: Palantir Technologies Inc.
- Inventors: Rebecca Moore; Michael Tuer; Westin Miller; Leah Anderson; Gabe Boning; Madeleine Becker; Jason Xu
- Web page: https://patentgrep.com/patent/US20260311429A1

## CPC

- G06T 17/05: Geographic models
- G06F 16/29: Geographical information databases
- G06T: IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system or computerized method may receive a request from a front-end application for visualizing a plurality of data objects on a geospatial map, each of the data objects associated with a corresponding data object type. A system or method may access an ontology that includes associations between data object types and rendering specifications, the rendering specifications being in a standard format for a plurality of front-end applications. A system or method may be based on the rendering specifications associated with the plurality of data objects, generating a plurality of renderables corresponding to each of the plurality of front-end applications. A system or method may provide corresponding renderables to the requesting front-end application that are usable to visualize the plurality of data objects on the geospatial map.

## Claims

### Claim 1

A computerized method, performed by a computing system having one or more hardware computer processors and one or more non-transitory computer readable storage device storing software instructions executable by the computing system to perform the computerized method comprising:
receiving a request from a front-end application for visualizing a plurality of data objects on a geospatial map, each of the data objects associated with a corresponding data object type;
accessing an ontology that includes associations between data object types and rendering specifications, the rendering specifications being in a standard format for a plurality of front-end applications;
based on the rendering specifications associated with the plurality of data objects, generating a plurality of renderables corresponding to each of the plurality of front-end applications; and
providing corresponding renderables to the requesting front-end application that are usable to visualize the plurality of data objects on the geospatial map.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving a request from a second front-end application for visualizing the plurality of data objects on a second geospatial map, the second front-end application being one of the plurality of front-end applications; and
providing the corresponding renderables to the requesting second front-end application that are usable to visualize the plurality of data objects on the second geospatial map.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
receiving a second request from the front-end application for visualizing the plurality of data objects on the geospatial map, the second request associated with a different rendering behavior than the first request;
updating the ontology that includes associations between data object types and rendering specifications by updating the rendering specification to be associated with the different rendering behavior;
based on the updated rendering specifications associated with the plurality of data objects, generating an updated plurality of renderables corresponding to the front-end applications; and
providing the corresponding updated renderables to the requesting front-end application that are usable to visualize the plurality of data objects on the geospatial map.

### Claim 4 (depends on 3)

The method of claim 3, wherein the different rendering behavior is not in the standard format for the plurality of front-end applications.

### Claim 5 (depends on 4)

The method of claim 4, further comprising receiving data from at least one of the plurality of front-end applications that the updated rendering specification is incompatible with the at least one of the plurality of front-end applications.

### Claim 6 (depends on 1)

The method of claim 1, wherein the rendering specification is configured to be customized by the front-end application or by adjustment of program code associated with the rendering specification.

### Claim 7 (depends on 6)

The method of claim 6, wherein the first rendering specifications of a first subset of the data object type can be customized to be different from a second rendering specifications of a second subset of the data object types.

### Claim 8 (depends on 7)

The method of claim 7, wherein the first subset and the second subset of the data object types are different based on properties of the data object types.

### Claim 9 (depends on 7)

The method of claim 7, further comprising visualizing the plurality of data objects on the geospatial map according to the first rendering specification of the first subset of the data object types concurrently with the second rendering specification of the second subset of the data object types.

### Claim 10 (depends on 6)

The method of claim 6, wherein at least one of the original rendering specification and the customized rendering specification can be saved to be accessed for later use.

### Claim 11 (depends on 6)

The method of claim 6, wherein the rendering specification is configured to be customized by filtering a sub-set of the data object types based on properties associated with the data object types, and the rendering specification customized only on the sub-set.

### Claim 12 (depends on 11)

The method of claim 11, wherein the filtering comprises conditional styling, wherein the conditional styling comprises program code setting conditions associated with the properties of the data object types to filter the sub-set of the data object types.

### Claim 13 (depends on 6)

The method of claim 6, further comprising:
generating customized renderables corresponding to the front-end application based on the customized rendering specification associated with the plurality of data objects; and
displaying, on an interactive user interface, a visualization of the plurality of data objects on the geospatial map using both the corresponding renderables and the corresponding customized renderables on the front-end application.

### Claim 14 (depends on 1)

The method of claim 1, wherein the front-end application is configured to display three-dimensional (3-D) geospatial maps, and the corresponding renderables are usable to visualize the plurality of data objects as 3-D renderings based on the rendering specification.

### Claim 15 (depends on 1)

The method of claim 1, wherein the front-end application is configured to display high scale renderings, and the corresponding renderables are embedded with map vector tiles usable to visualize the plurality of data objects based on the rendering specification.

### Claim 16 (depends on 15)

The method of claim 15, wherein the plurality of data object comprises at least one million data objects.

### Claim 17 (depends on 1)

The method of claim 1, wherein generating the plurality of renderables corresponding to each of the plurality of front-end applications comprises executing rendering functions for each of the plurality of front-end applications based on the rendering specification, wherein the rendering specifications is associated with rendering functions corresponding to the plurality of data objects.

### Claim 18 (depends on 17)

The method of claim 17, further comprising receiving user input associated with one or more rendering functions that correspond with at least one of the plurality of front-end applications, the one or more rendering functions executable with the rendering specification to generate corresponding renderables with the at least one of the plurality of front-end applications.

### Claim 19 (depends on 1)

The method of claim 1, wherein the plurality of renderables are associated with application programming interfaces (APIs) configured generate a rendering behavior based on the association between the data object type and the rendering specification.

### Claim 20 (depends on 1)

The method of claim 1, further comprising:
receiving user input indicating one or more capabilities of a new front-end application for visualizing the plurality of data objects on a geospatial map; and
receiving user input indicating at least one of features or functionalities of the new front-end applications usable to generate corresponding renderables based on the rendering specification.
