[Talk-us] Operation Cowboy - Preaparing Thank you gift

[Matthias Meißer]

Hi,

if we look at the current stats, >150 users joined the OPC2012 which 
results in 300 active mappers in the US (as the usual 200 ones).
Personally I like to send out an "Thank you all!" message, but maybe we 
all can build something more personal? Just a few ideas:


1. Collecting photo snapshots of the american OSM community and build a 
collage with it? Maybe the string "Thank you" with your faces? Or as 
part in a animation? (who can do this videoediting?)


2. Writing the String in all possible languages (in german: "Vielen 
Dank!") in the USA deserts at OSM, taking a snapshot and removing them 
afterwards?


Maybe you have another ideas, how you can thank people contributing from 
the other end of the world?


Matthias

___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us

[Talk-us] street name expansion thoughts

[Richard Welty]

there's been a bit of talk about running street name expansion over the 
eastern US.
i'm reasonably happy with what i've seen in the expanded Tiger 2012 
tiles, the

name expansion algorithm looks pretty good.

however, should we perhaps also run expansion over the addr:street tags at
the same time?

i'm becoming involved in the effort to get house number addressing and
routing working in mkgmap and it'd be nice if it could be presumed that
addr:street on an address and name on a street probably matched without
doing any fooling around.

richard


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] street name expansion thoughts

[Mike N]

On 11/25/2012 8:20 PM, Richard Welty wrote:

however, should we perhaps also run expansion over the addr:street tags at
the same time?


  No objection here - we can expand the addr:street tag based on its 
proximity to the actual street, and therefore the root TIGER tags that 
ensure a quality expansion.



i'm becoming involved in the effort to get house number addressing and
routing working in mkgmap and it'd be nice if it could be presumed that
addr:street on an address and name on a street probably matched without
doing any fooling around.


  One complication is hand-entered street data, which may result in an 
abbreviation in addr:street with no TIGER ancestor to trace back for 
finding the base name and type for a safe machine expansion.



___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] street name expansion thoughts

[Clifford Snow]

I've been cleaning up are area of Jackson County, NC and found roads where
the name expansion algorithm failed to expand all of the abbreviations .
For example Yellow Bird Br Road.
http://www.openstreetmap.org/?lat=35.36564&lon=-83.24253&zoom=17&layers=M(not
fixed yet)

I didn't write down the problems thinking at first it was just
an abnormality.

I think it might be worth while to look at the names in the TIGER database
for Jackson County NC to see why the names are not being expanded properly.
 I'll try to pull up a list tomorrow to see if it can help improve the
expansion algorithm.

Clifford



On Sun, Nov 25, 2012 at 5:20 PM, Richard Welty wrote:

> there's been a bit of talk about running street name expansion over the
> eastern US.
> i'm reasonably happy with what i've seen in the expanded Tiger 2012 tiles,
> the
> name expansion algorithm looks pretty good.
>
> however, should we perhaps also run expansion over the addr:street tags at
> the same time?
>
> i'm becoming involved in the effort to get house number addressing and
> routing working in mkgmap and it'd be nice if it could be presumed that
> addr:street on an address and name on a street probably matched without
> doing any fooling around.
>
> richard
>
>
> __**_
> Talk-us mailing list
> Talk-us@openstreetmap.org
> http://lists.openstreetmap.**org/listinfo/talk-us
>



-- 
Clifford

I have promised to cut down on my swearing and drinking, which I have.
 Unfortunately, this has left me dim-witted and nearly speechless. Adapted
from *The Lion* by Nelson DeMille

-or-

If you can't explain it simply, you don't understand it well enough.
 Albert Einstein
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] street name expansion thoughts

[Richard Welty]

On 11/25/12 8:31 PM, Mike N wrote:


  One complication is hand-entered street data, which may result in an 
abbreviation in addr:street with no TIGER ancestor to trace back for 
finding the base name and type for a safe machine expansion.


my normal reaction would be that an expansion run should generate a 
report on values that don't make

