Latest Contributions by SpencerSmith5

‎02-01-2017

My company has all of our frames and files set up to use British National Grid as the projection. However, when adding in basemaps such as google imagery it becomes painfully slow and virtually unusable. After some tweaking I found that changing the data frames projection to "WGS_1984_Web_Mercator_Auxiliary_Sphere" this solves the slow loading issue, it all becomes super quick. I have begun to use "WGS_1984_Web_Mercator_Auxiliary_Sphere" however it appears to be scaling wrong? I have measured a distance on the same map, one with BNG and one with "WGS_1984_Web_Mercator_Auxiliary_Sphere" and both give drastically different distances. Have I not set transformation correctly? How do I do this?

‎01-06-2017

Thanks for the response, I am glad it will cause no other issue. From now on I will project all of my data in Web Mercator instead of BNG then. It does make me wonder why the basemaps are slow with BNG compared to WebMercator though...

‎01-06-2017

My company has all of our frames and files set up to use British National Grid as the projection. However, when adding in basemaps such as google imagery it becomes painfully slow and virtually unusable. After some tweaking I found that changing the data frames projection to "WGS_1984_Web_Mercator_Auxiliary_Sphere" this solves the slow loading issue, it all becomes super quick. My question is, what knock on effect will this have if I start creating shape files and maps to this new projection? Will shape files I make in this new projection still work on my old files that used British National Grid? Is there anything else I should know? Kind Regards, Spencer

Online Status	Offline
Date Last Visited	‎11-11-2020 02:24 AM

My Ideas

Latest Contributions by SpencerSmith5

Changing co-ordinate system in data frame causes wrong distances and scale

Re: Slow loading google image basemaps in data frame

Slow loading google image basemaps in data frame