Latest Contributions by AllenScully

Update -  While the tool worked fine in ArcMap, I had a hell of time getting the GP service to work correctly.  Ended up using CopyFeatures_management to create the desired in_memory feature classes instead of FeatureClasstoFeatureClass_management. ... View more

Hi Erica -  I've implemented this in a draft GP service.   It's super straightforward, and it works.  However there are a couple of things to report back -  1 - it does indeed add time to the GP tool returning results - went from 3.5 seconds to about 6 seconds in our case. 2 - in this case, I actually needed to use 2 FeatureClassToFeatureClass_conversion tools - the first allows you to delete fields from it.  However - when publishing the GP service with this as the output dataset, it still returns all of the fields, including those that were deleted.  Again, looking at the GP service REST end point, it does look correct - the deleted fields are not shown, but they are in the JSON results.  So, you actually need to create another in_memory feature class after dropping the fields - this one will be 'clean' and when used as the output of the GP tool only includes the desired fields. 3 - Even though the feature classes are in_memory, they are 'sticky' as far as holding on to data from a previous run of the tool.  So, for each in_memory feature class, I added: if arcpy.exists(in_memory_fc):        Delete_management(in_memory_fc) these are at the beginning of the script, to ensure the tool does not actually just return the same results from the last run. Thanks -  Allen ... View more

Thanks Erica -  I'll give the in memory FC a shot.  Main issue is performance - since it's a GP service we're looking to maximize speed and keep things lightweight.  Will follow up with results. ... View more

Hi Erica -  Yes, that's correct.  I have published the GP service from the python script where the MakeFeatureLayer_management includes "Field_info=..." and lists all of the fields, including setting the unneeded ones to Hidden. Looking at the rest URL, where it lists the fields, it appears to respect the 'Hidden' settings, displaying only those we need.  However on running the tool via REST, the output json returned includes all fields. ... View more

John - Many thanks for looking in to this and the detailed response.  This works well, and has helped us understand some implications of our basemap-building decisions.   So just to clarify - the source data used to build our basemap is in our local State Plane system but we make the data frame Web Mercator (without re-projecting the individual feature classes) in order to make it more friendly in web applications.   This is what creates the need for the extra coding within leaflet, correct? Allen ... View more

Thanks for posting this, it is helpful (and kind of therapeutic) to see what other folks have encountered during this process.  Just a minor but really frustrating issue we have noticed since going to Portal/enterprise 10.5.1 from 10.5 - Operations views do not load for people directly through the url - we have users who are not Portal/GIS folks that just go to a Dashboard URL, log in, and go about their day, at least they did until 10.5.1.  Now they cannot get the dashboard to open, it merely spins after log in and says that some of the items are not available and it's taking a while to load - this never resolves. It spins while showing the black-background Ops Dash screen. What's frustrating is that if they log in to the Portal home site, find the group they are in, then the dashboard, then click the dropdown next to 'Open' and select 'Open in Browser app' it will open - so the layers are actually available to them.  However this is actually a big ask given our user group for our dashboard.  Way too many steps.   New dashboard can't come to Portal soon enough. ... View more

Will add that I missed the last edit you had - I saw that and believe it would be simpler - would remove the additional step of re-setting the text values to their generic keywords. ... View more

This is perfect - each text value is populated with a variable in the script, so when done with the pdf generation I can still reference the variable and reset the value to the keyword - works like a charm: Example:  Set text value to desired attribute (extracted in variable creation) for elm in arcpy.mapping.ListLayoutElements(ownerMxd, "TEXT_ELEMENT"): if elm.text == "NHA": elm.text = siteNHA  (this is the formatted + attribute-based variable) print elm.text Reset text value to default after pdf generation: for elm in arcpy.mapping.ListLayoutElements(ownerMxd, "TEXT_ELEMENT"): if elm.text == siteNHA:  elm.text = "NHA" print elm.text Essentially just reversing the value in the 'if' and next elm.text = ... lines Many thanks, this is super useful. ... View more