CityEngine is a great way to create entire cities of textured, 3D building models without designing every building. These models can be used in 3D scenes, animations, and game platforms. However, when exporting models made in CityEngine to third-party software, there are a number of considerations. This blog post reviews settings options in the Export wizard to help you render CityEngine models in third-party software.
Esri Technical Support is unlike any other Technical Support on the planet. But if you’ve ever opened a Support case before, you already know that. We provide world class support to our customers to help make them as successful as possible … Continue reading
ArcGIS Runtime SDK for WPF version 10.2.5 is significant in that it is the final release of this product. While technical support will be available through July 1, 2016, maintenance of this product has been discontinued. Customers who develop with this product … Continue reading
A proxy page stands between a server and an application. By using a proxy, you allow an application to authenticate on your behalf, bypassing a challenge and accessing secured services inside of an application. While the token is hidden, an application can access secured services with token-based authentication; a proxy handles massive post requests over 2,048 characters. Additionally, you can use a proxy when a resource and an application are on separate domains, as well as when cross-origin resource sharing (CORS) support is unavailable. Continue reading
The ArcGIS 10.3 release includes the new Space Time Pattern Mining toolbox for analyzing data distributions and patterns in the context of both space and time in ArcMap and ArcGIS Pro. Unfortunately, the initial release contains a substantial logic flaw … Continue reading
In a versioned environment, all edits are stored in what we call delta tables, or Adds and Deletes tables, and these tables are assigned to a unique state ID. Edits are held in the delta tables to handle any conflicts in a multi-user enterprise geodatabase. A compress operation trims the delta tables of any unreferenced state ids, consolidating the states lineage down to one state. If a state is still being referenced, it will remain in the delta tables, resulting in a partial compress.
In a fully compressed geodatabase, there are no rows in the delta tables, and the state tree is trimmed back to one state, state_id=0. Although a full compress is ideal, it is not always necessary and in some cases may not even be practical. For example, if there are many multi-generation replicas in your geodatabase that are not unregistered before the compress, you will need to send changes for all of these replicas to achieve a full compress. If there are many Two-way replicas, and you intend to fully compress both the parent and the child geodatabases, this process of synchronization will need to be done separately from both geodatabases, even if there are no changes to be sent.
This blog post provides updated deprecation information regarding ArcGIS 10.3 and 10.2.x. The first version of the 10.3 series was released in December 2014. Starting in 2014, with the release of ArcGIS 10.2.1, the pattern for the deprecation plan changed from a … Continue reading
The Esri Support Services team will be at the 2015 Esri Developer Summit, and we will be offering appointments for your technical questions. Specialists in all areas of Esri software will be available to assist with your questions. Users attending the … Continue reading