Latest Contributions by GIS_Spellblade

This ArcGIS Idea is to allow an additional option, when utilizing the H3 spatial index, to output the integer-based ID in either a BigInt or String format. This functionality would be a huge quality of life improvement and create better interoperability for utilizing this open-source spatial index specification.   While the new addition to utilizing the open-source H3 Spatial Index within the Generate Tessellation (basic, standard, advanced licenses) and Generate Grids and Hexagons (business analyst extension) is an excellent step forward; however, there currently exists a limitation that severely impacts interoperability with other platforms that utilize H3 which is that these hex tiles can be identified through their integer-based or hexadecimaI IDs. The current toolset in ArcGIS only outputs H3 tiles utilizing their hexadecimal IDs, this is an issue because the integer IDs require a somewhat complex formula for translating this into the integer ID-- --this is not a well-known piece of knowledge and a cursory search in a stack exchange will bring up results for a simple hexadecimal to integer conversion function. The easiest way to convert the two IDs (without looking up the formula spec on the H3 API documentation) is to utilize the Python library h3-py which can be downloaded utilizing the ArcGIS Pro GUI-based package manager (if a user knew that this is what was required). This significantly ups the requirement to interoperability with other H3 datasets (that may not have the hexadecimal ID included in favor of the integer-based ID) as a user will need to have in-depth knowledge that may not be required for what would otherwise be a simple data request/process.   import h3 some_hex_id = "8826c20001fffff" print(h3.string_to_h3(some_hex_id)) #613171383972659199   This ArcGIS Idea is to allow an additional option when utilizing the H3 spatial index to optionally output the integer-based ID in either a BigInt or String format. This would be a huge quality of life improvement and create better interoperability for utilizing this open-source spatial index specification. https://www.esri.com/arcgis-blog/products/arcgis-pro/analytics/use-h3-to-create-multiresolution-hexagon-grids-in-arcgis-pro-3-1/ https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/generatetesellation.htm https://pro.arcgis.com/en/pro-app/latest/tool-reference/business-analyst/generate-grids-and-hexagons.htm @MargaretCrawford    ... View more

GeoEvent Version 11.1 -  So I ran into what I think is an issue, but I don't have time to properly test, it looks like there is an issue with the Field Enricher (Feature Service) when you are working with a GeoEvent definition and spatiotemporal datastore that has been edited from its original creation. The results that I have seen are that when Target Fields are set to New Fields, the join works as expected and fields can be populated; however, when Target Fields is set to Existing Fields, the join does not work as expected and no fields are populated. The schema between the two GeoEvent definitions are the same and there shouldn't be any differences between them. I'm failing to understand how a difference in these options would affect a join which should match regardless of option selected. Based on preliminary testing with a fresh GeoEvent definition (created for purpose without additional added fields post-deployment) the Field Enricher (Feature Service) works when set to Existing Fields. ... View more

As we're all aware, there's a thousand ways to skin the GIS cat. Having an ability to measure the resource consumption of a GeoEvent Service (ideally with a pre-programmed & repeatable feed) would allow users to better optimize their GeoEvent Services and pursue different implementation strategies. This can be encapsulated into the following thought; should you pre-program your geofences or create them ad-hoc within the service? Obviously the answer is, it depends. Which is kind of a non-answer. We can whiteboard and conceptualize different ways to accomplish a task and list likely considerations but most users will not have a great understanding of which operations are more performant. While there is an argument for, if it works, it works. There are plenty of shops what would like to minimize resource utilization, a tool to measure that would help them achieve that goal through better prototyping. ... View more

The current service designer has extremely limited layout controls and are almost useless for organizing flows. This idea is to suggest some level of parity with the ArcGIS Pro Model builder in terms of Groups and Auto Layouts. Current State of GeoEvent Server: Current Layout Controls Proposed to have similar functionality as model builder: https://pro.arcgis.com/en/pro-app/3.1/help/analysis/geoprocessing/modelbuilder/grouping.htm ... View more

The ability to split incoming data based on groups or geotags seems a fairly standard process-- --especially if you are trying to populate downstream applications with the ability to filter based on a single attribute. Since much of the data streams are outside of a user's control, these processors are invaluable to split up data into a way that is usable within the downstream apps (experience builder, dashboards, etc.) which are not well-designed to ingest multi-categorical data. Since this tool is already Esri supported, let's add it into the standard installation and allow users to utilize it without the need to install the GeoEvent SDK. https://www.arcgis.com/home/item.html?id=68238a93e5fd4043ad0bbb501b265566 https://github.com/Esri/field-splitter-for-geoevent https://github.com/Esri/multi-cardinal-field-splitter-for-geoevent   ... View more