[talk-au] Correcting inland water features

Fri May 18 09:02:36 UTC 2018

Hi folks,

Bay or river closing lines are defined here

http://www.ga.gov.au/scientific-topics/marine/jurisdiction/maritime-boundary-definitions

There is also the GA Coastline which may help

http://services.ga.gov.au/site_11/rest/services/Global_Map_Project_Australian_Base_Map/MapServer/6

Cheers - Phil

From: Andrew Wiseman [mailto:andrew_wiseman at apple.com] 
Sent: Friday, May 18, 2018 10:07 AM
To: OSM Australian Talk List
Subject: Re: [talk-au] Correcting inland water features

Thanks for the feedback and suggestions everyone, that’s very helpful. We have also added AGRI to our list of sources.

Where the inland water meets the coastlines, we have seen a few different styles of modeling so I wanted to see if you had a local policy about it. 

In some cases we’ve seen things like this, where the coastline goes very far upstream: https://www.openstreetmap.org/way/14763476#map=11/-12.4279/132.4683 

In other cases, the coastline is farther downstream, like where the Pine River stops here: https://www.openstreetmap.org/way/159813122#map=14/-27.2842/153.0761

We were thinking the second example is better. If that’s the case for the Alligator River we would put the coastline here (which is also where the GA Surface Hydrology polygon has the river starting) https://www.openstreetmap.org/?mlat=-12.2296501875 <https://www.openstreetmap.org/?mlat=-12.2296501875&mlon=132.402678198#map=15/-12.2293/132.4083> &mlon=132.402678198#map=15/-12.2293/132.4083 and change the existing coastline to riverbank.

Please let me know what you think.

Thanks,

Andrew

Andrew Wiseman |  Maps | andrew_wiseman at apple.com

APPLE CONFIDENTIAL

This message (including attachments if any) is for the private use of the addressee only and may contain confidential or privileged information. If you have received this message by mistake please notify the sender by return e-mail and delete this message and any attachments from your system. Any unauthorized use or dissemination of this message, and any attachments in whole or in part is strictly prohibited.

On May 16, 2018, at 9:26 AM, Andrew Harvey <andrew.harvey4 at gmail.com> wrote:

Agreed with Warin and Ewen.

I'd like to point out the AGRI imagery [1], yes it's old (2006-2011), black and white, and missing parts of the imagery due to cloud and seams, but it may help as an extra source to compare. It's good enough to make out rivers and it should be accurate positionally since it was validated with ground surveys. CC BY 4.0 and usable in OSM from the blanket Geoscience Australia wavier[5].

GA also has a Surface Hydrology dataset [2] [3] [4] which could be used as well.

Some features are better tagged as a wetland https://wiki.openstreetmap.org/wiki/Tag:natural%3Dwetland. Local knowledge is always prefered, but so long as features mapped from local knowledge are not impacted, something mapped from other sources is better than nothing, which can be improved further by local knowledge.

I'm interested to know more about the alignment issues when they meet the coast, is there a specific example of where this needs work at the moment in OSM?

PS. Microsoft's Open Maps team has similar tasks at https://github.com/Microsoft/Open-Maps/issues/14 and https://github.com/Microsoft/Open-Maps/issues/11

[1] https://github.com/osmlab/editor-layer-index/blob/gh-pages/sources/australia/au/AGRIblack-and-white25m.geojson?short_path=4ca9ae8

[2] https://ecat.ga.gov.au/geonetwork/srv/eng/catalog.search?node=srv#/metadata/1186e898-14b5-812e-e053-10a3070a76f0

[3] https://ecat.ga.gov.au/geonetwork/srv/eng/catalog.search?node=srv#/metadata/12777e32-ec4f-055a-e053-10a3070a2ce2

[4] https://ecat.ga.gov.au/geonetwork/srv/eng/catalog.search?node=srv#/metadata/123f4803-04d7-32d1-e053-12a3070a99ac

[5] https://wiki.openstreetmap.org/wiki/File:GeoscienceAustralia_CCBY_Waiver_EmailAcceptance.pdf

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-au/attachments/20180518/3b3668dd/attachment-0001.html>