Latest Contributions by Trippetoe

Hello. I'm looking for some recommendations on the best ways to test layer load performance via the 4.x jsapi. We are trying to document the differences in load times between AGOL vs our hosted map services.  My initial speculation is that a good way to go would be using the 'before-add' and 'after-add' events on the map.layers collection. Are those events specific to adding an item to a collection (just increasing the length of the list by one), or would they also capture the time needed to fetch a layer and load it in the map? Is there a better way / place to measure the time needed to fetch the layer and add it to a map?  Thank you. ... View more

Hello. Does AGOL provide a way for us to know "who" is using a public hosted feature layer in AGOL?  I'm aware of the standard Usage Reports that show a count of hits on the service, but i'd like more detailed info on who is using the service. I'm asking because one of our services has gone from averaging about 50 hits per day over the last year to spikes of over 1100 hits per day on a somewhat 'regular' pattern. We'd like to know who is using the service with that level of intensity. Thank you. ... View more

Hello. We have problems with the map rendering for many of our AGOL feature layers. Generally speaking, the map is zoomed out to the 'world' extent and no data are drawn, regardless of the extent of the map. We've noticed that the problem seems to be specific to the date when the feature layer was first created in AGOL. The majority of our layers were created in the Sep/Oct 2020 time frame. None of those layers has the map drawn correctly at the /explore endpoint. However, layers that we created/published in the May 2021 timeframe do have the maps drawn correctly. We've tested this theory on about 5 of our layers and the results are consistent. The "old" layer does not have the correct map. We published a new version of the feature layer - same data, same everything, except for the creation date - that works as expected. We could simply re-publish every layer, but the problem is we have about 100 layers and we don't want to go thru the re-publishing processes 100 times.  Is there something we can do other than republish the feature layers? OLD NEW (everything is the same as 'OLD' except when it was published) ... View more

Hub should enable a shopping cart experience where users could find/select multiple layers and add them to their 'download cart'. when done searching for layers, the user could click a button which kicks off a process to download all the layers in the cart. Here's a use case ... we are a Government agency which has about 100 or so layers available for community download.  If a user were interested in downloading, say 10 of those layers, the user would have to go thru the download workflow ten times to get all those layers. If there were a typical shopping cart experience (i am thinking something like Amazon.com) then the user would need click a download button only once. A more specific example might be a user interested in our public transit data - bus lines, rail lines, bus stops (points), rail stops (points). Each of the datasets are a separate layer so the user has to find, select, and download 4 different data sets (and manage each of the downloads on their local machine). In the shopping cart experience, the user would find and select the four layers, but there would be a single download step and a single file to manage locally.  I am imagining that each of the layers could be placed in a single file geodatabase for downloading (or multiple shapefiles zipped together, or multiple KML files zipped together, etc). ... View more