Latest Contributions by Luke_Pinner

Specified_Polygon is a Result object not a FeatureLayer. Use Specified_Polygon = arcpy.SelectLayerByAttribute_management(etc...)[0] or arcpy.SelectLayerByAttribute_management(etc...).getOutput(0)  ... View more

Can you provide some actual detail about the API output format? Perhaps an example response. ... View more

Can you provide more details about the API and its output format? ... View more

How are parameters 3 & 4 defined in the toolbox? Data type, type, direction especially. Can you provide a screenshot of the toolbox script parameter properties? ... View more

I don't think the bug with "\n" in the code block is the problem. You're actually passing a multi line string literal into the Result function Expression: Result(r"%Value (3)%") Is getting converted by ArcGIS to:  Result(r"Your text file contents with lots of new lines...") Which is a syntax error. You can use triple quotes to handle multi line string literals (did you see my other post?) Result(r"""%Value (3)%""") ... View more

chr(10) is equivalent to "\n".   print(f"X{chr(10)}X") X X   Or the os.linesep workaround noted in the bug @DuncanHornby  submitted. 2019, that's pretty poor... ... View more

Leave your new lines/ carriage returns in and just wrap in triple quotes instead of single quotes in the calculate field expression.  String literals inside triple quotes, """ or ''', can span multiple lines of text. r"""%Value%"""  ... View more

You don't return anything from your function.  Also, readlines() returns a list, not a string.   Here's a simpler version that returns a string containing the text of the file.   Expression: Result(r"%Text File%")   Code block: def Result(txtfile):     return open(txtfile).read()       You could probably even just use the following without a code block   Expression: open(r"%Text File%").read()     ... View more

Ugly workaround - use a "SQL Expression" datatype...?     ... View more

That's the ++ increment operator. If used postfix, with operator after operand (for example, x++), the increment operator increments and returns the value before incrementing. So count++ means get current value of count variable then increment it.  The code you refer to starts with an empty array (transformers = []) and an zero index (count = 0). It then loops through the objects i in fsDeviceIntersects and assigns i.globalid to the transformers array at index count, then increments count by 1 before the next iteration. It's doing the same as this:   var transformers = []; var count = 0; for (var i in fsDeviceIntersects) { transformers[count] = i.globalid; count = count + 1; };         ... View more

Why am I not surprised... I'm assuming since you can import utils.utils then it is a proper python package with a utils/__init__.py and then the other submodules like utils.py etc. Possible dodgy workaround (I can't test publishing) - the docs only discuss importing modules not packages (other docs discuss how to install external 3rd party packages, but that's not relevant). But there is a section in there that talks about sys.path.append: Another technique for referencing modules to import is to use the sys.path.append method. This allows you to set a path to a folder containing scripts that you need to import. ... note that the sys.path.append method requires a folder as an argument. Since r'e:\Warehousing\Scripts' is a folder, the entire contents of the folder will be consolidated. I paraphrased the quote slightly, but it makes me think you might be able to throw in sys.path.append("utils") and the utils package and all its submodules would get consolidated and published. I don't think there would be any issue with the import utils.utils call after appending the utils dir to sys.path, I just tried in a simple python script on my local drive and it worked.  But if there is, you could always sys.path.pop() or del sys.path[-1] directly after the append. ... View more

Multipart geometry confuses things, it's a bit of an artificial construct. Each part is a 1D line, but I guess a multipart line needs 2 values to locate a point on it, an x or y coordinate and the part number. So maybe it could be considered 2D......? To theoretical for me though! I prefer the inner->outer Esri definition rather than the outer->inner order you describe. Just the way I think, building things up rather than picking it apart. ... View more