Latest Contributions by AryleButler

Hello Don, I'm unsure what you mean by a custom schema for lxtgaz files. Are you referring to the output generated by LocateXT? Currently, LocateXT lxtgaz files require a location (in LAT/LONG form), a name, and--optionally--keywords. There is a step by step process that can be followed when using LocateXT in Desktop or ArcGIS Pro, or you can upload a list of names and LAT/LONGS from a structured document (.xlsx, .csv etc) and create an lxtgaz file from that document. Note, the lxtgaz file will need the keywords manually added to each location. Let me know if you have additional questions! -Aryle ... View more

Hello Wan, Currently, LocateXT is unable to directly geocode scanned documents. However, there is a workaround, and I have written an article that is in the process of becoming public. I have attached the draft below and will include some test data you can use to follow along!: In this article some ways in which to leverage LocateXTs scanning capability for limited geocoding are discussed. When used with data containing a patter, LocateXT can be used as a tool in a workflow that scans for addresses and produces points. You are given data in the form of house listings. These locations do not include coordinates; however, rather than copy paste potentially hundreds of addresses, we are going to use LocateXTs Custom Attribute scanning ability to collate our addresses into a format usable in ArcGIS Pro. Note: This workflow works best with text that displays a consistent pattern, for example data in a form, or following a particular convention in speech, grammar, or writing. Our listings are in a standard format that provides us with a clear pattern of information: We can see that 'Address:' is always followed by an address and that at the end of an address the word 'Price:' begins on the next line. We can use this information to create a Custom Attribute file that scans for each of our fields. First, we need to select 'Add Data' in ArcGIS Pro and select 'Extract Locations': Create a new template (Listings) Select 'Properties' Toggle to the 'Custom Locations' tab Turn on 'Create features from custom locations' Select 'New File' Input 'Address' as location name and keep the default Location Coordinate We'll repeat this process with the Custom Attributes section of the Extract Locations pane. We can add attributes using the following process: Set the field name for the attribute Input the starting keyword, in this example we want LocateXT to start collecting text for the field once the word 'Address:' is spotted Capture everything between the start ('Address:') and the stop string The stop string is where we want LocateXT to stop collecting data for the field ('Price:') This will capture whatever is between 'Address:' and 'Price:' which is the full address we're looking for in our text Because we know this is a template, we know most if not all of our text documents will contain this same format. Once we have our Custom Attributes and Custom Locations input, we give our output a name, drag and drop the folder containing our documents, and click 'Extract': If we right click the resulting point feature class in the Contents pane and select 'Attributes' we can see that while our points are not in the correct place, our addresses have been captured in a format usable in ArcGIS Pro: We can export this to a table and geocode the Address field using the ArcGIS World Geocoder: Save the output as whatever you'd like and once exported as a table, we can use the Geocode Addresses tool: Input the exported table Select the ArcGIS World Geocoding Service or a locator of your choice NOTE: Use of the ArcGIS World Geocoding Service will consume credits (See: Understand Credits) Select 'Single Filed' and 'Addresses' for the Input Address Fields, and name the output Select the country most likely to be included in the data Select the address pattern(s) most likely to be used in your data After running the tool, you can see the geocoded output. Open the attribute table and see the fields that have been included. Let me know if you have any questions! -Aryle ... View more

Hi Andrew, Without looking at your data, it's hard to give a specific workflow, but I can tell you that this is possible! The Symbology Pane in ArcGIS Pro does have the ability to symbolize two fields. What this will do is combine two values to one group. For Example I have some fake data that includes 3 non-Pro generated fields: Name: Unique to each record Type: Repeats Grade: Repeats In my symbology pane, I can symbolize using a repeating value, and combine it with a unique value. This will allow me to select a particular record and set it to a unique color:  I set the yellow color by double clicking the color swatch next to 'Fill, Duho' and selecting yellow. All of my 'Type' categories are still there (Fill, Land, and Synthetic) but they've been combined with my 'Name' values to create unique values that I can then manually symbolize. The result looks like this: This will not work, however, if I combine my two repeating columns, and the polygon I want to symbolize no longer has a unique value. There are only 7 values out of 9 total records, meaning that two polygons are being symbolized by the same value. We can see this if we change the top option to yellow: I hope this helps! -Aryle ... View more

Hello Ryan, Without seeing the PDFs, I can't say exactly what's going on, but there is some general information I can give you. LocateXT for ArcGIS Pro 2.4.x is currently able to scan documents for certain coordinate formats. You can find a list of these coordinates, along with examples and efficacy within LocateXT by, in an open ArcGIS Pro Project: Click Add Data and select Extract Locations In the Extract Locations pane: Select the Properties tab In the Properties tab click the red icon Be sure the Coordinates tab is selected View the coordinates available You may want to compare your coordinates that did not match, with the coordinate formats available. For example: 116°W, 43°N may need to be written 43°00'00.0"N 116°00'00.0"W for LocateXT to recognize it.  If these are locations that come up frequently in your documents, you can create a custom location. For example, you could name it 116°W, 43°N and input the coordinates as 43°00'00.0"N 116°00'00.0"W , so that each time LocateXT sees 116°W, 43°N, it plots the point correctly, rather than ignoring the notation entirely. You can read more about this in our documentation: Extract custom locations. As for the two PDFs that LocateXT seems to produce no data from, are these PDFs readable? Meaning, is the text in the PDF a scanned image, or actual text? LocateXT is currently unable to scan images for text, and as such PDFs that contain scanned or image based text must be run through Optical Character Recognition software and then those output can be scanned by LocateXT. I hope this helps! -Aryle ... View more