|
POST
|
The LayerList also honors the title option in the layers array, I find that helpful for individual feature layers: var layerList = new LayerList({
map: mapMain,
showLegend: true,
layers: [{
layer: lyrSide,
title: "Sidewalks",
},
{
layer: lyrBike,
title: "Bicycle Lanes",
},
{
layer: lyrTrans,
title:"Transit Lines"
},
{
layer: lyrShlt,
title:"Sheltered Stops"
},
{
layer: lyrStops,
title:"Transit Stops"
}]
//layerInfo
}, "layerListDiv");
... View more
05-19-2016
01:34 PM
|
2
|
2
|
4780
|
|
POST
|
Hi Phu - Yes direct connect to 10.4 user geodatabases. Yes Sql Native Client. Yes we have geometric networks... I can't give you step by step on how to configure the raids, our IT group handled that but I will get back to you with the specs
... View more
05-18-2016
09:58 AM
|
2
|
0
|
2945
|
|
DOC
|
Maybe a bug? I checked to add the results as an operational layer and the results popup info window now populates, but does not populate when I do not add the result as an operational layer . . .
... View more
05-12-2016
10:57 AM
|
0
|
0
|
9500
|
|
DOC
|
Hi Robert - I'm sure I've overlooked something simple, but since I added this update the results info window popup is not displaying results - i.e. its blank. I just updated eSearch in my stemapp, saved my configs, removed and added the new build to my apps and replaced the configs. Am I missing something? Thanks David
... View more
05-12-2016
09:49 AM
|
0
|
0
|
9500
|
|
POST
|
Hi all- we just completed our production migration to windows server 2012 r2 running sqlserver 2014. For the server architecture, we increased our bytes per cluster (for all drive sectors in the RAID) to 64K, and we left hyperthreading (no more gsrv to worry about) enabled. Same memory as our sever 2008 r2 box, 64gb but now 16 logical processors as opposed to the physical 8. We updated all the sde instances to 10.4 and I must say we are quite pleased. Editing has been going really well, snapping is working really well, draw times are very fast. The autogrid spatial indices are behaving really well. Connections are faster. David
... View more
05-11-2016
02:18 PM
|
6
|
2
|
2945
|
|
POST
|
So it turn out that there is no issue with our COMODO Cert. The issue is in the SSL cipher type we are employing. We are employing ECDHE ciphers in response to the Log Jam vulnerability, instead of increasing the bit key size of our DHE cipher to 2048. Currently AGOL portal does not accept ECDHE, so our EIT team reverted the web server hosting our web adaptor back to a DHE key and moved the server to another switch.
... View more
05-09-2016
12:05 PM
|
0
|
0
|
1870
|
|
POST
|
Hi Bryan - Yes I just discovered all this as well and you are correct, no RSS feed on the new support page as far as I can tell either. In fact, I had difficulty finding patches and service packs at all on the beta page, had to revert back to the current page
... View more
05-06-2016
11:08 AM
|
0
|
1
|
4640
|
|
POST
|
Oh there it is, thanks Bjorn - don't know how I missed that!
... View more
05-06-2016
11:05 AM
|
0
|
0
|
4022
|
|
POST
|
Hi Bjorn - I'm assuming the available widgets will increase as they are migrated? In particular, Directions, Print, Basemap Gallery, LayerList? Thanks David
... View more
05-04-2016
02:18 PM
|
0
|
2
|
4022
|
|
DOC
|
Thanks Robert, yes if I am understanding this correctly: if a layer has field(s) visibility configured as 'false' in the AT AND that layer participates in the eSearch, the eSearch will override any 'false' setting and make those fields visible by default when a user displays the layers' attributes in the AT. When the eSearch opens the AT with a result, the visible fields are those configured as true in the eSearch. It's ok, I just could not figure out why no matter how I set AT fields visibility, all fields would continue to display for layers that also participate in eSearch. And of course now I can compensate when needed- Thanks!
... View more
04-26-2016
07:18 AM
|
0
|
0
|
9500
|
|
DOC
|
Are you also saying that even if I am not configuring the layer to interact with the AT that, the AT will still display all fields, because that's what I am seeing as well.
... View more
04-25-2016
08:51 AM
|
0
|
0
|
9692
|
|
DOC
|
Hi Robert - I may have noticed a potential conflict between eSearch and Attribute Table widgets. This will take more testing, but I think that when a layer participates in the eSearch widget, the attribute table widget column visibility settings are overridden, i.e all columns are visible. For layers that do not participate in eSeach, attribute table settings apply . . Thanks David
... View more
04-25-2016
07:40 AM
|
0
|
0
|
9692
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 07-01-2026 05:41 AM | |
| 1 | 06-26-2026 12:39 PM | |
| 6 | 06-25-2026 07:23 AM | |
| 1 | 06-17-2026 06:04 AM | |
| 1 | 06-08-2026 08:37 AM |
| Online Status |
Offline
|
| Date Last Visited |
Thursday
|