nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Set scale in python

josesanchez1

Hi all,

this is my code:

..

zoom = arcpy.mapping.ListLayers(mxd,cut,"")[0] # we locate cut layer in TOC. cut is a variable
df.extent = zoom.getExtent() # Zoom to Layer zoom
df.scale = 20000 # we set the scale to 1:20,000
arcpy.RefreshActiveView()
arcpy.RefreshTOC()
mxd.save()

it should work, right?

Well, when I open the map in PDF that I have generated and..time after time, I see Scale = 1:8,223, which means that after the Zoom to Layer, the line:

df.scale = 20000 does not work at all!! (df is the DATA FRAME previously created)

Any suggestions?

Thanks in advance.

Jose.

Encontre mais publicações marcadas com

Accepted answers

josesanchez1

Well, I got it!. Thanks anyway for all your comments.

NOW, my PDF does not have any 1:8.223, just 1:20.000!!!!

After the code lines:

list2 = [0,6,7,8,9] # we list the positions of the elements that not may appear in this map.
for i in list2:
    lyr = arcpy.mapping.ListLayers(mxd,"","")
    lyr.visible = False # we turn off these layers.
zoom = arcpy.mapping.ListLayers(mxd,cut,"")[0] # we locate cut (Study area extent) in TOC.

and before the line:

df.extent = zoom.getExtent()

I put:

arcpy.RefreshActiveView()
arcpy.RefreshTOC()

So, in the end, I have learned that after turning off layers in TOC, you must refresh everything..in order to get the desired scale.

Jose.

All comments

RichardKammer

Try setting the data_frame parameter of the ExportToPDF function to "PAGE_LAYOUT". This will export the layout view in the mxd. If this parameter in not set it will default to the data frame.

arcpy.mapping.ExportToPDF(mxd, dir + "\file.pdf", "PAGE_LAYOUT")

RobertBorchert

It has to be possible Your data frame is constantly returning you current scale.

you scroll in and out if is instantly updated. Also when you put in scale text or scale bar that changes. so the system has to be constantly quering it.

RobertBorchert

hee hee layer files is exactly what I have been trying to get away from for well over a decade.

I have actualy been posting this question ever now and then for a long long time.

I have one particular mxd from which I generate .pdf files for one of my clients. I have 4 levels of visibility for which I want certain features of a feature class to be visible. so as the scale gets larger more features become visible.

I normally have 5 features that would be to clutterd to show all of them at a small scale. So i have them in the mxd 4 times and using definition querys make certain features visible. When I drop below 1:20,000 the first layer goes gray and the second layer is visible with all features from the first and more now visible. It also then controls lables.

The major issue is when someone suddently wants a larger format product I have to redefine all the scale visibility or even worse when they want a change in labels I need to make that change multiple times for each copy of the attribute.

etc....

blake.terhune

I don't think you can combine a definition query and visible scale range with Python like that. You could use that definition query but it would never change the visible scale range in the MXD on its own. I recommend you try using layer files. When you create a layer file, it will save the visible scale range you set (as well as definition queries, symbology, labels, etc). So instead of adding the feature class from a geodatabase, just add it from the layer file and it will already have all that stuff set up. If you want your visible scale range to change, you'd have to save over the layer file with the new visible scale range set.

Your other option would be to run a Python script that checks for a vscale field in all (or certain) layers in the map and sets the visible scale range; it would have nothing to do with a definition query.

RobertBorchert

I would like to do something along this line and query data frame scale and put it in definition query.

i.e. I would like create an attribute and call it vscale ( visible scale) can be anything this is arbitrary.

I would like to create a definition query as such.

vscale >= CurrentDataFrameScale

So when I am at or above whatever value i have in vscale my feature becomes visible.

josesanchez1

Well, I got it!. Thanks anyway for all your comments.

NOW, my PDF does not have any 1:8.223, just 1:20.000!!!!

After the code lines:

list2 = [0,6,7,8,9] # we list the positions of the elements that not may appear in this map.
for i in list2:
    lyr = arcpy.mapping.ListLayers(mxd,"","")
    lyr.visible = False # we turn off these layers.
zoom = arcpy.mapping.ListLayers(mxd,cut,"")[0] # we locate cut (Study area extent) in TOC.

and before the line:

df.extent = zoom.getExtent()

