Latest Contributions by Trippetoe

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 hub-rail-stations-old.PNG NEW (everything is the same as 'OLD' except when it was published) hub-rail-stations-new.PNG ... 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

Hey there, It seems that in the new Hub view-contents version there are some 'bugs' (or at least an odd default behavior) around the Published Date that gets displayed.  We haven't figured out all the use cases, but here are some examples: when the Metadata publication date for a data layer is only a year (with neither month nor day), the displayed Published Date defaults to December 31, 1969.  For example, the metadata has a Published Date of 1999.  That date is rendered in Hub view-contents version as December 31, 1969 When the metadata publication date is a full date but with no time, e.g. 05/01/2010, the new Hub view-contents version shows the Published Date as April 30, 2010.  Similarly, for a metadata published date of 1/1/1998, the new Hub shows the published date as December 31, 1997.  Maybe that's some sort of UTC conversion error moving everything back 1 day? Our metadata dates do not have time component   ... View more

Hello, First of all, this is a long one - my apologies before getting started We are developing a new Hub site and i wanted to see how our content would appear in the new Hub content-views version being released May 25. Unfortunately, our data layers are not displaying as expected.  The AGOL data layers used in our new Hub site are 'reference' layers; that is, the data is not hosted in AGOL.  Instead, the data sources are our ArcGIS Server map services. We are using AGOL as a 'proxy' to access the data.  Our ArcGIS Server data is hosted as map services with many layers nested inside 'folders'.  For example for our 'vacant and developed land' data, we have 29 layers nested inside the 'develop' folder. So the URL looks like this:  https://gis.oregonmetro.gov/arcgis/rest/services/develop/develop/MapServer/0.  We use that URL as the "Feature Layer Data Source URL" in AGOL. It seems like the new Hub content page is 'confused' as to whether the item is a Map or a feature layer and thus showing elements of both a map and feature layer - but not completely either one - if that make sense. See the screen cap below.....Any thoughts about what's going on? hub-new-content-oddities.PNG   - The map is missing - Showing 29 Layers when should be a single layer. So its listing all the layers in the folder for the map service - Details - showing as both Map and Feature service - Details - published date isn't right (i'm still working on our end to see if that is bad data coming from our service) ... View more

In a Category card, i'd like to edit the font-size and font color for each card. The ability to change the appearance of the Category icon already exists, e.g. you can select the color of the icon. i'd like the ability to change the font color to match the icon color and the customize the font size. Currently i am customizing the font on Category cards by adding on to an existing esri class in a text card on my page.  .panel-footer { font-size:18px; color: #16a8b5; }  i suspect that approach (adding to base Hub classes) is not a recommended tact. Additionally it forces all category cards to have the same color and size. I can imagine a scenario where each Category card might have its own color and font size. ... View more