longitude / latitude in geocoded_data object in webrequest is quite imprecise (as it comes from the IP) so it is a field that at this time is just eating space and not very useful. CC-ing Product-Analytics to get feedback but we are thinking of removing it entirely

ping @kzimmerman

cc @razzi

Pinging @JAllemandou in case he can think of any reason why we should leave these fields, giving precision.

I quickly reviewed refinery and refine-to-druid jobs and found that none uses either postqal-code not lat/long. I think we're safe to remove them :)

Moving to kanban and @razzi to work on this.

Change 635085 had a related patch set uploaded (by Razzi; owner: Razzi):
[analytics/refinery/source@master] Remove postal code, latitude, and longitude from geodata

https://gerrit.wikimedia.org/r/635085

@Nuria Product Analytics hasn't used this data (except for once, maybe, a few years ago), and we think it's reasonable to remove it.

Change 635085 merged by Razzi:
[analytics/refinery/source@master] Remove postal code, latitude, and longitude from geodata

https://gerrit.wikimedia.org/r/635085

Change 635352 had a related patch set uploaded (by Razzi; owner: Razzi):
[analytics/refinery@master] oozie: update webrequest/load hive jar version

https://gerrit.wikimedia.org/r/635352

Change 635352 merged by Mforns:
[analytics/refinery@master] oozie: update webrequest/load hive jar version

https://gerrit.wikimedia.org/r/635352

Moving this to done since everything seems already deployed.