Good morning,
A few years ago we had a discussion about this topic and I don't feel it was ever resolved. It has now come up again internally and I've been asked to take it on again in case something has changed between version 4.5 and 6.0 that I am unaware of.
At times we come across the need to be able to both reproject and rotate layers. But as far as I can tell, we can't do both of them at the same time.
(1) We are using MsSql2008FeatureLayer to display data which is currently stored in SRID 3395. This can't easily be changed without impacting hundreds of installations. The goal would be to reproject this to the projection used by Bing, OSM, Google, etc.
(2) In the layer's FeatureSource, there is a place for a Projection. It's easy enough to create a Managed4ProjProjection to convert on the fly from 3395 to Google, etc. I did this yesterday and placed our SQL data on top of OpenStreetMap and it worked quite well...this was something that didn't work well in 4.5. I believe there were accuracy issues with the Proj4 implementation.
(3) In our current application the map rotates. To do this I place a RotationProjection in the Projection slot of the Feature Source.
(4) The Projection slot is now occupied by the RotationProjectection and thus I cannot add the Managed4ProjProjection to reproject on the fly.
(5) In other words, to both reproject and rotate I need to insert something into the Projection of the FeatureSource, but it's not a collection: it only takes one item.
(6) I'm just throwing out ideas on what might work to solve this problem:
#1: A RotationProjection class that can accept a Managed4ProjProjection
#2: An MsSql2008FeatureLayer constructor that could be supplied TWO SRIDs or projection strings to trigger on-the-fly reprojection which would leave the Projection slot open for the Rotation.
I certainly understand there might be technical complications in doing either of these. I am just trying to find out if anything has changed between 4.5 and 6.0 that might let us do this now.
Thoughts?
Thanks,
Allen