Re: [Talk-GB] featdesc & featcode
On 19/11/2020 20:57, Brian Prangle wrote: Dump for external databases? Surely not! FHRS? Well that's why I've been trying to clean up FHRS tags. The only tag that should really exist is the ID code which refers /back/ to the external database. UPRN? USRN? I'm struggling to see the benefit of these ATM, & given some of the comments, I'm reminded of the US Tiger dump. Edubase? A reference to an external database, not a dump. DaveF ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
Re: [Talk-GB] featdesc & featcode
On Thu, Nov 19, 2020, at 8:57 PM, Brian Prangle wrote: > Dump for external databases? Surely not! FHRS? UPRN? USRN? Edubase? > Haha. Yes, these tags are useless. I have accidentally added some in the past when working with OS OpenData and I think deleted them soon after. UPRN and USRN aren't going to be much more useful, fortunately I can't see many contributors wasting their time adding those either. Kevin user:devonshire___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
Re: [Talk-GB] featdesc & featcode
Dump for external databases? Surely not! FHRS? UPRN? USRN? Edubase? Regards Brian On Thu, 19 Nov 2020 at 19:09, Dave F via Talk-GB wrote: > Thanks for that. > > I'm struggling to see the benefit of this in OSM, & given only one > contributor has added them I presume I'm not alone. > The codes appear to be another company's database reference system, of > which OSM has its own. > OSM should not become a dump for external databases. Anyone with valid > reasons for not removing these tags? > > DaveF > > On 19/11/2020 16:49, Martin Wynne wrote: > > On 19/11/2020 16:24, Dave F via Talk-GB wrote: > > > > > > Anybody know what featdesc & featcode refer to? Local authority > > > references? > > > > Hi Dave, > > > > Sorry about poor formatting, copied from: > > > > > > > https://www.ordnancesurvey.co.uk/documents/os-vectormap-district-product-guide.pdf > > > > > > > > > > OS VectorMap District technical specification feature codes v1.8 – > > 09/2016 © Crown copyright Page 51 of 56 > > > > Feature Codes > > > > > > Feature Codes represented in the vector product > > > > FeatureType classification featureCode > > Building25014 > > Glasshouse25016 > > Road Motorway 25710 > > Primary Road 25723 > > A Road 25729 > > B Road 25743 > > Minor Road 25750 > > Local Street 25760 > > Private Road Publicly Accessible 25780 > > Pedestrianised Street 25790 > > Motorway, Collapsed Dual Carriageway 25719 > > Primary Road, Collapsed Dual Carriageway 25735 > > A Road, Collapsed Dual Carriageway 25739 > > B Road, Collapsed Dual Carriageway 25749 > > Minor Road, Collapsed Dual Carriageway 25759 > > RoadTunnel25792 > > MotorwayJunction25796 > > Roundabout Primary Road 25703 > > A Road 25704 > > B Road 25705 > > Minor Road 25706 > > Local Street 25707 > > Private Road Publicly Accessible 25708 > > SurfaceWater_Line25600 > > SurfaceWater_Area25609 > > TidalWater High Water Mark 25608 > > TidalBoundary High Water Mark Low Water Mark 25604 > > Low Water Mark 25605 > > Foreshore25612 > > AdministrativeBoundary National 25204 > > Parish Or Community 25200 > > District Or London Borough 25201 > > County Or Region Or Island 25202 > > RailwayTrack Multi Track 25300 > > Single Track 25301 > > Narrow Gauge 25302 > > RailwayTunnel25303 > > RailwayStation Light Rapid Transit Station 25420 > > Railway Station 25422 > > London Underground Station 25423 > > Railway Station And London Underground Station 25424 > > OS VectorMap District technical specification feature codes v1.8 – > > 09/2016 © Crown copyright Page 52 of 56 > > Light Rapid Transit Station And Railway Station 25425 > > Light Rapid Transit Station And London Underground Station 25426 > > FunctionalSite Education Facility - School 25250 > > Police Station 25251 > > Medical Care 25252 > > Place Of Worship 25253 > > Leisure Or Sports Centre 25254 > > Air Transport 25255 > > Education Facility - Higher 25256 > > Water Transport 25257 > > Road Transport 25258 > > Road Services 25259 > > Woodland25999 > > Ornament25550 > > ElectricityTransmissionLine25102 > > NamedPlace Populated Place 25801 > > Landform 25802 > > Woodland Or Forest 25803 > > Hydrography 25804 > > Landcover 25805 > > SpotHeight25810 > > > > > > > > > > ___ > > Talk-GB mailing list > > Talk-GB@openstreetmap.org > > https://lists.openstreetmap.org/listinfo/talk-gb > > > ___ > Talk-GB mailing list > Talk-GB@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-gb > ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
Re: [Talk-GB] featdesc & featcode
Hi Dave, The wood/forest and water ones I've seen are entirely useless in OSM as the relevant natural tags represent exactly the same information. For some external sources imported to OSM retaining the original codes is useful when there is not a precise 1:1 correspondence to tags, but that is not the case here. Not only can they be removed safely, but there may be merit in adding them to the tags automatically deleted when something is edited (such as the editor tag). There are one or two rareish codes in the data according to taginfo which I dont recognise ( https://taginfo.openstreetmap.org.uk/search?q=FEATCODE). Regards, Jerry On Thu, 19 Nov 2020 at 19:09, Dave F via Talk-GB wrote: > Thanks for that. > > I'm struggling to see the benefit of this in OSM, & given only one > contributor has added them I presume I'm not alone. > The codes appear to be another company's database reference system, of > which OSM has its own. > OSM should not become a dump for external databases. Anyone with valid > reasons for not removing these tags? > > DaveF > > On 19/11/2020 16:49, Martin Wynne wrote: > > On 19/11/2020 16:24, Dave F via Talk-GB wrote: > > > > > > Anybody know what featdesc & featcode refer to? Local authority > > > references? > > > > Hi Dave, > > > > Sorry about poor formatting, copied from: > > > > > > > https://www.ordnancesurvey.co.uk/documents/os-vectormap-district-product-guide.pdf > > > > > > > > > > OS VectorMap District technical specification feature codes v1.8 – > > 09/2016 © Crown copyright Page 51 of 56 > > > > Feature Codes > > > > > > Feature Codes represented in the vector product > > > > FeatureType classification featureCode > > Building25014 > > Glasshouse25016 > > Road Motorway 25710 > > Primary Road 25723 > > A Road 25729 > > B Road 25743 > > Minor Road 25750 > > Local Street 25760 > > Private Road Publicly Accessible 25780 > > Pedestrianised Street 25790 > > Motorway, Collapsed Dual Carriageway 25719 > > Primary Road, Collapsed Dual Carriageway 25735 > > A Road, Collapsed Dual Carriageway 25739 > > B Road, Collapsed Dual Carriageway 25749 > > Minor Road, Collapsed Dual Carriageway 25759 > > RoadTunnel25792 > > MotorwayJunction25796 > > Roundabout Primary Road 25703 > > A Road 25704 > > B Road 25705 > > Minor Road 25706 > > Local Street 25707 > > Private Road Publicly Accessible 25708 > > SurfaceWater_Line25600 > > SurfaceWater_Area25609 > > TidalWater High Water Mark 25608 > > TidalBoundary High Water Mark Low Water Mark 25604 > > Low Water Mark 25605 > > Foreshore25612 > > AdministrativeBoundary National 25204 > > Parish Or Community 25200 > > District Or London Borough 25201 > > County Or Region Or Island 25202 > > RailwayTrack Multi Track 25300 > > Single Track 25301 > > Narrow Gauge 25302 > > RailwayTunnel25303 > > RailwayStation Light Rapid Transit Station 25420 > > Railway Station 25422 > > London Underground Station 25423 > > Railway Station And London Underground Station 25424 > > OS VectorMap District technical specification feature codes v1.8 – > > 09/2016 © Crown copyright Page 52 of 56 > > Light Rapid Transit Station And Railway Station 25425 > > Light Rapid Transit Station And London Underground Station 25426 > > FunctionalSite Education Facility - School 25250 > > Police Station 25251 > > Medical Care 25252 > > Place Of Worship 25253 > > Leisure Or Sports Centre 25254 > > Air Transport 25255 > > Education Facility - Higher 25256 > > Water Transport 25257 > > Road Transport 25258 > > Road Services 25259 > > Woodland25999 > > Ornament25550 > > ElectricityTransmissionLine25102 > > NamedPlace Populated Place 25801 > > Landform 25802 > > Woodland Or Forest 25803 > > Hydrography 25804 > > Landcover 25805 > > SpotHeight25810 > > > > > > > > > > ___ > > Talk-GB mailing list > > Talk-GB@openstreetmap.org > > https://lists.openstreetmap.org/listinfo/talk-gb > > > ___ > Talk-GB mailing list > Talk-GB@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-gb > ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
Re: [Talk-GB] featdesc & featcode
Thanks for that. I'm struggling to see the benefit of this in OSM, & given only one contributor has added them I presume I'm not alone. The codes appear to be another company's database reference system, of which OSM has its own. OSM should not become a dump for external databases. Anyone with valid reasons for not removing these tags? DaveF On 19/11/2020 16:49, Martin Wynne wrote: On 19/11/2020 16:24, Dave F via Talk-GB wrote: > > Anybody know what featdesc & featcode refer to? Local authority > references? Hi Dave, Sorry about poor formatting, copied from: https://www.ordnancesurvey.co.uk/documents/os-vectormap-district-product-guide.pdf OS VectorMap District technical specification feature codes v1.8 – 09/2016 © Crown copyright Page 51 of 56 Feature Codes Feature Codes represented in the vector product FeatureType classification featureCode Building 25014 Glasshouse 25016 Road Motorway 25710 Primary Road 25723 A Road 25729 B Road 25743 Minor Road 25750 Local Street 25760 Private Road Publicly Accessible 25780 Pedestrianised Street 25790 Motorway, Collapsed Dual Carriageway 25719 Primary Road, Collapsed Dual Carriageway 25735 A Road, Collapsed Dual Carriageway 25739 B Road, Collapsed Dual Carriageway 25749 Minor Road, Collapsed Dual Carriageway 25759 RoadTunnel 25792 MotorwayJunction 25796 Roundabout Primary Road 25703 A Road 25704 B Road 25705 Minor Road 25706 Local Street 25707 Private Road Publicly Accessible 25708 SurfaceWater_Line 25600 SurfaceWater_Area 25609 TidalWater High Water Mark 25608 TidalBoundary High Water Mark Low Water Mark 25604 Low Water Mark 25605 Foreshore 25612 AdministrativeBoundary National 25204 Parish Or Community 25200 District Or London Borough 25201 County Or Region Or Island 25202 RailwayTrack Multi Track 25300 Single Track 25301 Narrow Gauge 25302 RailwayTunnel 25303 RailwayStation Light Rapid Transit Station 25420 Railway Station 25422 London Underground Station 25423 Railway Station And London Underground Station 25424 OS VectorMap District technical specification feature codes v1.8 – 09/2016 © Crown copyright Page 52 of 56 Light Rapid Transit Station And Railway Station 25425 Light Rapid Transit Station And London Underground Station 25426 FunctionalSite Education Facility - School 25250 Police Station 25251 Medical Care 25252 Place Of Worship 25253 Leisure Or Sports Centre 25254 Air Transport 25255 Education Facility - Higher 25256 Water Transport 25257 Road Transport 25258 Road Services 25259 Woodland 25999 Ornament 25550 ElectricityTransmissionLine 25102 NamedPlace Populated Place 25801 Landform 25802 Woodland Or Forest 25803 Hydrography 25804 Landcover 25805 SpotHeight 25810 ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
Re: [Talk-GB] featdesc & featcode
On 19/11/2020 16:24, Dave F via Talk-GB wrote: > > Anybody know what featdesc & featcode refer to? Local authority > references? Hi Dave, Sorry about poor formatting, copied from: https://www.ordnancesurvey.co.uk/documents/os-vectormap-district-product-guide.pdf OS VectorMap District technical specification feature codes v1.8 – 09/2016 © Crown copyright Page 51 of 56 Feature Codes Feature Codes represented in the vector product FeatureType classification featureCode Building25014 Glasshouse25016 Road Motorway 25710 Primary Road 25723 A Road 25729 B Road 25743 Minor Road 25750 Local Street 25760 Private Road Publicly Accessible 25780 Pedestrianised Street 25790 Motorway, Collapsed Dual Carriageway 25719 Primary Road, Collapsed Dual Carriageway 25735 A Road, Collapsed Dual Carriageway 25739 B Road, Collapsed Dual Carriageway 25749 Minor Road, Collapsed Dual Carriageway 25759 RoadTunnel25792 MotorwayJunction25796 Roundabout Primary Road 25703 A Road 25704 B Road 25705 Minor Road 25706 Local Street 25707 Private Road Publicly Accessible 25708 SurfaceWater_Line25600 SurfaceWater_Area25609 TidalWater High Water Mark 25608 TidalBoundary High Water Mark Low Water Mark 25604 Low Water Mark 25605 Foreshore25612 AdministrativeBoundary National 25204 Parish Or Community 25200 District Or London Borough 25201 County Or Region Or Island 25202 RailwayTrack Multi Track 25300 Single Track 25301 Narrow Gauge 25302 RailwayTunnel25303 RailwayStation Light Rapid Transit Station 25420 Railway Station 25422 London Underground Station 25423 Railway Station And London Underground Station 25424 OS VectorMap District technical specification feature codes v1.8 – 09/2016 © Crown copyright Page 52 of 56 Light Rapid Transit Station And Railway Station 25425 Light Rapid Transit Station And London Underground Station 25426 FunctionalSite Education Facility - School 25250 Police Station 25251 Medical Care 25252 Place Of Worship 25253 Leisure Or Sports Centre 25254 Air Transport 25255 Education Facility - Higher 25256 Water Transport 25257 Road Transport 25258 Road Services 25259 Woodland25999 Ornament25550 ElectricityTransmissionLine25102 NamedPlace Populated Place 25801 Landform 25802 Woodland Or Forest 25803 Hydrography 25804 Landcover 25805 SpotHeight25810 ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
Re: [Talk-GB] featdesc & featcode
On 19/11/2020 16:35, George Honeywood wrote: Hi, I have a feeling it might be related to OS OpenData, perhaps from importing without deleting the original tags. Yes, if memory serves it's from the now defunct OS 50k gazetteer. Mark ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
Re: [Talk-GB] featdesc & featcode
Hi, I have a feeling it might be related to OS OpenData, perhaps from importing without deleting the original tags. Good luck, George Honeywood On Thu, 19 Nov 2020, at 4:24 PM, Dave F via Talk-GB wrote: > Hi > > https://overpass-turbo.eu/s/10kw > > Anybody know what featdesc & featcode refer to? Local authority > references? Appears to be only rivers & woods.These are the only > examples in the UK > The contributor who added them hasn't responded. > > DaveF > > ___ > Talk-GB mailing list > Talk-GB@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-gb > ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
[Talk-GB] featdesc & featcode
Hi https://overpass-turbo.eu/s/10kw Anybody know what featdesc & featcode refer to? Local authority references? Appears to be only rivers & woods.These are the only examples in the UK The contributor who added them hasn't responded. DaveF ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
Re: [Talk-GB] UPRN wiki page
On 18/11/2020 11:10, Robert Whittaker (OSM lists) wrote: It could well vary by local authority, but looking at the pattern of URPNs near where I live, it certainly seems that there is one assigned to every public road. There is consistently exactly UPRN at one end or the other of each road. The pattern is quite obvious if you look at a housing estate with lots of little roads. Not every street has them. Mine doesn't, for example. But others in my town do. Having had a look at various examples, I'm pretty sure that every newbuild street that was constructed since UPRNs became a requirement has one, but they only get applied retrospectively to existing streets if either the local authority has a policy of bulk-adding them or an operational need arises to do so. The fact that they are always at the extreme end of the street, though (a pattern I hadn't previously spotted), gave me an idea. I've run a load of queries against the data, and it's possible, with very high reliability, to find the street record UPRN for a USRN by looking for a UPRN which precisely matches the geometry of the street. You can see the results of that here, for example, where I've changed the icon for street records to be red instead of blue: https://uprn.uk/map?loc=17,52.1714708,-2.2041535 If anyone wants to replicate that, the process I, broadly speaking (after a few false starts!) was, iterating over each USRN sequentially... 1. Find any associated UPRNs that are linked to that USRN in the OS Open Linked Identifiers (LIDS) database. If there are none, then presumably this USRN doesn't have a street record. 2. If there are linked UPRNs, then run a spatial SQL query to find which, if any, intersect the geometry of the USRN. 3. Any that match are street records. Normally, there is only one street record for a USRN. I was a bit surprised to find some USRNs that matched multiple UPRNs in this way, but, on checking them, all of the UPRNs have identical coordinates! So, in those cases, I think what we have is a set of one or more historic (archived) UPRNs that share coordinates with the currently active one. Doing this found me 301,645 UPRNs that I think are street records, which is in the right ballpark if a little on the low side. Picking some at random, and checking them against non-open sources has, so far, resulted in no false positives - that is, all the ones I think are street records really are street records. That gives me confidence to assume that a precise match is reliable. However, there are false negatives. That is, there are some UPRNs that I know to be street records (both from a visual check on the map and cross-checking against non-open sources), but that don't get matched by this algorithm. Having had a look, this appears to be caused by a slight mismatch between the two sets of coordinates. In all the ones I've checked, it's a simple question of a different number of significant digits - truncating the one with more digits results in a match. So I think what I need to do next is modify my algorithm to look for a UPRN that precisely matches, or is very close to (less than 1m distance), the first or last node in the USRN geometry. I'll report back when I've done that. It may take a while, though! Mark ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
[Talk-gb-london] Tree mapping in Hackney
Hello there, I’m part of a group based in Hackney called the Tree Musketeers. We do a variety of tree-related things around the borough & beyond, one of which being annual planting of young trees in a selection of parks. We’re planning this year’s planting at the moment, & we’re thinking of mapping these new trees on OSM, for our own use & also as a tester for potentially mapping notable trees throughout the borough in the future (publicly-available tree data is currently very sparse/outdated for Hackney). I’m writing here to put out feelers for any related projects/groups: are there any mapping-enthusiast tree folk out there? Or tree-enthusiast mappers? At present we have arborists (tree experts) with identification skills & a group of keen local volunteers (tree fans) with local knowledge & access, but everyone is quite new to mapping & OSM. Any info or contacts would be greatly welcomed! Best, Helen p.s. We should be featured on Countryfile on BBC1 on 29 Nov, if you’d like to learn more about the group! ___ Talk-gb-london mailing list Talk-gb-london@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb-london
