Reminder that the next Midlands OSM social is this Thursday evening 3rd June
in Bilston to the southeast of Wolverhampton. Weather is set fair so we
expect to be mapping till around 8 or 8:15pm. See the cake on the wiki page
for locations to map [1].
Call me on 0777 553 7872 if anyone wants to find
On 29 May 2010 20:31, TimSC wrote:
> Hi all,
>
> I have updated the code and put out a new version of mapseg (now v0.2).
> As Roy Jamison discovered, the previous version was broken by upper case
> filenames. The program is now case insensitive to that. Available here:
> http://wiki.openstreetmap.
Peter Miller writes:
>We have created a map layer for Potlatch showing OS Locator names
>which are not in the nearby OSM data in a nice visual way.
>Note our proposed 'not:name' tag for suppressing errors in OS Locator
>data.
I have sometimes used incorrect_name for noting mistakes in stree
Peter Miller writes:
>We have created a map layer for Potlatch showing OS Locator names
>which are not in the nearby OSM data in a nice visual way.
>To access the tiles paste the following into the custom layer box in
>Potlatch (or similar in JOSM).
>http://tiles.itoworld.com/os_locator/!/!/
On 1 June 2010 12:18, Ed Avis wrote:
> I have sometimes used incorrect_name for noting mistakes in street names.
> The intention was that if somebody tagged it wrongly, it's likely that
> somebody could also do a search for the incorrect name. OSM search engines
> might want to use incorrect_nam
On 1 Jun 2010, at 12:18, Ed Avis wrote:
> Peter Miller writes:
>
>> We have created a map layer for Potlatch showing OS Locator names
>> which are not in the nearby OSM data in a nice visual way.
>
>> Note our proposed 'not:name' tag for suppressing errors in OS Locator
>> data.
>
> I have somet
On 1 Jun 2010, at 12:36, Ed Avis wrote:
> Peter Miller writes:
>
>> We have created a map layer for Potlatch showing OS Locator names
>> which are not in the nearby OSM data in a nice visual way.
>
>> To access the tiles paste the following into the custom layer box in
>> Potlatch (or similar in
I don't believe there would be any point in creating more tags for
possibly incorrect names that are being searched for. A good search
engine can do all that legwork for the end user giving suggestions like
Google maps or something similar taking the hassle away.
As far as street names vs OS Locat
Peter Miller wrote:
> We have created a map layer for Potlatch showing OS Locator names
> which are not in the nearby OSM data in a nice visual way.
>
> Details in our blog post of the subject.
> http://itoworld.blogspot.com/2010/05/os-locator-validation-mapping-for-uk.html
>
> To access the tile
Is there an easy way to find the tile reference for a given area. I
have found what I need so far by trial and error, but with 400 tiles
it can be a bit of a pain.
--
Philip Stubbs
Philip,
A quick sketch on the method to go from tile filename to coordinates.
Say we use the filen//ame su85
On Tue, Jun 1, 2010 at 3:39 PM, Chris Hill wrote:
> On a rainy afternoon I took a look at your overlay and I think it is
> potentially very useful. The main issue I guess is this new tag. I think
> "not:*" is imaginative, but it rankles with me somehow. How about just
> putting source:name=survey
On 1 June 2010 15:43, TimSC wrote:
> Is there an easy way to find the tile reference for a given area. I
> have found what I need so far by trial and error, but with 400 tiles
> it can be a bit of a pain.
>
> --
> Philip Stubbs
>
>
> Philip,
>
> A quick sketch on the method to go from tile filenam
On 1 Jun 2010, at 15:00, Ian Spencer wrote:
Peter Miller wrote on 31/05/2010 11:02:
We have created a map layer for Potlatch showing OS Locator names
which are not in the nearby OSM data in a nice visual way.
Details in our blog post of the subject.
http://itoworld.blogspot.com/2010/05/os-
On 1 Jun 2010, at 15:39, Chris Hill wrote:
> Peter Miller wrote:
>> We have created a map layer for Potlatch showing OS Locator names
>> which are not in the nearby OSM data in a nice visual way.
>>
>> Details in our blog post of the subject.
>> http://itoworld.blogspot.com/2010/05/os-locator-
On 1 Jun 2010, at 15:50, Andy Allan wrote:
> On Tue, Jun 1, 2010 at 3:39 PM, Chris Hill wrote:
>
>> On a rainy afternoon I took a look at your overlay and I think it is
>> potentially very useful. The main issue I guess is this new tag. I
>> think
>> "not:*" is imaginative, but it rankles with
On 31 May 2010, at 12:00, Robert Scott wrote:
> On Monday 31 May 2010, Peter Miller wrote:
>> We have created a map layer for Potlatch showing OS Locator names
>> which are not in the nearby OSM data in a nice visual way.
>>
>> Details in our blog post of the subject.
>> http://itoworld.blogspot.
On 31 May 2010 11:02, Peter Miller wrote:
>
> We have created a map layer for Potlatch showing OS Locator names
> which are not in the nearby OSM data in a nice visual way.
This is a great tool. I thought all the roads in my area had been
mapped, but this highlights some new closes etc that have
Peter Miller wrote:
>
> On 1 Jun 2010, at 15:39, Chris Hill wrote:
>
>> Peter Miller wrote:
>>> We have created a map layer for Potlatch showing OS Locator names
>>> which are not in the nearby OSM data in a nice visual way.
>>>
>>> Details in our blog post of the subject.
>>> http://itoworld.blo
On 1 Jun 2010, at 19:03, Chris Hill wrote:
> Peter Miller wrote:
>>
>> On 1 Jun 2010, at 15:39, Chris Hill wrote:
>>
>>> Peter Miller wrote:
We have created a map layer for Potlatch showing OS Locator names
which are not in the nearby OSM data in a nice visual way.
Details in
On Tuesday 01 June 2010, Peter Miller wrote:
> We did have a similar discussion in-house at the design stage. We
> could of course implement this and the data would then be locked away
> into our systems and be hard for others to access and use for other
> purposes unless we do further work t
Totally agree. Flooding OSM with not: tags is both pointless and
counter-productive. Why not implement a search engine type feature like
google suggest that spell checks and autocorrects. If the differences
between OS Locater and OSM are only minor, i.e. apostrophes, spaces in
names, etc then these
I've used old_name=* in places that might also be good to be a
warning suppressor.
Sometimes visible signs remain but may fade away, sometimes it's been a
place I've resurveyed for OSM (changes from marketing during new development
and road sign installation). There was one case where the end of th
22 matches
Mail list logo