Closed mojodna closed 6 years ago
Thanks, @mojodna! Greg's going to look this over. I assume the changes you made here need to be merged in (of course) and then somehow applied to the production database, right?
Yup!
make db/migrate
(pointed to the production database) will apply all of the database changes.
This updates the version of CPAD to 2017a and applies changes based on CPAD_ChangeLog-CPAD_2015a_SuperUnits-CPAD_2017a_SuperUnits.xls.
Re-associating
flickr_photos
andinstagram_photos
will take a long time (~hours). Photos without associated superunits in the new CPAD will havesuperunit_id
values of-1
. Many of these result from CPAD now excluding road right-of-ways (GitHub isn't allowing me to upload screenshots right now). This could be mitigated by buffering CPAD geometries by ~250m at the expense of additional migration time, but I (currently) think it makes the most sense to post-process them after based on @danrademacher and @gregallensworth's thoughts.Refs #656