Re: [Talk-us] Map spam

Hi, On 07/10/2016 09:45 PM, Mike N wrote: > I have seen a number of these - at first there was some app generating > invalid OSM tags, but excellent geolocation (to OSM standards, center of > main business building). Side note on "we place you on the map" businesses - they often don't have

Re: [Talk-us] Map spam

On 7/10/2016 3:30 PM, OSM Volunteer stevea wrote: It is just not that big of a problem. I am weirdly impressed by the odd combination of "quite well-formed data tagging, yet I can still (nearly always) determine that the node is spam." In other words, they are trying hard to fly in under our

Re: [Talk-us] Map spam

> Circa 07/10/2016 08:28 PM, Jack Burke and Frederik Ramm > wrote: >> Is anyone else starting to see map spam popping up in their areas? and > DWG here. We see lots, but not to a degree that would concern us. Thank you to Jack for bringing this up and

Re: [Talk-us] Map spam

Hi, On 07/10/2016 08:28 PM, Jack Burke wrote: > Is anyone else starting to see map spam popping up in their areas? DWG here. We see lots, but not to a degree that would concern us. Occasionally individual IP numbers from Asia were blocked for signups because they would create account after

[Talk-us] Map spam

Is anyone else starting to see map spam popping up in their areas? Over the past few months, I've seen 3 OSM entries that I'm calling map spam for lack of a better term. I know that doesn't seem like a lot, but it could be a new trend. Specifically, what I'm finding is a well-formed node for a

Re: [Talk-us] Common names of highways do not match road signs.

On Sun, 2016-07-10 at 12:07 -0400, Kevin Morgan wrote: > Here is an idea. An additional tag is added called signage. The tag > use the following format name;ref;text. Each item is added to the tag > if the information is in clued on road signs. The tag has the > following sub tags color, icon,

Re: [Talk-us] Common names of highways do not match road signs.

I think this would be great for point-based data in order to help others properly determine the correct name=* tag. However, given the circumstances, I tend to also use source:name or name:source (not sure which is correct) citing the state law renaming the road, since that's verifable and

[Talk-us] Common names of highways do not match road signs.

Here is an idea. An additional tag is added called signage. The tag use the following format name;ref;text. Each item is added to the tag if the information is in clued on road signs. The tag has the following sub tags color, icon, description, direction and text. The text sub tag is used to add

Re: [Talk-us] Common names of highways do not match road signs.

On Sun, Jul 10, 2016 at 5:47 AM, Richard Fairhurst wrote: > Greg Troxel wrote: > > When converting to garmin format with mkgmap, and I think with osmand, > > I will tend to hear both the name and the ref. That's a big lengthy, but > > there's no real pattern on which to

Re: [Talk-us] Common names of highways do not match road signs.

Greg Troxel wrote: > When converting to garmin format with mkgmap, and I think with osmand, > I will tend to hear both the name and the ref. That's a big lengthy, but > there's no real pattern on which to leave out. For cycle.travel's directions in the US, I've started post-processing the name