I can revert it if the data hasn't been changed and you didn't do other edits
in the same changeset.
check the changeset and if you think it should be reverted as a whole let me
know.
If you prefer to revert just some portion it's best to use Potlatch and with
key 'U' you will see all deleted
a portion of the nodes was referenced 2 times. and then the way isn't closed
anymore.
easy to spot if you open the osm file oand search for a node which is listed
twice.
In Josm you can enable segment numbers and as soon as 2 are drawn above each
other you will know the problematic area.
On Sat,
On Sat, Mar 6, 2010 at 9:53 AM, James Ewen wrote:
> On Sat, Mar 6, 2010 at 8:35 AM, Adam Dunn wrote:
>
> > I think it should be pointed out that vreimer hasn't made any edits since
> > the blocking, and this buggering up was done beforehand (Feb 13, 2010 to
> be
> > exact). I just think it's wor
luckily no other edits have been done on the changeset. quick check shows it's
malicious or at least careless deletion
revert is done
but it seems there are 2 duplicated way which should be deleted, maybe veimar
tried to fix it but damaged in Potlatch live mode and has no clue about undo
good: h
usually tiger is wrong, yahoo resolution is not very good but still good enough
to confirm that the tiger roads don't match at all.
On 19 Feb 2010, at 19:26 , Adam Dunn wrote:
> Working on NRN import on BC/Alaska border, in the town of Stewart, and it
> looks like there is a mismatch in positio
Yeah, and that does sound like a really nice way to do it, especially
when there is existing data.
Anybody want to be on the USA "conversion team"? :)
sure, post all your ideas and improvements. if the noise is too high we can create another list f
this is great work, signs could be a bit smaller tough.
why not stick with the symbol tag? see
http://wiki.openstreetmap.org/wiki/United_States_roads_tagging
the symbols tagging should be transparent to the mappers not only to
some internal notation of a renderer.
and tags should be human readab
On 12 Apr 2009, at 9:01 , Adam Schreiber wrote:
>
> Probably because the mapper can easily identify the type of road (i.e.
> Interstate, US Hwy, etc.). I'm not sure that the mapper should be
> specifying the URL of the sign since it requires extra work to find it
> and any renderer should be able
>
>
> The lower case has nothing to do with a renderer, just OSM convention
> for key value pairs other than name.
>
network name is an officially documented and commonly used name. it
should be treated like the name tag or the ref tag.
how else could a renderer come up with the correct use if
>
>
> I'm in danger of spending more time flaming than fixing the map, but
> have always been interested in the database schema aspect of OSM.
> Evolving tags is messier than a designed scheme, but I see the
> wisdom of
> how it avoids the wrong design persisting. Still, I think it may make
> s
On 13 Apr 2009, at 5:36 , Adam Schreiber wrote:
>
> What about:
>
> addr:country=us
> addr:state=ca
> network=us
>
> or
>
> addr:country=us
> addr:state=ca
> network=i
>
network should be US, I,
all signs use uppercase, there can be so many uses for the data.
network should reflect the r
On 12 Apr 2009, at 11:58 , Richard Weait wrote:
> On Sun, 2009-04-12 at 13:23 -0500, Joseph Jon Booker wrote:
>> On Sun, 12 Apr 2009 08:39:45 -0700
>> Apollinaris Schoell wrote:
>>> 2 relations are easier. adding role to thousands of members is a
>>> pain. an
12 matches
Mail list logo
