I'm getting invalid LAT ranges when using ANY data in Arc SDE, Geography Data Type. Perhaps this is ignorance? To reproduce:
Either this is a new "feature" of 10.2.2 or I celebrated Columbus Day way to hard and I'm missing something obnoxiously obvious.
Just recovering from Canadian Thanksgiving...so my answer may be off...Is there the slightest chance that longitude and latitude are somehow being switched?
Using many, numerous SQL checks and validation tools, there are no issues in the data having LAT outside of -90/90 degrees>
SELECT a.OBJECTID, b.n,
a.SHAPE.STPointN(b.n).Lat AS Lattitude,
a.SHAPE.STPointN(b.n).Long AS Longitude
FROM dbo.STATES AS a, num_seq AS b
WHERE b.n <= a.SHAPE.STNumPoints()
ORDER BY a.SHAPE.STPointN(b.n).Lat, b.n;
Shows all LAT falling well inside -90/90 .
In addition, SSMS and Arc Catalog seem to handle this data nicely. I can use the data in numerous SQL expressions and no errors occur. Only when displayed in Arc Map does the error occur, which leads me to suspect that this is an issue with the Arc Map translation of the SQL Geography Type?
Based on another post you answered, that was the first thing I checked, and is not the case. Recalculating the extent, or defining a custom extent, does not remove the error.