Populate SQL Expression in Toolbox based on hard coded parameter [on hold] The 2019 Stack Overflow Developer Survey Results Are InSet ArcGIS Tool Parameter to Obtain From it's own Source?Setting output parameter in Python script tool to be PDF?Issue with using arcpy.GetParameter and arcpy.GetParameterAsText to write layer source to text fileMaking Parameter List Update/Refresh in Python Toolbox?Generating SQL expression from multivalue pick list in ArcGIS toolUpdating ESRI mxd definition query variable via python?Creating ArcPy scripting tool with dropdown box for sql expression choiceQuery over all layers in a mxd ArcpyList layers in dataframe as parameters in script validationCreating script tool for definition query using user input
How to charge AirPods to keep battery healthy?
Does HR tell a hiring manager about salary negotiations?
Short story: child made less intelligent and less attractive
What is preventing me from simply constructing a hash that's lower than the current target?
Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?
What is the meaning of Triage in Cybersec world?
What does Linus Torvalds mean when he says that Git "never ever" tracks a file?
Getting crown tickets for Statue of Liberty
If I score a critical hit on an 18 or higher, what are my chances of getting a critical hit if I roll 3d20?
writing variables above the numbers in tikz picture
Is it safe to harvest rainwater that fell on solar panels?
"as much details as you can remember"
Loose spokes after only a few rides
Is it okay to consider publishing in my first year of PhD?
Why are there uneven bright areas in this photo of black hole?
Are spiders unable to hurt humans, especially very small spiders?
Why not take a picture of a closer black hole?
Is bread bad for ducks?
Output the Arecibo Message
Likelihood that a superbug or lethal virus could come from a landfill
Why can I use a list index as an indexing variable in a for loop?
Cooking pasta in a water boiler
What does もの mean in this sentence?
How to support a colleague who finds meetings extremely tiring?
Populate SQL Expression in Toolbox based on hard coded parameter [on hold]
The 2019 Stack Overflow Developer Survey Results Are InSet ArcGIS Tool Parameter to Obtain From it's own Source?Setting output parameter in Python script tool to be PDF?Issue with using arcpy.GetParameter and arcpy.GetParameterAsText to write layer source to text fileMaking Parameter List Update/Refresh in Python Toolbox?Generating SQL expression from multivalue pick list in ArcGIS toolUpdating ESRI mxd definition query variable via python?Creating ArcPy scripting tool with dropdown box for sql expression choiceQuery over all layers in a mxd ArcpyList layers in dataframe as parameters in script validationCreating script tool for definition query using user input
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I have an ArcGIS toolbox script that applies a user-defined definition query to multiple layers within the current MXD.
The only user variable currently required is the definition query itself, which I have listed as an "SQL expression". The script works fine, but it would be nice if the SQL validation box on the toolbox GUI was populated with the details of the first layer in the MXD, allowing the user to construct and validate a definition query against the first layer.
How can I achieve this using a hard-coded variable pointing to the first layer in the TOC?
It's fairly straightforward in a one-to-one scenario, by asking the user to input the feature layer as a parameter and then making the SQL expression parameter "Obtained from", but I can't figure out how to do it by defining it myself.
arcpy sql parameters
edited 2 days ago
PolyGeo♦
53.9k1782246
asked Feb 28 at 10:47
RichRich
1
put on hold as off-topic by PolyGeo♦ 2 days ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "When seeking help to debug/write/improve code always provide the desired behavior, a specific problem/error and the shortest code (as formatted text, not pictures) needed to reproduce it in the question body. Providing a clear problem statement and a code attempt helps others to help you." – PolyGeo
add a comment |
I have an ArcGIS toolbox script that applies a user-defined definition query to multiple layers within the current MXD.
The only user variable currently required is the definition query itself, which I have listed as an "SQL expression". The script works fine, but it would be nice if the SQL validation box on the toolbox GUI was populated with the details of the first layer in the MXD, allowing the user to construct and validate a definition query against the first layer.
How can I achieve this using a hard-coded variable pointing to the first layer in the TOC?
It's fairly straightforward in a one-to-one scenario, by asking the user to input the feature layer as a parameter and then making the SQL expression parameter "Obtained from", but I can't figure out how to do it by defining it myself.
arcpy sql parameters
edited 2 days ago
PolyGeo♦
53.9k1782246
asked Feb 28 at 10:47
RichRich
1
put on hold as off-topic by PolyGeo♦ 2 days ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "When seeking help to debug/write/improve code always provide the desired behavior, a specific problem/error and the shortest code (as formatted text, not pictures) needed to reproduce it in the question body. Providing a clear problem statement and a code attempt helps others to help you." – PolyGeo
add a comment |
I have an ArcGIS toolbox script that applies a user-defined definition query to multiple layers within the current MXD.
The only user variable currently required is the definition query itself, which I have listed as an "SQL expression". The script works fine, but it would be nice if the SQL validation box on the toolbox GUI was populated with the details of the first layer in the MXD, allowing the user to construct and validate a definition query against the first layer.
How can I achieve this using a hard-coded variable pointing to the first layer in the TOC?
It's fairly straightforward in a one-to-one scenario, by asking the user to input the feature layer as a parameter and then making the SQL expression parameter "Obtained from", but I can't figure out how to do it by defining it myself.
arcpy sql parameters
edited 2 days ago
PolyGeo♦
53.9k1782246
asked Feb 28 at 10:47
RichRich
1
I have an ArcGIS toolbox script that applies a user-defined definition query to multiple layers within the current MXD.
The only user variable currently required is the definition query itself, which I have listed as an "SQL expression". The script works fine, but it would be nice if the SQL validation box on the toolbox GUI was populated with the details of the first layer in the MXD, allowing the user to construct and validate a definition query against the first layer.
How can I achieve this using a hard-coded variable pointing to the first layer in the TOC?
It's fairly straightforward in a one-to-one scenario, by asking the user to input the feature layer as a parameter and then making the SQL expression parameter "Obtained from", but I can't figure out how to do it by defining it myself.
arcpy sql parameters
arcpy sql parameters
edited 2 days ago
PolyGeo♦
53.9k1782246
asked Feb 28 at 10:47
RichRich
1
edited 2 days ago
PolyGeo♦
53.9k1782246
asked Feb 28 at 10:47
RichRich
1
edited 2 days ago
PolyGeo♦
53.9k1782246
edited 2 days ago
PolyGeo♦
53.9k1782246
edited 2 days ago
PolyGeo♦
53.9k1782246
53.9k1782246
asked Feb 28 at 10:47
RichRich
1
asked Feb 28 at 10:47
RichRich
1
asked Feb 28 at 10:47
RichRich
1
1
put on hold as off-topic by PolyGeo♦ 2 days ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "When seeking help to debug/write/improve code always provide the desired behavior, a specific problem/error and the shortest code (as formatted text, not pictures) needed to reproduce it in the question body. Providing a clear problem statement and a code attempt helps others to help you." – PolyGeo
put on hold as off-topic by PolyGeo♦ 2 days ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "When seeking help to debug/write/improve code always provide the desired behavior, a specific problem/error and the shortest code (as formatted text, not pictures) needed to reproduce it in the question body. Providing a clear problem statement and a code attempt helps others to help you." – PolyGeo
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I think this is what you're looking for:
# stores current map doc in a variable
mxd = arcpy.mapping.MapDocument("CURRENT")
# accesses the first layer in mxd
lyr = arcpy.mapping.ListLayers(mxd)[0]
answered Mar 6 at 17:01
scookscook
211
Thanks. I already had the code to access the first layer. It was making another parameter dependent upon it that I was struggling with. I have a solution though which I will post below.
– Rich
Mar 7 at 9:58
add a comment |
I eventually figured this out with some help from an ESRI trainer.
The key was to feed the hardcoded parameter in using tool validation at the initialisation stage and list it as a parameter of type "derrived" (which hid it on the GUI) and then make the user input parameter "obtained from" it.
answered Mar 7 at 10:03
RichRich
1
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I think this is what you're looking for:
# stores current map doc in a variable
mxd = arcpy.mapping.MapDocument("CURRENT")
# accesses the first layer in mxd
lyr = arcpy.mapping.ListLayers(mxd)[0]
answered Mar 6 at 17:01
scookscook
211
Thanks. I already had the code to access the first layer. It was making another parameter dependent upon it that I was struggling with. I have a solution though which I will post below.
– Rich
Mar 7 at 9:58
add a comment |
I think this is what you're looking for:
# stores current map doc in a variable
mxd = arcpy.mapping.MapDocument("CURRENT")
# accesses the first layer in mxd
lyr = arcpy.mapping.ListLayers(mxd)[0]
answered Mar 6 at 17:01
scookscook
211
Thanks. I already had the code to access the first layer. It was making another parameter dependent upon it that I was struggling with. I have a solution though which I will post below.
– Rich
Mar 7 at 9:58
add a comment |
I think this is what you're looking for:
# stores current map doc in a variable
mxd = arcpy.mapping.MapDocument("CURRENT")
# accesses the first layer in mxd
lyr = arcpy.mapping.ListLayers(mxd)[0]
answered Mar 6 at 17:01
scookscook
211
I think this is what you're looking for:
# stores current map doc in a variable
mxd = arcpy.mapping.MapDocument("CURRENT")
# accesses the first layer in mxd
lyr = arcpy.mapping.ListLayers(mxd)[0]
answered Mar 6 at 17:01
scookscook
211
answered Mar 6 at 17:01
scookscook
211
answered Mar 6 at 17:01
scookscook
211
answered Mar 6 at 17:01
scookscook
211
211
Thanks. I already had the code to access the first layer. It was making another parameter dependent upon it that I was struggling with. I have a solution though which I will post below.
– Rich
Mar 7 at 9:58
add a comment |
Thanks. I already had the code to access the first layer. It was making another parameter dependent upon it that I was struggling with. I have a solution though which I will post below.
– Rich
Mar 7 at 9:58
Thanks. I already had the code to access the first layer. It was making another parameter dependent upon it that I was struggling with. I have a solution though which I will post below.
– Rich
Mar 7 at 9:58
Thanks. I already had the code to access the first layer. It was making another parameter dependent upon it that I was struggling with. I have a solution though which I will post below.
– Rich
Mar 7 at 9:58
add a comment |
I eventually figured this out with some help from an ESRI trainer.
The key was to feed the hardcoded parameter in using tool validation at the initialisation stage and list it as a parameter of type "derrived" (which hid it on the GUI) and then make the user input parameter "obtained from" it.
answered Mar 7 at 10:03
RichRich
1
add a comment |
I eventually figured this out with some help from an ESRI trainer.
The key was to feed the hardcoded parameter in using tool validation at the initialisation stage and list it as a parameter of type "derrived" (which hid it on the GUI) and then make the user input parameter "obtained from" it.
answered Mar 7 at 10:03
RichRich
1
add a comment |
I eventually figured this out with some help from an ESRI trainer.
The key was to feed the hardcoded parameter in using tool validation at the initialisation stage and list it as a parameter of type "derrived" (which hid it on the GUI) and then make the user input parameter "obtained from" it.
answered Mar 7 at 10:03
RichRich
1
I eventually figured this out with some help from an ESRI trainer.
The key was to feed the hardcoded parameter in using tool validation at the initialisation stage and list it as a parameter of type "derrived" (which hid it on the GUI) and then make the user input parameter "obtained from" it.
answered Mar 7 at 10:03
RichRich
1
answered Mar 7 at 10:03
RichRich
1
answered Mar 7 at 10:03
RichRich
1
answered Mar 7 at 10:03
RichRich
1
1
add a comment |
add a comment |
