Iván Sánchez Ortega wrote:
> I don't think OSM is the place for statistics... it has been said over and
> over "map what is on the ground".
But what we should be able to do is use the OSM data to easily correlate
with available statistical sources, which means things like official
boundaries an
There has been some discussion about what might be a similar problem on
talk-us, where different states have different signs on Interstate
highways.
I have a few questions; it might be good to explain the answers on the
tag proposal page. (I'm sure in .es the answers are obvious but I think
road
El Domingo, 19 de Abril de 2009, Greg Troxel escribió:
> There has been some discussion about what might be a similar problem on
> talk-us, where different states have different signs on Interstate
> highways.
[...]
> In the US, the essence of the issue is that we have Interstate highways,
> which
Iván Sánchez Ortega writes:
>> In the US, the essence of the issue is that we have Interstate highways,
>> which have a standard sign, but some states, especially California, have
>> variants, and people want maps to show the local variants so they match
>> what's on the ground.
>
> Here in Spai
El Domingo, 19 de Abril de 2009, Greg Troxel escribió:
> I am also starting to think that the US proposal to do "us_i_ca" for
> california interstate is maybe not the right answer. The road really is
> "network=us_i" but maybe needs a "network:sign_variant=us_i_ca" tag.
I think that usage of "net
Iván Sánchez Ortega writes:
>> As an example, near me in the US you can be on a road which is both I-95
>> S and Massachusetts state route 128 south. Then there is an
>> intersection where I-95 splits off. After the interchange you are on
>> 128S and I-93N.
>
> Hm, sounds a little bit like the
I've come across a handy trick for determining the reference number for a L
road here in Tipperary - the county council
publishes the Speed Limit By-Laws; and nicely refers to most roads by the
L-ref value. The by-laws are available for free download off their website.
In most cases this makes it
2009/4/19 Iván Sánchez Ortega :
> Do you really think we can work that network->color table out, and make
> software that fits into osm2pgsql to derive the shields?
Remember that it doesn't need to be osm2pgsql to do this - large-scale
.osm manipluation can be done with osmosis, and see also the
On Sun, Apr 19, 2009 at 05:20:09PM +0200, Iván Sánchez Ortega wrote:
> Do you really think we can work that network->color table out, and make
> software that fits into osm2pgsql to derive the shields**?
>
>
> ** I don't like the word "shield". We use frakking rectangles.
Like these ones?
http
On Mon, Mar 30, 2009 at 6:33 PM, Matt Amos wrote:
> On Mon, Mar 30, 2009 at 5:31 PM, MP wrote:
>>> after the wembley mapping party last year i heard suggestions of a
>>> "locals=angry" tag. maybe we should expand that to include
>>> "locals=violent" or "locals=heavily_armed"?
>>
>> What happened
I'm not on IRC, so I've got no idea, but anyone how the upgrade is going so far?
Regards,
Maarten
___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk
Maarten Deen schrieb:
> I'm not on IRC, so I've got no idea, but anyone how the upgrade is going so
> far?
>
>
firefishy about 2h ago on twitter: migrating API 0.6 database - phase 5
(i started at the wrong number): re-creating consistent current tables.
No major problems yet.
Jonas
__
2009/4/20 Andy Allan
> On Mon, Mar 30, 2009 at 6:33 PM, Matt Amos wrote:
> > On Mon, Mar 30, 2009 at 5:31 PM, MP wrote:
> >>> after the wembley mapping party last year i heard suggestions of a
> >>> "locals=angry" tag. maybe we should expand that to include
> >>> "locals=violent" or "locals=hea
2009/4/20 D Tucny
> 2009/4/20 Andy Allan
>
>> On Mon, Mar 30, 2009 at 6:33 PM, Matt Amos wrote:
>> > On Mon, Mar 30, 2009 at 5:31 PM, MP wrote:
>> >>> after the wembley mapping party last year i heard suggestions of a
>> >>> "locals=angry" tag. maybe we should expand that to include
>> >>> "lo
One data point: my Garmin eTrex unit has recently broken the 'zoom in' button on
the side - it broke off underneath the rubber bumper and started rattling around
inside, so now the map display can be zoomed out but not in. I bought it a few
months ago, so will try to get it repaired under warranty
Hi all,
as im going through the rules.txt file and adding in the 'entity' and
'value' tags, im thinking that adding the tag 'canvec:definition'
would help.
On some tags its a few lines of text, but it shouldnt go over the max
number of characters permitted.
Any thoughts? (before i spend uneeded ti
On Sun, Apr 19, 2009 at 3:05 PM, Ed Avis wrote:
> One data point: my Garmin eTrex unit has recently broken the 'zoom in'
> button on
> the side - it broke off underneath the rubber bumper and started rattling
> around
> inside, so now the map display can be zoomed out but not in. I bought it a
>
17 matches
Mail list logo
