IDEA
|
Mark, are you saying that we're allowed to pass out a single username & password to clients in order to view a protected / sensitive item, for the cost of a single viewer license? Because that's what it sounds like.
... View more
01-22-2020
08:47 AM
|
0
|
0
|
1626
|
IDEA
|
This idea would be instrumental in collaboration between a contractor and an organization that's GIS savvy. It would especially make the transfer of data from one organization to another a streamlined process. Say I am contractor A, who made a story map for client B. Well, right now I need to pass on detailed instructions for client B to follow to set up the same thing I made but stored with their credits. This would enable contract cartography as a business model without putting undue burden on the cartographer after the product was made, a simple transfer that would allow the cartographer to work and update any problems with the webmap on the client's storage credits while they pay for their own license.
... View more
01-22-2020
08:40 AM
|
2
|
0
|
1414
|
IDEA
|
Say I want to make a table frame a bit more special, something like changing row backgrounds based on what category that row belongs to, or maybe even changing font color for specific rows based on a field called "Important". Well, I could be able to do that by having it choose colors from a string field with hex values in the same manner as symbol property connections for layer symbology works. Is such a thing possible? Instead of the current setup of background 1 and background 2, there could be a checkbox that disables that property and turns on the more dynamic approach. Otherwise, I have to create rectangles and individually color them after placing them below the table or create them in some other manner of editing outside of ArcPro.
... View more
07-30-2019
06:50 AM
|
8
|
5
|
735
|
IDEA
|
Yes, as a parameter. But I can also get that it's better to just write that check into my own scripts at the same time. It'd likely cause confusion though as an optional parameter. Not a good enough reason to change arcpy.DeleteField_management, I suppose.
... View more
01-07-2019
07:47 AM
|
0
|
0
|
1107
|
IDEA
|
Currently with ArcPro the delete field tool in data management will generate a warning if a field doesn't exist in the input and error out the task. Now this might be a bug, as I don't think warnings are supposed to stop an iterating script dead in its tracks, but what if you made the code like so: inFC = arcpy.GetParameterAsText(0) ListOfInputFields = arcpy.GetParameterAsText(1) ListOfInputFields = ListOfInputFields.split(";") for delField in ListOfInputFields: fldLst = arcpy.ListFields(inFC) fldLst2 = [] for fld in fldLst: fldLst2.append(fld.baseName) if delField is in fldLst: arcpy.DeleteField_management(inputFC,delField) else: arcpy.AddMessage(deleteField + " was not found in " + inputFC) continue Anyways just an idea. It's probably not the best way of writing out the code but maybe you get the point?
... View more
01-04-2019
01:52 PM
|
1
|
3
|
1433
|
POST
|
So I have a python script that has two parameters They are an input feature class and then an input field obtained from that feature class. How would I go about making a third parameter that's a boolean checklist of all unique values from that input field in that feature class, which updates after you select a field? I'd like it to have a checkbox but I recognize that I might have to have a dropdown->add sort of functionality instead. In the end I'd like to essentially choose values that I want to 'turn on' in a feature class by changing a value of 0 or 1, which I have set up in my python script: import arcpy ## This code is to quickly choose which states get the selected color and which ones don't inFC = arcpy.GetParameterAsText(0) inFld = arcpy.GetParameterAsText(1) stateList = arcpy.GetParameter(2) ## Check to see if it has the Lightswitch field fldLst = arcpy.ListFields(inFC) fldLst2 = [] x=0 for fld in fldLst: fldLst2.append(fld.name) del fld arcpy.AddMessage("It's pitch dark... you are likely to be eaten by a grue...") arcpy.AddMessage(">Find lightswitch") arcpy.AddMessage("You begin stumbling around in the dark, searching for a lightswitch") for fld in fldLst2: if fld is not 'Lightswitch': ##If the field isn't a lightswitch, add a strike x+=1 elif fld is 'Lightswitch': arcpy.AddMessage("You found the dang* Lightswitch and turned it on.") break elif x == len(fldLst2): ##If the field isn't a lightswitch and you've checked every field, build your own arcpy.AddMessage("You couldn't find the lightswitch, so instead you decide to build your own") arcpy.AddField_management(inFC,'Lightswitch','SHORT',1) break with arcpy.da.UpdateCursor(inFC,[inFld,'Lightswitch']) as cursor: for state in cursor: state[1]=0 ##Default switch is set to off cursor.updateRow(state) for stat in stateList: ##Check it against selected states, if it's in the selected state list, turn it on if state[0]!=stat: continue elif state[0]==stat: state[1]=1 cursor.updateRow(state)
... View more
12-06-2018
07:26 AM
|
0
|
2
|
542
|
Title | Kudos | Posted |
---|---|---|
8 | 07-30-2019 06:50 AM | |
2 | 01-22-2020 08:40 AM | |
1 | 01-04-2019 01:52 PM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:25 AM
|