Output valid TileJSON for PostgreSQL Function Sources

[ohrie]

Output valid TileJSON for PostgreSQL Function Sources

[sharkAndshark]

Hi @ohrie
I tried this on the test database and it still works. Would you mind share you SQL here?

COMMENT ON FUNCTION "public"."function_zxy_query" ( "z" int4, "x" int4, "y" int4, "query" json ) IS '
{
	"description": null,
	"fields":{
		"Gid":"int4",
		"TABLE":"text"
	},
	"foo": {"bar": "foo"}
}
';

async@LAPTOP-PLI51BMO:~/repos/martin$ curl http://localhost:3000/function_zxy_query
{"tilejson":"3.0.0","tiles":["http://localhost:3000/function_zxy_query/{z}/{x}/{y}"],"name":"function_zxy_query","fields":{"Gid":"int4","TABLE":"text"},"foo":{"bar":"foo"}}

[nyurik]

@ohrie you are correct that, per specification, tilejson must include vector_layers value that has a fields sub-value. The example in the documentation actually does that. There is one issue: in the Modifying TileJSON section it says that it generates tilejson automatically, but does not say that it is not a fully valid tilejson unless the content of the tile is non-vector (but at the moment there is no way for the user to specify that).

We cannot really fix this automatically because Martin has no idea which tiles are available. Only after the first tiles have been requested, we could, in theory, wait until the first tiles start being generated, parse them, figure out available fields, and update vector_layers, but this feels like a very hacky, imperfect, and unstable solution (tiles may not include all possible fields).