The current implementation of the maybeEnum method throws when the needle value is unexpected, but it should return null instead. This particular plugin is "vulnerable" to this because the GIS API is somewhat in flux, and we've had other enums fail before.

This could be rewritten to be more similar to the google_adsense version, so it withstands (and maybe logs) unknown enum values.