sense (e.g., don't match a nearby street) for manual review.

richard



___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us

[Talk-us] Alaska CPD boundaries

[Paul Norman]

I've been cleaning up and converting the Alaska admin boundaries and
relations and I've come across two questions where I could use some more
local feedback. I'm not finished yet, I still have to go back and fix some
mistakes (ugh) and de-duplicate more ways.

As no one had touched most of the boundaries since an import in 2008 I doubt
that anyone feels too strongly about them.

(a) CPD tagging

Alaska is not divided into counties[1] but into boroughs instead. These
boroughs do not cover the entire land area of the state. The remainder is
part of the unorganized borough (see
http://en.wikipedia.org/wiki/Unorganized_borough)

The census bureau divided the unorganized borough into 11 census areas.
These have no legal significance but serve to sub-divided the state into
convenient parts. In spite of this they are in many ways like counties. I've
tagged them the same as counties (admin_level=6) but I'm not convinced that
this is the best tagging.

(b) Coastline boroughs/CPDs

For a reference on terms, see
http://www.nauticalcharts.noaa.gov/csdl/images/GIS_marineboundaries.jpg

I'm not sure where the way showing the limit of the coastline boroughs
should be. Currently it is an approximated offset coastline with digitizing
artifacts. The options I see are

(1) The 12 nautical mile limit (US territorial sea claims)

(2) The 3 nautical mile limit (state submerged land limit, traditional
territorial sea claims limit)

(3) The coastline way

(4) The existing crudely drawn inaccurate imported limit.

The way for (2) does not exist and would need to be created.

Within the accuracy we're likely to have in the region there is no
difference between the mean higher high water coastline and the mean lower
low water coastline.


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] street name expansion thoughts

[Clifford Snow]

The problem in Jackson County NC is that the name field in the TIGER
 featnames table contains abbreviations. For example, Mountain is shown as
Mtn. There are 227 individual names with the Mtn abbreviation. My guess is
there are other counties with similar problems. I'm not sure how to run a
query to capture other abbreviations.

I'm not sure we ready to run a bot to expand names without first
understanding the impact it would have on roads that have been manually
fixed.

Clifford


On Sun, Nov 25, 2012 at 5:34 PM, Clifford Snow wrote:

> I've been cleaning up are area of Jackson County, NC and found roads where
> the name expansion algorithm failed to expand all of the abbreviations .
> For example Yellow Bird Br Road.
> http://www.openstreetmap.org/?lat=35.36564&lon=-83.24253&zoom=17&layers=M(not 
> fixed yet)
>
> I didn't write down the problems thinking at first it was just
> an abnormality.
>
> I think it might be worth while to look at the names in the TIGER database
> for Jackson County NC to see why the names are not being expanded properly.
>  I'll try to pull up a list tomorrow to see if it can help improve the
> expansion algorithm.
>
> Clifford
>
>
>
> On Sun, Nov 25, 2012 at 5:20 PM, Richard Welty wrote:
>
>> there's been a bit of talk about running street name expansion over the
>> eastern US.
>> i'm reasonably happy with what i've seen in the expanded Tiger 2012
>> tiles, the
>> name expansion algorithm looks pretty good.
>>
>> however, should we perhaps also run expansion over the addr:street tags at
>> the same time?
>>
>> i'm becoming involved in the effort to get house number addressing and
>> routing working in mkgmap and it'd be nice if it could be presumed that
>> addr:street on an address and name on a street probably matched without
>> doing any fooling around.
>>
>> richard
>>
>>
>> __**_
>> Talk-us mailing list
>> Talk-us@openstreetmap.org
>> http://lists.openstreetmap.**org/listinfo/talk-us
>>
>
>
>
> --
> Clifford
>
> I have promised to cut down on my swearing and drinking, which I have.
>  Unfortunately, this has left me dim-witted and nearly speechless. Adapted
> from *The Lion* by Nelson DeMille
>
> -or-
>
> If you can't explain it simply, you don't understand it well enough.
>  Albert Einstein
>
>


-- 
Clifford

I have promised to cut down on my swearing and drinking, which I have.
 Unfortunately, this has left me dim-witted and nearly speechless. Adapted
from *The Lion* by Nelson DeMille

-or-

If you can't explain it simply, you don't understand it well enough.
 Albert Einstein
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Alaska CPD boundaries

[Paul Norman]

> From: Paul Norman [mailto:penor...@mac.com]
> Subject: [Talk-us] Alaska CPD boundaries
> 
> (2) The 3 nautical mile limit (state submerged land limit, traditional
> territorial sea claims limit)

I'm sort of answering my own question, but the latest TIGER data has it at
this limit.

I'll go ahead and propose reimporting these - what's existing is too messy
to fix up piecemeal and after having reviewed it, it's all unmodified old
imported data anyways.


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us

[Talk-us] Proposed import: Alaska Boroughs/CPDs

[Paul Norman]

In Alaska the Boroughs and CPDs are the equivalent of counties. 

I recently cleaned up much of the Canada/Alaska border and in the process
looked at the counties data.

I have come to the conclusion that it is better and easier to remove the
existing counties data and reimport from TIGER 2012.

Additionally Alaska created new counties in 2007 and 2008 and these are not
reflected in the existing data.

Before I did my edits the counties were essentially untouched. Now they're
half-fixed but many remain a mess, particularly in coastal regions where
there is poor alignment. The majority of the data is in regions where the
population density is minimal and we are unlikely to get any eyes on the
ground.

There is more detail at
http://wiki.openstreetmap.org/wiki/Alaska/TIGER_Counties, but in brief the
import will be more accurate, not override any existing contributions except
mine and be better tagged.

I started a discussion about the tagging of boroughs/CPDs which are not
exactly like counties at
http://lists.openstreetmap.org/pipermail/talk-us/2012-November/009563.html
but it shouldn't be difficult to come back later and retag if required as
there are a total of 29 objects that could potentially need retagging. It
would be a lot easier to retag them post import then to try to retag the
current data.

I will have to integrate the data with the existing Canada/Alaska border and
will preserve that as it is based on the extremely accurate IBC data.


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us