Re: [Talk-us] San Diego Address Import Update

This is how I have always used addr:city. It reflects the postal address since it is a property of the address and not the parcel itself. People once used the is_in tag to capture the other meaning, but it seems unnecessary to me since one can simply check for an enclosing admin boundary. On

Re: [Talk-us] San Diego Address Import Update

On 11/10/15 11:09 AM, Clifford Snow wrote: > > On Tue, Nov 10, 2015 at 7:48 AM, Tod Fitch > wrote: > > So what is a good definition for what should go in the addr:city > tag? If it is based on being within a formal administrative >

Re: [Talk-us] San Diego Address Import Update

> On Nov 10, 2015, at 5:59 AM, Greg Troxel wrote: > > > Tod Fitch writes: > >> What is a “city” in US specific OSM terms? >> >> I prefer a postal city definition as that is the most useful for >> routing purposes which I feel is the primary use of

Re: [Talk-us] San Diego Address Import Update

Richard Welty wrote: > the real problem is that the tagging scheme we are using didn't consider the > divergence between postal and administrative city names and is insufficiently > rich to express the details. I agree. There are areas near me in unincorporated Orange County that can go by

Re: [Talk-us] San Diego Address Import Update

On Tue, Nov 10, 2015 at 7:48 AM, Tod Fitch wrote: > So what is a good definition for what should go in the addr:city tag? If > it is based on being within a formal administrative boundary then we may > not need the tag at all as it should be easy for a data consumer to

Re: [Talk-us] San Diego Address Import Update

> On Nov 9, 2015, at 8:42 PM, Richard Welty wrote: > > maybe but i would do some more research before making an assumption. i'm aware of many postal city addresses that are in different counties than the "real" cities and i believe there are at least 4 cases where

Re: [Talk-us] Proposal: Sunset ref=* on ways in, favor of relations

Richard Welty wrote: the key thing, i think, is that mappers have little motivation to work on route relations if they don't actually get used by anything. This is so, so true. Not just about route relations, but in the general sense of "crowdsourced data SHOULD become visible by at least

[Talk-us] time-conditioned turn restriction

Looking at the pages for turn restrictions and conditional restrictions, I gather that you would map a left turn restriction that is only valid between 6am and 9am and again between 4pm and 7pm as: type=restriction;restriction=no_left_turn; no_left_turn:conditional=no @ (Mo-Fr

Re: [Talk-us] Proposal: Sunset ref=* on ways in, favor of relations

> > Anybody up for writing a quick-and-dirty "here's how to develop an OSM > renderer from scratch" wiki? (Maybe I just haven't seen this if it already > exists). It may not be drop-dead easy, but an intermediate coder should be > able to make one in short order (weeks, not months). I would

Re: [Talk-us] San Diego Address Import Update

Tod Fitch writes: > What is a “city” in US specific OSM terms? > > I prefer a postal city definition as that is the most useful for > routing purposes which I feel is the primary use of address data in > OSM. Or are we dealing with some other concept of addr:city? I see

[Talk-us] Whole-US Garmin Map update - 2015-11-07

These are based off of Lambertus's work here: http://garmin.openstreetmap.nl If you have questions or comments about these maps, please feel free to ask. However, please do not send me private mail. The odds are, someone else will have the same questions, and by asking on the talk-us@