GID is incorrect on locality fields replaced by Geonames values

[orangejulius]

After #93, we now have much more consistent hierarchy data for Geonames records, but the GIDs are sometimes not correct. As can be seen in the query below, the ID section of the GID is correctly replaced with the Geonames ID, but the source section stays whosonfirst:

http://pelias.github.io/compare/#/v1/search%3Fsources=wof&text=mexico%20city

The left column is production, without #93, the right is prod_build with #93. Note that the locality_gid field on the right is whosonfirst:locality:3530597: the id section has been updated to 3530597 to match the id of the record, but the source is still whosonfirst.

Update: this may be a bug in pelias/model and pelias/api: see this snippet of code from api

function makeNewId(placeType, id) {
  var doc = new Document('whosonfirst', placeType, id);
  return doc.getGid();
}

[orangejulius]

Fixed in pelias/api#843!