Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Feature Request: Support updating location geometry (latitude/longitude) in UpdateLocationRequest

Abierto
  • ¿Algo no está bien?
#183 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@devsjc ya está trabajando en esto.

Desde el 9/7/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Verification
  • I have searched the existing issues to ensure this feature has not already been requested.
Provide a detailed description of the proposed feature.

In the quartz-api service, the PUT /sites/{site_uuid} endpoint allows users to update a site's properties, including its latitude and longitude coordinates.

However, the Data Platform (DP) gRPC service currently does not support updating coordinates for an existing location. The UpdateLocationRequest message only exposes fields to update capacity, name, and metadata, but has no geometry/WKT fields:

protobuf
// Current UpdateLocationRequest Schema
message UpdateLocationRequest {
    string location_uuid = 1;
    EnergySource energy_source = 2;
    string new_location_name = 3;
    int64 new_effective_capacity_watts = 4;
    google.protobuf.Struct new_metadata = 5;
    google.protobuf.Timestamp valid_from_utc = 6;
}

Because of this limitation:

quartz-api must ignore any coordinate updates passed during PUT requests for existing sites.
Coordinates are immutable after location creation.
Proposed Solution
Update the Data Platform gRPC API schema to support updating location geometry.

Specifically, we propose adding a new_geometry_wkt string field (or separate new_latitude/new_longitude fields) to UpdateLocationRequest:

protobuf
message UpdateLocationRequest {
    string location_uuid = 1;
    EnergySource energy_source = 2;
    string new_location_name = 3;
    int64 new_effective_capacity_watts = 4;
    google.protobuf.Struct new_metadata = 5;
    google.protobuf.Timestamp valid_from_utc = 6;
    string new_geometry_wkt = 7; // <--- ADD THIS FIELD
}

This will allow the downstream database engines to execute geometry updates (e.g., UPDATE locations SET geometry = ST_GeomFromText(new_geometry_wkt) WHERE ...) and align the API client behavior.

What is the motivation for the feature?

Correcting Seeding Errors: Clients should be able to update the locations lat lon

Outline a potential approach or solution (optional).
Lenguaje dominante
Go
Estrellas
3
Forks
1
Merge medio
1 h 42 min
PR fusionados (30 d)
11

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de openclimatefix/data-platform

Todos los issues de openclimatefix/data-platform

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.