Latest Contributions by JoshuaBixby

At first glance, you seem to be mixing older/original cursors and the newer data access (arcpy.da) cursors.  Your syntax for the update cursors seems wrong.  The arcpy.da.UpdateCursor syntax is (in_table, field_names, {where_clause}, {spatial_reference}, {explode_to_points}, {sql_clause}) whereas the arcpy.UpdateCursor syntax is (dataset, {where_clause}, {spatial_reference}, {fields}, {sort_fields}).  You appear to be passing your field list as a where clause to your update cursors. Overall, I recommend switching to using all arcpy.da cursors. ... View more

Tough part about forums and not knowing people personally, comments can be read multiple ways.... Anyhow, two other bugs were issued related to the aforementioned Support case:  BUG-000084666 and BUG-000084667.  Even though the impact might seem limited on the surface, cases like this can point to larger issues with managing precision deeper in the software stack.  What isn't stated in the public-facing Support system is that the "bug is not coordinate specific and it is not spatial reference specific."  Although the illustrative example involved working in a coordinate system that presented an unusual real-world case, it has been demonstrated the issue is abstracted from a single coordinate system. In the end, the true impact may be small but maybe not.  It isn't always easy to tell until developers dig into the bug deeper. ... View more

Esri Support issued a formal bug: Bug BUG-000084665: Attempting to create an equilateral triangle with lengths of 0.0027 gives, "The feature could not be created. The geometry is invalid." However, the distance between each vertex is greater than the XY Tolerance (0.001) and the XY Resolution (0.0001). Alternate Solution: Ensure the distance between each vertex is at least 0.0029 units. I can't say I am a fan of the Summary text.  I think it downplays the scope and impact of the bug, i.e., someone might think it is about triangles and not the much larger issue of all polygons and lines. The workaround is basically to not trust the XY Tolerance or XY Resolution of spatial references.  Caveat utilitor. ... View more

OK, I think I got a better picture of what you are after now.  Are you planning on using ArcGIS API for JavaScript and consuming GIS services or build something in ArcGIS Online?  I ask because the example you provide is javascript driven and tends to lend itself to Web-based APIs.  Unfortunately, my background isn't in those Web-based APIs, so I don't think my advice would be worth much. ... View more

Did you see the screenshot before you posted it?  I see your Inbox and other stuff.  Trimming the screenshot to relevant parts makes it easier to work with. Anyhow, yes, layer files are supported, but I think you are looking at this from the wrong perspective.  Layer files reference data sources, so are you sure the actual data source is supported?  Are you working with a personal geodatabases possibly? ... View more

It would be helpful if you would elaborate a bit more on what the final product will look like and how users will interact with it.  I have a sense of what you are after, but with this much data, understanding the final product can make a big difference on how it should be structured and processed. ... View more

Bad hyperlink, missing colon after http. ... View more

If you have 13.000.000 points in total, what percentage do you think will be dropped?  If you are working with upper millions or more than 10.000.000 unique points, then you are likely running into a memory error related to using 32-bit Python.  Quoting from Windows Dev Center: Virtual Address Space .... The virtual address space for 32-bit Windows is 4 gigabytes (GB) in size and divided into two partitions: one for use by the process [2 GB] and the other reserved for use by the system [2 GB]. .... If 4-gigabyte tuning (4GT) is enabled, ... a process that has the IMAGE_FILE_LARGE_ADDRESS_AWARE flag set in its image header will have access to the additional 1 GB of memory above the low 2 GB. Even if your operating system is 64-bit and you have lots of RAM, 32-bit applications are still bound by the 4 GB address space.  If 32-bit applications are compiled as large-address aware, they can take advantage of more (3 GB for 32-bit OS or 4 GB for 64-bit OS) address space than the normal 2 GB.  If you want to dive into the weeds, check out the Memory Limits for Windows and Windows Server Releases. Although Esri has compiled the primary ArcGIS Desktop binaries (arcmap.exe, arccatalog.exe, etc...) as large-address aware, the Python executables that get installed don't seem to be large-address aware.  I am not sure how the memory limits play out since ArcMap is LAA but Python.exe isn't.  When running a standalone 32-bit Python script, you start to see memory errors once the process gets above 1.5 GB of address space. One way to potentially get around this is to use 64-bit Background Geoprocessing.  Installing that software installs 64-bit versions of Python and ArcPy libraries.  That said, Python code from the interactive Python window will not be executed as 64-bit so your script would have to be run as a standalone script outside of ArcGIS Desktop, but at least you could still use ArcPy. ... View more

Haven't had time to re-review the post yet, but I did notice the restricted visibility.  Opening it up might get more feedback, maybe better feedback. ... View more

It isn't an issue with the ArcGIS tool.  The tool is passing through part of an SQL expression the user generates.  In this case, the tool is just passing along an error message from other code that is saying an invalid SQL expression was used. ... View more

It could be a SQL Syntax issue.  The SQL "IN" operator requires the set of values to be enclosed in parentheses, e.g., expression IN (value1, value2, value3, ...).  ... View more

Not that Esri's Deprecation Plans always hold water, but at least they are something.  Unfortunately, I have yet to find the Deprecation Plan for ArcGIS 10.3.  Usually, the deprecation plans come out before or at least with the release, not sure what Esri is doing this time around. ... View more

Michael Grossman‌, thanks for the update and more importantly taking customer feedback to heart. I think the idea of a built-in Software Update mechanism is a good one, just not in exclusivity to other mechanisms for updating the software.  I work for an organization with thousands of GIS users scattered across the country, and there are times we prefer to deploy updates to Esri software through the same infrastructure that updates non-Esri software. My overarching concern with the Software Update mechanism, as implemented to date, is that "updates" have been complete installs.  Downloading and installing an update that is patch-like is much easier on wide-area networks at small, remote offices rather than grabbing an entire 700 MB or larger download every time an update comes out. Thanks again, and I look forward to seeing the Software Update mechanism improve over time. ... View more

Opened a case with Esri Support back on 12/19.  Esri Support was able to narrow the issue down even further, but the case remains open until Esri Development decides they have some time to look into it more.  I will post the bug number when it gets formally issued. ... View more

You are getting the syntax error on line 3 because there is no variable !Angle! in the Python function you defined.  This also explains why the second block of code doesn't give you an error. Are you saying the second code block above, the one that works, doesn't return the correct result? ... View more