piebro/osm-data huggingface dataset:
giorgio92 (2022-05-18 18:48:24+00:00): Ciao Andrea, ti ringrazio della segnalazione. 
Perdona per la confusione creata, ho sistemato i refusi in zona Mathi, ho notato tuttavia che questo changeset è stato chiuso.
Warin61 (2022-05-15 23:25:41+00:00): Looks like your creating a few errors... I think I fixed one of these yesterday .. today.. 

See https://tools.geofabrik.de/osmi/?view=areas&lon=115.75258&lat=-32.06407&zoom=18
Sam Wilson (2022-05-16 02:23:17+00:00): Thanks for the heads up! I should've taken more care.

Fixed now, and I'll try hard to not do this. It's the extrude tool in Josm that causes it.
Warin61 (2022-05-16 07:37:26+00:00): Keep an eye on that inspector website. I use it to find my own errors. Can take a while for errors to be found so an error made some days ago may not show up for some time. 
I'm not a great 'tool' user... prefer to know what is going on.
user_5359 (2022-05-16 10:12:44+00:00): Hello! Please have a look on your schools. What is the meaning of the tag isced: = Primary? Did you mean isced:level (but this needs a numerical value)? Did you know the key school:<country code>=Primary?
user_5359 (2022-05-26 14:43:36+00:00): changed!
woodpeck_repair (2022-05-28 12:47:55+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:46:37+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:51:28+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:43:06+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:41:15+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:46:20+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:42:34+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:47:19+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:49:58+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:47:27+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:49:17+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:49:20+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:41:37+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
GPar (2022-05-15 17:53:02+00:00): Gli edifici sono stati sovrapposti alle  strade, disallineati rispetto al reale. 
Questo ad esempio : 
https://www.openstreetmap.org/way/1060027218/history#map=19/45.27201/7.82026

Per favore correggi usando bing aerial 
Grazie
giorgio92 (2022-05-17 07:45:06+00:00): corretto, un saluto
woodpeck_repair (2022-05-28 12:45:09+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:43:01+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:46:01+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:37:23+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:50:11+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:50:37+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:41:08+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
20180911 (2023-01-12 21:42:25+00:00): Do you have a source for your edits? I do not believe that you add a 120 km pipeline just from imagery. Be sure that your source has a license which permits making derivations or copys on OpenStreetmap or is in public domain.
Why do you tag with substance=gas_topology and not with substance=gas?
kesterlester (2023-01-12 23:19:15+00:00): Hi.  The answer to the two of your questions is related. I am making two parallel/related maps of the gas infrastructure. The "actual" gas pipes are tagged "substance=gas" (not gas_topology) and those are all the sections that can be seen from aerial clues, etc, which indeed usually means that they are short (e.g. half a field up to 20 fields long).  These I only put where I know the exact geographical position of each section of the pipe. In parallel I am also putting in the "gas_topology" network which is another representation of the same system but focussing on connectivity and end points rather than route. This is a bit like the difference between a physical map and the london underground tube map. The London Underground tube maps in stations mainly exist to show what is connected to what, and not how.  In OSM there are features (relations) that can be (and eventually might/be) used to described such relationships. However, it is sometimes very hard to work out what connects to what until a lot of the intermediate things have been put together.  But eventually some of the links become clear by process of elimination or other large-scale clues. For example, it may become abantly clear from 100 small pipe sections, each about one field long and lined up with each other, but separated by ~10 field gaps, that they all form a large chain linking two major hubs.  When I spot something lke that, I then make a gas_topology link between those two endpoints, so that (on something like overpass turbo) I can start to better visualuse what connects to what, so that I can then focus on finding more clues to the "real" pipes ("gas") between those links.  It's a back and forth process: over time more "gas" links lead to better knowledge of "gas_topology" links, and more "gas_topology" links lead to better understanding of where the "gas" pipes are. So far as I know, only one site (openinframap) actually plots any of what I map, and they just plot "gas".  In principle I could call everything "gas" but label some as "topology=yes" and "topology=no", or something like that, but that would lead to double-rendering of gas pipes by systems which didn't know about the dual layer.  So, for now, the best system seemed to call the topological network maps (really only defined by endpoints) by a different thing. As I say, eventually, it may be possible to replace gas_topology with relations between separated gas segments, in the same way that roads (such as the A10) which have isolated segments are all part of a "this is an A10 segment" relation.  But that can't happen yet as I have not yet acuired enough ground data to enable that to be done well.
kesterlester (2023-01-12 23:22:09+00:00): PS: I should add that I am very aware of all the copyright issues about data that can go into the map, and you can't steal it from elsewhere, etc. That's why you will see a large number of gaps in my gas mapping, particularly in the south east of England (Kent/Sussex) where it is remarkably hard to get good traces due to the ground geology and hydrology.  There I often have only ~2% of the physical "gas" route identified, though this can still be enough to very clearly identify 100% of the associated "gas_topology" routes.
kesterlester (2023-01-12 23:23:08+00:00): I would be happy to show you some maps I can create on overpass turbo if you want to see the different views (overlayed or not) so that you can see how gas complements gas_topology.  But I think I can't do that in this thread, easily, as I don't think I can put images into this discussion.
kesterlester (2023-01-12 23:27:22+00:00): Interestingly its almost possibly to do dispance with any difference between oil and oil_topology (i.e. one can pretty much call all of it "oil") because, in contrast to gas, the markers by the side of the road usually have nice readable names for the pipes. E.g. (from memory) the pipe from Buncefield to Epping is called something like BUN-EPP. So when you find any isolated marker you can then immediately know what pipe it's on.  You (mostly) can't do that with gas so I have to maintain the two separate networks (topolgy and not) until the one determines the other.
kesterlester (2023-01-12 23:29:28+00:00): P.S.  What got you interested in this particular edit. It's from ab out 8 months ago. I am aware that ONCE in the last year I mis-clicked in the upload box and accidentally requested that one of my edits be reviewed. I wonder if it was this one? Am just curious.
20180911 (2023-01-13 17:09:35+00:00): Interesting concept. I now understand the difference between where the pipes go in topology and the small physical pipes where you know exactly where they are.
I was asking not because of requesting a review but because I added some gas posts that I saw when cycling through the UK in changeset https://www.openstreetmap.org/changeset/131146937 .

I was wondering about your data source, maybe I could use it too, maybe I have to tell you about copyright.
I usually mark the position of marker=post, utility=gas and sometimes a reference. On some pipes reference numbers are sequentially so I can be sure that they belong to the same pipe, sometimes there is a marker=plate with a pipeline number and a cathodic protection test point number so I have a ref for the pipeline. Often a post is marked as LTS or NTS (local or national transmission system).

When posts are in a regular distance, I draw a pipeline but the posts are not part of the pipeline. I assume that the pipe is nearby, especially if the posts are in a straight line. When there are 2 posts on both sides of a road I add the posts and a small pipeline crossing the road.

You can share overpass turbo queries using the share button and obtain a link like this here. https://overpass-turbo.eu/s/1q6O

In case you didn't know one can also run an overpass query from inside Josm. Download map data, Download from Overpass api instead of Download from Osm, query wizard.
kesterlester (2023-01-13 19:07:51+00:00): Oh yes. I didn't think to share the overpass turbo link itself. In that case, for your interest, take for example the following query:
http://overpass-turbo.eu/s/1q7r
It should, approximately, zoom to the Kent/Sussex area of the UK, and then should show you the gas only (i.e. real physical pipe sections and markers) in that area ... the vast majority of which are probably put in by me.
And then, for contrast, you could compare that to:
https://overpass-turbo.eu/s/1q7t
which (if I've pasted it right) should zoom to the same area but show you the gas_topology network corresponding to the same area.  99% of the latter is deduced from the former, even though the former constitutes only ~2% of the pipe-length of the latter.
If that proves interesting you can then look at east-anglia or the region around coventry, as those are the two other areas I have concentrated on.

As to my main sources, see my next post in this thread.
kesterlester (2023-01-13 19:14:32+00:00): OK: sources.  Mine are a mix. Many probably the same as yours, some perhaps different.  For pipe runs through fields and across roads, etc, we probably have the same main sources, namely (1) crop marks or signs of changed/altered vegetation, earthworks, vents, etc, i.e. anything you can see on aerial photography , (2) roadside or hedge-side markers of numerous types. Having done lots of mapping in some areas where its easy to see pipe runs, one gradually gets a pretty good idea of when pipe runs can be predicted to be straight. E.g. if there are numerous markers in a straight line, and no roads, streams, woods, or natural barriers to cross, there would have been no reason to kink the pipe, and I will happily draw a straight physical pipe run between those markers(*) even if a crop mark is not visible, as one can be sure that's where the pipe went. However, if there is any ambiguity, or barriers in the way, things that might have had to been worked around, then I will only mark pipes where I have direct evidence of their route. Continued in next post.
kesterlester (2023-01-13 19:18:46+00:00): Next: where to get evidence of the markers. Like you, some I have found just by cycling around. To get further away ones I sometimes wait until I have to make a long car trip for some other purpose, and then I deviate the route to take me past an area that I think will have markers in.  In some regions of the UK a great source of markers which I can't get to by car can be www.geograph.org.uk or geograph for short. If you don't know what sort of game geograph is the page will explain.  In short, it is not unusual in many areas for random people to have chosen to make detailed close-up pictures of markers with all the writing visible. You just have to get lucky with the interests of the people in some areas.  That's all free for public use stuff.
kesterlester (2023-01-13 19:27:00+00:00): Another source I use a lot is google street view. I know it's wrong (completely wrong) to steal mapping from, say, google street map. Not only would I do that, it would also be counter productive, in many cases OSM is better, AND of course there could be fake streets, AND it would break copyright. However, I believe there is nothing wrong with going to google street view, and looking at photos of nature within it.  Quite frequently it is possible to identify gas pipe markers on field boundaries in such data.  The downside is that the labels cannot usually be read in detail (unlike Geograph) however it is ususally possible to determine, just, whether they indicate NTS or LTS, either by text or by colour or by type.
Regrettably the aerial vs post, pedestal vs post tagging practices are very different between different countries, not helped (of course) by the fact that the markers themselves are different in different countries.  I have done no off-shore gas mapping, but I have proabably done >80% of all the on-shore gas mapping in the UK. I based my tagging conventions on the most widespread conventions that  I saw in use in east anglia before I started (as I began in east anglia and worked out).  When it got to the point that I had done > 80% of the gas mapping in the UK I thought I had better document what my approach tagwise has been, so I have listed the approach in the UK-gas sections of https://wiki.openstreetmap.org/wiki/Tag:marker%3Daerial#Oil_%26_Gas and in the UK-gas sections of https://wiki.openstreetmap.org/wiki/Tag:marker%3Dpost#Oil_%26_Gas
kesterlester (2023-01-13 19:28:54+00:00): Finally, I have managed to acquire photos of markers or the signs on the gates outside stations I can't reach or see on any other source by finding out who has done the most mapping in some area, and then contacting them to ask if they would mind sending me a photo of X if ever they are in the area.  They are often willing.
kesterlester (2023-01-13 19:34:20+00:00): Dang. I Just lost a lot of what I typed in the last message. I will try again but with less patience this time.
kesterlester (2023-01-13 19:39:33+00:00): What I was just saying (but lost) is that heavy consumers (industry) get a better deal on their gas supply if they are willing to accept outages at a greater rate than, say, domestic consumers.  And so roughly every six months british gas or cadent send out large mailings to such companies (and put the mailings publicly on their websites too) to say things like "Feeder 7 may be shut off between Castle ACre and Kings Lynn in June 2022.  Feeder 4 between Epping and Cambridge may operate at reduced pressure on May". Etc. That info is all public on the operators web pages, and clearly is designed to works on the principle that the names are meaningful and make sense to the people receiving them, so I regard that info as essentially public domain evidence of what the pipes joining the stated routes are called.  Any particular section pipe might only have a scheduled maintenance outage once every 10 years. However, back issues of these notices are available for a number of years, AND it's only necessary to get some hits on a pipe to be able to name it along its entire length. So those sort of notices give me most of the pipe names.
20180911 (2023-01-13 19:54:41+00:00): The mailings are interesting to get the names from. It is a bit like when I researched information for power stations in news articles like maximum power or start date.
woodpeck_repair (2022-05-28 12:43:20+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:47:51+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:47:24+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
user_5359 (2022-05-16 09:16:04+00:00): Welcome to OSM! What is the meaning of the tag addraddress:barangay = Sampaguita Village?
DP24PH (2022-05-17 05:16:36+00:00): This POI as described has been fixed already in the latest changeset 121078205 due to typo on tagging as per DP24 Research: https://www.openstreetmap.org/changeset/121078205


DP24
woodpeck_repair (2022-05-28 12:38:33+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:43:33+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:44:03+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:37:19+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:39:59+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:48:58+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:46:07+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:42:32+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:36:54+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:50:36+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:51:50+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:51:21+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:41:47+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:39:58+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:39:08+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:39:22+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:42:20+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:51:25+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:42:46+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:43:53+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:37:42+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data
woodpeck_repair (2022-05-28 12:42:31+00:00): This changeset has been reverted fully or in part by changeset 121614336 where the changeset comment is: remove undiscussed and buggy import of copyrighted camping site data