Latest Contributions by DavidKnudsen

I can provide clues about what causes this to happen, but I haven't found a solution yet. It has to do with font scaling that takes place outside of AGOL. The two common causes are that the browser zoom level is not default and that the Windows "Scale and layout" display setting is not set to 100%. Laptops are often affected by the latter, as Windows defaults to scaling by 125% or 150%. Browser scaling is typically triggered by the user, either intentionally (to make small text easier to read) or accidentally (there are keyboard shortcuts that can do this--Ctrl-+, Ctrl--, and Ctrl-0). When you set scaling to 100% in both of these environments, the splash widget will likely behave as configured. ... View more

On our network, users connect to a central server to use ArcGIS, so ArcGIS isn't newly installed for each user, but each server user running ArcGIS for the first time would normally get an empty list of folder connections. In older versions of Windows, we used to manage this by copying the Esri user profile from a user who had folder connections set up in the desired way to the "Default" user profile. The key file was ArcCatalog.gx, which resided in %APPDATA%\Esri\DesktopN.N\ArcCatalog. Users starting ArcGIS for the first time would have the default user profile copied to their own user profile automatically by Windows. Unfortunately, later versions of Windows (8, 2012, 10, 2016) don't use the default user profile anymore. I'm at a loss as to how to accomplish my task under these newer versions, but this idea could help in both the shared server case and the separate installations case. ... View more

I should probably also have explicitly mentioned that the many-to-many relationship class table could be an event table on the links instead (or you could treat it as such). The links feature class needs to have measure values, which can be automatically created. Each event table record stores from- and to-measures for the link (presumably most of them span whole links), the link ID (route ID) and the business data ID. You can add the links and event table as an event layer to a map document and save it as new features—which does the work of chopping up link shapes for any that are only partly used—then dissolve on business data ID, as you point out. (Those steps can also be easily automated using Model Builder or Python.) Event tables allow overlaps, too, in the case where any of your business data routes overlap. (If a given link is part of two business data routes, the event table has two records for that link, differing only by their business data ID.) ... View more

Do your business data records need to reference portions of links rather than whole links? If not, you might consider creating an attributed many-to-many (M:N) relationship class between your business data records and the roads layer. In fact, you could possibly handle referencing portions of links as well, storing the from- and to- measures of the links in the relationship class attribute table. Unfortunately, this approach does not automatically provide for a "single graphic" for each business data record. Such graphics would have to be built, essentially by joining from the road layer to the relationship class attribute table and dissolving on the joined business record ID. If each road link is associated with no more than one business record, then this could be done all at once, but if links can be associated with more than one business record you'd need a tool that loops through each business record, selecting and dissolving the associated road links and appending them all together into one feature class. That approach was baked into the custom software behind the Massachusetts Road Inventory up until this year, when the Inventory was migrated to Roads and Highways. As in your case, each Inventory link was its own route, while numbered routes as drivers perceive them (the equivalent to your business records) were listed in a table that participated in an attributed relationship class with the links. A nightly build process regenerated a numbered route feature class. ... View more

I've never tried it but it looks like IDatasetEdit.IsBeingEdited might be what you're looking for. It does, indeed. I just wasn't using quite the right search terms to pull that up, I guess. Many thanks for your quick, on-target reply! --David ... View more

In addition, I really wish that relative paths would support traversal through parents, like UNIX paths. For example, it is quite common to keep map documents in sister directories to data directories, and currently ArcGIS relative paths are no use in this case (I think, though I haven't checked recently). Data has to be in same directory or a descendant directory for relative paths to work. ... View more

Yes, the tool is a help as far as it goes because of the ease of configuring it to compare records on some or all of their attributes (including geometry) all at once (laborious to script such comparisons when working through a join), but I am always comparing feature classes that have both added and deleted records. To make the comparison work requires pre-processing the two feature classes--using a join--to remove the features not common to both by ID. I add my vote for extending the flexibility of this tool to make it directly useful in more cases. ... View more

@Chris_Fox Sorry I missed your reply. I think in the case I was talking about, both the location of the feature class and the location of the table change. For example \\old_server\share\internally_owned_data.fgdb\featureclass and \\old_server\share\externally_supplied_data.mdb\table both move to a new server, remaining in separate workspaces: \\new_server\share\internally_owned_data.fgdb\featureclass and \\new_server\share\externally_supplied_data.mdb\table. This thread is old now, but my recollection is that the only way the source of a table on the right side of a join could be updated was if it shared the tablespace of the featureclass it was joined to; it would be updated at the same time that the source of the featureclass was fixed. Otherwise there was no direct way to access and change the source of a joined table. I don't know if my interpretation of the documentation was correct on that score and if it still holds, if so. ... View more

I like this idea, but I worry about the RAM/file space that could end up being consumed. I work with data sets of several hundred thousand records, and though the time savings in just recalling a previous selected set would be correspondingly greater, Imagine how the file size could balloon after I had made forty or fifty selections on that set... Maybe it's manageable, but if not, at least being able to store the history of the selection criteria would be great. I think that has been suggested elsewhere. ... View more

I agree--field maps are powerful and useful, but I have been particularly frustrated when trying to use them in Python scripts. Three principal problems stem from the verbose parameter structure: The "convert to Python code snippet" functionality does not introduce line breaks, and the lengthy parameter text causes a very, very wide line that must be laboriously reformated to make it all visible in the Python IDE on one screen without scrolling horizontally. The internal structure of the field map parameter is very poorly documented, making it difficult to write from scratch without using the "convert to Python code snippet" functionality. The format of the parameter is particularly awkward when used on a joined table, and even more so when the tables used in the join are themselves parameters supplied to the larger script. That is, the field map specifies fields by their fully qualified names ("a_certain_table.field_one"), but if the component table names are subject to change, the parameter must be written in Python as sz_table_name_variable + ".field_one" to allow the tool to operate correctly when "some_other_table" is used as input to the join instead of the original "a_certain_table". If the field map could replace the fully-qualified field names with an unqualified field name together with an ordinal number indicating the table component it came from (omitted, or "1" for unjoined table input), using the tool in parameterized scripts would become much easier. ... View more

I may be wrong, but the "Pivot Table" tool in the Toolbox may accomplish the crosstab that you want, under a different name. Have you tried it? ... View more

I may be wrong, but the "Pivot Table" tool in the Toolbox may accomplish the crosstab that you want, under a different name. Have you tried it? ... View more

Is this kind of functionality addressed by feature-linked annotation in ArcGIS? Granted, if you change the rules for label placement, then the annotation must be regenerated and any manual placement/removal has to be redone. But apart from that, annonation offers a way to "remember" manual changes to individual labels. ... View more