Latest Contributions by AndrewRudin1

Thank you Peter, I'll see if I can use that endpoint to extract the logins on a regular basis and aggregate login counts by user in Excel or BI tools to get a general feel for how much staff are using Pro. ... View more

Is there a way to obtain this admin token programmatically via the REST API?  Is it different then the token obtained by the/sharing/rest/oauth2/authorize endpoint or the /sharing/rest/generateToken endpoint? I ask because I'm trying to get an ETL tool to retrieve data from the AGOL REST API's portal_history endpoint via my federated admin account, but the authentication documentation for the API sends me in circles for this type of Portal administrative workflow where I just need to connect to the ArcGIS Online Org or Enterprise Portal and query out some details about users, items, licenses, etc. I assume the code is as basic as two lines 1) Submit REST call containing my credentials to obtain the token 2) Submit REST call to the Portal_History endpoint containing my credentials ... View more

Thank you.  That was the ticket! Here's some new code you can run the Pro python window.  Not pretty at all, but it does print the title and list of users from the group. from arcgis.gis import GIS gis = GIS("pro") all_groups = gis.groups.search('1=1') for group in all_groups:    members = group.get_members()    users_list = members['users']    users_string = ','.join(users_list)    print(group.title + '...' + users_string) ... View more

Thanks for the response.  I think I'm going to put in a support ticket.  For me, running print(arcgis.__path__) returns the path to my default environment, even though the cloned environment is shown as the active one in the Pro python package manager. ... View more

Thank you! I used the "Settings Keys" section here: (https://github.com/Esri/arcgis-pro-sdk/wiki/ArcGIS-Pro-Registry-Keys#settings-keys-1).  Manually created a new registry key and pasted in my folder path.  Appears to work.  If I open Pro and remove the add-in, then close and reopen it appears.  Will try on Monday with a colleague logging in for the first time. ... View more

Okay, I think I see the issue.  I do not get those options to create a view or alter time settings on the SBDS layer I created in GeoEvent manager. To be specific, in GeoEvent Manager go to Site->Spatiotemporal Big Dat Stores->Create Data Source.   I guess GeoEvent created SBDS layers are not considered hosted layers.  To test I created a second SBDS layer a different way...by going into Pro and running GeoAnalytics->Copy to Data Store on the sample data housed on my PC.   That creates a portal item labeled as hosted and does provide the "time settings" and "create view" options. Perhaps if I create a hosted SBDS layer first via Pro, I can get GeoEvent to write to it.  Something to try later.  Regardless, given this little discrepancy, sounds like we'll have to put some forethought into how we want to use any data from GeoEvent for analysis before we put any GeoEvent services into production. Thank for walking through this example with me.  This really helps me understand how these servers fit into solutions for our business needs. -Andrew ... View more

Thank you Sarah,  That helps to know the projection I'm aiming for so I can design GeoEvent processes to do as little as possible.  Would hate to project to State Plane only to have the data auto-reprojected back. I'm using fresh 10.6.1 servers and Pro 2.2.3.  I've now redeployed a default GeoEvent SBDS output layer and have some sample data populated.  When I try to create a space time cube from it using the GeoAnalytics toolbar in Pro, I see that it was just giving me a warning about the coordinate system and that the tool will apply the "World Cylindrical Equal Area" projection.  However, right after that it bombed out because the input layer is time interval based, and that is what caused it to error out. I pasted the results window text below.   The data I'm using for my sample are city 311 service request tickets.  There are 500,000 records covering requests for all the various City services and we have history for the last 5 years, so it seemed like a good candidate to try spatiotemporal hosting on, I used Geoevent to create it since I can see us loading in tickets as they come in during every day.  The data has a few date fields in them that would be useful in various spatiotemporal analysis operations depending on what an analyst wants to look at. In my case those fields are created_date, last_status_update_date,  and close_date. When I defined the GeoEvent Definition for this data, I tagged the created_data as the START_TIME tag, and the closed_date as the END_TIME tag.  Therefore, I guess when the overlying feature service got created , it was then time-enabled as interval based with those two fields hard coded as start-end time values.  The space-time cube wants a dataset that is instant time...meaning only one field like created_date is used to time-enable.   So as an analyst, if I stumble upon this amazing GeoEvent output layer in my Portal and I want to do spatiotemporal analysis on it, then how would I go about it?   For example, maybe I want to investigate "how many tickets were created in various parts of the city over space and time the last 5 years?" and then "is there a spatiotemporal variance in how long tickets are open in parts of the city". With how it's setup now I don't see how I can do it without extracting the SBDS data to my desktop or another hosted copy where I can redefine the time-enablement on a Pro layer or a separate nearly-identical feature service.  If I load the SBDS feature service into Pro, the time-enablement section of the properties is grayed-out so I can't redefine it there before creating the space-time cube.  I also don't see a way to alter the properties of the feature service in GeoEvent or Portal to tinker with the time-enable properties.  I think hosted views aren't an option for this kind of data either. I really wish users could alter/override the time-enablement of web layers inside of applications (Pro, Portal map layers), rather than it being hard coded into service definitions. This would give analysts freedom to explore lots of different attributes from a single dataset, rather than being limited to whatever the data admin that initially created the web service picked. Here is the output from the processing. Parameters Point Layer AustinOpenData_311UnifiedData\AustinOpenData_311UnifiedData Output Name junkspacetimecube.nc Distance Interval 1000 Feet Time Interval 1 Months Time Interval Alignment REFERENCE_TIME Reference Time 1/1/2013 Summary Fields Output File Messages Start Time: Thursday, October 11, 2018 5:04:48 PM Running script Create Space Time Cube... Submitted. Executing... Executing (CreateSpaceTimeCube): CreateSpaceTimeCube "Feature Set" 1000 Feet 1 Months ReferenceTime 1/1/2013 [] junkspacetimecube.nc # Start Time: Thu Oct 11 17:04:51 2018 Using URL based GPRecordSet param: https://coagisentd1.coacd.org/server/rest/services/Hosted/AustinOpenData_311UnifiedData/FeatureServer/0 WARNING 120094: Bin generation and analysis requires a projected coordinate system and a default projection of World Cylindrical Equal Area has been applied. ERROR 120040: Wrong time type for 'Input Features'. Expected 'instant', got 'interval'. Failed to execute (CreateSpaceTimeCube). Failed at Thu Oct 11 17:04:55 2018 (Elapsed Time: 3.91 seconds) Failed. ERROR 000582: Error occurred during execution. Completed script Create Space Time Cube... Failed to execute (CreateSpaceTimeCube). Failed at Thursday, October 11, 2018 5:04:55 PM (Elapsed Time: 6.66 seconds) -Andrew ... View more