You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 2, 2021. It is now read-only.
In the table of OSM entities with invalid FHRS IDs for each district, include a column of those FHRS establishments not yet successfully matched which have the same postcode as the OSM entity. Each establishment should be a link to add the appropriate FHRS ID to the OSM entity in JOSM.
I'm sure you've realised, these are often where a restaurant has changed hands or closed and another opened. A useful trigger for tasks in Street Complete or similar some time.
@jnicho02 Yes, invalid FHRS IDs are already included in my tool at https://osm.mathmos.net/survey/ thanks to a feed from @gregrs-uk . In my experience they seem to be about 50/50 between updated IDs for the same place (which can be fixed remotely using the FHRS data) and changes of name/use (which usually require a ground survey). There have been a couple of cases recently of authorities assigning new numbers to all their registered establishments -- for which the feature suggested above would be very helpful.
gregrs-uk
changed the title
Invalid FHRS IDs table: include suggested FHRS matches with same postcode
Table with suggested FHRS matches with same postcode
Apr 21, 2019
This could also include suggested FHRS matches for OSM nodes/ways which have a matching postcode. I've started coding this in the postcode-matching-table branch, although it doesn't include FHRS mismatches yet.
Given the size of the table, it should probably go on a separate page for each district.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the table of OSM entities with invalid FHRS IDs for each district, include a column of those FHRS establishments not yet successfully matched which have the same postcode as the OSM entity. Each establishment should be a link to add the appropriate FHRS ID to the OSM entity in JOSM.
Thanks @rjw62 for the suggested method.
The text was updated successfully, but these errors were encountered: