# Type Change to GeoIP2 Metro Code Field

_April 1, 2014_

> **⚠️ Warning**
>
> This release note is more than two years old and may no longer reflect
> current behavior. View the
> [latest release notes](/geoip/release-notes/).

In previous GeoIP2 databases, the `metro_code` was incorrectly represented as a
string. This has been corrected and now `metro_code` is internally represented
as an `uint16`. This should not affect users of the official Java, .NET, Perl,
or PHP GeoIP2 APIs. The Python API will now return an integer rather than a
string for `metro_code`. Users of libmaxminddb or third-party APIs may be
affected.