![]() If you find yourself unable to resolve this problem with either of the previous options, you could reproject all of your data into a common projection. If this is the case, follow the instructions in the previous option, but instead of Web Mercator, match the projection of your own dataset. It may be that basemaps aren’t your slowest layer to reproject – maybe reprojecting your own data is even slower, or similar. Option 2b: Change the projection of the data frame to match your other layers For this reason, you should plan to switch your data frame’s projection back to its original projection (or another desirable one) before you produce map exports. Selecting a new projection introduces distortion into your map – maybe distortion you don’t like – because the Web Mercator projection is optimized for the whole planet, and if your data is stored well, it’s probably using a projection optimized for your area – depending on many factors.If your dataset is large, you may find that it takes a long time to reproject too – maybe long enough to warrant switching the map document back to its original projection (if you’ve forgotten, look at the Source tab of the Properties dialog for your dataset). ![]() Now, ArcGIS no longer needs to reproject your basemap tiles, and instead will reproject your other data to match the new projection. Select WGS 1984 Web Mercator (auxiliary sphere ) when it appears.In the search box, type Web mercator and hit the Enter key on your keyboard.Right click on Layers in your Table of Contents.Want to speed it up? You can switch the data frame to use the projection of the basemap. It’s rare for your own data to be in that projection, so if you add your data before you add the basemap, then the data frame takes on the projection of your data and is reprojecting the basemap tiles to match. The basemaps available from the Add Basemap dialog in ArcGIS all come in the projection “WGS 1984 Web Mercator (auxiliary sphere)” (EPSG 3857). You decide you want some context for your data, so you add a Basemap – and now ArcGIS slows down. You open ArcMap and add your data to the map. Option 2: Change the projection of the data frame to match the basemap This is often not a good option for people. Your first option is simple – figure out which layers are slow and disable them. This reprojection is where things get slow. Here are some options to handle that problem. Your map document also has its own projection – more accurately, your data frame does – and if your datasets don’t use the same projection as your map document, then ArcMap reprojects the data into the map document’s projection behind the scenes in order to display it on the screen together. Your geospatial information has projection information attached to it that helps software like ArcGIS understand how the coordinates in the dataset should be interpreted, and which can be used to line that data up with the rest of the data on your map. To be brief, a projection is a set of parameters that allows us to draw the mostly spherical features of the Earth on a flat surface like your computer screen or a piece of paper. What are projections and how are they used in ArcMap? To understand how, we first need a quick overview of projections. While you may be inclined to chalk it up to the software or complexities in your data, it’s often fixable. Still on WinOMS 9.1 so not sure if going to 9.2 will help or not.Every so often, I get a question about how to speed up ArcGIS – specifically that the interface is slow, or that it’s slow to draw layers. I can download the older reader but you have to purchase a newer version of Acrobat Standard/Pro. I don't know if 10, 11 version of Reader or Standard/Pro would work or not. I have looked through settings in Acrobat DC thinking maybe it was some sort of security option or whatnot and nothing fixes the problem other than to uninstall Acrobat Reader DC and install Acrobat 9 Standard. I eliminated as many variables as possible and it's the same result (Security, Application Conflicts, Networking etc). It happens whether it's Windows 7, 8.1 or Windows 10. I have seen this at two different practices. No freezes ups, Hiccups, works as normal. On computers that have Acrobat 9 Standard (it's an old version i know but it's what they have) there is no problem when it's the default PDF viewer for WinOMS. It just sits there thinking then finally will go to the next screen. On computers where Acrobat Reader DC is the PDF viewer for WinOMS it's causing WinOMS to freeze up, a lot of times it's when the preview window displays, then you try to move to another area of WinOMS. The issue is one that i have tested on multiple machines.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |