Using "id" instead of "osm_id" ?

[nyurik]

Would it make sense to use the "id" field of the vector tile, instead of "osm_id"? The "id" SHOULD be unique per layer, which I think is generally the case.

[MaxSem]

OSM ID is not guaranteed to be unique, you can totally have more than one geometry with the same osm_id in the same tile. Also, even now Meddo supports sources other than OSM. My question is does it make sense to have osm_id, ne_id, etc separately?

[nyurik]

Wouldn't that geometry be merged into one for a tile? In any case, osm_id is a bit confusing - is it a polygon, a line, a relation id? In a general case - I think we might as well keep osm_id for now, while the data layer is being actively worked on.

[pnorman]

In any case, osm_id is a bit confusing - is it a polygon, a line, a relation id?

Node IDs are passed through node_id which offsets them by 1000000000, but this isn't documented. Relations and way IDs are handled in the usual manner of relation IDs being negative. Polygon IDs don't exist since these are OSM ids, and polygons aren't part of the OSM data model.