|
POST
|
It takes a some time to work with but I would recommend trying the jinja2 library or alternative templating library. It has many options for looping over python objects. We have standardized our formatted email's using html and attachments. It works very well, it is much easier to copy and reuse existing templates than to understand inline print statements.
... View more
12-19-2016
06:54 AM
|
0
|
0
|
2332
|
|
IDEA
|
Please provide a test / dev / qa ArcGIS site for organizations to perform and test functionality. This site does not have to be a full mirror or contain all user licenses and counts, credits but please some place to play with functionality without making a complete mess in the "LIVE" production site. Most cloud providers provide access to a "production" as well as a "test" site as this is expected in such an important platform. The test site would be helpful to play with site organization, scripting and new capabilities without touching the LIVE / production site.
... View more
12-05-2016
03:37 PM
|
2
|
0
|
434
|
|
IDEA
|
Why have a user enter this at all? You might consider post-processing this until a version of "attribute assistant" is available for the arcgis platform. There are bigger problems when considering the potential for multiple users and the possibility of disconnected states in Collector/Mobile. We have the same problem with sde geodatabase unique fields as they are not supported in a multi-user environment so the only solution for us has been attribute assistant and/or post processing the generation of the ID's.
... View more
11-28-2016
01:58 PM
|
1
|
0
|
977
|
|
IDEA
|
This appears to be a new "feature" in 10.4.1 which did not exist in previous releases. If the .sde connection file cannot be found this breaks the MXD. In previous releases the sde connection information persisted in the map document if the password option was saved in the original .sde connection file. Thanks! Now we have a number of broken MXD's which open just fine in previous releases, what was the intention of this change especially at this point in the lifecycle of the ArcMap product which is end-of-life . Guess we have to contact support who probably have no clue this change was introduced and spend a 1/2 day explaining it and demonstrating it to them. How about reverting the functionality back to how it used to be? Unfortunately arcpy will not be able "respond" to a check data source option unless the mapping modules are updated.
... View more
09-23-2016
12:21 PM
|
0
|
0
|
506
|
|
IDEA
|
We used to use Query Layers to append into existing ArcSDE Feature Classes but something changed in recent releases and the ability to do this. The problem is Arcpy cannot determine the difference between Multi-point vs point feature class in the query layer. This requires us to save a LYR file with these properties to be set for arcpy operations to be successful. Please allow ArcCatalog, ArcMap, ArcPro the ability to auto-detect the spatial data type. Multi-Point, Point, Polygon, Multi-Polygon should able to be determined based on the spatial engine. Spatial databases provide the type to be determined based on a spatial property so assuming the Query layer supports all of the ArcGIS rules, why can't it determine the spatial data type?
... View more
09-19-2016
02:01 PM
|
1
|
0
|
812
|
|
POST
|
Thank you Joshua! I was hoping to be able to access the unique IDs assigned to layers in the MXD when reading the MXD using Arcpy. It appears this property is missing from the Arcpy.mapping module and will likely submit an idea for this one.
... View more
06-10-2016
01:38 PM
|
0
|
0
|
2682
|
|
POST
|
In ArcMap 10.3 the option to assign unique layer ID's was enabled. When enabled this allows map authors to set the numeric ID's accordingly. Can this data frame property be read in Arcpy to determine if an MXD is using this setting? Can arcpy access the layer ID thru the layer object? Thanks for any info Ronnie
... View more
06-08-2016
04:14 PM
|
0
|
5
|
6451
|
|
IDEA
|
ArcPy functionality using and detecting Query Layers is very limited. Identification - In the arcpy.mapping module there is no proper way to identify a query layer. There should be a method or property to identify the layer in question is a query layer. Update Query - In the arcpy.mapping module there is no ability to modify the query portion of the query layer. repathDataSource - This method does not work properly for Query Layers especially if the database name has changed. Using SQL Server the database name is part of the query and this method does not update the database inside the query layer properties. This could be dealt with if updating the query was possible but currently it is not so repathing a map document using query layers with differing databases is not an easy task or nearly impossible.
... View more
06-06-2016
01:01 PM
|
7
|
1
|
1437
|
|
IDEA
|
ArcPy functionality using and detecting Query Layers is very limited. Identification - In the arcpy.mapping module there is no proper way to identify a query layer. There should be a method or property to identify the layer in question is a query layer. Update Query - In the arcpy.mapping module there is no ability to modify the query portion of the query layer. repathDataSource - This method does not work properly for Query Layers especially if the database name has changed. Using SQL Server the database name is part of the query and this method does not update the database inside the query layer properties. This could be dealt with if updating the query was possible but currently it is not so repathing a map document using query layers with differing databases is not an easy task or nearly impossible.
... View more
06-06-2016
01:01 PM
|
5
|
0
|
1098
|
|
POST
|
Is it even possible to detect a if a layer is a query layer using ArcPy?
... View more
06-06-2016
09:40 AM
|
0
|
0
|
1347
|
|
POST
|
Yes the fix is we have to change our APT values to # which is very silly when the source data matches USPS standards. The locator supports the unit_type column and it is mapped to our column but clearly does not work. Changing to a # only provides a 98.0 score because the unit_type does not match, huh?? Something is wrong here and improving the scoring is not documented anywhere. This is what #BUG-000093854 refers to. Give it a try with your source data. W were not happy with the results and we have wasted months of time trying to get it to work well.
... View more
05-06-2016
01:49 PM
|
0
|
2
|
2273
|
|
POST
|
Hello Gabi, Unfortunately no we have reverted back to the 9.x locator style for units because the 10.x locators are still not documented well or work very well for that matter. We expect an address locator with units to match at 100% and this is not the case in the current versions and locator style. There are bugs in the new styles. Below are all of my ArcGIS Ideas, enhancements and bugs which you might consider reviewing and voting for if you agree. Several releases and years later we are still waiting and now looking at 3rd party solutions because when we call support they call this a "Customization" yet no complete documentation exists and we are using the out of the box locator style. Fully document the Customizing Locator process and update Locator documentation https://c.na9.visual.force.com/apex/ideaView?id=087E00000005AR4IAM Standardize Addresses Tool mixed case results and other inconsistencies https://c.na9.visual.force.com/apex/ideaView?id=087E00000004GOqIAM #NIM070066 The Standardize Addresses tool does not return the same address standardization using ArcGIS Version 10 address locators as compared to version 9.3.1 address locators. Update File based locator's reference feature class https://c.na9.visual.force.com/apex/ideaView?id=087E00000004EhvIAE Locator style for Apartment / Units in core product https://c.na9.visual.force.com/apex/ideaView?id=08730000000by67AAA #NIM081240 [Enhancement] Please add support for building/unit/apartment numbers in the standard locator styles. #BUG-000093854 When using the US Address-Single House Subaddress locator style with the Find tool, the match score is improved if using '#' as the unit indicator instead of 'APT' even if the original input data uses 'APT'. #NIM059962 Cannot create an address locator with a multipoint shape file. The result is a Background Processing Error or ArcGIS Application Error. schemaLockingEnabled for Geocode services https://c.na9.visual.force.com/apex/ideaView?id=087E0000000CxTRIA0
... View more
05-06-2016
12:36 PM
|
0
|
5
|
2273
|
|
POST
|
Yes I am surprised they work thru mxd import but not Layer files or add Data? I agree with above if they are going away why supported them at all with mxd import? Raster Catalogs do have a place how else do you do a time-series enabled raster publication?
... View more
04-22-2016
01:26 PM
|
1
|
0
|
1959
|