Latest Contributions by ColeAndrews

‎03-01-2019

Jay Sandhu‌ Another question related to this (and every ArcGIS routing problem in general). If your input origin points are rooftop geocoded, the solver begins the routing at the street network segment and not the rooftop itself. Makes sense. So does it find the nearest starting vertex of a street line segment, or can it start midway along the line (which may be closer to the rooftop), not at an existing start vertex? If it starts only at first vertex of a street, then it would make sense that it includes the whole segment as a line to traverse. But, if the solver can start the route midway along a line segment closest to the rooftop, then how does it allocate the travel time along the partial segment? Seems it would either include the full street segment travel time regardless of where on the line it started, or it can programmatically allocate portions of street segments as traversed? Same concept would apply to destination locations relative to proximity to street network.

‎02-26-2019

Vince Angelo‌ you're accomplishing that in what? Surely not in Desktop...

‎02-21-2019

Brian Wade When you run the iterator linked to get count as Duncan Hornby instructed, write the values to a gdb table. Pass the feature class name of the iterator as the field name, and field calculate the %get count% value. If you want to view it outside of Arc in a csv, then add a table to table tool to export that QA table to a csv. You'd need to nest the above as a submodel so that the csv isn't written until the end. This would give you a field for every feature class name, and 1 row with the value from get count. If you want to view it vertically instead of horizontally, add in the transpose tool in the main model before the csv export. I haven't tried this with get count tool, but I've used it for a very similar situation. Be the gineau pig!

‎02-21-2019

If you want the geoprocessing to be interactive ("need to be able to have the option of selecting my inputs"), then what is the reason you do not want to leave it as a tool/model in ArcGIS?

‎02-18-2019

#ENH-000120111 [Enhancement] Request to add a new delimiters while exporting table in ArcGIS Pro Geoprocessing Tools. "This enhancement request is to implement a new delimiter option while exporting a table/feature out using ArcGIS Pro Copy Rows, Table to Table, Export Table Geoprocessing tools. Currently the only formats in which a table can be exported are, .csv, .dbf and .txt for these tools. This is to include the delimiters such as Pipe while exporting to CSV or a TXT format using the above tools. Currently the option to add Pipe Delimiter is only available with Roads and Highways extension and that too in ArcMap but not in ArcGIS Pro. Thus it would be helpful to get this format in all other tools too rather than providing it with the extension only."

‎02-12-2019

"it should be a simple thing to allow it to move multiple fields". You can move multiple input fields to 1 field in the field map. But you need to select them interactively, it won't automatically select the 400 fields to map to the 1 output field. If you had 400 variations of input field names to merge, then you'd be stuck doing something like this or coding. But since you only had 2 variations, that why I would not go this route and stick with the field calc you did or the 2 consecutive merges. See image-- you can multi select all the fields of inputs to map to 1 output field.

‎02-12-2019

Field mapping is only required if you don't have common field names between the files to merge, but you want all the data in one column. You said half of the 400 feature classes had one set identical field names, and the other half had identical. Running the merge tool twice, as I described, is equivalent to what you did with the field calculator. Instead of using the field map settings when merging the two intermediate feature classes, you calculated the field back in to a common column after merging.

‎02-12-2019

Desktop will show you the count of features falling in to each symbology class. So yes, add the ability to select and/or view the table records driving those feature counts without setting up completely independent select by attribute statements.

‎02-12-2019

There may be other ways to go about it, but I would probably merge the two halves independently. Merge the ~200 with the one variation of fields, then merge the other ~200 with other variation. Then merge those 2, so you're only field mapping for 2 feature classes.

‎02-11-2019

So the fields are different between each of the 400?

‎02-11-2019

For "what have you already tried", do not use a toolbox to store tools/models/scripts that will be used in both ArcMap and Pro. Meaning, if you have toolbox items that ArcMap needs to run, then do not store any tools in it that Pro will use. Do not use toolboxes stored in a geodatabase, only create and use file toolboxes (outside the gdb). I did not do it this way and everything got wrecked and I had to start over. Pro creates a litany of files/folders when you create a project. I still set up and manage GDB's and data outside all of those erroneous files a project creates.

