POST
|
We have taken route of making our own "items" of some data sources we do not own so that we could improve the symbology or, more importantly, metadata. But we've found that even for datasets we completely own, the difference between the visualization settings and ReST endpoint drawing info remains an issue.
... View more
06-18-2024
07:09 AM
|
0
|
0
|
375
|
POST
|
Not sure if it is helpful, but our custom Legend is used in this Experience. https://www.stone-env.net/opdgig-view-data/ As described, we're having an issue where the symbology swatches are showing old symbols after the client has updated the layer's symbology in the AGO Visualization tab... because we are fetching the drawing info (renderer info) from the ReST endpoint.
... View more
06-14-2024
12:55 PM
|
0
|
2
|
430
|
POST
|
This looks promising. I'll explore. Thank you. The issue with where we pull the renderer info from is that there seems to be a disconnect between the ReST endpoint and the ArcGIS Online "Visualization" tab settings. Consider this in the Visualization tab: And this is what the ReST endpoint says for the drawing info (renderer): They are not the same and I know (since i changed it a few hours ago) the "Visualization" tab is the most recently changed. So, needing to pull symbology settings from the Visualization tab is because we need to avoid this disconnect. But I can't find any documentation in the ArcGIS Rest API stuff that talks about how to query the Visualization settings, nor any examples.
... View more
06-14-2024
12:49 PM
|
0
|
0
|
435
|
POST
|
We have "rolled our own" legend in Experience Builder because the out-of-box legend lacks functionality we needed it. It works fine for most things. Of course it has a key defecit ... it depends on the renderer settings of the ReST endpoint of the feature layer to determine what symbology to should be for the layers, and to draw a little symbol. This is SUPER tedious to deal with because there are so many types of layers and symbologies, that you need a giant chunk of switch or if-then logic to figure out what each layer type is and how to draw a symbol. We keep thinking, there must be some standard Esri way of doing this? It is bonkers that Esri is expecting us to recreate all the logic for legend rendering, right? But we just can't find any examples that really cover all the potential cases for layer types and generate a cute little symbol swatch like we see in the AGO map viewers. I thought I found the source code for it in Esri's GitHub once ... specifically the source for the Experience Builder Dev Edition Legend Widget... but when I went back later to use it, I couldn't find it again. Additionally, not only can we not find a complete example of the logic to handle the layer types for legend rendering, but we also do not see how to access the symbolization settings that are stored in the "visualization" tab for an AGO item. In other words, a feature layer might have some renderer defined for it, but it appears that the settings in the visualization tab for an AGO item can override the ReST endpoint. An example is a layer I created that has a Drawing Info value of: {"labelingInfo":null,"renderer":{"label":"Survey Point","symbol":{"angle":0,"color":[255,0,0,255],"outline":{"color":[255,255,0,255],"width":1},"size":8,"style":"esriSMSCircle","type":"esriSMS","xoffset":0,"yoffset":0},"type":"simple"},"transparency":0} However, five minutes ago I changed the fill color to purple, not red (so it should be something like [255,0,128,255] instead of [255,0,0,255]). So the ReST endpoint either gets overridden by the visualization setting, or takes a while to update from it. However, we would really like to just be able to directly access the updated visualization setting. Which I cannot seem to figure out how to find in the ArcGIS Online API ... I can't even find it in the ArcGIS Online Assistant. So what is the standard method by which someone would render their own legend symbolx? Do we really need to re-invent a wheel that Esri has conquered a million times over?
... View more
06-14-2024
11:08 AM
|
0
|
5
|
448
|
POST
|
@JayDev awesome - perfect. Thank you! Just what I needed for clarification.
... View more
04-25-2024
09:55 AM
|
0
|
0
|
335
|
POST
|
Hi Hubbers and Hub Team! After a long wait we finally have the code to enable Hub Premium for our Hub @ opdgig.dos.ny.gov One of the first things we need to do when using the Hub Premium code is name the community organization. Can someone clarify - this will not in any way change our current public Hub site at "opdgig.dos.ny.gov" ... it is simply the URL that registered community members will access? IF a person is registered in the Hub community related to opdgig.dos.ny.gov will they still be able to comment on datasets, or participate in discussions on the "opdgig.dos.ny.gov" Hub site?
... View more
04-23-2024
08:12 AM
|
0
|
2
|
415
|
POST
|
That's a very helpful bit of knowledge to keep in mind and I could see that biting us. However, my XB app folder is only 120 megabytes right now. So I do not think it is size related unless I'm missing something.
... View more
01-03-2024
12:58 PM
|
0
|
0
|
842
|
POST
|
We are using Experience Builder Developer Edition. We want to publish our custom Experience. It requires no login or OAuth or anything. When I download the app Zip file and extracted it, I can put it into a folder on one of our development Windows Servers with IIS and I can open the app no problem. I have tried to publish the exact same app to GitHub pages and I get a host of errors in the console. Here is the URL of the app at GH Pages so you can also look at the console. https://opdgig-dos-ny.github.io/ I saw that @GavinRehkemper had done a CI workflow that published to GitHub pages, but the example appears to be dead. I tried switching the service worker cache, but that did not help. The error messages in the console now are the same as before I switch the service worker cache build number etc. I am curious if we know if there is a reason that an Developer Edition Experience cannot be hosted on GitHub Pages? Thanks! Nick
... View more
01-03-2024
11:33 AM
|
0
|
3
|
919
|
POST
|
We've done this - there are few options. 1. Use a Python Notebook to build the stats and save them to, for example, a hosted feature table. 2. Use the DCAT feed in Hub/OpenData and parse the resultant JSON to count things. We built the Python Notebook approach to populate the stats for the Experience Builder embed at the bottom of this page: https://opdgig.dos.ny.gov/pages/engage Reach out to @mhaley_stone_env if you need more deets than the general idea.
... View more
12-05-2023
02:32 PM
|
0
|
1
|
627
|
POST
|
Hi @ThomasHervey1 - thanks for looking at it. We're looking into where those special characters came from. It certainly does seem that they should be ignored, at least, if not stripped entirely, from submitted values for the URL attribute.
... View more
09-21-2023
04:32 AM
|
0
|
0
|
917
|
POST
|
This does not appear to be fixed a week later... I've tried accessing this dataset a few different ways and still get the API error message in the download screen. https://opdgig.dos.ny.gov/datasets/NYSDOS::oil-gas-and-other-regulated-wells/explore
... View more
09-20-2023
07:12 AM
|
0
|
2
|
937
|
IDEA
|
When photo attachments are stored in the feature layer, and later accessed from Power Apps, for example, they are not rotated correctly based on the orientation of the camera. While it would be great if Power Apps got better, this also suggested that some very basic image transformation capabilities in Power Automate would be really useful and powerful for those of building around and in the Power platform. For my workflow, to be able to pre-process photos to rotate them 90 or 180 or 270 degrees as a Power Automate pre-processing step and have them stored as actually rotated pixels, instead of depending on the client display to respect the photo orientation metadata, would be very nice. Then if it can do that, doing some basic resizing and cropping would not seem to be a huge extra lift. All images are sideways ....
... View more
03-09-2023
12:44 PM
|
0
|
1
|
850
|
POST
|
Hi @ErichSchreier - sadly, last I checked, you cannot embed <SCRIPT> tags (and thusly JavaScript) into a Hub site. I think it is actually more generally just not available in AGOL at all. Esri has noted in the past that they have safety and stability concerns around allowing embedded JavaScript on their sites. I'm not sure if this is exhaustive for Hub specifically, but it is a good place to start: https://doc.arcgis.com/en/arcgis-online/reference/supported-html.htm If you need a custom widget of some sort on your site the only real option is to host it elsewhere as a separate web page, and embed that page / URL into your Hub site with an iFrame.
... View more
05-24-2022
06:38 PM
|
0
|
0
|
669
|
POST
|
Oh - sorry - I thought had Esri had the ability to just ignore the sharing settings. Should be viewable. Had to change the map for privacy reasons.
... View more
01-26-2022
02:25 PM
|
0
|
2
|
746
|
Title | Kudos | Posted |
---|---|---|
1 | 06-07-2023 10:24 AM | |
4 | 08-24-2021 07:54 AM | |
1 | 01-26-2022 10:10 AM | |
1 | 04-27-2020 01:01 PM | |
3 | 11-05-2019 09:33 AM |
Online Status |
Offline
|
Date Last Visited |
a week ago
|