Latest Contributions by MichaelBranscomb

Hi, Glad you got it working. Regarding performance, what type of data are you trying to display in the feature layer? (geometry type, number of features, intended purpose). The FeatureLayer/LocalFeatureLayer isn't intended for the display of large numbers of map features - these should either be within a Tile Package (or server tiled map service) if they are relatively static or if more dynamic in nature and are to allow user interaction then they should be within a Map Package (or server dynamic map service). There are some ways you can optimize the performance of feature layers: If you're working with polylines/polygons you can use the MaxAllowableOffset property on FeatureLayer/LocalFeatureLayer to have some generalization applied to the feature geometries before they are returned to the client:  http://blogs.esri.com/Dev/blogs/arcgisserver/archive/2011/06/13/Feature-layers-can-generalize-geometries-on-the-fly.aspx. If you're hoping to use a PictureMarkerSymbol to render points then you should look at using an ImageBrush (http://support.esri.com/en/knowledgebase/techarticles/detail/37033). Cheers Mike Cheers Mike ... View more

Hi, The MaxRecords property is on the LocalFeatureService class so you'll need to create/manage that in code. The following below is approximately what you would write. Currently you always need to set the Path property on a LocalFeatureLayer (or LocalArcGISDynamicMapServiceLayer). We are actually just reviewing this part of the API so now's an ideal time to provide feedback on the process of creating/managing local feature services and their relationship to local feature layers.             string mpkPath =@"Maps_and_Data\OperationalLayers.mpk";             LocalFeatureService localFeatureService = new LocalFeatureService()             {                 Path=mpkPath,                 MaxRecords=100000             };             localFeatureService.StartAsync(lfs =>             {                 LocalFeatureLayer localFeatureLayer = new LocalFeatureLayer(mpkPath, 0);                 MapControl.Layers.Add(localFeatureLayer);             });   Cheers Mike ... View more

Hi, ArcMap (within ArcGIS for Desktop 10.1 Beta 1) is the authoring environment for your Map Packages. ArcMap allows you to specify all the properties you're looking for (scale thresholds, visibility, symbology). Once you're happy with your Map, which might obviously contian several layers of data, you then use the UI within ArcMap (File > Share As) or the packaging GP tools to create a Map Package with ArcGIS Runtime support. That Map Package can then be added to the map control as a LocalArcGISDynamicMapServiceLayer (based on a LocalMapService).    The reason you only saw 2% of the street features is that there's a default limit of 1000 on the number of features returned but you can override this with the MaxRecords property. The feature layer is also not intended for the display of significant numbers of features. In fact - a layer such as streets sounds like a background mapping layer, or base map, and would likely be much better implemented as a Tile Package (TPK). This is a lot like an online tiled service but in a single, portable package file. For more information on these I definitely recommend checking out the conceptual doc: http://resourcesbeta.arcgis.com/en/help/runtime-wpf/help/#/About_tile_packages/01700000004w000000/. Hope all this helps, and if anything in the documentation isn't clear or needs more explanation then please let us know - we're looking for feedback on the entire SDK (API, API reference, conceptual doc, samples, project templates) as well as the runtime itself. Cheers Mike ... View more

Hi, Wow, you've certainly gone the roundabout route. But fortunately there is a much easier way to do this - it's just a case of switching on ArcGIS Runtime support in the ArcMap options: 1. Click Customize > ArcMap Options... 2. Select the Sharing tab 3. Under Packaging, check the box to "Enable ArcGIS Runtime Tools". For more info check out the conceptual docs on Preparing Data: - High level package info: http://resourcesbeta.arcgis.com/en/help/runtime-wpf/help/#/Packages_used_by_the_ArcGIS_Runtime/01700000005v000000/ - Creating a Map Package: http://resourcesbeta.arcgis.com/en/help/runtime-wpf/help/#/How_to_create_a_map_package/01700000005t000000/ Cheers Mike ... View more

Hi, There are two elements to this: (1) Basic mosaic dataset support within the existing local map service = we hope to support this in the first release at 10.1 (but unfortunately cannot guarantee it at this time). (2) Providing local image service support (for which the source may be a mosaic dataset) = we aim to support these in an off-cycle release some time after the first release. Unfortunately I can't be more specific at present. Cheers Mike ... View more