‎02-11-2019

AWS is not the same price for every organization. That is the point. You pay for what you use. Esri (AGO) does not pay AWS the same as what I pay them, because we are at different scales. Credits may not be the right answer. But neither is across the board flat rate pricing. Multiple commentors have suggested the exact same pricing no matter how much you use. They see it as either enabled or disabled. That model doesn't work: "If a user is not licensed for a task, product, analysis or action. PUT A LOCK ON IT" -- It's how much the task or analysis is run, and to what degree, that matters. "I will pay upfront to just "Own" the tool, and run it to my hearts content, than have to pay every time it is ran." -- Not sustainable. If Eric want's to geocode millions of records per day in AGO, he is using more resources and thus should pay more than John Doe who geocodes 20 blockbuster stores per year.

‎02-11-2019

To go devils advocate here, do you want the little guy to be subsidizing the big guys? AGO is running in the cloud. The assumption is that as more users/organizations/processes start happening in AGO, Esri has to scale it accordingly. For the desktop license, esri's 'monetary responsibility' is the same whether your desktop hardware is geocoding 1 hour per month or 23 hours per day. Alternatively, if you're doing all of your processing in AGO, the esri cloud resources required are not equivalent in both scenarios. They would have to scale up as many organizations eat up the cloud resources ($$$). So if a large organization is running processes and mapping all day every day for many users, their cost would be the same or similar to the self employed consultant not using many cloud resources? I think the pay-to-play credit model is trying to account of those disparities. Otherwise, the little guy would likely end up paying too much and the big guy too little.

‎02-11-2019

I know there's another idea thread out there on this, it's an OLE object we want Pro to be able to use like ArcMap. We use this in ArcMap for adding in spreadsheet tables that are linked. Very important feature.

‎02-06-2019

Submitted an enhancement request via support due to lack of ability to export table with a pipe delimiter in Pro. Suggestion was to also add here. There are several existing tools to export a table to a flat file .txt or .csv, such as copy rows, table to table, or export features rows to ASCII. The last option at least gives you the ability to choose comma, space, or semicolon delimiters. The first 2 tools default to commas with no configuration option. ArcMap Roads and Highways has a tool 'Convert Table to CSV' that gives the delimiter options of pipe or comma. But, this extension is not yet available in Pro, nor should you need to purchase an extension just to choose a pipe delimiter. There is no consistency in delimiter options between these tools. Our organization needs to utilize pipe delimiters in an application that is receiving the table data. Please add delimiter options such as a pipe to one or all of the table export options, or allow a freeform text field for the user to enter the delimiter. Does not seem like too much development required if a tool already has comma, space, or semicolon options.

Online Status	Offline
Date Last Visited	‎12-06-2022 05:13 PM

My Ideas

Latest Contributions by ColeAndrews

Re: Performance Comparison: Large Scale OD Matrix Summarizing versus Closest Facility

Re: Problem while Geoprocessing (Intersecting) large amount on data in Arcpro and Arcmap.

Re: I would like to get a record count for many shapefiles created during a process into a table for a QA process

Re: Model Builder exported to Script defciency

Re: Add More Delimiter Options in Table Export Tools (i.e., pipe delimiter)

Re: Field mapping in Merge Tool

Re: Field mapping in Merge Tool

Re: Select by Symbology

Re: Field mapping in Merge Tool

Re: Field mapping in Merge Tool

Re: Folder structure for shared Pro and Map projects

Re: Just Get RID of the CREDITS!!!!

Re: Just Get RID of the CREDITS!!!!

Re: Insert of Office Objects (word-documents, pdf, ...) in ArcGIS Pro

Add More Delimiter Options in Table Export Tools (i.e., pipe delimiter)

Allow App User to Save Their Personal Settings

Re: GIS Managers - what do you look for when hirin...

Re: Clip Zip Ship on Portal for ArcGIS

Re: Remove powered by ESRI logo

Re: Folder structure for shared Pro and Map projec...