Latest Contributions by KyleGruber

‎04-23-2019

Fantastic, thank you Mike!

‎04-23-2019

Just wondering if anyone has taken a look at this, especially the crash that cannot really be debugged by me as it is a native crash in RuntimeCore?

‎04-15-2019

Ciara, This is excellent news! This latest release of Runtime/Pro has been awesome for consistency between what you see/are capable of in Pro vs Runtime. Thank you.

‎04-12-2019

When creating a street address locator with suggestions enabled, is there a way to include fields such as Predirection, Postdirection, Suffix, etc but not make them a required part of the geocoding process? For example, when I do this search with the World Geocoding Service: Despite the fact that I'm not entering predirection as part of my inquiry, it's able to pull up 100 E Main and 100 W Main. Does this require custom logic outside of the standard locator calls, or possibly a point address locator needs to be part of a composite? I can't seem to achieve this using a Locator and Runtime SuggestAsync, even turning the minimum score down to 0. Thanks!

‎04-10-2019

I'm getting an Access Violation in runtimecore.dll when calling SuggestAsync on LocatorTask (ArcGIS Runtime 100.5). This is a composite address locator comprised of 3 Street Address locators embedded in a mobile map package (created with ArcGIS Pro 2.3.2). What I'm trying to accomplish is less strict enforcement of the address suggestion/geolocation when it comes to pre/post directions and suffixes. For example, if the user enters "100 MAIN", I would like the suggestions to include 100 E MAIN ST if it exists. I have not found a way to accomplish this with a single locator, so instead I stacked locators in a composite (first one contains all elements, second one removes pre/post directions, third one further removes suffix). If there is a better way to accomplish this, I would certainly be open to hearing it. A sample project with this issue can be downloaded here: https://helpdesk.alertts.com/content/Debugging/ArcGISApp1.7z Note: Just in case it's not obvious, to reproduce the issue type anything in the textbox in the upper-left corner.

‎04-10-2019

I tried this with ArcGIS Pro 2.3.2 and the newest version of runtime (100.5) and can confirm that it works perfectly! Thank you Pro and Runtime teams!

‎02-27-2019

Thanks for the confirmation Mark!

‎02-27-2019

Getting an exception when trying to load an MMPK I just created from ArcGIS Pro. Esri.ArcGISRuntime.ArcGISRuntimeException: 'Mobile map package version is not supported.: Mobile map package version not supported : 3.0'Esri.ArcGISRuntime.ArcGISRuntimeException: 'Mobile map package version is not supported.: Mobile map package version not supported : 3.0' Having no problems with MMPKs created 2-3 months ago. ArcGIS Pro v2.3.1 ESRI.ArcGISRuntime v100.4.0.0 EDIT: Upon further research, it appears that using the Create a Locator geoprocessing tool causes the MMPK version to be updated to 3.0.

‎10-09-2018

Tim Witt‌ Thanks! I'm with Alert Public Safety Solutions (alertpss.com). We're a tier-2 and 3 CAD/RMS/JMS provider based out of Columbus, OH. We are currently in the process of redeveloping our 3rd party ESRI "compatible" mapping solution with the ArcGIS Runtime.

‎10-09-2018

Tim Witt, Thank you very much for providing this awesome tool. I work for a CAD/Mapping provider and we're trying to be proactive with helping our clients make this transition, would you mind if we pointed them in the direction of this post/tool with obviously some disclaimers as a helpful resource? Thanks!

‎04-19-2018

Joe, Thank you very much for the information. After wrestling with it for a few hours getting 9999 error codes trying to generate a vector tile package, I was finally able to accomplish this. Are you actually loading the vtpk file locally, and if so, would you mind pointing me in the right direction on how to do so? Every attempt using ArcGISVectorTiledLayer has resulted in a blank map, and I get a "File Not Found" error when actually calling LoadAsync on the layer which I believe actually means that it's not a supported file type (this is a known, misleading exception). EDIT: Joe, I'm an idiot, and you're a genius. Forgot that you use forward slashes with URIs pointing to file paths. Map looks perfect as a Vector Tile Package, thank you so much!!

‎04-19-2018

Thank you for the clarification! I do think this would be a very crucial feature to support for MMPKs, it sort of kills the styling and readability of the map without it. I do however think I have found a pattern of splitting files based on feature type and setting min/max visibilities that will end up accomplishing what I am looking for. Sometimes you just have to ask stupid questions to spark a good idea.

‎04-19-2018

Any ideas/clarification on this? Even a simple yes/no on scale based sizing support would be helpful, and let me know I'm not doing something wrong. Furthermore, this project consists of imported shapefiles that have styled/labeled. I'm taking GIS data (roads, addresses, ESN, hydrants, etc) from municipal GIS departments in this format because they are not prepared to migrate from ArcMap to ArcGIS Pro. The application we're developing has to follow an offline-first model, so taking this shapefile data and creating MMPKs from them seems to be the best way to handle this (I'm aware that the Runtime SDK directly supports reading shapefiles, but we're trying to move away from this model, and it still seems to be a bit buggy in the 100.x series compared to reading MMPKs). Am I totally off-base here, is this an unrealistic method of going about this?

‎04-11-2018

Hopefully to give you a better idea of the issue... What the map looks like in ArcGIS Pro: What the map looks like when loading the MMPK into a simple WPF app: Many things don't seem to be sizing correctly, some labels are completely missing (or I now notice barely showing up) for unknown reasons (the city names highlighted in orange). The thick white lines throughout the county appear to be the roads that shouldn't be showing up with the scale sizing. Any help or clarification on these differences would be greatly appreciated!

‎04-10-2018

Is scale-based sizing supported in the Runtime SDK with MMPKs generated from ArcGIS Pro 2.1.2 (or will it ever be)? It doesn't seem to be carrying over whatsoever from Pro to Runtime. Opening the MMPK in Pro displays everything exactly as it does editing within the original project.

Online Status	Offline
Date Last Visited	‎08-05-2025 08:44 AM

My Ideas

Latest Contributions by KyleGruber

Re: Access Violation In Runtime 100.5 With MMPK Containing Composite Locator

Re: Access Violation In Runtime 100.5 With MMPK Containing Composite Locator

Re: MMPK - Scale-Based Sizing

Flexible Locator Suggestions Like ArcGIS World Geocoding Service

Access Violation In Runtime 100.5 With Composite Locator Containing New Locator

Re: Some suggestions of Geocoding Service invalid

Re: Mobile Map Package Version Is Not Supported

Mobile Map Package Version Is Not Supported

Re: NENA NG911 street tool

Re: NENA NG911 street tool

Re: MMPK - Scale-Based Sizing

Re: MMPK - Scale-Based Sizing

Re: MMPK - Scale-Based Sizing

Re: MMPK - Scale-Based Sizing

MMPK - Scale-Based Sizing

Re: Locator Custom Output Fields In Runtime

Re: Is URISA using the "P" in GISP correctly?

Local Locators not working in 100.7?

Re: Local Locators not working in 100.7?

Re: MMPK - Scale-Based Sizing