Latest Contributions by RPGIS

Hi @SaraJL, Another option you can try is: Dissolve the line features by a common field value to create a single line/multi-part feature. Create a point feature using the centroid of the line. Spatial join the point feature to the polygon. Join the spatial joined point back the line feature using the IDs of the line feature. This would be my recommendation but there are other ways to tackle this problem. ... View more

Seems like an expression issue on the server side. It is probably something that a recent update may have caused a java handeling error. The purpose of the $originalfeature is coded to look at the original record before any changes. For some of the codes it seems like it might be referencing a record that possibly doesnt exist on the first place. Its common in attribute rules to reference a nonexisting record. ... View more

Try taking ownership of the feature layer, with permission of course, create the view and then try giving ownership back and see if that works ... View more

Hi @DataOfficer, So the closest recommendation that I can offer is to create a new featureset from a data expression. This would give you something akin to creating a new featureset from existing data and is populated to your output. Here is an small example on how to construct a separate featureset as a datasource in Dashboards. var customfields = [ { 'name' : 'fieldsA' , 'type' : 'esriFieldTypeSmallInteger' }, { 'name' : 'fieldsB' , 'type' : 'esriFieldTypeDouble' }, { 'name' : 'fieldsC' , 'type' : 'esriFieldTypeString', Length:7 } ] var Values = { 'attributes': {} } var Geometry = '' var FS = FeatureSet(Text({ 'fields': customfields, 'geometryType':Geometry, 'features' : Values })) return FeatureSet() ... View more

Hi @mhaley_stone_env, Not me but a simple CoPilot answer. Yes, it is possible to create a view layer from a shared update content group, but there are some important considerations: Ownership Matters: Only the owner of the original hosted feature layer typically has the ability to create a view layer. Even if you are part of a shared update content group, you may not have the necessary permissions unless explicitly granted. Administrative Privileges: If you need to create a view layer and are not the owner, your organization's administrator can adjust your role or permissions. They can either: Assign you a custom role with the privilege to create view layers. Transfer ownership of the hosted feature layer to you. Shared Update Group Limitations: While shared update groups allow members to edit and manage content collaboratively, creating a view layer is often restricted to the item's owner unless specific permissions are configured. If you're encountering issues, you may need to contact your administrator to ensure your role includes the necessary privileges or to discuss transferring ownership of the layer. In regards to the answer above, I can say for certain that if you have administrative privileges or have the owner temporarily transfer ownership then it should be possible.  ... View more

