SomeoneElse's Comments
Post | When | Comment |
---|---|---|
OSM Sandbox | See osm.wiki/Sandbox_for_editing#Experiment_with_the_API_.28advanced.29 . |
|
1st diary entry | I can hide it if you want (moderators normally only do that for spammers). |
|
PMD // Piano More Details | What would also be excellent would be if you could reply to some of the questions that other mappers have asked you at http://resultmaps.neis-one.org/osm-discussion-comments?uid=10474167 . Best Regards, Andy Sarebbe anche eccellente se tu potessi rispondere ad alcune delle domande che altri mappatori ti hanno posto su http://resultmaps.neis-one.org/osm-discussion-comments?uid=10474167. I migliori saluti, Andy |
|
Mark paracel islands and spratly islands as international area |
As set out in https://wiki.osmfoundation.org/w/images/d/d8/DisputedTerritoriesInformation.pdf , the “on the ground” situation is what you’ll see reflected in the OSM “standard” map tiles.
As I’ve said above - the data already reflects this.
I wouldn’t describe “vandalising a shared international resource” or “sending messages full of expletives to people” as “fighting”, personally. If you want to do something constructive, I’d suggest (in the order of “simple” to “more difficult”):
|
|
Mark paracel islands and spratly islands as international area |
Actually, no. The reverted edits were mostly just vandalism (deleting data, writing obscenities, removing names in some langages). 3 edits by NM$L were made in the area in the last 3 weeks or so; Iv’e commented on one of them osm.org/changeset/82702598
No - constructive edits, that try and better reflect the situation on the ground, are welcome from anywhere. Mass deletions and sending lists of obscenities to people (which you yourself have done) are not.
When it comes to places where people live and work, English has no special status as a language within OSM. We try and use local languages where possible. There are a few exceptions - The Indian OSM community uses English placenames in the “name” tag, and some countries with multiple languages have opted to use combinations of thise languages in names (e.g. Belgium). In each case though it’s a decision of the people that live there, not the decision of a claiming country.
As I’ve already said, if you’d like the rules that the tiles that you see at OpenStreetMap.org by default use to change then raise that at https://github.com/gravitystorm/openstreetmap-carto/issues - but any suggestion will need to be practical and scalable. |
|
Mark paracel islands and spratly islands as international area | “OSM” does not “ mark these areas” by any name - English, Vietnamese or Chinese. All of these names will be available in the data, and it’s up to people creating maps to decide which to use. If you’d like the rules that the tiles that you see at OpenStreetMap.org by default use to change then raise that at https://github.com/gravitystorm/openstreetmap-carto/issues - but any suggestion will need to be practical and scalable. Currently, as noted in https://wiki.osmfoundation.org/w/images/d/d8/DisputedTerritoriesInformation.pdf , the language that you’ll actually need to use on the ground is the one used. Google Maps isn’t a direct comparison here because it actually gives a different result depending on where you access it from. The maps that you see at OpenStreetMap don’t do this, and in any case aren’t designed as a “service” to be used by allcomers in the same way. Lots of options exist for showing names in different languages - if you’d like to use OSM data to create one showing your desired names and country boundaries you are welcome to do so, and plenty of people already have. |
|
Mark paracel islands and spratly islands as international area | Various mappers have over the years tried to have OSM represent their country’s (and their country’s alone) claim to these islands. The wikipedia article that you linked to for the Paracels notes 3 claims and says “Administered by People’s Republic of China”. The Spratlys are more complicated, with apparently 5 different occupying powers of bits of the archipelago. I’m aware that a post-COVID-19 campaign has been whipped up by the Vietnamese press (see here for example). This isn’t relevant to OSM. OpenStreetMap has historically represented disputed boundaries with a “disputed” tag, and that tag is already present on the main Paracels boundary. By all means try and work with the rest of the OSM community towards a better representation of disputed areas. Last year one was proposed but was rejected largely because it was just too complicated. If you’d like to engage with other mappers and try and work forward to a solution please do so. Like COVID-19, only an international solution will work. However, sending expletive-ridden OSM messages to people and writing (now hidden by us) expletive-filled diary entries will only suggest to people that you are not worthy of trying to have a conversation with. Best Regards, Andy Townsend, on behalf of OSM’s Data Working Group |
|
To Jason. | @Jason_Brown - you always have the option to edit diary entries, so at any stage you could have removed you expletive-laden rant. You didn’t do this, so someone has hidden it. The advice that I gave at osm.org/changeset/83634605 still stands - please do follow it. |
|
Google Maps | I’d suggest talking having a chat with people at https://lists.openstreetmap.org/listinfo/talk-au - the various licences and waivers from potential government sources get discussed there quite a bit. |
|
Nobody seems to know where Tesla gets its map data for speed limits | Who have you asked? |
|
My phone GPS is so inacurate, uploading a GPS trace LOWERS the quality of OSM. | I don’t think that “uploading a GPS trace LOWERS the quality of OSM” - it only would if you then converted that trace to some sort of highway without looking at any other data source (which is something that I would hope that no-one in 2020 would ever do, except in the very unusual case that there’s no other data sorce available). If you can provide a bit more information about where you’re interested in adding data, I’m sure local mappers can explain which sources locally they find most helpful - both in terms of being not offset and also in terms of being recent. |
|
Use of private supplier information to improve road attributes in Germany | @Rob perhaps you need to reread what I actually said:
That applies to everyone - my edits, your edits, someone working for Amazon’s edits, everyone. Best Regards, Andy |
|
Use of private supplier information to improve road attributes in Germany | Hello, How do we know that the source that you are using is licence-compatible with OSM? Can you publish that licence, so that it is clear to the community that you do have the right to use that data and there are no potential future problems? Also, there is a very real problem here with osm.wiki/Verifiability . If an individual mapper on the ground can’t verify your edits made from this source, then they have every right to change the data to what they believe to be correct. They’ll only have access to the normal sources available in the usual OSM editors, so it’s very possible that some of your changes will be removed because they don’t match what other mappers can see. In the event that such a dispute is escalated to the Data Working Group, we’d have to favour the publicly available imagery over private imagery that no-one else has access to. I’d therefore suggest, in order to avoid the issues above, that you find some way of working where the data that you’re using is actually verifiable by the rest of the OSM community. Best Regards, Andy Townsend, from OSM’s Data Working Group. |
|
Displaying accessibility information in map icons |
Ah, OK. A problem would be that there are many more than 3 colours in use - if you look here you can see a selection of them.
Something like that would be a possibility (but with 4 states not 3 of course - “don’t know, no, restricted, yes”). The wheelchair indicator is already intentionally not “in your face” - you can use two fingers on a leaflet map to quickly magnify a section, and there it might be possible to count 0,1,2,3 or 4 pixels. |
|
Displaying accessibility information in map icons | @trial I’ve no idea what your link is supposed to show? On the more general point - no, common forms of colourblindness were not taken into account when choosing the colour palette used, mainly because pretty much every possible colour variation is in use for something. If you can suggest how to show the same variation of information and make it work for people who are colourblind as well that’d be great - the best way to start would be by opening an issue explaining what you propose to do, and then if that sounds sensible pull requests as necessary. |
|
Displaying accessibility information in map icons | Although it’s not that that time consuming to create a few more icons that differ only slightly from the originals, it would be interesting to be able create at least some of the variations automatically. I think that Imagemagick supports scripting (though I’ve never used them with it), and I’ve no idea if it supports things like “change pixel x, y to colour z”. |
|
Displaying accessibility information in map icons | It’s a lot of icons but not a lot of pixels - it doesn’t take long to take 3 copies of an existing icon and dab in two dots of green, yellow or red. The original pub icon was an old OSM Carto one - that started out as an empty beer glass, with the other features added to that. |
|
Displaying accessibility information in map icons |
It would - and one of the problems that I’ve spotted elsewhere is that the name is currently displayed quite close to the bottom of the icon, which means a “b”, “d” or “h” can have the upstroke obscure the indicator. However, part of the idea was to make the “wheelchair tag” visible, but not the “most obvious thing” about the icon as displayed. I’ll possibly experiment with slightly larger ones, or differently placed ones. |
|
Understand the map | Select the layer switcher (the “stack of books”) at the right-hand side of OpenStreetMap.org . The cycle map layer and transport map layers both show English names. Also look at openstreetmap.de. |
|
Angry OSM editors? | Hello Beachmiles, Andy from OSM’s Data Working Group here. I’ve hidden the note with the offensive comment on there, since comments like that have no place within OSM. I’ll separately message the person who made it explaining why that comment was not appropriate. With regard to the problem that caused you to add the note in the first place, it does look as if the turn lane information is now in OSM (actually added by the person who made the offensive comment) - see osm.org/way/755568005 - but that doesn’t contain information about the destination of each HOV lane. I’ve re-added the note contents at osm.org/note/2060067 , but I suspect that it’s really a more general question (“how should we tag the destinations of individual lanes”). The answer to that is that there seems to be some usage of “destination:lanes” - see https://taginfo.openstreetmap.org/keys/destination:lanes#overview for the number in use around the world and osm.org/way/375327794 for an example on the I5 South not far from you. What I don’t know is whether a Tesla will actually use that information (osm.wiki/Key:destination#destination:lanes.3D.2A_tagging asks that question more generally). You’d have to ask Tesla that question. Generally speaking, if you see problems with offensive comments you can either email OSM’s Data Working Group directly on data@osmfoundation.org . In most cases you can report the item on which they appear, but in this case it’s your own note, so you may not be able to do that. You can ask future “how to tag…” questions at https://help.openstreetmap.org/ , and if you want to talk to people in the OSM US community, you can use the link to request to join “OSM US” from osm.wiki/List_of_OSM_centric_Slack_workspaces . I know that Tesla’s use of OSM data occasionally gets mentioned there. Best Regards, Andy |