As of 67f0675, fields like Washington and Grambling State have slightly incorrect widths. Washington's is too wide (it should not extend over the sidelines); Grambling State's is too narrow.
Common elements with these two fields:
- The 100-yard field is located at one extreme of the full-length field
- The field is long
- The field is not generally north-south aligned
San Diego State's field (not north-south, but not long either) isn't affected.
Purdue's field is the next candidate that meets the above, but doesn't appear to be affected severely enough (although the field markings aren't great in the default terrain/buildings view, so it's hard to tell for sure).
It's likely the width correction code isn't perfectly right:
|
fn adjust_width(self, at: Coordinate, width: Length) -> LatLonBox { |
|
let lon = (self.east + self.west) / 2.0; |
|
let angle = Point::from(at) |
|
.haversine_destination(90.0, width.get::<meter>() / 2.0) |
|
.x() |
|
- at.x; |
|
LatLonBox { |
|
east: lon + angle, |
|
west: lon - angle, |
|
..self |
|
} |
|
} |
... but I don't yet have a correlation between enough problematic fields to figure out how to fix this problem yet, and I don't know enough about the myriad of map projections in use in Google Earth, let alone enough about map projections at all, to figure this one out "correctly".
As of 67f0675, fields like Washington and Grambling State have slightly incorrect widths. Washington's is too wide (it should not extend over the sidelines); Grambling State's is too narrow.
Common elements with these two fields:
San Diego State's field (not north-south, but not long either) isn't affected.
Purdue's field is the next candidate that meets the above, but doesn't appear to be affected severely enough (although the field markings aren't great in the default terrain/buildings view, so it's hard to tell for sure).
It's likely the width correction code isn't perfectly right:
20020-map/src/main.rs
Lines 173 to 184 in 67f0675
... but I don't yet have a correlation between enough problematic fields to figure out how to fix this problem yet, and I don't know enough about the myriad of map projections in use in Google Earth, let alone enough about map projections at all, to figure this one out "correctly".