The LocateXT documentation says this:
When custom locations are turned on, content in the documents that are being scanned is compared against the place names specified in the custom locations file. By default, the content has to exactly match one of the specified place names to create a location in the output feature class.
This approach is deeply, deeply flawed. The entire point of using something like LocateXT is to crawl information for explicit and implicit locations so that a human doesn't have to read them in the first place. Under this, a person would have to read all the content, and enter a place name-coordinate pair for each non-coordinate location in a "custom locations file." This is insane!
This is exactly what gazetteers exist for. This is precisely what Geonames and OSM Nominatim exist for. So this idea is for LocateXT to support gazetteer sources out of the box, including an OSM Nominatim service so that plain text names can be checked (completely or fuzzily) against Nominatim or other custom gazetteer sources.
I just bought 12 of these things so I'll have more ideas as we go along but for now, this is baseline type stuff that is required for the extension to be useful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.