Skip to content
New issue

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

Standardized display_name/label field for shape GeoJSON features #326

Open
brlodi opened this issue Jul 28, 2017 · 0 comments
Open

Standardized display_name/label field for shape GeoJSON features #326

brlodi opened this issue Jul 28, 2017 · 0 comments

Comments

@brlodi
Copy link
Collaborator

brlodi commented Jul 28, 2017

Currently, each shape dataset returns a collection of GeoJSON Features, each with the Properties property populated by with a hash of the item's database fields. Unfortunately the names of these fields are completely non-standard and depend greatly on the dataset. This makes it essentially impossible to provide a standardized visualization of that data except by dumping the entire properties list to display.

I'm proposing adding, both in existing shape datasets (which I'm happy to assist with) and as part of the submission process, a property defining which dataset-specific column name(s) contains the principal representation of the constituent shapes. For example, a neighborhood boundary dataset might expose the properties

hash: "5840c27ec13df1793245c395de5a9526"
pri_neigh: "Sheffield & DePaul"
sec_neigh: "SHEFFIELD & DEPAUL"
shape_area: 10482592.2987
shape_len: 13227.049745

for a certain shape. To a human this clearly represents a neighborhood called "Sheffeild & DePaul", and that is probably how the human would refer to that particular Feature, but it is essentially impossible to infer without a semantic understanding of the dataset's content and the entry's property names.

My proposal would add something like display_name: "pri_neigh", either to the individual shapes or to the dataset itself, simply describing which column represents the common name of the elements. This allows the dataset's structure to be maintained while allowing some amount of standardized display.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant