So, if I understand correctly, this fixes a problem with the input longitude being outside the range ±π radians? I think it’d be reasonable to fix that by replacing the use of d3_geo_equirectangular with a new d3_geo_rotationIdentity that just does the wraparound check on longitude. (Also, I guess we’re not concerned with wraparound on φ?)