Latest Contributions by JoeFaliti

‎08-31-2015

Thanks Kelly!

‎08-27-2015

Thanks Kelly, Chad's suggestion sounds good, but I'll work with you to resolve the issue when I get some more time. This would probably be within the next two weeks... Thanks again!

‎08-27-2015

Thanks for the suggestion, Chad. I'll have to try this next week... Regards!

‎08-19-2015

Trying to add an item to our ArcGIS Online organizational account from my computer and have encountered this error: "Invalid name '<name>.gdb' found in input publish parameters" I have checked the name for non-alphanumeric characters and still returning error. I was able to upload this same file geodatabase a few months ago. Any ideas? Thanks!

‎11-26-2014

Chris, I believe the setting is correctly configured to NEW_SELECTION. Thanks for the suggestion. -Joe

‎11-25-2014

The suggested branched method yields the same result.

‎11-25-2014

Thanks, I'll try skipping the save to layer step. The trouble is that 118 of the 311 outputs have all features selected. This is coming from the select by features, or the layers that you advise not to save. I will try again without saving the %Value%lyr(s). Thanks again! -Joe

‎11-25-2014

Hi Chris, Thanks for the response. To clarify, the iterator selects and creates seperate layers based on like named features. The select by location tool is meant to select the adjacent polygons and then save those to layer files as well. Thanks again! -Joe

‎11-25-2014

Hi, I have not used iterators too much but according to what I have read, the tools you want to run with each iteration go into a single model and the tools that you want to run differently than the iterator need to go into a "main" model and the iterator in a submodel. I conceptualize the process I am trying to develop as iterating all tools; however, when running the model, it returns some outputs as expected, while others are not. The first part runs fine, selecting polygons grouped by a field value. Then it saves each to layer file. When I add a select by location tool, using the same input layer and the inline variable of the individual grouped by layers (%Value%) as the selecting features, it works, but not correctly for every iteration. I have some more processes down stream, but this is where it seems to go wrong. Please see the two screen shots... Thanks for any advice 🙂 -Joe

‎12-13-2013

Hello, The locators I am using are older, customized .lot files that I would like to add the "additional field" option to. This is the user defined reference data variable that is usually either one field or in dual range locators a left and right side set of variables. Can this be done by modifying the .xat and encoding a .pat using Standardizer Editor? Any advice on this would be welcomed. I don't want to change anything except for adding the additional field(s). Thanks, Joe

‎10-24-2012

Hello Again, I thank you all, especially mzcoyle, for the assistance in using this script tool. I want to mention here, as it may be helpful to know that if using geocoded point features as the input for this script tool, it is important to excluded unmatched records from the dataset in order to avoid the "The coordinates or measures are out of bounds." error. This was my earlier issue and I thought you may find this useful... Thanks again! -Joe

‎10-23-2012

Hello, I reduced the number of points and it seems to work. I now need to work out the best way to populate the sort field for creating the line features in a meaningful manner. Thanks! -Joe

‎10-23-2012

Hello, First and foremost, thanks for the replies! I am attempting to use the script tool directly, by doubleclicking the tool in the toolbox and filling in the form interface as seen in this image: [ATTACH=CONFIG]18649[/ATTACH] I am assuming that the "Line Field" values would be used to differentiate which points are to participate in generating which individual resulting line segments, and that the "Sort Field" would be used to order the verticies of the line to be generated. Please correct my assumptions if this is not the case. There are 4550 points in the point feature class that are stored in a fGDB. I shall try other methods of using the script tool for now and in the meantime, could someone let me know what attributes are needed in the table to create lines from points using this script tool? Thanks, -Joe

‎10-22-2012

In an attempt to create line features from point features, I am experiencing error code 999999, which is not a very helpful error code. How does one properly run that script located under Data Management Tools/Features? Thanks for any help! -Joe

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by JoeFaliti

Re: Invalid name '<name>.gdb' found in input publish parameters

Re: Invalid name '<name>.gdb' found in input publish parameters

Re: Invalid name '<name>.gdb' found in input publish parameters

Invalid name '<name>.gdb' found in input publish parameters

Re: ArcGIS 10.0 - Iterate Issue

Re: ArcGIS 10.0 - Iterate Issue

Re: ArcGIS 10.0 - Iterate Issue

Re: ArcGIS 10.0 - Iterate Issue

ArcGIS 10.0 - Iterate Issue

How to add a user defined reference data variable to a locator style?

Re: ERROR 999999 When running PointsToLine ArcGIS Desktop 10.0

Re: ERROR 999999 When running PointsToLine ArcGIS Desktop 10.0

Re: ERROR 999999 When running PointsToLine ArcGIS Desktop 10.0

ERROR 999999 When running PointsToLine ArcGIS Desktop 10.0