Latest Contributions by JoshuaBixby

I am glad you got a solution.  Since you are using a mobile geodatabase, I was going to suggest a more complex definition query, and it seems you went down that route on your own.  I will note that the code as shared here does not guarantee a single record for each GpsNumber (I am assuming each GpsNumber represents a different collar/animal), i.e., there may be edge cases where multiple GPSTime records exist in the layer for a single GpsNumber. ... View more

To quote myself from an earlier response: @JoshuaBixby wrote:   It helps to: Provide your data schema (field names, data types, etc...), or at least the relevant parts Even better, provide sample data.  If sharing data itself isn't possible, create an example dataset that can be shared. Share code snippets of what has been tried so far Share expected result and what results you are currently getting. Item #3 could be replaced with an explanation of a workflow instead of code snippets.  For example, how exactly are you interacting with the data?  You state: I have a dataset with 100,000 records, each one taken about every 15 minutes. I only need one per day for most cases. I'd like to make a view to grab just one record per day. Most cases?  What exactly does that mean, and what are the cases you wouldn't need just 1 record per day?   And what are you doing with a collection of 1 record per day?  Are you interacting with it in Pro for data exploration, are you making a static/hardcopy map, are you publishing it as a GIS service to make an interactive web map, etc....? Sharing what the requirements are will help people determine if there is a completely different approach entirely than focusing on how to manage date fields and objectids in a table view. ... View more

It helps to: Provide your data schema (field names, data types, etc...), or at least the relevant parts Even better, provide sample data.  If sharing data itself isn't possible, create an example dataset that can be shared. Share code snippets of what has been tried so far Share expected result and what results you are currently getting. ... View more

@HannesZiegler , great news, thanks for sharing and for getting the functionality fixed/updated. ... View more

For parameters names that are the same, e.g., mergePolicy and merge_policy, I understand how the difference comes about since Python's best practice for naming variables uses snake case while camel case is the convention with some other languages like C, C++, etc...  Where things get dicey for me is when the name itself is different, e.g., description and domain_description.  Even if one converts snake case domain_description to camel case domainDescription, they aren't the same name although they refer to the same item.  At least if the names were exactly the same and it was just a snake case versus camel case issue, it would be more straightforward to translate. Unfortunately, the discrepancy with handling parameter names propagates down into the accepted literals, which exacerbates the situation.   ... View more

Unfortunately, Python doesn't support parameter name aliases like some other languages because that would allow for a fairly straightforward way to address it. ... View more

See BUG-000125894 for ArcGIS Pro, Esri has no plans to address. ... View more

I agree about CTE.  I suggest you submit an ArcGIS Pro Idea to support using CTE with SQL Server query layers. ... View more

Something like the following should work or get you close: tbl = # full path to table or feature class text_fields = [ field.name for field in arcpy.Describe(tbl).fields if field.type == "String" ] with arcpy.da.UpdateCursor(tbl, text_fields) as cur: for row in cur: row = [ item.upper() if item else None for item in row ] cur.updateRow(row) ... View more

One must remember that ArcGIS Server accesses file-based data sources, including network file shares, using its own credentials and not the credentials of the person who ran and published the tool.  If the credentials running ArcGIS Server don't have access to the data set location, the tool will fail. ... View more

@TanuHoque , thanks for chiming in on this discussion and for considering the idea.  @DavidFotheringham1 , thanks for posting the idea and getting the discussion wrong.  I am always open to being wrong, even happy at times about it, when it means improvements come quicker than I expected. ... View more

Although I understand the value of having this functionality dynamic, and I don't think implementing a naive approach to it would be difficult, the fact that spatial operations are so compute intensive makes implementing an efficient means of doing it very challenging.  For the example given here, even a naive approach would likely perform fine, but what happens when there are millions of points or the polygon itself has tens of thousands of vertices?  In that case simply panning or zooming a basic map would result in the noticeable, if not significant, delay in refreshing the screen. Raising ideas is good, and I think the discussion around them in the community is good for Esri to read, but this is one where I would not hold my breath.  ... View more

Unfortunately, no, this is a major shortcoming of Esri's Named User licensing model.  My personal belief is that the shortcoming is purposeful, i.e., they could have addressed it by now if they wanted to address it.  So, organizations are left to come up with their own myriad of automations to address time-based Named User licensing. ... View more

More information would have to be shared before community members could provide anything beyond anecdote and links to general documentation.  For example, is this a hosted feature service or a referenced one?  If referenced, what is the back-end data store and what style of versioning is being used with the data?  Depending on the answers to these questions, there are even more questions. ... View more