|
POST
|
I have a series of points that I have buffered and generated as Circles. I now want those circles to be used to select features from my featureLayer. I'm getting stuck on the input geometry, because Circle is not in the list of acceptable geometry types for Query. It lists Extent, Point, Multipoint, Polyline, or Polygon I need to be precise, so I don't want to just use the extent of the circle as my input. I assume there is a way to convert my circles to polygons, but I haven't figured out how to do it yet.
... View more
12-12-2014
08:00 AM
|
0
|
7
|
7216
|
|
POST
|
That works, thanks. I'm not sure what the documentation means for the syntax I was trying.
... View more
12-12-2014
07:46 AM
|
0
|
1
|
1382
|
|
POST
|
I am buffering points and I want to put the attributes of original point on the resultant buffer polygon. I also want to add an extra attribute for 'source' to indicate which layer I was buffering. The graphic is getting the feature.attributes from the original point. I thought I could use graphic.attr('name','value') to add the extra attribute I want. It doesn't seem to be doing anything. It's not generating any error either. Is this not the proper method? //create a buffer graphic for every point
function generateBufferGraphic(features){
bufferLayer.clear();
var radius = registry.byId("bufferSelect").value;//user can select buffer distance
var idPoint,circle;
arrayUtils.forEach(features, function (feature){
idPoint = feature.geometry;
circle = new Circle({
center: idPoint,
geodesic: true,
radius: radius,
radiusUnit: "esriMiles"
});
var graphic = new Graphic(circle, bufferSymbol,feature.attributes);
graphic.attr('source','layername');
bufferLayer.add(graphic);
});
}
... View more
12-12-2014
06:47 AM
|
0
|
3
|
3482
|
|
POST
|
I had no luck opening the fiddle.jshell.net in my IE 8. It's just empty. It could be something that is getting suppressed. The security group is constantly having to tighten what gets through the firewall. When I tried that style, it looks like this:
... View more
12-11-2014
06:16 AM
|
0
|
1
|
2195
|
|
POST
|
What version of IE? The State users have IE 8. It doesn't work there. The padding addition helped in all the other browsers.
... View more
12-10-2014
11:15 AM
|
0
|
3
|
2195
|
|
POST
|
You're right, it's OK in Chrome. I"m seeing it in Firefox. Unfortunately I need this to work in multiple browsers.
... View more
12-10-2014
10:19 AM
|
0
|
6
|
2195
|
|
POST
|
I'm always open to suggestions, especially when it comes to styling. Most of the time it's the one combination you haven't tried yet that is the answer.
... View more
12-10-2014
10:08 AM
|
0
|
0
|
3013
|
|
POST
|
That's closer, but now it's pushed the top choice all the way over to the right, so that all you see is part of the first address number.
... View more
12-10-2014
10:05 AM
|
0
|
8
|
3013
|
|
POST
|
Nope, that was one I tried before I even posted the question. I'm wondering if I can use a dojo/query to change the height of the titlePane, assuming that 'suggest' is something that I can listen for.
... View more
12-10-2014
09:25 AM
|
0
|
3
|
3013
|
|
POST
|
There are instances where the user benefits from having more than one pane open at a time. Rather than go with a mix accordion and title, I just always use TitlePanes. I tried the style change, it didn't help. I feel like that's where the change needs to happen, I just haven't discovered which style I need to set.
... View more
12-10-2014
09:11 AM
|
0
|
5
|
3013
|
|
POST
|
I have all my tools stored in TitlePanes within a ContentPane as a side panel so the users can have more than one set of tools open at a time. I have my geocoder in a titlePane and it looks fine until I start to enter something. The suggestions aren't showing well. You can sort of see them, but mostly there are cut off and the user gets scroll bars to deal with. It seems like I ought to be able to set a style on the geocoder, but I haven't figured out which style it is. I tried .simpleGeocoder .esriGeocoderResults, which seemed likely, but that didn't fix this. I tried adding a z-index, but that didn't do anything. <div id="rightPane" data-dojo-type="dijit/layout/ContentPane" data-dojo-props="region:'right',splitter:true">
<div id="tp_geocode" data-dojo-type="dijit/TitlePane" data-dojo-props="title:'Identify District by Address', closable:false, open:true">
<div id="geocodeDiv"> </div>
</div>
</div>
... View more
12-09-2014
02:40 PM
|
0
|
18
|
6586
|
|
POST
|
I'd say my results are still rather random. For example, the zip 65043, works. But that doesn't take care of everything. When I try this address: 2727 N Main St, Sikeston, MO, 'suggest' offers that address. Great, I think it's works! But, when I click to complete the search, it takes me to Missouri Valley, Iowa. I'm sure that's a very nice place, but not the one I'm searching for. There is definitely a difference between suggest and find.
... View more
12-05-2014
06:17 AM
|
0
|
0
|
1086
|
|
POST
|
I'm not sure I understand exactly what Kelly is saying, but maybe there are parameters that are honored in the 'find', that are ignored at the point while it's still in 'suggest' mode? I've tried several variations of sourceCountry and suffix as a parameter for my Geocoder definition, but nothing refines both the suggestions and returned results. I ended up taking them out, because it didn't look like it was helping. In your screenshot, you are getting completely different suggestions compared to what I have seen. Again, I have to wonder why. Is it the scale threshold you're at when you enter the ZIP? You're obviously not centered on Missouri, so it's not an extent. Somewhere in the calls and responses something is broken. Hopefully it will be fixed in the next release (the standard answer we all take with a grain of salt).
... View more
12-04-2014
02:45 PM
|
0
|
3
|
1086
|
|
POST
|
Yes, I'm using version 3.11. The versions of the API change so fast, it's hard to keep track of the threads that might relate to an older version. I'm trying to figure out what's going on behind the scenes. Shouldn't this work for ZIP codes? I've been using Locator this whole time, because I feel like I get less flaky results compared to the Geocoder dijit. Working with state-wide data, users want to be able to enter a ZIP to get to a particular part of the state. In my example, 65043, it returns just a set of codes for Brazil: If I then click to search, it does take me to the right location in central MO, not Brazil. If I try the same search again, this time I get the match in the list of choices along with all those Brazil codes. Why? I started out centered on the state in the first place, so I would think that extent and the sourceCountry would be enough to limit to US ZIP codes. Here is my code. It's basically the example from Geocoder widget | Guide | ArcGIS API for JavaScript <!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="viewport" content="initial-scale=1, maximum-scale=1,user-scalable=no"/>
<title>Geocode Dijit</title>
<link rel="stylesheet" href="http://js.arcgis.com/3.11/esri/css/esri.css">
<style>
html, body, #map {
height:100%;
width:100%;
margin:0;
padding:0;
}
#search {
display: block;
position: absolute;
z-index: 2;
top: 20px;
left: 74px;
}
</style>
<script type="text/javascript">
var djConfig = {
parseOnLoad: false
};
</script>
<script src="http://js.arcgis.com/3.11/"></script>
<script>
var map, geocoder;
require(["dojo/parser","esri/map", "esri/dijit/Geocoder", "esri/layers/GraphicsLayer","esri/graphic",
"esri/symbols/SimpleMarkerSymbol","esri/InfoTemplate","dojo/_base/Color", "dojo/_base/array", "dojo/dom",
"esri/request", "dojo/domReady!"
], function(
parser,Map,Geocoder,GraphicsLayer,Graphic,SimpleMarkerSymbol,InfoTemplate,Color,arrayUtils,dom,esriRequest
) {
parser.parse();
var symbol = new SimpleMarkerSymbol();
symbol.setStyle(SimpleMarkerSymbol.STYLE_CIRCLE);
symbol.setColor(new Color([255,128,0,0.75]));
// create the map
map = new Map("map",{
basemap: "topo",
center: [-92.593, 38.5],
zoom: 7,
});
// create the geocoder
var geocoder = new Geocoder({
autoComplete: true,
map: map,
arcgisGeocoder: {
placeholder: "Find a place",
sourceCountry:"US",
}
}, dom.byId("search"));
geocoder.startup();
geocoder.focus();
geocoder.on("select", showLocation);
function showLocation(evt) {
map.graphics.clear();
var point = evt.result.feature.geometry;
var graphic = new Graphic(point, symbol);
map.graphics.add(graphic);
// map.infoWindow.setTitle("Search Result");
map.infoWindow.setContent(evt.result.name);
map.infoWindow.show(evt.result.feature.geometry);
}
geocoder.on('clear', function (evt){
map.graphics.clear();
map.infoWindow.hide();
});
});
</script>
</head>
<body>
<div id="search"></div>
<div id="map"></div>
</body>
</html>
... View more
12-04-2014
01:56 PM
|
0
|
6
|
2851
|
|
POST
|
I can't believe how confusing this is. It doesn't look to me like the esriRequest for the preCallback is doing anything, or at least nothing to fix the issue of suggested matches outside the US. I'd also like to see this work for a ZIP code search. When you try that, you see some conflicting feedback. For example, 65043. If I just enter that, I get a whole bunch of suggested locations in Brazil. But if I click the find icon, I am properly taken to the location I expect in central Missouri. The users are going to LOVE that. I tried adding a suffix of Missouri, but that just gives additional confusing results. Is this part of the bug?
... View more
12-04-2014
01:31 PM
|
0
|
8
|
2851
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 06-02-2017 02:38 PM | |
| 2 | 03-18-2022 10:14 AM | |
| 2 | 02-18-2016 06:28 AM | |
| 1 | 03-18-2024 07:29 AM | |
| 4 | 08-02-2023 06:08 AM |
| Online Status |
Offline
|
| Date Last Visited |
02-25-2025
01:56 PM
|