Understood Steve. I very rarely use source tags and all my changeset
comments mostly follow the same Mapillary survey theme. I have however
been using them to explain (say) differing road names within a Mapillary
based changeset. eg what is shown on a physical sign vs original data
upload, or (in AU) the use of a local but formal street name over a
state highway name (as alt_name)
On 2/10/25 14:27, stevea wrote:
In the last 15 years, I've noticed a distinct trend away from using a source=*
tag actually IN the data (an early-2010s convention) much more towards noting
source attribution(s) in the changeset comments. This got more prevalent in
the late 2010s, continuing strongly into these mid-2020s.
Sure, you still CAN enter a source=* tag, but why? Tagging the changeset comment is
becoming "the new convention" for source attribution.
Remember, what you enter into OSM, STAYS in OSM (these paper-trails are now much more easier to see
with object History versions in our web-based data). So, "once is enough," (for source=*
attribution) and "in the changeset" seems to be how many are doing it — and that's just
fine.
Whether the press-release URL gets put into a source=* tag, a website=* tag
(that would be not-quite-correct for source-attribution) or BEST, a changeset
comment, it is important to enter source data. I say (and so do many others),
put this in the changeset comments. Please and thank you.
On Oct 1, 2025, at 9:13 PM, Ben Ritter<[email protected]> wrote:
When you are manually making individual changes, and cross referencing
different sources like you are describing, I don't think the elements need a
source tag. The ideal source for information in OSM is the contributors
themselves, so the best outcome is that you are the source of the info in the
tags, based on your observations of the world (which includes the satellite,
local reporting, and on-the-ground surveys).
A source tag on a feature indicates that the person submitting the changes
hasn't had any input on the information, it is directly from the source.
Instead, I would include the sources in the changeset comment or changeset
tags. That leaves a paper-trail for other mappers to discover if needed without
adding source tags to the map data that would require maintenance.
I hope that reasoning makes sense, and that others here agree!
Cheers,
Ben
On Thu, 2 Oct 2025 at 11:57, Bob Cameron<[email protected]> wrote:
I have often used local/state/federal govt road reports and press releases on
road surfacing to use as a source for then checking against the available
overhead imagery or using as an excuse to go for a drive!
I wonder though does a press release actually make it public domain information
that can be used directly? I note for example that Bourke Shire Council
released one (actually copy-write on their website) that says all of the
Bourke-Wanaaring Road is sealed except for the last 9.4km. (The press release
was actually about that it would be 100% sealed later this year)
If that case were okay does the information source URL (as a tag) pointing to a
normally copy-write page get used?
Tnx
_______________________________________________
Talk-au mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-au
_______________________________________________
Talk-au mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-au
_______________________________________________
Talk-au mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-au
