Re: [Talk-us] Parks in the USA, leisure=park, park:type
On 4/26/2019 9:49 PM, OSM Volunteer stevea wrote: >> Other than that I can't think of any tags that would be applicable to >> these sorts of situations. We tend to tag the regulations themselves, >> not the extent to which they're adhered to. Certainly just calling it a >> park because kids play there doesn't seem consistent with OSM standards. >> We don't raise the speed limit in places where everyone speeds, or tag >> bicycle=yes on ways where they're prohibited but frequently used. > > > No, I think leisure=playground aligns a bit more closely with "kids play > here," though some people like snap-tight definitions, others consider > things as much more elastic. It's difficult to please everybody; semantics > can be messy. I disagree. Going by that definition, my front yard would be leisure:playground. I believe the tag should be used for "a place designated as an area for children to play". Also, just because someone puts a swing set in their back yard, shouldn't mean their back yard should be tagged as a playground. On another note, there are places defined as “city parks” here that are no more than land that can't really be used for anything. For instance, a lot in a subdivision that’s used for storm drainage is labeled as a nature park. It's due to the fact they planted native plants on the lot to attract wildlife. You would not know it's a "park" if you didn't read the small sign stating so. It just looks like an overgrown, unleveled lot. Aaron Forsythe ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] trail tagging
> From: brad > > cycleway ; bike path ; paved path, open to bikes, & I've never seen one that > wasn't open to pedestrian too These do exist. There are a few around here (Missouri, USA). In these cases, there’s usually a separate path for pedestrians so cyclists can have a path off the roadway, but not have to dodge pedestrians. They are rare enough though that defaulting to allow pedestrians would likely still be the best option. Aaron Forsythe ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] motel vs. hotel
>> As I believe the etymology of the word "motel" (circa 1920s) is a contraction >> of "motor hotel," I believe it is fair to say that a motel is a hotel which >> caters to motorists. That is, patrons who arrive in an automobile and wish >> for it to be immediately accessible, as in parked directly outside the room >> in the case of a single story facility, or very nearby for multiple story. Pretty much this. I would define a motel as a place you would stay at just to rest and shower while on a long, multiple day, drive. Like driving from the East coast to the West coast in USA without extra stops. Simply a room to stay in with possible a common area that provides cold breakfast (cereal/bagels/etc.). A hotel would be more somewhere you would stay at for multiple days in a row on a vacation or business trip. These usually have extra features (hot breakfast/pool/room service/etc.). Aaron Forsythe ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road name update challenges
These are all just my opinions, so don't take as fact. I could be wrong. >> 1. Original TIGER had Ruppe Dr at a nearby but incorrect location. This seems a common enough occurrence that a TIGER data should not be used as permanent source. It's only there to get the map started and adjustments from TIGER are required. >> 2. Updated TIGER caught Ruppe Dr at the correct location, but introduced a typo when entered: Tuppe instead of Ruppe, and didn't remove or just move the original Ruppe Dr. If we have verifiable data that Ruppe Drive is correct and Tuppe Drive is wrong, then Ruppe Drive should be used. I'm not against putting Tuppe Drive in alt_name just in case. >> 5. A second update was applied using older / wrong TIGER data. Neither noticed the wrong duplicate Ruppe Drive that ran through a house. If newer, verifiable data shows this (obvious from aerial maps taken after the TIGER data, or BOTG survey) then it should be removed. >> The wrong Tuppe Drive still has a "source" tag which is now misleading. It's not really misleading, as that is still where it came from. >> We were able to get a local GIS to release data to OSM. In analyzing the data, I notice that address tags are much more carefully updated than road names. So I could create a local project to correct some local roads based on corrections from the address data. I hesitate because then those changes will be reverted when they don't match TIGER. Usually, at least around here, addresses have the correct street names. Street signs are sometimes wrong, especially if it will save a few dollars. Quite common for older street signs to leave out spaces in the name, leave off the Dr/St/Ave, or leave off East/West/North/South just to save money with a shorter sign. If the correct name includes the shorter name, I only put the correct name. If it has spaced removed, like River Bend becoming Riverbend, then I put one in alt_name. >> 2.) Just as if I surveyed the name on a street sign and was able to confirm it with public records, how would I detect / prevent loss of work when it mismatches our other public sources for several years? Use the source tag and include a date of the survey. This won’t directly stop an overwrite, but will at least give a date to compare against. It seems the whole issue stems from an automatic edit without proper integration. https://wiki.openstreetmap.org/wiki/Automated_Edits_code_of_conduct ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] USPS Post Boxes
I’d be weary of using what’s on the box as the operator. There are multiple types of drop boxes provided by USPS (also UPS and FedEx have multiple types). These have different restrictions on the type of mail/packages that should go in those boxes. Putting in the wrong box can likely cause a delay in the transit time, and even could cause a return to sender. Personally, I’d rather go by what the operator uses with legal terms. Examples: Copyright © 2018 USPS, Copyright ©1994- 2018 United Parcel Service of America, Inc., © FedEx 1995-2018, 2018 © DHL International GmbH. This shows 3/4 of the major operations near here use abbreviations. Therefore, I would suggest abbreviations for all. Sorry for joining this discussion late. - Aaron Forsythe > For those tagged with an operator, most are one of the many variations on the US Postal Service name: > 3609 * usps > 199 *us postal service > 125 * u.s. postal service > 12 * us post > 11 * united states postal service (used to be popular before Leif's mass edit) > 4 * us mail (some older post boxes still say this on the side) > 1 * united states postal office > 1 * usps express mail > 1 * usps.com ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Address data for Miami Florida United States
I would just like to point out two things. addr:unit – I get there are a lot of tall buildings where this isn’t useful in Miami. It is useful for large footprint buildings to know what entrance to park by. Sometimes around here (unsure of in Miami) one address will even serve multiple buildings. For instance at a hospital there may be 3 buildings containing doctors offices with the same address. zip codes – Zip codes are USPS routing codes. They do not align to cities and may even cross over each other often. USPS only uses the city field on mail as a backup to zip codes. They fudge the cities intentionally to make it easier on their sorting machines. I’d be cautious when getting city data from USPS based on zip codes. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
