ElliottPlack's Comments
Changeset | When | Comment |
---|---|---|
153313375 | 10 months ago | Hi there, Elliott here with the OSMF Data Working Group. How exactly was this speed limit field verified? According to the Maryland SHA, the entire beltway is 55 MPH: https://data-maryland.opendata.arcgis.com/datasets/maryland::mdot-sha-roadway-posted-speed-limit-signs/about Additionally much of this area is under a speed limit reduction for a temporary work zone, where speeds are dropped lower than 55 during construction. In other changesets you've set the DC beltway to 70 MPH yet it is also 55. Why did you do this? |
151166796 | about 1 year ago | Aaron! I love to see that you're back mapping. How are you doing? I'd love to catch up sometime. -Elliott |
153752243 | about 1 year ago | thanks for the corrections while working on the import! |
153746640 | about 1 year ago | Review: 1. If you know this to be paved in asphalt or concrete, please do specify that the surface is one of those options. "paved" is generic. 2. try to vary your changeset comments a bit, such as noting when you have noticed the change or what is unique about one road or another. |
153746595 | about 1 year ago | Thanks for adding your local knowledge to the map! |
153751846 | about 1 year ago | Welcome, thanks for adding this school! |
48603942 | about 1 year ago | Hi there, someone recently deleted this park. Please discuss: osm.org/changeset/153750960 |
153750960 | about 1 year ago | This changeset deleted a number of parks without explanation. Please see osm.org/user_blocks/16430 and comment as to the reason for these deletions. |
153700032 | about 1 year ago | Nick, you should report these issues to Lyft (and the Data Working Group) before fixing them. That way Lyft will not simply roll them back. I've commented on Lyft's changeset to get you started. Elliott Plack
|
153559315 | about 1 year ago | Hi there. Whether or not a road is on private property on a "GIS map" is immaterial to how it should be tagged in OSM. It is possible for a public road to be on private property, such as via an easement, or when the GIS is out of date. Further, any GIS data you are using to cross reference against OSM needs to be vetted through the import process. See osm.wiki/How_We_Map "don't copy copyrighted data without permission" We need a written sign off from the city that they are ok with you using their data to update OSM unless the city's data is public domain. Before referencing any more city maps into OSM, I suggest proposing an import following the instructions here: osm.wiki/Import Thanks, Elliott Plack
|
153143361 | about 1 year ago | Edit: signature: thanks, Elliott Plack
|
153143361 | about 1 year ago | Hi there, another user is claiming most of what you've mapped here is not in fact private. can you clarify? If people are allowed to walk around on the roads but cars are not allowed, then you should not add the blanket access=private tag. Perhaps sharing what sources you have will help other mappers understand. |
152919242 | about 1 year ago | Nick, in this changeset you broke the boundary of Honolulu by added a new part of the boundary and not adding the role of inner to it. Please be mindful of boundary relations when working around them. |
152111912 | about 1 year ago | Hi there. In this changeset you've edited the boundary of "Unincorporated Colma" to include the admin_level=8 tag. This is inappropriate for an unincorporated area. admin_level=8 are reserved for areas with a town government (e.g., a mayor and city council). This unincorporated area should either be removed entirely or not be tagged as an incorporated town. Thanks! Elliott Plack
|
153480879 | about 1 year ago | Hi there Tyler. In this edit you have added congressional districts to the map. What is the source for these boundaries? Data added to OSM via sources other than what is observable on the ground or from the air are prohibited without proposing to import the data through the import process. Even if the source is a public domain dataset, such as US Census TIGER, you must still discuss this work with the community. I came across this by chance while reviewing another boundary type in NYC of dubious origin: community boards. https://community.openstreetmap.org/t/manhattan-community-boards-as-administrative-boundaries/115549 Before you continue importing these boundaries, please review our import guidelines. osm.wiki/Import As an example, check out https://community.openstreetmap.org/t/proposed-import-of-all-the-places-data-onto-existing-big-box-retail-pois-in-the-us/114939 I look forward to hearing from you via this changeset comment discussion. Elliott Plack
|
134952157 | about 1 year ago | any reason why to create the relation and not add to the building? The building already has all the tags. I stopped by today and it looks like they have moved. no signs on the building anymore and it is for lease |
152392464 | about 1 year ago | Henry, glad you found some gravel roads! Gravel, in an OSM sense, is not likely what you encountered here however. An American "gravel" road is surface=compacted in OSM. Gravel is reserved for the surface of something like railroad ballast covering a track. You will find it on BGE access roads but not too many other places. When you think 'gravel' bikes, think compacted. There is also "fine_gravel" which may be tempting but don't use that one either. Fine gravel is slippery on a bike, you would have trouble riding fine gravel without one of those fat tire bikes. This surface is also relatively rare on improved roads but may appear on some garden type paths. |
153180969 | about 1 year ago | Hi there. I'm Elliott with the Data Working Group. The GIS you are citing in this changeset, what is it precisely? Referencing GIS data requires the data be in an OSM compatible license, or you must have explicit permission to use it that is documented in the wiki. Further, the municode site caries a copyright (Copyright © 2024 Municode.com ) which is inherently incompatible with the OSM ODBL. Municode would need to give permission for you to use it as a reference. Remember that only federal works of the United States **Federal** government are in public domain by default. Every state and lower government is free to copyright their works. Just because it is a government source, does not make it able to be used in OSM. Please contact us at data@openstreetmap.org or in this changeset if you'd like to discuss further. In the meantime, please refrain from using any GIS sources for justification unless you first secure permission and document it on the OSM wiki just like any import. Thanks! |
153214591 | about 1 year ago | Hi there, Elliott with the DWG here. I've blocked lomtitude as a warning that this sort of edit needs be discussed with the community first: osm.org/user_blocks/16315 |
153093512 | about 1 year ago | 👍 |