Ok well so far I see no opposition to deleting tiger:upload_uuid. I
might go ahead and work on some code for this.
Other than that we have some votes for keeping tiger:county, tiger:zip
and tiger:separated although I personally still have it in for
tiger:separated :)
Any thoughts on
I happened to be looking at Kern County and noticed two problems with the
imports that seem to be systemic over the area.
The first is classification of empty areas as landuse=residential (e.g.
http://www.openstreetmap.org/browse/relation/540695
http://www.openstreetmap.org/browse/way/53993995)
At 2012-07-29 00:30, Paul Norman wrote:
While doing this cleanup I would suggest removing attribution, description,
kern:Comb_Zn, kern:Zn_Cd1 and setting source=Kern_County_GIS
There might be some objects that have been edited, so you'll want to add
;Kern_County_GIS if there is an existing
At 2012-07-29 01:04, Toby Murray wrote:
And then we end up with things that are off by 15-20
meters and look crappy:
http://www.openstreetmap.org/?lat=34.95455lon=-118.16858zoom=16layers=M
It looks like the landuses are shifted by about 28m at 126 degrees from
Bing z19 dated
When it comes to Interstates multiplexing, I think we should list first the one
that the exit numbers are for on the highway. Some examples would be as
follows: ref=I 76;I 70 on the PA Turnpike since I-76 is the main route and
all the exits along there use I-76's mileage.ref=I 77;I 74 in NC
On Thu, Jul 19, 2012 at 4:50 AM, Phil! Gold phi...@pobox.com wrote:
* Toby Murray toby.mur...@gmail.com [2012-07-19 00:42 -0500]:
Any other common problems that people have seen?
The most common problem I see is a missing way. But all the nodes are
there sitting in space.
I've also tried:
On Thu, Jul 19, 2012 at 9:06 AM, Richard Fairhurst rich...@systemed.netwrote:
Depends whether you visit LA I guess ;) , but assuming you do, let's roll
up
our sleeves and fix it. I don't think that one self-proclaimed viking
deciding not to agree to the new licence completely damns OSM!
An
Bryce Nesbitt wrote:
I rather think the non-responders could have been a separate category,
and their data could have been kept.
Doesn't fly legally, sadly. You can't say I'm ignoring any rights on
this item just because the rights-holder hasn't responded to my e-mails.
That said, I did
Here's my 2 cents on the mentioned tiger tags, fwiw:
tiger:cfcc - As I understand, its original purpose was to classify
different highway types, but once the appropriate OSM tags [derived in
part from this tag, and then also from whatever other sources,
imagery, personal visit, etc] have been
Personally, I think there should be a tag to differentiate between a
one-way road and half of a divided road; yes, a human can look at the map
and make that determination instantly, but a computer requires some
advanced analysis. (I can imagine some extra-nice rendering could benefit
from this
Hi,
Sorry to be late to chip in.
I would keep CFCC. It's a good tag to have both to be able to generate
statistics (how much of original TIGER class mapping remains intact?)
as well as for reference; I find the CFCC classification is usually
good - even if the mapping onto OSM k/v is sometimes
On Sun, Jul 29, 2012 at 1:21 PM, william skora skorasau...@gmail.com wrote:
Tiger:tlid - Could be removed. I've had newbies ask me at mapping
parties what it means, I haven't been able to answer them. I haven't
seen any use for its inclusion at this point.
FWIW, I strongly support removing
On Sat, Jul 28, 2012 at 2:33 AM, Toby Murray toby.mur...@gmail.com wrote:
Some people may not even be aware of this but JOSM silently discards
the created_by tag if it exists on any object you change and upload to
the API. This tag was deemed unnecessary and counterproductive a long
time ago
On Sun, Jul 29, 2012 at 3:25 PM, Ian Dees ian.d...@gmail.com wrote:
While we're incrementing every single version number of TIGER data, we
should think about expanding the road names, too. Using the prefix and
suffix data already on the majority of the ways makes this pretty
fool-proof, so
On 29 July 2012 23:21, Toby Murray toby.mur...@gmail.com wrote:
On Sun, Jul 29, 2012 at 3:25 PM, Ian Dees ian.d...@gmail.com wrote:
While we're incrementing every single version number of TIGER data, we
should think about expanding the road names, too. Using the prefix and
suffix data
At 2012-07-28 00:33, Toby Murray wrote:
What do you think about adding a couple of TIGER tags to be silently
dropped? ...
tiger:separated
tiger:upload_uuid
+1
tiger:separated
I never knew what it was supposed to mean. If it was (as its name suggests)
to indicate a physical separation
Kern County does have its set of unique challenges. As mentioned, the rural
areas of Kern County I imported from the official county files tend to be too
generalized - either landuse=farm for agricultural land or landuse=residential
for any type of residential area even if it is rural
Hi,
On Sun, Jul 29, 2012 at 7:54 PM, Alan Mintz
alan_mintz+...@earthlink.net wrote:
Some people have been removing some TIGER tags already for a while. My only
concern would be that, if all the TIGER tags are removed from an object, we
should add TIGER05 to the source tag, so as not to
Hi all,
I'm going to discuss this with the local NYC community (some of which
are on this list) but I'm going through NYC and I'm looking for things
that aren't right.
I've tried to do some nominatim queries and the results have been
frustrating at best.
Some of these appear to be TIGER
Brooklyn actually does come up way down in the Nominatim list.. I
think part of the confusion may be that this is technically Kings
County (which renders invalid the possibility of using the
administrative level of county as the key for the boroughs).
Boroughs are somewhat unique beasts to New
20 matches
Mail list logo
