Latest Contributions by ReneRubalcava

Would a FeatureLayer in MODE_ONDEMAND or MODE_SELECTION meet your needs using the selectFeatures method? https://developers.arcgis.com/javascript/jssamples/fl_selectfeatures.html ... View more

You would create separate modules to keep your code modular. Here's a diagram I have been using to kind of explain how require/define work together a little easier for people. [ATTACH=CONFIG]31596[/ATTACH] So you could have a module that somehow produces your coordinates, and can return them via a pattern like the revealing module pattern in the module. You can then call the module from your the methods inside the require() of your application. Every Dojo app needs at least one require() method, but can have multiple modules using define(). Some good refs. http://dojotoolkit.org/documentation/ http://dojotoolkit.org/documentation/tutorials/1.9/modules/ ... View more

There's a sample on using jQuery with the Esri JS API. https://developers.arcgis.com/javascript/jssamples/framework_jquery.html It's an older example and not AMD compatible. The basics of using any 3rd party framework with the Esri JS API is you still need to use the Dojo loader, so you still have to wrap modules in // define a module define() // initialize application require() But inside those modules, you can use jQuery as normal. Here is a sample using Angular in much the same way https://github.com/odoe/angular-esri Here are some samples using other frameworks like Backbone and Knockout with the Esri JS API https://github.com/driskull/framework-samples-js ... View more

You could use hide() when the map loads and show() on a button click. I should also mention there has been some (non-esri) work recently to modify the ClusterLayer to work more like a FeatureLayer. https://github.com/odoe/esri-clusterfeaturelayer ... View more

Nevermind, I just published a new locator with less coverage. It works as a band-aid until they push a rewrite through. ... View more

I updated the README with some instructions and requirements for use. https://github.com/odoe/esri-js-starterkit/blob/master/README.md It requires having git, node, Grunt and bower installed. http://git-scm.com/ http://nodejs.org/ http://gruntjs.com/ http://bower.io/ ... View more

Try adding a 2nd function after the callback to listen for a possible error and see if there is more information. updateFeature.getLayer().applyEdits(null, [updateFeature], null, function(){ map.infoWindow.hide();        }, function(err) {     console.warn('Error occured: ', err); }); ... View more

I have had really good luck so far. My first recommendation for people is to test out LocalStorage first. If that meets your needs, count yourself lucky. I don't want to pimp, but I cover this type of disconnected editing in my book in a much simpler method. In my production application, the field users are only ever concerned with very specific neighborhood level data, so using the TileStorage extension of tiled layers is working ok, but I do clear it every time the app starts, just in case, because you can hit the LocalStorage limit pretty quickly. Now, if you want to get into IndexedDB for data collection and not pollute your LocalStorage with it, I tested out writing an IndexedDB Store that worked pretty well. https://gist.github.com/odoe/6911676#file-indexeddbstore-js At least it worked everywhere except for iOS devices. iOS does not support IndexedDB no matter the browser, not even Chrome. Unless that's changed in the past couple of months, iOS browsers only support LocalStorage and WebSQL. This puts the developer in a silly situation of having to check which type of storage solution is available to use and pick it as necessary. Basically create a service interface that will call the appropriate storage methods for you. Plus, I didn't feel like writing a WebSQL Store. Again, there is a neat solution for that in the form of PouchDB. http://pouchdb.com/ It's a great little tool that handles all the heavy lifting of working with backend databases. They don't make it very clear in the documentation that I could see, but it will normally use IndexedDB for storage, but on iOS will use WebSQL without you having to tell it to. I using was an adapter at first and twitter raving about PouchDB when the author told me it was now integrated into PouchDB core, so that was a pleasant surprise. So now, I use this PouchDB Store in my production app. https://gist.github.com/odoe/6911676#file-pouchdbstore-js It works great saving and pulling my data out, it's all just a matter of converting the graphics to json strings and parsing them back to json and pushing the adds/updates/deletes. I'm still waiting on feedback from field testing on how the users prefer to so sync the data. Either by manually pushing a sync button or behind the scenes as soon as a connection becomes available. The other challenge is determining when you are offline. Here is a great SO answer discussing What does it mean to be "online"? I have not tackled the Application Cache yet, but my basic plan is to run through the app with a few tasks, make a list of all the JS files used via CDN as well my own for the app and add them to the cache list, which would be pretty long. I'm not even sure I'll go this route as these types of web apps need some sort of connection mainly for base data. I suppose if your data set is not that large, you could store it locally and load it as a FeatureCollection to a FeatureLayer, maybe save some Tiles in local storage and combinged with the Application Cache have a fully offline capable map. It would probably need to be really simple though. The native SDKs have the advantage of access to new tools for offline, which are looking very attractive for field apps. https://developers.arcgis.com/en/android/whats-new.html#beta https://developers.arcgis.com/en/ios/info/whats-new.htm#ESRI_SECTION2_71BFA93C1AE64D58BBFAB139D173209A My long, and apparently drawn out point, is that you can do a lot with disconnected editing with ArcGIS JS apps. Not everything and not without some trial & error, but you can do something. ... View more

There are still parts of the REST API not implemented in the JS API yet, probably because of how they return results. You could try the setRequestPreCallback method advised for this similar situation in this thread. http://forums.arcgis.com/threads/95739-Why-isn-t-quot-returnDistinctValues-quot-an-option-for-the-quot-Query-quot-object-in-the-JS-API ... View more

How about coverting the features to JSON and convert the JSON to csv directly on the client? http://stackoverflow.com/questions/4130849/convert-json-format-to-csv-format-for-ms-excel ... View more