Robert Whittaker

@pietervdvn@en.osm.town @harry_wood@en.osm.town Yes but the street names and numbers are assigned by the councils, so it should be their data to release. But somehow OS/Geoplace position themselves as maintainers of the NPLG, suck in all the data from the councils. and then provide it back to them under a restrictive licence, meaning Councils can't release their own data. 1/2

@hisdeedsaredust@mastodon.online BTW, if you found it useful and would like any more local streets adding, just let me know.

@pietervdvn@en.osm.town @harry_wood@en.osm.town The question with the Council Tax data the Owen's been collecting is whether it's maintained independently of the NPLG. AFAICT, OS thinks this is so unlikely, they've forced Owen to take down any datasets where the council hasn't explicitly confirmed *to them* that it's independent, even if the Council has told Owen there are no third party IP rights in the data. Some data undoubtedly has been released 'in error'. But OS and it's lawyers would be tough to argue with. 2/2

@osm_tech Since the change I've been getting "503 First Byte Timeout" errors on an API call https://api.openstreetmap.org/api/0.6/notes/search.json?q=%23survey me&closed=0&limit=3500 used by one of my tools. It works fine with a lower limit (eg 350) but that misses some of the notes I want. Can you set a longer timeout with Fastly? (Unfortunately there's no direct paging option documented for that API call.)

@harry_wood@en.osm.town Many thanks. Looks like the numbers aren't that large at the moment so the API should be fine for now. Interesting that there's so many #surveyme tags, as I haven't actively been promoting it.

@osm_tech@en.osm.town @maplibre@mastodon.social Not sure if this is know / expected / already reported, but the z-order of the green pins doesn't seem to be right. Some markers further north are consistently displayed on top of some further south. (Chrome on Android)