POST
|
Matthew, Michael and I work together, and he's the one who alerted me to your other post. Our problem is two-fold, with one issue being the ready identification of any Beziers (we're thinking we've got a mixed bag), and the other being a general reluctance (to put it mildly) to simply generalize all such data, as that defeats the purpose of ever having improved the data w/ Beziers in the first place. Also, of the (4) tools mentioned by Ayan Palit in the other post, all of them exclusively seem to convert curvilinear data to splined, straight segments, not true curves. In our aforementioned prior cleanup from several years ago, we opted to manually replace the ugly, splined, straight-segmented "curves" by hand, because the output of the Simplify by Straight Lines and Circular Arcs tool was awful - resulting in kinked, non-smooth strings of segments. I just hate the idea of regressing our data because of the shortcomings of the Fabric model itself.
... View more
01-05-2023
11:59 AM
|
0
|
1
|
711
|
IDEA
|
@MatthewBeal What do you mean by "converting them to true curves"? I've always used both the proper name Bezier curves and the generic term "true curves" interchangeably, as they're simply mathematical curves (as all curves are). In @AyanPalit 's reply above, all (4) of his proffered solutions involve removing any and all curves - planarizing the linework to densified splines. This seems like a low-tech, retrograde way to go. By way of background, we had set upon an aggressive cleanup project about 6 years ago now of our countywide parcel data (in SDE), to remove millions of unnecessary vertices from our splined geometry (originally created in an ArcINFO 7.2 environment), converting them to Bezier/true curves, as a preparatory step to get our data into the Parcel Fabric - specifically because the Fabric at that time couldn't handle the number of vertices during the import process. We spent several months painstakingly creating Bezier curves... In any event, and for a variety of other reasons, we aborted the move to the Fabric. Fast forward to now, and we're re-embarking on the effort, albeit w/ a very different version of the Fabric as it exists now. At no point has our consultant indicated any issues whatsoever w/ having Bezier curves in the Fabric (and they know our data is filled with them). Gavin
... View more
12-23-2022
07:59 AM
|
0
|
0
|
936
|
POST
|
I've requested the full output/logging from our developer of our other tools, as well, hoping to see what the interaction is. The AA log shows nothing. I'll forward anything pertinent that might be useful. Thx.
... View more
05-12-2020
10:09 AM
|
0
|
0
|
1615
|
POST
|
We have NO rules set in the DynamicValue table for Aliases; we're handling them exclusively using our custom tools. I'm attaching the debug log... which really only shows the segment ID generation, as well as the creator/editor (database user) and time/date stamps. Thanks, Gavin
... View more
05-12-2020
09:11 AM
|
0
|
2
|
1615
|
POST
|
We're encountering some unexpected behavior with regard to related records... We're currently testing the interaction between AA and some custom edit tools we also have in place for our RoadCenterline feature class and two related table(s) in SDE. I'm using AA to obtain new SEG_IDs using the GenerateID table (on create). Because the ID values are generated on create, they're already present when our custom tools pull the attribute values into a data grid to be presented in a form for further user interaction. That works fine. In addition to the main segment tab, the user form also has an Alias tab where the editors can provide road name alias detail to be added to the related Road_Name_Alias related table (1:0-M relationship). This relationship uses the SEG_ID as the primary/foreign key. What's supposed to occur is that the tools read the current segment's SEG_ID and apply it to the SEG_ID of the alias record being created. However, what appears to be happening (according to our developer tracing the code) is that AA is firing again, to create new ID values for the new Alias record - despite the fact that there are NO linked record method(s) whatsoever defined in the DynamicValue table. Nothing should be triggering AA to be generating another ID... But, because it apparently is, it clobbers the creation of the related record, dropping it altogether. This same issue is also affecting the custom tool's code which handles the splitting/merging of segments - i.e. the deletion/creation of split/merged related records. Our developer found this BUG (BUG-000103189 Attribute Assistant Copy Linked Record method, fails to run when making a geometry change on a polygon th… ), but I'm not clear that it relates to our issue, since it presupposes that you'd have the Copy Linked Record method in the DynamicValue table in the first place - which we don't. Any ideas what might be occurring? Gavin #GenerateID #RelatedRecords #LinkedRecords
... View more
05-12-2020
08:29 AM
|
0
|
4
|
1615
|
POST
|
A little bit of further testing would seem to indicate that it matters when AA is toggled on in relation to the edit session... I first edited the config file to alter the following, in order to maintain explicit control over the order of operations: "AttributeAssistant_EnabledOnStartUp" value="False" "AttributeAssistant_EnabledOnStartEditing" value="False" "AttributeAssistant_ClearLastValue" value="True" "AttributeAssistant_ClearLastValueStopEdit" value="True" I reopened my edit MXD, making sure that AA was off. I started an edit session, and then toggled AA on. At that point, the CURRENT_USER method will grab the appropriate database username. If this is done in reverse, or if AA is already toggled on, prior to an edit session being started, it seems that the CURRENT_USER variable remains unset/null.
... View more
04-17-2020
01:09 PM
|
0
|
0
|
1615
|
POST
|
Thanks, Michael. I created a new MXD and loaded my layers back into it. I had already, in a separate MXD that I created just for editing the AA tables, made sure to reset my parameter back to 'D'. I also made sure that I had no other ArcMap sessions open concurrently. When I created a new road feature in my new MXD, it correctly populated the Creator field, as expected. I suppose the other MXD had some crossed wires in it... which is odd, as I really didn't have that many other layers or tables loaded into it; it was pretty sparse to begin with. I guess I'll just move forward and keep my eye on its behavior during our testing. Thanks.
... View more
04-17-2020
08:14 AM
|
0
|
1
|
933
|
POST
|
The section of the log file pertaining to this method returns the following: ------------------------------------------------ ------------------------------------------------ Row Info Row Number 3 TableName: RoadCenterline FieldName: Creator ValueInfo: D ValueMethod: CURRENT_USER On Create: 1 On Change: 0 Checking for Subtype Restriction Field Name: Creator was found at index: 47 Trying: CURRENT_USER Username: Finished: CURRENT_USER ------------------------------------------------ ------------------------------------------------ You can see the Username is blank. When I switch the parameter to 'W' instead of 'D', the value is captured here, as well.
... View more
04-16-2020
01:13 PM
|
0
|
3
|
933
|
POST
|
I’m having some issues with the CURRENT_USER method in our SDE environment… My DynamicValue table is stored in SDE, owned by our LGIM schema, and in turn is loaded into my edit MXD using the LGIM user credentials (in order to make it editable as I tweak things iteratively, etc.). The data I'm testing against is a RoadCenterline feature class which is also stored in SDE, owned by our TRANSPORTATION schema, and subsequently loaded into my edit MXD under my user credentials, hitting an edit version. I configured the DynamicValue table to populate a Creator field in RoadCenterline using the CURRENT_USER method, w/ On Create = True, and using the 'D' parameter in the Value Info to pull the username from the current database user. However, when a new segment/feature is added, my results have been varied (but never correct😞 the Creator field is either left null, or is populated with 'LGIM'. I'm not sure how either value is possible, given that the connected user editing the dataset in question is never the LGIM user... If I specify the 'W' option for ValueInfo field, I do get the correct Windows User, but that defeats my purpose. Has anyone run into similar difficulties with this? #CURRENT_USER
... View more
04-16-2020
12:36 PM
|
0
|
5
|
933
|
POST
|
Ok, thanks - I'll give this a try. One question, though: I'm assuming that the return resp['token'] line will simply pass the value just the same as the original return token (even though it's setting/using a different variable name)? In other words, the token = createToken(baseURL,username,password) line simply receives the returned value from the function regardless of what it's called? Gavin
... View more
04-01-2019
07:50 AM
|
0
|
1
|
1282
|
POST
|
Jonathan, I'm working w/ Mike to revise and test our code, and I've gotten the above to work when bypassing the certificate verification. However, when I comment out and alter the code as you've indicated above, I receive the following Python error (ignore line numbers, as they differ from your raw script above): Traceback (most recent call last): File "Stop_GeocodeService_Cert.py", line 148, in <module> token = createToken(baseURL,username,password) File "Stop_GeocodeService_Cert.py", line 118, in createToken token = openURL(tokenURL,params)['token'] TypeError: sequence index must be integer, not 'str' For whatever reason, it appears to no longer like the ['token'] parameter... Any ideas why this might be? Gavin
... View more
03-29-2019
12:24 PM
|
0
|
3
|
2234
|
IDEA
|
Thanks, Kory - I'll give this a try. I'll still have to convert our existing EMFs to PNGs first, but this helps. Gavin
... View more
08-09-2018
07:12 AM
|
0
|
1
|
1489
|
IDEA
|
Pro currently provides for Picture Symbols under the standard layer Symbology tab, allowing users to import raster or vector artwork by browsing to a file – however, this ability is not available for the symbol properties within the Label Class tab (under the Symbol > General > Callout section). Our organization has previously created custom vector artwork for our major roads’ highway shields in ArcMap, but are unable to utilize it in Pro. To be clear, importing an existing ArcMap MXD (which has this label symbology applied) into a new APRX will import the artwork so that it appears (as a Point Symbol), but the graphic/file itself is inaccessible/unbrowsable, once imported. More than that, if creating a brand new APRX (applying label symbology from scratch), there is no way whatsoever to import such graphics files. This functionality is as necessary in the label context as it is in the general symbology context for our organization. Also, the Picture Symbols which can be imported under the Layer Symbology tab are limited to the PNG file type (where vectors are concerned). It would be helpful if the older EMF/WMF vector file type(s) were also able to be imported, since this was the format that ArcMap required – otherwise, all such vector symbols would have to be recreated/exported (from the original Adobe Illustrator files) as PNGs in order to be utilized.
... View more
08-06-2018
08:54 AM
|
11
|
3
|
1961
|
IDEA
|
In ArcCatalog (Desktop), the Geodatabase Administration window is accessed via the right-click Administration > Administer Geodatabase… context menu, and displays as an independently threaded window, allowing interaction with the rest of the ArcCatalog interface. In Pro, the Geodatabase Administration window is nested under the Database Properties > Connections > Show connected users and locks…, and doesn’t allow simultaneous focus/interaction with the rest of the application. Additionally, since you cannot keep this window open, it becomes necessary to exit, make changes, and check back. The wasted steps in having to drill down through the Properties window(s) each time is very inefficient and frustrating. As an ArcSDE admin., the GUI setup/focus in Desktop was advantageous, as it’s common to be interacting with datasets in Catalog while simultaneously needing to monitor/refresh the connections and locks in order to manage them. Ideally, the Geodatabase Administration window would be a dockable window which allowed the administrator to choose from available database connections the one that was to be administered, remaining as an independent and persistent window throughout the .aprx session. As it stands, due to the way that Pro handles database connections on a per-aprx basis, it will already be necessary to have a dedicated "SDE Admin" aprx (or several, per environment) with admin-level connections saved in it. Having a dedicated Geodatabase Administration window would be very helpful in this regard.
... View more
07-23-2018
11:05 AM
|
15
|
5
|
1497
|
POST
|
Mike, I guess that’s where I’m remaining confused… It was my understanding that even if a feature class is enabled for non-versioned editing, the edit still needs to be done using the same valid credentials that would be required otherwise. In the case of the GenerateID table, only the Schema User (under which the table was created and data loaded) has that level of privileges. The individual editor/user account (under whose credentials the table was loaded into the MXD) does not have these privileges, yet is apparently able to write to the table, nonetheless. Does the ITransactions Interface, by nature, bypass the otherwise applied SDE permissions in doing what it does? Gavin
... View more
05-21-2018
08:15 AM
|
0
|
0
|
881
|
Title | Kudos | Posted |
---|---|---|
15 | 07-23-2018 11:05 AM | |
11 | 08-06-2018 08:54 AM | |
1 | 04-21-2017 11:52 AM | |
4 | 04-20-2018 07:57 AM | |
3 | 04-21-2017 07:27 AM |
Online Status |
Offline
|
Date Last Visited |
09-28-2023
07:34 PM
|