I put:

arcpy.RefreshActiveView()
arcpy.RefreshTOC()

So, in the end, I have learned that after turning off layers in TOC, you must refresh everything..in order to get the desired scale.

Jose.

rzufelt

First, thanks to everybody for considering my issue. then:

1.- What I am trying to do is exporting into a PDF my Layout View using python. The scale of this map may be 1:20.000 (1:20000)

2.- Before executing the script: Data Frame Properties --> Extent : Automatic

3.- Before executing the script: The scale is set to 30000 (purposely) in order to see if the script works or not.

5.- OK, when I run the script, I look at the Map Scale (Data View) and the sequence I see with my own eyes is:

....1:30,000 (good).......1:20,000 (good!).....1:8,223..(not good).

Result: PDF Scale --> 1:8,223

That is all I can say so far.

Jose.

So, understand the 1:30,000 as you set it manually in the mxd
the 1:20,000 is what your script tells it to do
Where is the 1:8223 coming from? you say you get all of them, but you only have one spot in the code that is making a change, why (or when) do you get three different values?

Just to make sure, you do understand, that, unless you set Data Frame Properties --> Fixed Scale, you will likely "never" get the Layout scale to be exactly 1:20000 as long as you are also zooming to some extent in the dataframe?

R_

josesanchez1

First, thanks to everybody for considering my issue. then:

1.- What I am trying to do is exporting into a PDF my Layout View using python. The scale of this map may be 1:20.000 (1:20000)

2.- Before executing the script: Data Frame Properties --> Extent : Automatic

3.- Before executing the script: The scale is set to 30000 (purposely) in order to see if the script works or not.

4.- The code would be:

import arcpy
mxd = arcpy.mapping.MapDocument("CURRENT")
df = arcpy.mapping.ListDataFrames(mxd, "Layers")[0]
cut = arcpy.GetParameterAsText(0) # from TOC by Default (LAYER).
dir = arcpy.GetParameterAsText(1) # folder type
list2 = [0,6,7,8,9] # we list the positions of the elements that not may appear in this map.
for i in list2:
    lyr = arcpy.mapping.ListLayers(mxd,"","")
    lyr.visible = False # we turn off these layers. CUT IS NUMBER 5, SO IT IS NOT AFFECTED HERE
zoom = arcpy.mapping.ListLayers(mxd,cut,"")[0] # we locate cut (Study area extent) in TOC.
df.extent = zoom.getExtent() # Zoom to Layer
df.scale = 20000 # we set the scale of the output to 1:20,000
arcpy.RefreshActiveView()
arcpy.RefreshTOC()
mxd.save()
arcpy.mapping.ExportToPDF(mxd, dir + "\file.pdf") # we export the map into a PDF file.

5.- OK, when I run the script, I look at the Map Scale (Data View) and the sequence I see with my own eyes is:

....1:30,000 (good).......1:20,000 (good!).....1:8,223..(not good).

Result: PDF Scale --> 1:8,223

That is all I can say so far.

Jose.

rzufelt

It sets the scale properly into ArcMap, but not when it goes into the PDF.
arcpy.mapping.ExportToPDF(mxd, dir + "\FILE.pdf")

In where in ArcMap? The layout or the dataframe as you are setting?

Unless you have went into the dataframe properties in ArcMap and set the extent to "Fixed Scale", you will likely never get the same scale for the dataframe that you have for the Layout (which is what is exported to pdf unless you specify otherwise).

If you want it to be 1:20000 all the time, just set it in the dataframe properties as fixed scale.

R_

markdenil

Sometimes you have to set such settings twice with python
(the snake has a bug).
But you say it does seem to change in ArcMap...
You don't however, provide your ExportToPDF parameters....

It is also unclear if you are exporting your layout or just a data frame.
Exporting a layout is almost always a better idea.

josesanchez1

It sets the scale properly into ArcMap, but not when it goes into the PDF.

arcpy.mapping.ExportToPDF(mxd, dir + "\FILE.pdf")

rzufelt

Are you sure it isn't being set? normally, when you export to pdf, you export the Layout, not the dataframe.

After it has run, open the mxd in ArcMap, switch to data view and see what your "dataframe" scale is set to.

Depending on your constraints, etc. the Layout view scale is not the same as Data frame scale.

R_

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.