Latest Contributions by JamesCrandall

Hi again! I was finally able to give this another try and it DOES allow for populating that Feature Set input parameter from a selected feature!  It's a little quirky in that it asks the user to specify from which layer to use, but it does work! My problem was in expecting less click-I-ness from the workflow.  Essentially I was overlooking the input parameter selection workflow: I remember seeing "Feature Set *" but did not click the dropdown as I was simply expecting this to just work without user interactivity ... View more

Oh, right.  Yes, I am aware that this will populate the Feature Set parameter!  My problem is that instead of a user-created feature (point, line or poly), I need to just pass in the currently selected feature. As far as I know there is nothing that will accomplish this type of behavior without some extra JavaScript added in somewhere, which is perfectly fine but I need some guidance on where this should go and how it should be structured. Thanks again for your input! ... View more

Hi! Just to clarify/validate: your Feature Set input parameter is from a selection made in the map? Thanks for your input! ... View more

Oh I see what you mean.  Yes, that works however the user requirements are to select features that intersect (or fall inside of) the selected feature.  That is, the user does not want to have to draw anything.  The required process workflow is: 1. Enhanced Search Widget makes selection by attribute on layer 1. 2. Click Geoprocessing widget to select the features in layer 2 that fall inside or intersect the selected feature of layer 1. So, I'd need to be able to pass in that selected feature from 1. into the Feature Set as in input parameter. Thanks again! ... View more

Thanks Kevin -- that makes sense. Follow up question: would the Geoprocessing widget be smart enough to pass in that Feature Set?  What I mean is, will I be required to add some additional JavaScript modification to be able to pull the Selecting Features into that input Feature Set parameter that the model requires? Thanks again for your input! ... View more

I typically use pandas DataFrame.to_csv for this operation as I mostly work with that library.  But NumPy also has similar method that you could just convert your feature class or table to a NumPy array and save it out from there. import numpy import arcpy lyr = r'H:\Documents\ArcGIS\Default.gdb\MyFeatureClass' nparr = arcpy.da.FeatureClassToNumPyArray(lyr, ['OBJECTID','STNAME','CNTYFIPS','Shape_Area']) numpy.savetxt('H:\MyFeatureClass.csv', nparr, delimiter=",", fmt="%s") ... View more

"Production" means that the map owners have generally agreed not to change it without coordinating the change with stakeholders who have made their needs known" Please note that I am officially stealing and incorporating this.  But do not worry as I will be sure to reference it as some obscure internet resource found on some blog somewhere. Thanks. I think for now I'm having to stick with this idea of stacks of things that can contain items with specific attributes, properties and sources to help define what that stack is.  A "dev", "test" and "prod" stack each has it's own unique collection of things (which may be separated by physical environments or not!) but at least the overall stack can now be defined. Your insights are greatly appreciated!!! ... View more

Welcome to the wonderful world of date manipulation!  I think Jake has your answer below. ... View more

Use a timedelta.  It should work for seconds, days, weeks, months, years, etc...  Easiest example I found is below.  Just get your minimum and maximum dates in the field/table and determine the difference. http://stackoverflow.com/questions/1345827/how-do-i-find-the-time-difference-between-two-datetime-objects-in-python ... View more

Thanks, Xander! I noticed one thing that stood out from that seems quite different is that we've got specific directives to maintain what I describe as silo's of "versions" of various items.  That is we cannot just "switch" an Web AppBuilder Application to point to "production" sources/attributes -- the system admins want physical/virtual copies to exist.  Should a "prod" version go down for some reason then the "dev" version can be re-tooled rapidly to stand up a new prod version (if you think in terms of a SVN repository, it's complimentary to the idea of having specific tags of source code that gets deployed). So if we're talking about Web AppBuilder apps there is an entire hierarchy of individual components that must be defined and exist in it's own silo. "Development" Silo for a Web AppBuilder Application: Web AppBuilder App Published with "Beta" in the name (tags and description too), shared with specific group (business unit within the organization, or if shared with entire org or public then it MUST sunset at a future date), owned by developer, and deployed to "test" endpoint (url must contain "test" in the name). Web Map source published with "Beta" in the name (tags and description too), shared with specific group (business unit within the organization, or if shared with entire org or public then it MUST sunset at a future date), owned by developer or steward, contain services pointing to non-production SDE/FGDB or hosted FeatuerService and published to a non-production endpoint (eg, "test" or "dev" AGS deployment). ETL or other scripting deployed to non-production endpoints, servers or environments. It's definitely a challenge to inventory, document and create individual deployments for the various environments, whether those environments are physical, virtual, hosted or otherwise non-locational in nature. Thanks again! ... View more

Thanks a bunch, Tim. What specifically defines a "production" Web Map in your environment?  Or better yet, how do you answer the question: "Hey Tim....  When can we say that Web Map going to be in production?" Your input is greatly appreciated! ... View more

Hi Jennifer! To answer your question we are going to be maintaining separate "dev", "test" and "prod" versions of each Web AppBuilder application that we deploy to our AGOL environment.  This means that everything in my OP above needs to apply to each version as well. Therefore only "production" services that are pointing to production data sources will be added to the prod Web Map source document and the "production" Web AppBuilder application using any of those resources. Only "dev" services that are pointing to development data sources (eg, dev SDE environments), ETL scripting, etc will be resourced in "dev" web maps and apps. We are starting to build a process for each, documenting each item (saving to our sharepoint), as well as creating workflow diagrams for each.  Also there are deployment documentation requirements that are associated with Web AppBuilder applications. Just some food for thought. ... View more