Hey @whatisgalen, could you provide a little more detail on what needs to be done for this ticket?

@chiatt sorry for the delay on this. It's surfaced as a blocker to #10816

When an MVT request gets sent, the features in the response are defined thus out of the geojson_geometries table:

"""SELECT ST_AsMVT(tile, %s, 4096, 'geom', 'id') FROM (SELECT tileid,
                            id,
                            resourceinstanceid,
                            nodeid,
                            ST_AsMVTGeom(
                                geom,
                                TileBBox(%s, %s, %s, 3857)
                            ) AS geom,
                            1 AS total
                        FROM geojson_geometries
                        WHERE nodeid = %s and resourceinstanceid not in %s) AS tile;""",
                        [nodeid, zoom, x, y, nodeid, resource_ids],

The issue is that when you click on a popup, an int feature.id from geojson_geometries gets compared against a uuid tile-based feature.id. The part of the code where the resource_descriptors bring in that tile data is here. So the feature.id property is a uuid that looks nothing like the id property coming from geojson_geometries and in #10827 if I try to compare a clicked feature against the feature properties available via resource_descriptors, I'll never have a match on feature.id despite comparing features with identical geometries.

Essentially we're maintaining two parallel ids for the same feature: an int feature id in geojson_geometries and a uuid feature id in tile.data...geometries...{feature}. I think we should either conform them to a single common featureid, or else maintain a link in geojson_geometries to the featureid used when saving geojson tile data here.