Following an upgrade from Arc 9 to 10, I noticed a change that I didn't see documented and wanted to confirm.
Previously in version 9, Features such as Polyline, could not cross the international date line. It required special handling code to detect when the dateline was crossed and to cut up the feature so as not to draw a line around the entire earth, when only 2 degrees were warranted. In 10, handling code failed to work. After removing it all together the code that would have had problems in 9 due to the dateline worked perfectly without any issues.
Is crossing the international date line something that was added in or is there another issue I'm seeing here? Is the change documented in detail anywhere?
Previously in version 9, Features such as Polyline, could not cross the international date line. It required special handling code to detect when the dateline was crossed and to cut up the feature so as not to draw a line around the entire earth, when only 2 degrees were warranted. In 10, handling code failed to work. After removing it all together the code that would have had problems in 9 due to the dateline worked perfectly without any issues.
Is crossing the international date line something that was added in or is there another issue I'm seeing here? Is the change documented in detail anywhere?
I have just been using South Polar Stereographic where I can ignore any dateline issues, draw polygons across the dateline and have no issues. That is because the coordinates are in projected metres.
I do notice that users near the equator often draw maps in geographic units because there is small distortion, but in the higher latitudes the distortion between latitude and longitude units is unacceptable. To me it is either a lack of understanding of the difference between spherical coordinates and projected units, or it is just being lazy. Some viewers have implied projections for display, such as Google Earth.