Add custom field types for standardized location identifiers

[jeremystretch]

NetBox version

v3.4.7

Feature type

New functionality

Proposed functionality

Add three new types of custom field:

• ISO 3166 country code
• UN-LOCODE
• IATA airport codes

Custom fields of either type would render as selection fields listing only valid values as selectable options. These would be maintained within NetBox core, with no additional setup needed on the part of the administrator.

Use case

These are well-known values with a wide range of useful applications concerning the assignment of location data. For example, it is common practice to designate the LOCODE for each site on a network.

Database changes

N/A

External dependencies

There are a few ways we might source this data, such as the locode Python package. Further evaluation of the available options is needed.

[BarbarossaTM]

This would be awesome, especially UN-LOCODE!

Do you have some idea in mind how to model this? Like for example would there be two levels for country and city?

[jeremystretch]

My initial thought here was to introduce new custom field types to hold the types of data mentioned above, but in retrospect that seems like a poor approach that won't scale well. Instead, I've just opened #12988 which proposes moving stored custom field choices into a separate model, which will allow for the efficient reuse of choice sets across multiple custom fields.

Marking this as blocked pending the acceptance of that proposal.

[gdprdatasubect]

Would it be possible to include NUTS1-3 for regions too?