Hi, In Beta 1 there is no SDK license. To license the ArcGIS Runtime itself, while beta testing you should use the Standard license - in Beta 1 there is no functionality which requires the Advanced level but eventually this will be additional Geoprocessing tools. Just to make sure - here are the steps to license an application: 1. After installing the ArcGIS Runtime SDK, launch the Software Authorization Wizard by going to Start > Programs > ArcGIS > ArcGIS Runtime Tools. 2. Select the default option I have installed my software and need to authorize it. 3. Select Authorize with ESRI now using the Internet. 4. Enter your personal information. 5. Enter your ArcGIS Runtime (SDK or Deployment) authorization number. (ECPxxxxxxxxx). This information is provided to you by Esri Customer Service. If you do not have this information, contact Esri Customer Service. 6. When prompted, save the Keycodes.txt file to a location on disk. 7. Click Finish after the authorization process is complete. 8. The keycodes.txt file has a feature line containing the following information: Product name (runtimebasic, runtimestandard, runtimeadvanced), software version number, Authorization number, timeout date, signature hash code, string and FID number. 9. Open the keycodes.txt. The keycodes.txt file has a feature line containing the following information: Product name (runtimebasic, runtimestandard, runtimeadvanced), software version number, Authorization number, timeout date, signature hash code, string and FID number. 10. Copy the first five elements of the feature line. It should look similar to runtimestandard,101,ecp999999999,DD-mon-YYYY,XXXXXXXXXXXXXXXXXXXX 11. Note: The last 2 parameters in the feature line are not required. 12. Paste this copied string into the licensing section of your application's code. For more information on licensing your application refer to the licensing documentation provided by the specific SDK you are using. http://resourcesbeta.arcgis.com/en/help/runtime-wpf/help/#/How_to_obtain_a_license_for_your_deployment/017000000055000000/ Cheers Mike ... View more

Hi, Sounds like it's just a case of switching on ArcGIS Runtime support in the ArcMap options: 1. Click Customize > ArcMap Options... 2. Select the Sharing tab 3. Under Packaging, check the box to "Enable ArcGIS Runtime Tools". Cheers Mike ... View more

Hi, The Beta 1 API itself does not contain functionality for adding Shapefiles directly to the map. However, we really appreciate the feedback and will be investigating API support for adding adhoc  datasets to the map at runtime. UPDATE 04/19/2012: The Package Map Geoprocessing Tool is not supported within the ArcGIS Runtime. Map Packages must be produced within ArcGIS for Desktop where the the full authoring process is supported. Cheers Mike ... View more

Hi, Any future synchronization framework will be designed to work in an enterprise scenario so therefore will work with Enterprise Geodatabases. However, it's possible that your workflow could be automated with Geoprocessing in the first release, although depending on how you intend to manage conflict resolution it might require some manual steps involving ArcGIS for Desktop. But that could still be true within any automated framework too. I'll confirm the question regarding ClickOnce deployment. If you're currently using ClickOnce - do your applications run Full Trust? Cheers Mike ... View more

Hi, There are several possible workflows for sharing maps and data depending on your requirements: ArcGIS.com; direct package exchange; or ArcSDE... But addressing the question about sharing a package directly, the ArcGIS Runtime can re-package maps and data into MPKs using Geoprocessing tools built in ArcGIS for Desktop. It is quite straightforward to create a model which: 1. Takes the path to a Map Document (.MXD) - this will be within the user profile in the unpacked package location (e.g. C:\Users\mbranscomb\Documents\ArcGIS\Packages\WaterDistributionSystem\v101\WaterDistributionSystem.mxd) 2. Optionally also exposes options such as package name, version support (10.0, 10.1, etc) or map extent. 3. Calls the Package Map tool to create an MPK which the user can share with others. (ArcToolbox > Data Management Tools > Package > Package Map). This model can then be shared/exported as a Geoprocessing Package (.GPK) for use within the ArcGIS Runtime. As the developer you would programmatically call the Geoprocessing package via the ArcGIS Runtime (LocalGeoprocessingService) taking the user defined MXD path and perhaps a package name and providing them with a suitable way to share the output Map Package. For example this might be via a function in your application to email the new MPK. See the attached picture for an example model. Note the "Map Package Name" variable is not connected to any process, but instead is used with in-line variable substitution to allow the user to specify the output map package name so the "Output Map Package" variable value becomes "%ScratchWorkspace%\%Map Package Name%.mpk". I hope this helps. Cheers Mike ... View more

Karl, An edit synchronization framework will be a strong focus for us after the 10.1 release. However, it is a significant piece of work so at this time I can't say how soon after 10.1 it might be available. Regarding post-10.1 releases, yes, we do plan to go "off cycle" with the ArcGIS Runtime and 3-6 months is probably a reasonable suggestion but beyond that it's impossible to say at this time. Thanks for your interest in the Runtime - beta 1 should be available for download within the next couple of weeks. Cheers Mike ... View more

Hi, 1) Map Packages can either contain the data within a File GDB within the Package, or reference File GDBs which are external to the Map Package. There is an option in the Sharing dialog in ArcMap to specify this behaviour. You could create multiple Map Documents (.MXDs) in ArcMap which reference the same data (e.g. within a File GDB) but with each map displaying the data differently, with different symbols/styles. Then you could package each map Document choosing to reference the data source rather than include it in the package. That way, you would have multiple Maps Packages, each with a different style, but pointing at the same data source to avoid data duplication. 2) Yes, the premise of Map Packages is that they make maps and data very easy to share/deploy with applications. The ArcGIS Runtime will resolve relative paths to Packages so you can ship the package alongside your application.  3) Exactly what data the user edits is up to you. Map Packages are a compressed bundle of files, a "package", so are therefore unpacked into the users profile to be used within the ArcGIS Runtime. In Beta 1 this is always  the user profile (\My Documents\ArcGIS\Packages) but after Beta 1 we hope to allow the developer to specify this location via the API. If you choose to include the data within the Map Package the data will be edited in the unpacked location within the user profile. The Package will not be unpacked a second time if it already exists in the user profile so the user will continue to see any edits they have made. However, if you choose to reference the data externally to the package then edits will be made against the external File GDB. 4) The spatial reference of the map control in the ArcGIS Runtime API can be changed - but it does not support reprojection on the fly. If you do not explicitly set the map control spatial reference, it is determined by the first layer added to the map. All subsequent layers must match that spatial reference. When creating Map Packages, the spatial reference of the Map Document can be different to the spatial reference of the data - the LocalMapService will perform reprojection. You can reproject GIS data using Geoprocessing within the ArcGIS Runtime - but the data would need to be referenced by a Map Package in order for it to be added to the Map Control. Cheers Mike ... View more

Hi, The ArcGIS Runtime API for WPF builds on the existing ArcGIS API for WPF to provide local data support via local services (i.e. map, feature, geoprocessing, etc). In order to be able to create a local service referencing a feature class, that feature class must first have been added to a Map Document (MXD) then shared as a Map Package (.MPK). The reason for this is two fold: 1) because the Runtime uses the optimised map rendering engine and 2) to keep the Runtime footprint as small as possible (through minimising the components required). Over time, the existing ArcGIS API for WPF product will become the basic product level within the ArcGIS Runtime API for WPF, with a standard level offering local services support (inc approx ArcView level geoprocessing) and an advanced level providing extended geoprocessing capabilities. In the application you are writing / are going to write, is one of your key requirements to support the end user being able to add feature classes in an adhoc manner? Cheers Mike ... View more

Hi Angel, 1) Managing the ArcGIS Runtime & local Feature Services: - Yes, the ArcGIS Runtime does run services on the local machine which are broadly equivalent to ArcGIS Server services. This means, when we talk about feature services, those feature services could be hosted by an ArcGIS Server or in the ArcGIS Runtime, often referred to as "online" or "local".  - The only limitation is that there are some datatypes / types of geometry  which cannot be edited outside of an edit session or which need to be versioned, for example feature classes which participate in a geometric network. In this case, currently (Beta 1), these cannot be edited via local feature services with the ArcGIS Runtime without a connection to the source ArcSDE Geodatabase. In this case - the Map Package must be created referencing the ArcSDE GDB. 2) Disconnected editing: ** The following steps are true for Beta 1 through to the first release. After the first release we aim to add a synchronization framework allowing for a more seamless disconnected enterprise editing workflow. ** The basic process is to use ArcMap (ArcGIS for Desktop 10.1 Beta 1) to create a Map Package (MPK) in which you can edit data using a local feature service provided by the ArcGIS Runtime then check those edits back into your ArcSDe GDB: a) Open ArcMap - ArcGIS for Desktop 10.1 (Beta 1) - and add the layers you wish to edit from your ArcSDE GDB. b) Create a checkout/checkin replica of these layers - this must be in a File GDB. c) Ensure the File GDB is being created in the required folder (e.g. your deployment folder) d) The checkout process can switch your Map to point to the new;y checked-out data or open a new ArcMap session and add the Feature Classes within the File GDB then symbolize as required. e) Ensure that ArcMap is set to use relative paths within ArcMap Document properties (off the File menu). f) Go to Customize > ArcMap Options and select the Sharing tab. Ensure that the Enable ArcGIS Runtime Tools option is checked. g) Open the Map Packaging dialog by using the File > Share As... > Map Package option within ArcMap. h) Ensure the "Make ArcGIS Runtime compatible" option is checked and that the option beneath this is also checked - to "Reference all data" and that the MPK is going to sit alongside the File GDB you created (so that the relative paths work). i) Then click Share - this will create a small Map Package (.MPK) which references the File GDB containing the replica. j) This MPK and File GDB should be deployed to the deployment machine when you deploy your application. The ArcGIS Runtime can also use relative paths (e.g. ..\..\Data\MyEditLayers.MPK). k) Now you can create a LocalFeatureService using the ArcGIS Runtime WPF API, based on that MPK and create one or more LocalFeatureLayers based on layers within that MPK (i.e. as you would with layers within an ArcGIS Server FeatureService). l) Develop an editing UI e.g. using the Template Picker or Editor with the Toolkit library. m) Once your edits are done - to reintegrate the edits to your ArcSDE GDB you need to grab the File GDB that you deployed and use ArcGIS for Desktop 10.1 (Beta 1) to checkin the edits. Alternatively you could explore using Geoprocessing tools for this purpose. I hope this helps - if you have any more questions, please keep posting - feedback is very important to us during the beta process for both product functionality and as a guide for areas in which we need more documentation. Cheers Mike ... View more

Björn, Sorry to hear you're experiencing an issue - however I can confirm there's no specific Windows 7 64-bit problem as we've been running ArcGIS Explorer on Windows 7 64-bit  without any trouble. The reason the basemap error is seen is a connectivity issue between your PC and the server hosting the basemaps which is often due to the firewall / proxyserver configuration. Regards Mike ... View more