I have noticed that any streaming service created/stored in Velocity is NOT able to be shared publicly?
We would love to share location of plows on our public map, but currently this seem not possible???
@ArmstKP Thanks for reaching out with your question! At the current release, ArcGIS Velocity backed feature layers and stream layers can be shared with groups or with your organization, but cannot be shared to the public.
The current option in ArcGIS Velocity to share data to the public is to create an output feature layer hosted in an ArcGIS Online layer using the Feature layer (new) or Feature layer (existing) outputs.
With our 3.3 release in early November 2022, the Feature layer (existing) output will also support writing to ArcGIS Enterprise/ArcGIS Server backed layers which of course can be configured to be public facing.
https://doc.arcgis.com/en/iot/disseminate-and-notify/feature-layer-new-.htm
https://doc.arcgis.com/en/iot/disseminate-and-notify/feature-layer-existing-.htm
@PeterNasuti Perfect! Thank you for that information; very helpful!
@PeterNasuti Peter, I have followed your steps in creating an output feature layer hosted in ArcGIS Online, by creating a new Feature layer. When I go to share it publicly, I get this error:
@ArmstKP If ArcGIS Online is not providing any additional information or context associated with that error, please reach out to Esri Support Services for assistance investigating why the given layer cannot be shared to the public. Once Velocity creates an ArcGIS Online hosted feature layer, it is a native ArcGIS Online layer that could be treated like any other online layer.
@PeterNasuti Peter, I noticed that the icon is not the normal ArcGIS Online Hosted Feature layer icon, but has the Velocity Feature layer icon. Is this the issue, that it is still seeing it as coming from Velocity?
Based on the icons and the fact that there is an accompanying map image layer, you have created a "Velocity feature layer" with data stored in a spatiotemporal layer. This layer type cannot be shared to the public, thus the error message you witnessed.
ArcGIS Online hosted feature layers however can be shared to the public. The Velocity "Feature layer (new)" output can be configured to create an ArcGIS Online hosted feature layer. See the following screenshot for reference. By unclicking the toggle "store data in a spatiotemporal feature layer", when unchecked the corresponding feature layer created will exist in the ArcGIS Online hosted feature layer. You can also use the "Feature layer (existing)" output to write to an existing ArcGIS Online hosted feature layer.
@PeterNasuti Thank you. I have tried this as well, but our AVL snowplow feed is usually around 10 e/s and thus our average is above 2 e/s in our feed. So, I am not able to save and start the feed to create the Feature layer (new) output. Does this basically mean that I just won't be able to share last vehicle locations to the public?
I’ve been following along here reading the comments and trying to figure out the best workflow to get my Velocity feed output to a public map. Goal is to show where our snow plows have been and where they currently are.
I have a the feed setup with our winter ops trucks, all the arcade expressions have been parsed the array coming in from the AVL source. Correct me if I’m wrong, but if I want to share a public facing layer I need to turn off “Store data in spatiotemporal feature layer and setup a (new) layer. I’ve read the documentation, but there’s a lot of it and it’s a little confusing. After turning off spatiotemporal, Choose Add all new features, keep existing features and schema. I could call this layer Winter fleet (past locations)
Then setup another layer, again (not a streaming layer output in Velocity), but another Configure feature layer (New) call it current locations and also don’t turn on spatiotemporal feature layer, choose “Keep only latest feature for each Track ID value.
Would this be the only way to get the Velocity feed onto a public facing map? Understood I’ll need to play around with how long I run the analytic that produces the outputs and watch my feeds to not burn up too many credits or grow the cloud storage too big. I suppose if this works it’s really one of the big differences between setting up on ArcGIS Server Geoevent vs Velocity?
Could someone explain when it be best to run a stream layer in Velocity if my above is the only way to get a public map out. My understanding is the stream layer is a Velocity feature which is why it won’t share to public, would choosing a stream layer be used for internal OpsDash features and functions.
Thanks, Matt
Happy to clarify a few items:
Velocity-backed layers (map, feature, or stream layers) cannot be shared to the public, however they can be shared to the Organization
ArcGIS Velocity can write to/create new ArcGIS Online hosted feature layers (uncheck store in spatiotemporal as you had mentioned), which can be shared with the public
ArcGIS Velocity can write to existing ArcGIS Online hosted feature layers which can be shared with the public, using the Feature layer (existing) output
ArcGIS Velocity can write to existing ArcGIS Server feature services using the Feature layer (existing) output, and of course your ArcGIS Server feature services can be shared to the public
Additionally, Feature layer (new) or Feature layer (existing) Velocity outputs to ArcGIS Online hosted feature layers only allow outputs of up to 120 records written per minute. This is an ArcGIS Online limitation.
@PeterNasuti Thanks Peter
Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