Hi @kapalczynski, You can look up the documentation ArcGIS Arcade in addition to Advanced Editing to help you get a better understanding of what the script is doing. Here are my answers to your questsions: The script above will trigger every time some hits submit and so long as whatever conditions are met. If you have multiple status types but you simply want to update the related record, then you would only need to have it to that if the record already exists then it will simply get updated. Updates in arcade look like the code below. var E = { 'edits':[{ 'className':'<featureclassname>', 'updates':[{ 'OBJECTID': $feature.RelObjID, 'attributes': Dictionary('RelFldA','Value','RelFldB','...')//If fields match then use the same as the original }] }] } Yes. The key is that the fields in one record must be mapped accordingly, otherwise the edits will not apply. I use Defaults as an example variable. You can replace it with anything that works for you. The script above is more of a general example but you can configure it to work however you like. Just make sure that the formatting is done correctly or the variables, fields, etc are the correct ones. If you need to the get the object id of the related record then change the script above to look like the one below. var FiltValue = $feature.RAMPID var Status = $feature.STATUS var OrigStatus = $originalfeature.STATUS var UpdteTble = FeatureSetByName($map,'<Name of table/featureclass>',['<fieldnames>'],False) UpdteTble = Filter(UpdteTble,'RAMPID = @FiltValue') /* var Values = Dictionary('STATUS', $feature.STATUS, fieldB, ValueB, ... ) */ var Defaults = { result: { attributes: {'STATUS': $feature.STATUS } } } var Edits = [] if( OrigStatus == 'OPEN' && Status == 'CLOSED' ){ var Changes = Dictionary('className','<TblName>') var TblDict = Dictionary() // Can use the same values in the values dictionary if the field names are the same if( Count(UpdteTble)==0 ){ Changes['adds'] = Dictionary('attributes',TblDict) } else if( Count(UpdteTble)==1 ){ var OID = First(UpdteTble).OBJECTID Changes['updates'] = Dictionary('OBJECTID',OID,'attributes',TblDict) } Push( Edits, Changes ) } if( Count( Edits ) > 0 ){ Defaults['edit'] = Edits } return Defaults   ... View more

Hi @AmyRoust . Try the following. var P = Portal('https://lawrenceks.maps.arcgis.com/') var Addr = FeatureSetByPortalItem(P, '0e4a33c0f05e483284f046c220b8f0c0',0,['*'],True) var Parcs = FeatureSetByPortalItem(P, '8cfd05010c2d4cc499cc701c91e3c2b0','*',['*'],True) var Test = [] for( var i in Parcs){ var N = First(Intersects( Addr, Geometry(i))) if( TypeOf(N)=='Feature' ){ N = Dictionary(N).attributes Console(N) Push(Test,N) } if( Count(Test) <= 10 ){Break} } If( Count(Test)>0){ Console(Concatenate(Test,'\n')) } You can play around with it in the Arcade Playground. ... View more

Hi @kapalczynski, You can definitely do this in Field Maps. You would simply need to configure the Field Calculation with a script similar to the one below. var FiltValue = $feature.RAMPID var Status = $feature.STATUS var OrigStatus = $originalfeature.STATUS var UpdteTble = FeatureSetByName($map,'<Name of table/featureclass>',['<fieldnames>'],False) UpdteTble = Filter(UpdteTble,'RAMPID = @FiltValue') /* var Values = Dictionary('STATUS', $feature.STATUS, fieldB, ValueB, ... ) */ var Defaults = { result: { attributes: {'STATUS': $feature.STATUS } } } var Edits = [] if( OrigStatus == 'OPEN' && Status == 'CLOSED' && Count(UpdteTble)==0 ){ var Changes = Dictionary('className','<TblName>') var TblDict = Dictionary() // Can use the same values in the values dictionary if the field names are the same Changes['adds'] = Dictionary('attributes',TblDict) Push( Edits, Changes ) } if( Count( Edits ) > 0 ){ Defaults['edit'] = Edits } return Defaults ... View more

Hi @LiveHus, I do not know if this is bug or not since there isn't enough information to be able to troubleshoot without knowing the client side configuration vs your portal configuration. Have you checked the following? (This is based on my previous knowledge since it has been sometime since I have messed with GeoEvent) Are both versions of your portal and the client the same or do they differ Does the service, when brought into the webmap, have all data required or is some of the data missing. Are the data types the same for the rotation field. i.e integer, float, double Have you tried switching from Geographic to Arithmetic to see if the results appear the same despite being the same field? If the answer to all questions is yes then it is likely a bug or a versioning/compatibility issue. Moreso a bug if everything else is working correctly. I have not messed with GeoEvent for some time since we use Velocity so it is difficult to say what the issue actually is. ... View more

Hi @KenBuja, Correct me if I am wrong but it might appear that @AmyRoust is referencing a grouped layer which, if it is setup correctly, should be a single service in which case the Within function should work. However, if it is created as separate feature services which are then grouped in the map then that would require a different work around. In which case @AmyRoust could try one of the following below. // Option 1: using union then the within function var FSets = [ FeatureSetByName($map,'ConditionalZoning'),['*'],True), FeatureSetByName($map,'LawrenceZoningDistrict'),['*'],True), FeatureSetByName($map,'DouglasCountyZoningDistrict'),['*'],True) ] var UnionSets = Union(FSets) var Address = $feature var Check = Within(Address,UnionSets) iif( TypeOf( Check ) == 'FeatureSet', Check, 'Nothing Within') // Option 2: looping through a list of layers and getting the appropriate values var FSets = [ FeatureSetByName($map,'ConditionalZoning'),['*'],True), FeatureSetByName($map,'LawrenceZoningDistrict'),['*'],True), FeatureSetByName($map,'DouglasCountyZoningDistrict'),['*'],True) ] var Address = $feature var TextValues = [] for( var fs in FSets ){ fs = FSets[i] var V = First(Intersects(Address,fs)) if(TypeOf(intfs)=='Feature'){ Push(TextValues,V['<fieldname>']) } } iif( Count(TextValues)>0, Concatenate(TextValues,'\n'), 'Address does not fall within') ... View more

Then it might helpful then to use the intersects function to get the information that you need. It may also require that you loop through multiple features to get a dictionary of field values to pull from. ... View more

Hi @LiveHus, Just out of curiosity, have you tried publishing the service as a reference with the rotation of the symbols as part of the service. It could be a bug but sometimes publishing a referenced source offers more control of symbology than the typical portal map. ... View more

Hi @AmyRoust, So the within function returns a feature set of the features that fall within the specified layer. If you have an instance where some layers may overlap others then what I might suggest is any of the following. var FS = FeatureSetByName($map, 'Zoning Districts - Lawrence Zoning District',['ZoningDistrict'],True) var Address = $feature if( TypeOf(Geometry($feature)) == 'Polygon' ){ Address = Centroid($feature) } var AddrWithin = Within(address,FS) iif( Count(AddrWithin)>0, AddrWithin, 'No features are within the layer') /* Note: the intersects function can also be used if the input layer is a point feature. */ ... View more

My recommendation is to test whether the feature geometry has changed in comparison to the field values. var fx = $feature.UTM_X var fy = $feature.UTM_Y var G = Geometry($feature) if( G.x != fx && G.y != fy ){ return { result: { attributes: Dictionary('UTM_X',G.x,'UTM_Y',G.y) } } } /* Note: the code above will update both fields with the changed values if there are values that have been updated in the field. */ That way it will only need to compare the latest changes to the geometry change. If there is a change it will update accordingly. ... View more