POST
|
I'm loving the new Geocoder Widget, but two issues are preventing me from using in production. I'm using 3.3, but get the same results with 3.4 at http://help.arcgis.com/en/webapi/javascript/arcgis/sandbox/sandbox.html?sample=locator_widget My extent is New York. 1. When the user first types an address, e.g. '19th st and 6th ave', no results are returned initially. If the user then presses a space, the search is repeated and a list of candidates is returned. Hitting backspace to remove the space and repeat the search, the list is preserved. Occasionally I have gotten a single result after the first search for a 'St Anne' address, which made me think that the search is being sent too quickly. But I tried setting searchDelay to a much larger number, with no improvement. 2. With autoNavigate set to true, sometimes, under conditions I can't precisely determine, once a user has a list of results, using arrow keys and then hitting the enter key fills the search box with the selected item but does not autoNavigate. Clicking the result with the mouse in these situations has the same effect. Any ideas? Here is the init function which when pasted into the sandbox above yields these results: function init() {
var map = new esri.Map("map",{
basemap: "topo",
center: [-74,40.73], //long, lat
zoom: 13
});
geocoder = new esri.dijit.Geocoder({
maxLocations: 10,
autoComplete: true,
map: map,
arcgisGeocoder: {
url: "http://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer",
name: "Esri World Geocoder",
suffix: "new york, ny",
placeholder: "Find a place",
sourceCountry: "USA" // limit search to the United States
}
},"search");
geocoder.startup();
}
... View more
04-28-2013
05:18 PM
|
0
|
0
|
595
|
POST
|
Thanks for the reply. I thought of option #2 but the task didn't warrant the effort. Your observation about process is a good one but in my current special case it's unavoidable. I was about to try your first suggestion but then option #3 reminded me that all along I hadn't been using my 64-bit geoprocessing, because it only works on background geoprocessing, and that running things in foreground (which I was doing for easier debugging from the message window) might very well be the problem. So I ran in background, and voila, no more GDI objects created. Thanks!
... View more
04-17-2013
06:20 PM
|
0
|
0
|
216
|
POST
|
Hello, I've got an arcpy script that essentially iterates over a polygon feature class and for each polygon extracts a raster, users RasterToNumPyArray to create a NumPy array, then does a few things with the values and writes to a postgres db. Everything works fine for small numbers of features. Despite using del to destroy variables at the end of each loop (following ArcGIS help at http://resources.arcgis.com/en/help/main/10.1/index.html#//002z00000028000000), this script generates large numbers of GDI objects (which I view in Task Manager), probably because of RasterToNumPyArray, and generally exceeds the default Windows maximum of 10000 after 2-300 polygons. This causes ArcMap to crash entirely. To deal with this, I changed the GDI object quota on my machine, but this is obviously not a longterm solution: http://msdn.microsoft.com/en-us/library/ms724291(v=vs.85).aspx I'm using ArcGIS 10.1 for Desktop SP1; there was a related bug fixed in a 10.0 service pack: http://support.esri.com/en/bugs/nimbus/TklNMDYzNjU2 My question is: what is the preferred strategy for avoiding GDI Object overruns (ie memory leaks), other than using del to explicitly destroy variables (which doesn't seem to work), with particular reference to RasterToNumPyArray? Has anybody else run into this? Best, Kim
... View more
04-15-2013
06:22 AM
|
0
|
2
|
467
|
POST
|
Thanks; it does indeed help. I'd forgotten that approach. I've used it with modest success; for immediate purposes, it gets me something with enough precision to use. Appreciate the help. But it doesn't quite equal what I can measure via the OS, it doesn't as you observe take compression into account, etc. Seems to me this would be a basic Data Management tool ESRI should offer out of the box, especially since they seem to do it internally -- looking at the properties of any given raster gives you uncompressed size on disk.
... View more
08-14-2011
12:46 PM
|
0
|
0
|
1771
|
POST
|
Hello all, I have a script that requires an input raster. I would like to get the size on disk of this raster, whether it be stored in files or gdb of whatever flavor, and in whatever raster format. I cannot find a built-in gp/arcpy function for this -- neither Describe() nor GetRasterProperties() seem to provide it. I know about os.path.getsize() and could write a function to find the size of a directory, but not inside a personal/enterprise gdb, and anyway writing a function to anticipate every possible raster format and storage location format seems like a daunting task. Has anybody done this already, or have suggestions about a good approach? Thanks, Kim Fisher
... View more
08-12-2011
02:30 PM
|
0
|
7
|
4854
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|