Re: [Talk-GB] Coastline confusion
On 03/11/2018 15:50, Colin Smale wrote: The coastline ways with source=PGS are really old and inaccurate. I am not sure of their exact provenance but I think they were traced from some primitive aerial imagery. https://wiki.openstreetmap.org/wiki/Tag:source%3DPGS Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
[Talk-GB] weeklyOSM #432 2018-10-23-2018-10-29
The weekly round-up of OSM news, issue # 432, is now available online in English, giving as always a summary of all things happening in the openstreetmap world: http://www.weeklyosm.eu/en/archives/10878/ Enjoy! weeklyOSM? who: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages where?: https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3 ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
Re: [Talk-GB] Coastline confusion
Hi Sean,
The coastline ways with source=PGS are really old and inaccurate. I am
not sure of their exact provenance but I think they were traced from
some primitive aerial imagery.
HWM data is available as part of OS Boundary-Line. It shows the "island"
("Inner Trial Bank") is (just) within the coastline, so it is surrounded
by (I guess) salt marsh which in this case is above the HWM (i.e. it
does not completely flood). On this basis the "island" should not be
tagged as natural=coastline.
Having said that, because of the nature of the geography of the area it
is possible for coastlines to move, and they are only resurveyed every
few years. So the age of the data source can also be very relevant.
But I see your point about the OS maps, which seem a little
inconsistent. If you zoom in, the foreshore becomes visible, and this
island is indeed depicted as an island. Zoom out and the foreshore is
flooded, including this island.
Colin
On 2018-11-03 16:18, Sean Blanchflower wrote:
> Hi all,
> I've been contacted by an OSM user confused about what to do on the coast of
> The Wash.
>
> Basically the two ways:
> https://www.openstreetmap.org/way/2961222
> https://www.openstreetmap.org/way/35834999
>
> are both natural=coastline there, but the former, an "island" is inside the
> latter so can't really be coastline.
>
> However, the latter (the main coastline) in this area is inaccurate, and
> should really follow the Mean High Water level more precisely.
>
> i) The MHW on OS OpenData StreetView runs around the 'island' to the north,
> meaning the island should be removed, or at least relabelled...
> ii) ...but the 'coastline' on OS LandRanger maps (which should also be the
> MHW, shouldn't it?) runs well to the south of the 'island'.
>
> So I'm confused. I think it's clear that the main coastline needs refining,
> but it's not clear where to.
>
> S.
> ___
> 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] Coastline confusion
Hi all, I've been contacted by an OSM user confused about what to do on the coast of The Wash. Basically the two ways: https://www.openstreetmap.org/way/2961222 https://www.openstreetmap.org/way/35834999 are both natural=coastline there, but the former, an "island" is inside the latter so can't really be coastline. However, the latter (the main coastline) in this area is inaccurate, and should really follow the Mean High Water level more precisely. i) The MHW on OS OpenData StreetView runs around the 'island' to the north, meaning the island should be removed, or at least relabelled... ii) ...but the 'coastline' on OS LandRanger maps (which should also be the MHW, shouldn't it?) runs well to the south of the 'island'. So I'm confused. I think it's clear that the main coastline needs refining, but it's not clear where to. S. ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
Re: [Talk-GB] Facebook Map Query - Thames rendered as Thanames
On 26/10/2018 10:56, Dave F wrote: I'd be more concerned that on Facebook's mobile website (Android/Silk Browser) that image clicks through to Google Maps. I suspect it depends (I did look into issues related to this in response to some DWG* tickets). The maps you saw depending on where you were, where (both geographically and how far away) and what the thing that you were looking for was (e.g. roughly "a destination", "some other place", "something else"), and how you were accessing FB (e.g. on the phone was it app or browser, and I suspect it'd depend on OS too). Any attribution issues you find are probably best handled by the LWG** though I'm not convinced that "clicking on a map from provider A and going to a map from provider B" necessarily is one. Instagram of course is something else again, despite being owned by Facebook. We (the DWG) have seen some misdirected reports come to us because Instagram's "report a problem" link (at least in the Android app a couple of weeks ago) pointed straight to OSM, and of course OSM has no influence on the search results that Instagram returns, which is usually what users are complaining about. However, I suspect it might result in businesses adding themselves to OSM that otherwise would not so I guess that "every cloud has a silver lining" :) Best Regards Andy * https://wiki.osmfoundation.org/wiki/Data_Working_Group ** https://wiki.osmfoundation.org/wiki/Licensing_Working_Group ___ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
