-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enrich georeferenced items with information from nominatim server #1487
Comments
nominatim server for a related address of a georeferenced item.
Hi nassif, I've made a stub of this in Nominatim branch. But I have some doubts about the design. First, the task makes one http request per item with geolocation. This can lead to many http requests. And this kind of request to complement information from other sources can become more common, made from other task also (maybe it already exists). There should be some centralized/normalized subsystem to control these kind of enrichment from http requests? Second: This external information complement are what some tools call enrichment. Should we make some visual differentiation of enrichment information from original artifacts? |
Sorry for my delay.
You can group items and make requests in batches, overriding the
We have the
Yes, WhatsAppParser adds the |
…mation." This reverts commit 4c72734.
reenqueue the item till a response is available. Add metadata info for country, state, city and suburb.
"Yes, WhatsAppParser adds the ExtraProperties.DOWNLOADED_DATA property to flag downloaded medias and it also put a |
nominatim server was unable to GEOCODE (error).
metadata, so it can be better processed in analysis gui.
nominatim responses that do not add certain nominatim fields.
exception, and also to inform error only for georeferenced file.
NominatimTask.NOMINATIM_METADATA metadata in the case.
Nominatim maps a geolocation to textual address information. It may be useful to search these items by their city name, for instance. Also, this information can be used to cluster the plotted items by their administrative address information (country, city, etc..).
An URL should be configured, and if so, the processing would lookup addresses for every geolocated item.
The text was updated successfully, but these errors were encountered: