There is some inconistency in the representation of GeoSpatial data in the referenced data sources.
NAD83 / Conus Albers vs WGS84 (standard Geograpgic Lat/Lon) being at the heart.
Conus albers is useful as it compensates at least somewhat for the lack of uniformity in the semi spherical/elliptical shape of the earth and can be used for distance calculations.
WGS84 has some rather ridiculously innacturate estimation formulas, BUT it is what people are used to looking at.
A modification must be made and code added to convert back and forth between the two and data needs to be converted at storage time to NAD83/Conus Albers, using that as the backend standard to allow calculations to occur quickly and accurately to the specified levels while keeping storage format consistent.
There is some inconistency in the representation of GeoSpatial data in the referenced data sources.
NAD83 / Conus Albers vs WGS84 (standard Geograpgic Lat/Lon) being at the heart.
Conus albers is useful as it compensates at least somewhat for the lack of uniformity in the semi spherical/elliptical shape of the earth and can be used for distance calculations.
WGS84 has some rather ridiculously innacturate estimation formulas, BUT it is what people are used to looking at.
A modification must be made and code added to convert back and forth between the two and data needs to be converted at storage time to NAD83/Conus Albers, using that as the backend standard to allow calculations to occur quickly and accurately to the specified levels while keeping storage format consistent.