IDEA
|
Reviewing the LocateXT documentation it appears the custom attribute function solely revolves around keyword searches. Due to variations of keywords or possible ocr issues it would be much more effective to have custom attributes to be able to be pulled out using regex expressions. This would be a powerful way to pull out specific values using single statements instead of multiple keyword definitions. In addition to regex , the tool might also benefit being able to run a custom python function or arcade expression. The same argument could be made for the use of regex or functions for locations. The location definition needs some work but ideally these locations would be defined by a set of regex functions. One example might be an expression to pull out zip codes or address strings and then potentially look up zip code features or geocode them against a service. The use of out of the box templates could benefit because right now there are only default templates. Once functions or regex are allowed then this could actually help others get going much quicker by sharing other libraries of templates including functions for parsing strings, regex expressions, etc... Thanks for the consideration!! Ronnie
... View more
09-01-2021
10:15 AM
|
6
|
0
|
573
|
IDEA
|
Agreed. Feature extraction should also be configured and able to be performed at the class level. So if we want zip codes features to be extracted ideally we could specify a regex expression , arcade expression or python and have those feature types be associated to a locator service. For the same document we might want to map any addresses mention so it would be defined we a regex which identifies address strings and want to geocode these against World Locator service? Defining 1 feature at a time as the author is running into is not sustainable and defeats the purpose of the product. It does not appear to support regex for locations or custom attributes so will likely be creating an idea for this type of support.
... View more
08-31-2021
12:58 PM
|
0
|
0
|
1102
|
IDEA
|
Similar to: Enable Cart for multiple Open Data downloads - Esri Community Select Multiple Items in Open Data and Download as... - Esri Community Multiple dataset downloads for Open Data Portals - Esri Community
... View more
07-06-2021
08:40 AM
|
0
|
0
|
767
|
IDEA
|
Please create a standardize address method to an existing Geocoding Service or possibly as its own service. Look ups should support a single candidate or possibly batch candidates.There are needs to standardize address information outside of geocoding the address, sometimes when an incomplete address or only the street name has been provided. We'd like to use this to convert Next Gen 911 style street names to legacy or vise versa. To make this work with a geocoding you must severely reducing the scoring which inherently creates other issues. Ideally an address candidate could enter the standardize method and the output results includes the candidate as well as the result split into the addressing components as configured in the service. The use of geoprocessing tasks is not a realistic option as the current standardize addresses tool takes in a dataset and requires an output dataset. This is overkill for simply standardizing a list of street names from Next Gen 911 style to the legacy style.
... View more
06-21-2021
12:24 PM
|
1
|
0
|
621
|
POST
|
We are experiencing this same issue when running the ESRI example code with python. We have been running this code for several years and this never used to happen. Performed a repair on the desktop install as Adityaraj Chavada mentioned above. This seemed to make Catalog work once and then it went back to reporting the "Function had no effect" error. We are on 10.7.1 . What finally worked for us was to upgrade our geodatabases from 10.5.1. -> 10.7.1 and the Analyze & Rebuild Indexes function worked as expected. Wish the tool would report such issues it is capable of knowing the GDB and software releases and should report this clearly to the administrator!!! In past versions the maintenance tools were rather stable working between versions of the geodatabase but that seems to be a new scenario which needs to be tested in future upgrades. bummer.
... View more
06-23-2020
12:51 PM
|
2
|
0
|
1239
|
IDEA
|
Thanks for the reference links and suggestion. This candidate does not exist yet so in this situation introducing the #STE did not work. We are expecting a no match like the SubAddress 10.x locator or the match without the unit with a score less than 100. This is one way we detect if an address exists or not. If addresses coming back with 100% score but do not match the input address this is a concern and should show up in the component scores but those don't appear to be available yet in the new locator roles. For us to inject # before the unit type into the single line input string will be challenging from our enterprise system if not nearly impossible. That does not seem like a reasonable solution. Shana Britt
... View more
06-16-2020
02:06 PM
|
0
|
0
|
1552
|
IDEA
|
For the new primary locator roles it would be really helpful to get the input search field values in the response. This way it can be checked to matched candidate. We are trying to use the new PointAddress and Streets Roles but getting invalid matches which did not occur in the SubAddress locator in 10.x. Due to these mismatches it would helpful to see what the input search address was so it can be compared to the result. In this example below, we are entering and a single line input: 4791 PELL DR STE 1, SACRAMENTO, 95837 However the match comes back without the STE which is not correct and should not have the 100% match score. The 10.x SubAddress locator returned no matches which is a better result but realistically there should be a candidate match with a lower score than 100. If the search input was in the result we would easily be able to compare the search string with the match string to weed thru these mismatches.
... View more
06-16-2020
12:50 PM
|
0
|
10
|
1632
|
POST
|
It would be nice to have an update on the search() functionality. Some of these threads are nearly 3 years old. We have the same need as Aaron & Cody as we would like to update several CSV's daily tied to select_one to represent an organizational structure 1 : many relationships so the select_ seems like the only way to model this Division -> Managers -> Staff This will be for employee check in related to the COVID-19 issues. Maybe the idea out there might get higher precedence if we tag the idea with COVID-19.
... View more
05-20-2020
01:28 PM
|
2
|
0
|
632
|
POST
|
Hello Celine, We experienced a very similar issue about a month or so ago. I reported a support incident and they only thing the support analyst advised me to do was to uninstall Data Store and reinstall. If you had any patches you will want to install those after the base install as well. In our case this allowed the database instance to start again and everything was in tact, although it took a very long time for this to uninstall and reinstall. Hope this helps! Ronnie
... View more
05-11-2020
12:37 PM
|
0
|
0
|
2153
|
IDEA
|
Mark, The field order action you are performing in this example is only for the map document in ArcGIS Pro just like reordering fields in an ArcGIS 10.x. map. If you inspect the fields in catalog, they are still in the original order. The intention of this idea is permanently reorder fields in the source feature class.
... View more
04-16-2020
07:43 AM
|
5
|
1
|
1614
|
IDEA
|
When using parameters it also restricts the category list to only None & the value in the parameter. This defeats the purpose of using url parameters as an initial filter since the other categories do not exist as a selection.
... View more
12-31-2019
12:24 PM
|
3
|
1
|
1526
|
POST
|
It would be nice if AppStudio had a simple wrapper to consume a Web App Builder application. We have tried this with the browserview and it works great but still not optimal because most of the browser navigation components are present. Many agencies still want to have a web and mobile version and WebAppBuilder solutions could solve these challenges. Maintaining 2 different code bases for very simple applications is an issue.
... View more
12-31-2019
11:04 AM
|
0
|
0
|
1048
|
POST
|
Yes because there are instances when publications do not work due to underlying database issues and these are not reported back to the end user. In the example of bug BUG-000122241 the publication failed. So knowing as much as possible before going into tech support saves us hours and hours on the phone. The additional details knowing the table published but all of the fields names did not have associations in the service was part of this root cause analysis.
... View more
12-09-2019
01:39 PM
|
1
|
0
|
2153
|
POST
|
Thanks Elijah, this solution worked for me for the hosted feature service database (9876) and really appreciate the help!! We needed to connect to the backend database to troubleshoot converting hosted feature service back to an enterprise data store. We were running into an issue with column names and case sensitivity since our widgets broke in an existing Web Application as we are trying to port the database to enterprise. This helped confirm all column names exist as lower case in the backend database including objectid & globalid. Also when column names exceeded 32 chars we did not know how it named them and it basically renamed all of the columns with numeric suffixes and alias values with the entire name.
... View more
12-09-2019
01:18 PM
|
1
|
2
|
2153
|
IDEA
|
This is a great idea and we have resorted to using tinyurl for this exact purpose.
... View more
12-04-2019
12:51 PM
|
0
|
0
|
628
|
Title | Kudos | Posted |
---|---|---|
1 | 01-04-2024 08:13 AM | |
1 | 12-07-2022 01:27 PM | |
1 | 02-03-2023 08:49 AM | |
2 | 10-25-2022 11:32 AM | |
6 | 09-01-2021 10:15 AM |
Online Status |
Offline
|
Date Last Visited |
Thursday
|