Skip to content

More granularity / additional levels? #2

@m-mohr

Description

@m-mohr

Originally posted by @m-mohr in fiboa/cli#130 (comment)

Seeing this fields more often, I'm wondering whether we should add it to the admin extension.

We'll likely have no common list of values as for the other fields, but probably is also good to just have a common name. We can just say that we keep the actual values undefined and it's up to the user to find the best practices for relevant countries themselves?

@ivorbosloper

After level 1 everything becomes a bit more fuzzy. Some countries have many layers, and there are many orthogonal subdivisions. I have seen "Waterboard / water region", or "Statistical reporting area level 1 and 2". Ideally, the "admin:"-prefix annotates an attribute as some subdivision... But that's probably not supported or usefull for an extension.

@m-mohr

Yeah, but in the other hand you already assign a common field name to them which is unfindabale in docs/extensions yet. But we can discuss this elswhere.

@ivorbosloper

Or, in the administrative_division extension, we could suggest/standardize the concept of using the admin-prefix (e.g. admin_xxx) in column names for things we might later add to the extension. For readability, I can imagine using a general admin_level2 or a specific admin_county column. What do you think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions