Latest Contributions by JonathanHouck

I'm doing this in one of my apps right now, I've got a big dynamicmapservicelayer and I'm removing several layers and group layers so I only display pertinent data.  Here's how I did it, but I'm sure someone more savvy could have a better way: private void Legend_Refreshed(object sender, Legend.RefreshedEventArgs e)         {             List<LayerItemViewModel> removeLayerItemVM = new List<LayerItemViewModel>();             List<LayerItemViewModel> removeLayerItemVM2 = new List<LayerItemViewModel>();             List<string> removeLayers = new List<string>();             removeLayers.Add("Service Agreement Areas");             removeLayers.Add("HTE Routes");             removeLayers.Add("Water 3-way");             removeLayers.Add("Water 4-way");             removeLayers.Add("Water 5-way");             removeLayers.Add("Water 6-way");                                     if (e.LayerItem.LayerItems != null)             {                 foreach (LayerItemViewModel layerItemVM in e.LayerItem.LayerItems)                 {                     //removes the feature layers in the water group layer from the legend:                     foreach (LayerItemViewModel livm in layerItemVM.LayerItems)                     {                         foreach (string rlayer in removeLayers)                         {                             if (livm.Label == rlayer)                                 removeLayerItemVM2.Add(livm);                         }                     }                     foreach (LayerItemViewModel rlivm in removeLayerItemVM2)                     {                         layerItemVM.LayerItems.Remove(rlivm);                     }                     //collapses all the legend items:                     if (layerItemVM.IsExpanded == true)                     {                         layerItemVM.IsExpanded = false;                         for (int i = 0; i < layerItemVM.LayerItems.Count; i++)                         {                             layerItemVM.LayerItems.IsExpanded = false;                         }                     }                     //removes all the other group layers from the legend:                     if (layerItemVM.Label == "General Layers")                         removeLayerItemVM.Add(layerItemVM);                     else if (layerItemVM.Label == "Storm Layers")                         removeLayerItemVM.Add(layerItemVM);                     else if (layerItemVM.Label == "Sewer Layers")                         removeLayerItemVM.Add(layerItemVM);                 }                 foreach (LayerItemViewModel remLayerItemVM in removeLayerItemVM)                 {                     e.LayerItem.LayerItems.Remove(remLayerItemVM);                 }             }                         else             {                 e.LayerItem.IsExpanded = false;             }         } Basically I create a few different lists of layers I want removed, append layers to the lists, and then remove the lists.  It got a little tricky with the first nested foreach because I had to break into the layer item view model's layeritems and only remove the layers I defined in the list above.  Just for context, the above code removes my general, sewer, and storm items from the legend, and leaves all the water layers except those I added to the removeLayers list. ... View more

Resolved!  The problem I was having is, I was creating the schema differences file from the database opposite where I was importing to.  If you're going to import the file from one side, you need to create the schema log from that side as well.  (Example: make schema changes on the parent, use the compare schema tool on the child with the parent as an input parameter, then import the XML file to the child.) ... View more

Seems good so far. I believe we went into Published Toolbox > Script Properties > Parameters and configured the data types and other parameter properties. I'm a little hazy on that part, it was awhile ago and we did it once and never revisited it. I'm looking at the published script now, though, and it does have all the parameters set to match what's in the python and code behind. ... View more

Well you'll notice in the script, it will have this for example: xMin = arcpy.GetParameterAsText(0) if xMin == '#' or not xMin:     xMin = "4357197" # provide a default value if unspecified yMin = arcpy.GetParameterAsText(1) if yMin == '#' or not yMin:     yMin = "1414133" # provide a default value if unspecified xMax = arcpy.GetParameterAsText(2) if xMax == '#' or not xMax:     xMax = "4357210" # provide a default value if unspecified yMax = arcpy.GetParameterAsText(3) if yMax == '#' or not yMax:     yMax = "1414160" # provide a default value if unspecified So you're setting these variables that the script will use equal to the arcpy.GetParameterAsText, and that GetParameterAsText method is what's reading the jobParameters that you're passing into the script. It goes to work once it receives them all. ... View more

As long as you get the job parameters set correctly I don't think I'm missing anything.  Keep in mind the samples I posted are in C#, I haven't used VB.net which I believe you initially inquired about. ... View more

To publish the geoprocessing service you just set the script up in an ArcGIS toolbox like you would any other python script (don't forget to set the parameters).  Then you right click on the toolbox and publish to ArcGIS Server.  You'll see it in the list with all your map services, except it will have a toolbox icon. ... View more

I'll try my best to explain this correctly... I apologize in advance, I'm a geographer that's learned to write some code, not a CS guy. From the link Patrick posted above, we got the Python script that ESRI staff developed for doing a print with Arcpy.mapping. The python script gets published in ArcServer as a geoprocessing service.  I'm sure you know all this already, but I'm starting from the beginning.  This geoprocessing service accepts a series of parameters that are passed to it, and then passes these parameters into a template (or multiple templates) that you have created, and are waiting for it to consume.  In fact, which template the GP service will use is one of the parameters. We edited the python script a bit for our needs, but it works right out of the box. The way our application works step by step is as follows: User opens the application and selects what they want to print.  They use combo boxes or text input boxes (depending which layer they're focusing on) to run a query task that zooms to the feature they want on their map. Once the query is complete and the feature they want to print is on their screen, they select which template they want to use from a separate combo box (for example, we have a map with map elements such as scale bar, locator map, etc, and a plain map without them.)  After they have everything selected, they press a button called "Export PDF" which is tied to an event handler that does the following: Sets the PDFTitle variable based on the feature that the query returned (in our app, they do not create their own title, but this is an easy change). Sets the Mapscale variable based on a map scale equation we use to make the features fit perfectly into the data frame. Sets theTemplate variable based on which template they have selected from the combobox. Passes these variables, and all the other arguments they require, to the parameters. Creates the Geoprocessor ExportTask. Executes the ExportTask.SubmitJobAsync Then under the ExportTask.JobCompleted event handler, we: Set our image.visibility = Visibility.Visible (the little PDF image they click to get their map) Set our pdfURL = the url of the PDF that was created (you can change the output location in the python script) Then we have a PDF image mouseleftbuttondown event handler, and when clicked we: HtmlPage.Window.Invoke("PDFs", pdfURL); And the map that was created is opened in a browser window and can be saved, printed, etc. Phew.  I hope that helped in some way, like I said if you need more code samples I'll look into getting those available. ... View more

The map title is passed into the GP service in one of the parameters as a string variable.  So you could set the variable equal to a textbox.Text that you provide for the user to enter the title, then execute the ExportTask on a button click event handler (or whatever you want). I'll look into hosting a project with as much of the code as I can, but in the meantime I'd be happy to answer any other questions you have about how the whole thing works. ... View more