Latest Contributions by JuliePowell

Hi David, sorry I don't have an update on the analysis widgets yet. At this time, all I know is that they won't be in 4.5 (~end Sept). ... View more

This is the draw sample I was referring to: Draw polygon for spatial query | ArcGIS API for JavaScript 4.4  ... View more

Here is the simple measure sample that I was referring to: Measure while drawing | ArcGIS API for JavaScript 4.4  ... View more

We are currently targeting the December release (4.6) for the measurement widget. However, 4.4 will have a sample demonstrating how you can implement simple measurement on your own using map events and the geometry engine.  ... View more

The team is currently working hard on the sketching implementation for 4.x. We had hoped that we'd have an initial release of 2D draw tools in the 4.4 release, and while the team made good progress on the overall design and beginning implementation, it isn't ready for release. 4.5 is due out in the fall and we are working towards getting 2D drawing into that release. I can share any updates to this thread as the release approaches. 3D drawing will likely be next year. The full *editing* experience will take more time and will be a multi-release implementation (that includes editing widgets).  That being said, we will likely have a sample released with 4.4 that shows how you can simply use map events to draw a polygon (that is then used for a spatial query). For those of you that have projects that can't wait for OOB drawing in the API, you can use this code as an example for writing (simple) custom drawing tools.  I hope that helps! ... View more

Correct, esri/dijit/analysis/* refers to the analysis widgets. We don't yet have these widgets scheduled yet; I will provide an update to this post once I have more information.  ... View more

Hi Adam, the print widget will be included in this release as well (and has been redesigned for 4.x; it's pretty nice!). The draw widget will be part of the summer release at the earliest.  ... View more

The SDK is now updated with IdentityTask and FindTask. We also just published the TypeScript definition files with both of these added back in:  https://github.com/Esri/jsapi-resources/commit/2978250 ... View more

We already spoke on the phone, but just in case others are following this thread - We are working towards having WMS support in 4.3. I will post an update closer to the release to confirm whether it will likely make it.  ... View more

Your questions are valid and you've helped us with an oversight. Please keep the feedback and questions coming! ... View more

Yes, we will recreate the TypeScript definitions along with the SDK update. I should have more info on timing by mid-next week. ... View more

Hi Jan, I support the JS API from a product management perspective. I understand your frustration and the difficulty you are experiencing right now. It may not make your job easier, but I'd like to be transparent about our release strategy to at least provide insight into why we released the API into production, and also some info about upcoming releases. As you know, 4.x was a complete rewrite of the API. While 4.0 didn’t have functional equivalence with 3.x, it did lay the foundation with a brand new architecture, programming patterns, and integrated new capabilities like 3D and map rotation. Developers wanting to build web apps with 3D visualization could start using this API and put them into production with the confidence of a fully-released API. In fact, there are already hundreds of great apps already out there that are built on 4.x. Developers that wanted to build 2D web apps could use the online SDK to figure out whether the current version of the API had the capabilities needed for their application requirements. In many cases, developers had to (and continue to) use 3.x because they needed something such as edit which is not yet available in 4. However, by releasing 4.0 to production, we are not holding back those developers who are building apps with requirements that are met by the current API. Because of the value we see in both APIs, we have committed to releasing both APIs concurrently – 4 releases of both 3.x and 4.x are planned for 2017. That being said, we received feedback from the developer community that they needed more help determining whether the current version of the 4.x API had the capabilities needed for their app. For that reason, we put together the Choosing a version guide and detailed matrix help developers quickly determine whether a particular functionality had been built, and also "map" 3.x classes/properties/methods to 4.x (especially useful for cases where the implementation has been redesigned for 4.x). To your point, we haven't provided extensive information about when each of the remaining capabilities will be implemented in 4.x. I understand that this could make it difficult for you when planning your development work. To share information on our release strategy, and a potential way in which we might be able to improve a bit: We have a very dynamic development and release process, with requirements that are driven by the ArcGIS platform (such as enhancements in ArcGIS Online, deeper support for 3D across the platform, vector tile layer support, etc), requirements specific to the API that we've collected from customers over time such as map rotation, and then all of the capabilities that will bring 4.x at parity with 3.x. At any given time, the team works on shorter-term advancements that make it into the subsequent release, and also longer design work that can span multiple releases. Because of all of this complexity and the dynamic nature of our work, we are careful about not committing to time frames unless we are very confident about the timing (so that developers don't plan their development schedule around something that they depend on and later find that it has been delayed). With this in mind, I think we can do better at communicating at least what we are working on, without a firm commitment to a particular release. I think this will give developers an idea about what capabilities are *in progress*, and those that will take longer to implement. One idea we had was to post a blog approximately one month before each release that describes this information. Do you think that would help?   I think it is also worth mentioning that 3.x is still a great option - it is a fully featured 2D API that will be supported through 2020. All versions of the API will also be hosted on our CDN indefinitely, so apps won't break, even after the API version reaches the retirement phase. More info here.    As you suggested, the 4.x API is in fact a moving target; I promise that we will do our best to support you as you plan your development and build your apps. If you have any specific questions about the status of an API feature, please post them on geonet or contact me directly and we can have a transparent conversation about it.   Thanks, Julie ... View more

Yes, we will add the ability to query a layer based on pixels (using a defined tolerance); the dev team is currently working on the design for this. ... View more

All, thank you for your feedback. IdentityTask is actually still part of the 4.1 API, but was removed from the online documentation because we had planned on introducing a new (elegant) implementation that would better integrate with the 4.x API design, and could also support 3D in the future. However, in hindsight, we should have left it in the documentation since it was already available with 4.0. We added a task in our queue to put it back; I will update this thread once it is available in the online SDK. In the meantime, here is a sample showing how you can use IdentityTask with the 4.1 API: IdentityTask Sample - jsbin  ... View more