Latest Contributions by derekswingley1

If you look at the source for the sample, you'll see the following: var from_segs = document.getElementById("from_text").value.split(","); var from_addr = { Address: from_segs[0], City: from_segs[1], State: from_segs[2], Zip: from_segs[3]}; There is similar code for the "to" address. What that means is that the sample expects addresses in a  specific format- all pieces of the address need to be comma separated. This is not ideal but it's how the geocoding/locator service used in the sample works. If you change your addresses to "3730 Allendale Circle, Pittsburgh, PA, 15204" and "3600 Forbes Ave., Pittsburgh, PA, 15261" the sample works (although routing did takes more than a few seconds for me...). ... View more

Hi Mark, I believe we fixed this at 2.4. Check out the What's New in 2.4 doc, specifically under bug fixes towards the bottom: The editor widgets (attribute inspector, editor etc) display a default value of 1/1/1970 for null date fields. Null date values should display as null instead of the default date. (NIM070071) Can you test with 2.4 and confirm? ... View more

By providing a variable name in the function declaration (line 30), you can refer to variables passed to the function as named variables (line 32). This is for readability and convenience. If you didn't do this, you would have to rely on the function's arguments array. Since addTileMap is passed to TiledMapServiceLayer as a callback, addTileMap is called when the layer loads and the newly loaded layer is passed to addTileMap as an argument. ... View more

Personally, I'd rather see the info window accomodate the map rather than the map moving around. But maybe that's just because I've worked with this API so much and I'm just used to that behavior. I also like the sidebar approach. The info window has four possible orientations: upper left, upper right, lower left and lower right. To figure out where to show it, the map is divided into four quadrants. If the anchor point for the info window is in the upper left, display the info window pointing to the lower right. If the anchor point is in the lower left, display the info window pointing to the upper right. Basically just show it so that it displays opposite the quadrant that was clicked so that the entire info window is visible. ... View more

You're correct in that your dynamic service cannot be displayed on top of your feature layer. Feature layers (and graphics layers) always display on top of dynamic and tiled map services. I can suggest a couple of approaches for showing labels: -continue to use your dynamic map layer for labels and use a fully or semi-transparent fill on your parcel boundaries feature layer -continue to use your dynamic map layer for labels and set one up for your parcel boundaries as well then create a feature layer with SELECTION mode for interaction with features -generate a label points layer, create a feature layer from it and symbolize with a text symbol (scale dependencies would be important here, there might be performance issues with lots of labels) ... View more

Instead of panning the map, the map opens the info window so that it is completely within the map. This isn't exactly what OP asked for but figured I'd put it out there anyway... ... View more

Steve's approach works, but why not use map.getInfoWindowAnchor? It's demonstrated one of the queryTask samples. ... View more

Do you see any messages in the Firefox or Chrome JavaScript console when you load the layer? Does this layer have a visible ObjectID field? Specifically, do you see an ObjectID field when you look at the layer via the services directory? Any chance you can provide a link to your services directory and/or your app? ... View more

I would try to explain why displaying large, complex geometries in a web app is a bad idea. Use these blog posts for evidence: http://blogs.esri.com/Dev/blogs/arcgisserver/archive/2011/06/13/Feature-layers-can-generalize-geometries-on-the-fly.aspx http://blogs.esri.com/Dev/blogs/arcgisserver/archive/2011/06/23/Determining-limits-for-map-graphics.aspx ... View more

You're talking about the tooltip that follows the mouse cursor when a tool from a drawing toolbar is active? If you want to change the appearance of those tooltips, you can do with with css and the .map .tooltip class. Here's the default css: .map .tooltip {     background-color: white;     border: 1px solid #7EABCD;     border-radius: 4px 4px 4px 4px;     font-size: 9pt;     padding: 5px;     width: 100px;     z-index: 9999; } You might need to specify !important to override certain styles... ... View more

How are your geometries being served to your user? Can you generalize them using maxAllowableOffset (available with feature layers and query tasks) before they are sent to the client? ... View more

Right, the JS API (and the other Web APIs, Flex and Silverlight) cannot talk directly to an Oracle database. ... View more

Any data you access via the JS API needs to be exposed via a web service. This can be a map service, feature service, etc. The tools provided by the API (queryTask, feature layers) make this easy. If you just need to hit a REST endpoint, you can use esri.request(). For editing, you can use feature layers. ... View more

You need to wait for your layer to load before you can call setVisibleLayers. Try this: layer = new esri.layers.ArcGISDynamicMapServiceLayer("http://server/ArcGIS/rest/services/features/MapServer"); dojo.connect(layer, 'onLoad', function(l) {     l.setVisibleLayers([1]); }); ... View more

That seems kind of convoluted, but if it works for you then OK. Are populating the hidden input tag on the server to serve a map with a different extent for different pages? ... View more