|
IDEA
|
Hi @AJR, So when it comes to displaying large datasets where you simply want to view a small subset of that dataset, then I would highly recommend creating a query layer so that it only pulls records based on what parameters you set and it can also limit the number of records that get returned. A query layer, if you don't know, can directly access a database table and pull records using a SQL query rather than trying to connect to the database and read the records in pro. Just a suggestion.
... View more
04-08-2026
12:40 PM
|
0
|
0
|
527
|
|
POST
|
Hi Matt, An option that you can try is using linear referencing to pick an approximate location rather than using an address. It works similar to addressing but will locate using a specified distance along a route using the address number rather than a full address. You can build that as part of the addressing so that locations can be identified at set intervals along routes.
... View more
04-08-2026
12:38 PM
|
0
|
0
|
261
|
|
POST
|
As @KenBuja has mentioned, It isn't atypical for arcade to pull the first record which makes testing difficult. Try Filtering for any other record to see if you get the same result. If not then that points to the fact that the first record simply either exists outside of the image(ry) and cannot get the pixel value or it is something else.
... View more
03-04-2026
01:08 PM
|
1
|
0
|
965
|
|
IDEA
|
You could simply create a dummy hosted service for the sole purpose of using it as a markup layer. We have done that from time to time and it also helps that we can download that layer if needed for other things.
... View more
03-03-2026
10:35 AM
|
0
|
0
|
710
|
|
POST
|
Hi @wizgis, So one of the many recommendations, especially when it comes to having multiple layers, is to have the layers published separately rather than all at once. The reasoning behind that is there might be some layers that are more intensive processing wise than others which could potentially consume more resources. The other things to check are: Drawing scale: Some layers drawn at higher extents will consume more resources than those drawn at lower extents. Sample Records or Maximum Return Records: This will determine how many records will be read and displayed by the server and the higher this number is the more resources will get consumed. Coded domains: If there are not many coded domains then try diminishing the count. Tile service: Try publishing a tile service vs a regular map service since tile services typically render faster since the pyramids are manually created using the data rather than dynamically. Try the options above and see if that improves the performance of your map services.
... View more
03-03-2026
10:33 AM
|
3
|
0
|
927
|
|
POST
|
I think the erase tool may help to some extent also. That might indicate which one is not the duplicate but I would need to test that. Another option is to run the frequency tool on both datasets and do a comparison that way. Otherwise, assuming the addresses have matching values, @DanPatterson recommendation would be best.
... View more
03-03-2026
10:24 AM
|
0
|
0
|
561
|
|
POST
|
Hi @MarkChambers1, I personally have never used Monitor before but I did some simple calculations and the only thing that I can think of is that Monitor may be looking at the different view states whereas your sql table might be the base table. Try comparing the total number of records the sql table but look under views and see if those record totals match what Monitor is looking at. We look at the view table rather than the base table to see how many active records exist before the base table is updated.
... View more
03-03-2026
10:21 AM
|
0
|
1
|
524
|
|
POST
|
Hi @RemWilson, Have you tried using any of the options below: Using an arcade field calculation to generate the necessary polygons. This may work for some features but if there are any records that lack any geometry then that could also return an error. Running python to generate the polygons. The other thing I would recommend checking is if there might be some slight change in the permissions since this can also cause some minor issues at times.
... View more
03-03-2026
10:18 AM
|
0
|
0
|
500
|
|
POST
|
Hi @JuliaReisemann_3J Is your data hosted because, as unfortunate as this might seem, it isn't unusual for hosted services to have some minor corruption. There isn't really a fix for that but if there is calculated geometry information that can referenced or scraped then that might be the only fix.
... View more
03-03-2026
10:13 AM
|
0
|
0
|
342
|
|
POST
|
Hi @TinaKwitkoski, So there a couple of things to check: The full extent. It might be possible that some are not drawing given that either the feature layer drawing might be set too low so that only a handful are showing. The extent in the tool may have been manually set which could be why some are not showing. Try updating that to see if that fixes the issues. It might be that some of the attributes are not populated so that could be it also. Is there a definition query on a layer. Check those and if that doesn't fix your issue then it might be something else.
... View more
02-24-2026
12:59 PM
|
1
|
0
|
1057
|
|
POST
|
Thank you very much @MDB_GIS, I will be sure to test this out and see how this works to align with our CAD coordinate system since that has been somewhat of a boondoggle.
... View more
02-16-2026
07:17 AM
|
0
|
1
|
1460
|
|
POST
|
You can also use the following: vr G = Geometry($feature) ; var Paths = G.paths:
for( var p in Paths ){ var lastpnt = p[-1] ; console(lastpnt ) }
... View more
02-11-2026
11:19 AM
|
0
|
1
|
665
|
|
POST
|
Yes. Simply because tenants may vary but generally the building will have similar utilities and safety requirements. We have it setup so the building will primarily house anything regarding safety but the tenants will have their own unique attributes. Both the building footprint and tenant table schemas are nearly identical. This is to identify if a building is the same as a tenant or if it houses multiple tenants. It also keeps the data clean and easily configurable. The other thing to consider is, as tenants are vacated in multi-tenant buildings, then that may impact other workflows such as addressing, billing, etc. We are working to create a dynamic addressing system so that instead of maintaining points, instead we will use a tool that will derive the information from the attributes and construct temporary address points.
... View more
02-11-2026
07:29 AM
|
0
|
1
|
525
|
|
POST
|
We had this exact conversation since I had been tasked with overhauling our preplan solution. We tried using the Esri solution, but that solution will only work if: You have clean data to work with or are starting from scratch You are not having to consolidate several datasets into a single working dataset The addresses, buildings, and anything else is updated in a timely manner The workflow we created is we built ours in house in our enterprise sde and are using the building footprints as the base working feature and have it setup in this manner: Building Feature/Footprint (polygon fc) Property Table The table is related to the building feature using a single numerical field The relationship created is a one to one Tenant Table The table is related to the building using the building id as the relational field The relationship to the building is a one to many
... View more
02-10-2026
08:02 AM
|
0
|
3
|
556
|
|
POST
|
In this case then you wouldn't need multiple datasets but rather a single featureset to return a basic table of values to filter by. You would need to construct a basic featureset, like the example below, so that it only returns a single table of records. This will require fields to be manually specified for the new featureset table, and the attributes must map accordingly. function SetFields(N,T,L){
var b = 'esriFieldType'; var types = ['Integer','Double','String','Date']
var V = When(
Includes(types,T) && T=='String',{name:N,type:b+T,'length':L}
,Includes(types,T) && T!='String',{name:N,type:b+T}
,Null
)
return V
}
var Fields = [
SetFields('ExampleA','String',25)
,SetFields('ExampleB','Integer',Null)
]
var Values = []
for( var row in somefeature ){
var attvals = {'ExampleA':'Something','ExampleB':1}
Push(Values,{attributes:attvals}
}
var FS = FeatureSet(Text({
'fields': Flds
,'geometryType': ''
,'features': Values
}))
return FS @KenBuja might be able to add to this in case I left something out. If you need to add a spatial component then you would simply need to pull that once. The configuration to add a spatial component has a similar structure but requires other spatial information to be returned. Here is a simple function for simply creating a union of multiple features, assuming they are the same geometry. function GetFSGeoms(InFS){
var Poly = []
for (var f in InFS) { var e=Geometry(f) ; if(!IsEmpty(e)){ Push(Poly,e) } }
iif(Count(Poly)>0,Union(Poly),Null)
}
... View more
02-10-2026
06:09 AM
|
1
|
1
|
739
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 05-07-2026 01:36 PM | |
| 1 | 02-10-2026 06:09 AM | |
| 1 | 03-04-2026 01:08 PM | |
| 1 | 02-24-2026 12:59 PM | |
| 3 | 03-03-2026 10:33 AM |
| Online Status |
Offline
|
| Date Last Visited |
Wednesday
|