We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It would be nice to specify what field to use as an object's key in a UTFGrid's data object.
data
For example, if we had the following GeoJSON object:
{ "type": "feature", "geometry": { ... }, "properties": { "name": "City Hall", "building_id": 15, ... } }
And we specified that building_id should be used, we'd get the following UTFGrid:
building_id
{ "grid": [" !", " "], "keys": ["", "15"], "data": { "15": {"name": "City Hall", "building_id": 15, ... } } }
Or if we specified name:
name
{ "grid": [" !", " "], "keys": ["", "City Hall"], "data": { "City Hall": {"name": "City Hall", "building_id": 15, ... } } }
This is probably not a huge deal, but I can imagine cases where it might be useful. Not top priority for sure, though.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It would be nice to specify what field to use as an object's key in a UTFGrid's
data
object.For example, if we had the following GeoJSON object:
And we specified that
building_id
should be used, we'd get the following UTFGrid:Or if we specified
name
:This is probably not a huge deal, but I can imagine cases where it might be useful. Not top priority for sure, though.
The text was updated successfully, but these errors were encountered: