|
POST
|
You may want to update the StatisticDefintion objects before assigning it on to query parameters.
... View more
08-17-2016
08:00 AM
|
1
|
0
|
3670
|
|
POST
|
While populating the searchParams you are storing the featureLayer property as url, and the same is assigned to sources. The featureLayer has to be of type FeatureLayer. Try this. searchParams.push({
featureLayer: new FeatureLayer(finalurl),
name: myData[i].Fname
});
... View more
08-16-2016
05:40 AM
|
2
|
3
|
2884
|
|
POST
|
It would be helpful, if you could share something, I have been replying with lot of assumptions, and I will not be able to confirm if something is wrong or correct.
... View more
08-15-2016
07:47 AM
|
0
|
0
|
2604
|
|
POST
|
The ids in linkedQuery are supposed to be empty while configuration and should be populated automatically. After looking into the implementation, I found there is an undocumented property required for this to work. You need to add linkField with fk field. linkField: "fk field",
linkedQuery: {
url: "<LayerA url>",
type: "spatial", //you could probably use more of the queryParameters options like outfields etc
idProperty: "pk field",
ids: []
}
... View more
08-15-2016
06:51 AM
|
1
|
0
|
2604
|
|
POST
|
Think like, you are queying tableB with a relation/linkedQuery to LayerA. and not the other way around. Without you sharing you configuration, I cannot confirm but,your configuration should look something like below //only the layers section
layers: [{
name: "LayerA&TableB",
.
.
queryParamerters:{
type:"table",
url: "<tableB url>",
.
.
},
attributeSearches:[{
name: "Search for TableB fields",
searchFields: [{tableBField options}],
gridOptions: {
columns: [],
sort: []
}
}],
linkedQuery: {
url: "<LayerA url>",
type: "spatial", //you could probably use more of the queryParameters options like outfields etc
idProperty: "pk field",
ids: []
}
}]
... View more
08-12-2016
05:33 AM
|
0
|
0
|
5261
|
|
POST
|
You can use polygonBarriers instead of point barriers. Convert the points to polygon by using geometryEngine.buffer function.
... View more
08-09-2016
01:34 PM
|
0
|
0
|
627
|
|
POST
|
I don't have the set or the layer table relation. If you attach you config file with search configuration, updated to best of you knowledge. I could look and fix/add the linkQuery for you. Or @Tim McGee can help you.
... View more
08-09-2016
01:12 PM
|
0
|
0
|
2657
|
|
POST
|
The map navigation is maintained within a module call MapNavigationManager. The keyboard panning is a hard-coded value of 10 (Surprised that its hard-coded !! ). Map resolution (zoom level) is also considered. The pan behaves differently for different projection system. For Projected Coordinate system, it ends up moving little. If you are hosting the api locally, you could update the values. It can be found in the function "_keyDown". If you are using a CDN vesion, then you could use dojo/aspect to hack in to the function and update the dx and dy. Make sure you require "dojo/aspect" and "dojo/keys". aspect.before(map.navigationManager, "_keyDown", function(evt){
var keyCode = evt.keyCode;
switch (keyCode) {
case dojoKeys.UP_ARROW:
case dojoKeys.NUMPAD_8:
this._keyDy += 100;
break;
case dojoKeys.RIGHT_ARROW:
case dojoKeys.NUMPAD_6:
this._keyDx -= 100;
break;
case dojoKeys.DOWN_ARROW:
case dojoKeys.NUMPAD_2:
this._keyDy -= 100;
break;
case dojoKeys.LEFT_ARROW:
case dojoKeys.NUMPAD_4:
this._keyDx += 100;
break;
case dojoKeys.PAGE_UP:
case dojoKeys.NUMPAD_9:
this._keyDx -= 100;
this._keyDy += 100;
break;
case dojoKeys.PAGE_DOWN:
case dojoKeys.NUMPAD_3:
this._keyDx -= 100;
this._keyDy -= 100;
break;
case dojoKeys.END:
case dojoKeys.NUMPAD_1:
this._keyDx += 100;
this._keyDy -= 100;
break;
case dojoKeys.HOME:
case dojoKeys.NUMPAD_7:
this._keyDx += 100;
this._keyDy += 100;
break;
default:
break;
}
return arguments;
});
... View more
08-09-2016
01:04 PM
|
3
|
0
|
1135
|
|
POST
|
In a way yes, the Search Widget in the below link already uses the "Attribute Table" widget (its a dependency for Search Widget). cmv-widgets/widgets/Search at master · tmcgee/cmv-widgets · GitHub
... View more
08-09-2016
12:20 PM
|
2
|
0
|
2657
|
|
POST
|
You can use the linkedQuery option to do that. This option is part of AttributeTable. But you can add it to the search layer or attributeSearches properties depending on your configurations for the search. If you add it to layer, it will apply for all attributeSearches, or you can have different one for each attributeSearches. so your configuration should have something like below. the layer will contain the table B details and the linkedQuery will contain layer A details. I hope the pk and fk are same names. linkedQuery: { url: layer A url, idProperty: fk, ids: [] // if linkedQuery, then store the linkedIDs for use in linked query }, Hope this works out.
... View more
08-09-2016
11:09 AM
|
1
|
0
|
2657
|
|
POST
|
How are you displaying the table? Are you using the user contributed widget "AttributeTable" or "Search widget" ?
... View more
08-09-2016
09:40 AM
|
0
|
0
|
2657
|
|
POST
|
You can use setContent method. Checkout this tutorial, mainly using custom function section. Format info window content | Guide | ArcGIS API for JavaScript 3.17
... View more
08-08-2016
01:08 PM
|
2
|
0
|
788
|
|
POST
|
I get what the issue is, The offset happens only when you pan the map. If zoom or change the level, the issue does not occur. Its because, whenever we pan, the 0,0 location of the map/layer is offset and that information is missing while scaling. To overcome that, add the following to maintain a variable with map delta offsets. var mapDelta;
map.on("extent-change", function(evt){
console.log(JSON.stringify(evt.delta));
if(!evt.levelChange && mapDelta){
mapDelta.x += evt.delta.x;
mapDelta.y += evt.delta.y;
} else {
mapDelta = evt.delta;
}
}); Now the scaling logic will looks like below screenPoint.x = (refPnt.x + mapDelta.x) + ((screenPoint.x - (refPnt.x + mapDelta.x)) * scaleX);
screenPoint.y = (refPnt.y + mapDelta.y) + ((screenPoint.y - (refPnt.y + mapDelta.y)) * scaleY);
... View more
08-08-2016
11:02 AM
|
2
|
0
|
1827
|
|
POST
|
The logic for scaling is working correctly. If I comment the line where you are using geometryEngine.offset. The Red graphic and the editor graphic seems to match.
... View more
08-05-2016
12:38 PM
|
0
|
3
|
1827
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-24-2017 07:15 AM | |
| 1 | 09-13-2016 06:27 AM | |
| 1 | 05-21-2015 08:06 AM | |
| 1 | 12-16-2015 05:43 AM | |
| 1 | 07-20-2015 09:33 AM |
| Online Status |
Offline
|
| Date Last Visited |
Wednesday
|