For the Container entity: a Facility may not move but a Container typically will. Whatever is done, the geoPointId should not be on the Container itself. I would recommend just not worrying about it at this point because Containers aren't used much in OFBiz yet. Also, when a Container is in a Facility you can look up the geoPointId of the Facility. Otherwise, you would need a ContainerGeoPoint entity to keep track of a series of points over time like the others.
On a side note, wasn't a big point of all of this to have a lat/long on a postal address? I don't see anything like that in this data model patch, so I'm not sure what you're thinking along those lines. I'd recommend adding a geoPointId to the PostalAddress entity (and not the ContactMech entity as this does not apply to all ContactMechs).