Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#183 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@devsjc ci sta già lavorando.

Dal 9/7/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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).
Lingua principale
Go
Stelle
3
Fork
1
Merge medio
1h 42m
PR unite (30g)
11

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openclimatefix/data-platform

Tutte le issue di openclimatefix/data-platform

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.