If you're planning on importing this data can I ask you put together some notes in an email on talk-au or on the OSM wiki so we can discuss this please?

For example I noticed here you have "surface" and "suface".

Regarding difficultly I don't think this should be included unless there is some documented guide on how to determine the difficulty. My guess is it has been assigned automatically based on infrastructure class so there's no benefit of including it in my opinion.

Lastly I'd omit the ref, is there any use for it?

Where's the OSM discourd server #asia-pacific channel?

I went to osm.wiki/Discord_servers and joined the International one but I can't see any #asia-pacific channel.

Absolutely, it's why I advocate against doing an import of this data. What I do think it is useful for is identifying areas which are different which may indicate an error in OSM (or in TfNSW data) and then we go and check those via imagery/mapillary/ground survey to see if OSM needs updating.

So far I haven't noticed anyone else bring this data in (except for a brief spell where a person from TfNSW was using this data to update OSM. Some of that ended up getting reverted due to data quality).

So generally the LPI NSW Imagery is created to a higher positional accuracy than other satellite sources, so it's usually best, however nothing is perfect and it will shift between imagery updates so generally if it's a long way off feel free to improve, but if it's close I wouldn't normally bother.

Since OSM doesn't support a dynamic datum and since the whole continent is moving, every day the coordinates entered in OSM are slowly drifting away from reality about 1m every 10 years so

At some point we'll do an import using TfNSW data, but we're not there yet. If there is a printed timetable it usually has the bus stop name at the top.

hi, the number is the ref=* for the bus stop, not the name, the name is usually the street name etc.

Just a tip, when adding wikipedia links you need to also specify the language code of the page. I've done this for this feature see https://osmlab.github.io/osm-deep-history/#/way/4631838. If you add it with the iD editor it should do that automatically if you select from the dropdown, it should also add the wikidata id.

I've edited way/23565958 now to reduce the area.

yep that's fine thanks. Just keep an eye out when using the data as it sometimes may be outdated.

did you mean to leave the name as pp? If it's underground you might want to use tunnel=culvert or location=underground

If you're using TfNSW cycleways data then per the waiver agreement osm.wiki/File:TfNSW_OSM_CCBY_Signed_Waiver.pdf we need to provide attribution at osm.wiki/Contributors#New_South_Wales_Government_data Can you add the attribution for the original source used to the Contributors wiki page please?

Agreed it's not military, that's why I just deleted the landuse=military tag, while retaining military=danger_area in changeset/81056371. The wiki page confirms that military=danger_area doesn't imply related in any way to the military. I know it's not the best tag being military= but it's the best one that I'm aware of which is documented and in use.

I'd very much welcome more work on a better tag for general projectile or weapons danger areas, but in the meantime I don't think it's warranted to have the pitch the way you changed it here. I'd rather change it back to the smaller area.

In my mind the danger area and the pitch are two different things, one being the larger area and one much smaller where the sport is actually practised on.

Hey Warin, in this changeset you increased the size of way/23565958 to extend to the range danger area. Since the range danger area is already mapped at way/434705783, I think the leisure=pitch way should only cover the original smaller area covering the shooting range only. Do you think that's okay?

Oh sorry I didn't realise, that's great!

@Luen Warneke ps you can also upload your GPS traces to osm.org/traces which go into OSM's gps traces layer which help to provide evidence and justification of trace locations as mapped in OSM but also aid in mapping.

If you want you can also check it out at https://dev.beyondtracks.com/carto/debug/#15.39/-43.236187/147.795203 and switch to "Satellite" and you can see this also aligns with the Tasmanian Government aerial imagery, though I'd still trust the GPS traces more.

@Warin61 this track is correct as confirmed by the OSM GPS traces layer (one of those traces should be my GPS trace), if you turn that on you'll see the track is aligned well. Don't trust the imagery here.

I think it's generally accepted within OSM that sourcing a few facts from a website is okay, eg. contact phone number of a business from their website. I asked this at https://lists.openstreetmap.org/pipermail/talk/2018-November/081637.html so I think that's okay, what's potentially not okay is when whole collections of data are mass copied. Of course it can be hard to determine where the cut off is, so of course we prefer ground surveyed data but I believe in this case a single depth and capacity numbers taken for this dam as published there is okay.

Hi Hb-, there has been concern raised at https://lists.openstreetmap.org/pipermail/talk-au/2020-February/013619.html that this data isn't able to be determined reliably by Bing and ESRI imagery and concerns that some of this information may have come from non-free sources. Are you able to confirm here what sources of information this changeset used? Did you refer to https://www.ddmrb.org.au/ for the location of the fence?

Many thanks,
Andrew Harvey
Data Working Group

https://osmlab.github.io/osm-deep-history/#/node/4313720776 are you sure it's not "Winston Hills Post Office"? We should keep Winston Hills in there if it's still known as that, either in the name or branch tag.