|
POST
|
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
01-20-2015
07:19 PM
|
0
|
2
|
1871
|
|
POST
|
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
01-20-2015
06:48 PM
|
2
|
2
|
2881
|
|
POST
|
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
01-20-2015
12:52 PM
|
0
|
0
|
2881
|
|
POST
|
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
01-20-2015
10:00 AM
|
0
|
0
|
1885
|
|
POST
|
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
01-20-2015
09:54 AM
|
0
|
0
|
1885
|
|
POST
|
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
01-20-2015
07:13 AM
|
0
|
2
|
2893
|
|
POST
|
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
01-16-2015
02:13 PM
|
1
|
0
|
1287
|
|
POST
|
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
01-16-2015
01:46 PM
|
0
|
4
|
3354
|
|
POST
|
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
01-16-2015
10:11 AM
|
0
|
1
|
1375
|
|
POST
|
It isn't called "code wrap" but Insert > Syntax Highlighting
... View more
01-16-2015
10:00 AM
|
0
|
0
|
1375
|
|
POST
|
It is a misnomer. "Last used ArcGIS Pro" really means the last time you authenticated against the license server to try and use ArcGIS Pro. Whether ArcGIS Pro is successfully launched once the license is obtained/checked isn't what is being tracked on Esri's side.
... View more
01-16-2015
09:50 AM
|
1
|
0
|
3661
|
|
POST
|
The code you provide above is from the Making Field Calculations help from ArcGIS 9.3/9.3.1, and therein lies your problem. The code Esri provided was VB/VBA and involved accessing ArcObjects. Starting with ArcGIS 10.0, Esri moved to a VBScript parser instead of a fuller-featured VB/VBA. Although some VB code still works in the code block for the field calculator, the specific code you used doesn't because you can't acess ArcObjects through VBScript. Even if the code you posted worked, VB support has been on life support for a long time, and you should really consider moving to Python. If you simply change the parser to Python, the following code will work in the expression box (you don't need a code block): !shape.extent.XMax! . Since it seems you are working with points, and single points at that, the extent of the geometry will be the geometry itself. You could also use !shape.firstPoint.X! as well.
... View more
01-16-2015
09:46 AM
|
2
|
0
|
15567
|
|
POST
|
If Esri is only posting ArcGIS Pro Prerelease (no updates) in MyEsri, and users need to update through ArcGIS Pro, how do you recommend he upgrades if he can't launch ArcGIS Pro?
... View more
01-16-2015
07:56 AM
|
2
|
0
|
3661
|
|
POST
|
You may want to check out Issue with SQUID Proxy server and ArcGIS Online and ArcGIS Pro.
... View more
01-15-2015
11:51 AM
|
1
|
1
|
1075
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 3 weeks ago | |
| 1 | a month ago | |
| 1 | 4 weeks ago | |
| 3 | 4 weeks ago | |
| 1 | 05-22-2026 05:27 AM |
| Online Status |
Offline
|
| Date Last Visited |
a week ago
|