Re: [Talk-us] Redacting 75, 000 street names contributed by user chdr

[Greg Morgan]

On Wed, Oct 18, 2017 at 12:52 PM, Tod Fitch  wrote:

Tod,

Thank you for your help in Arizona--mostly metro Phoenix.  I think that we
need to ask MapBox to revise the 2017 Tiger layer.  There were short ways
without names in Tiger 2017 that both the Tiger 2014  and Tiger 2015 layers
have/had.  It was a mistake for them to remove 2015.  That is why you could
not find some of the names with the 2017 layer.

He! He!  You left me some great challenges.  I think those are best consume
in small changes.  Thanks also for the overpass query.

I think I got them all. The ones that had a name on the Tiger 2017 overlay
> at least. The ones that did not have a Tiger name (looks to be mostly
> service roads) I changed to “fixme=chdr_USA_AZ_name_fixup_required”
>
>
> Here is a search for those:
>
> /*
> This query looks for nodes, ways and relations
> with the given key/value combination.
> Choose your region and hit the Run button above!
> */
> [out:xml]/*fixed by auto repair*/[timeout:25];
> // gather results
> (
>   // query part for: “name=chdr_USA_AZ_name_fixup_required”
>   node["fixme"="chdr_USA_AZ_name_fixup_required"](31.259769987394286,-116.
> 56494140625001,37.309014074275915,-108.0615234374);
>   way["fixme"="chdr_USA_AZ_name_fixup_required"](31.259769987394286,-116.
> 56494140625001,37.309014074275915,-108.0615234374);
>   relation["fixme"="chdr_USA_AZ_name_fixup_required"](31.
> 259769987394286,-116.56494140625001,37.309014074275915,-108.
> 0615234374);
> );
> // print results
> out meta;/*fixed by auto repair*/
> >;
> out meta qt;/*fixed by auto repair*/
>
>
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Allegheny County, PA: Building Footprints import

[GeoKitten]

The import is now online at http://tasks.openstreetmap.us/project/131

If you're interested, go ahead and contribute.

>  Original Message 
> Subject: [Talk-us] Allegheny County, PA: Building Footprints import
> Local Time: October 10, 2017 7:38 PM
> UTC Time: October 10, 2017 11:38 PM
> From: geokitten...@protonmail.com
> To: talk-us@openstreetmap.org 
>
> I would like to propose an import of buildings in Allegheny County from
> the county's open data. I'm contacting everyone because the import guidelines
> require all imports to be discussed within the local community. Since neither
> Pittsburgh nor Pennsylvania has much of a community where we can discuss these
> issues, I put this on the US list.
>
> The wiki page is here:
> http://wiki.openstreetmap.org/wiki/Allegheny_County_Building_Import
> In summary, I wish to import around 500,000 buildings in Allegheny County.
> The data is good quality and I've confirmed that we're allowed to use it. I
> already have a plan on how to import it: I will ask for an account on the OSM
> US Tasking Manager and put it there, where the community will be free to
> help add the buildings on chunk at a time. I am styling my import after some
> previous imports of Microsoft building data in the South (link:
> http://tasks.openstreetmap.us/project/122 ). I'm personally interested in this
> project so I plan on contributing to the actual import.
>
> Is this import a good idea? If you have any concerns, suggestions,
> or improvements, I am eager to hear them. I'm a mapper local to this area but
> this is the first import I've tried to conduct.___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Redacting 75, 000 street names contributed by user chdr

[Tod Fitch]

I think I got them all. The ones that had a name on the Tiger 2017 overlay at 
least. The ones that did not have a Tiger name (looks to be mostly service 
roads) I changed to “fixme=chdr_USA_AZ_name_fixup_required”


Here is a search for those:

/*
This query looks for nodes, ways and relations
with the given key/value combination.
Choose your region and hit the Run button above!
*/
[out:xml]/*fixed by auto repair*/[timeout:25];
// gather results
(
  // query part for: “name=chdr_USA_AZ_name_fixup_required”
  
node["fixme"="chdr_USA_AZ_name_fixup_required"](31.259769987394286,-116.56494140625001,37.309014074275915,-108.0615234374);
  
way["fixme"="chdr_USA_AZ_name_fixup_required"](31.259769987394286,-116.56494140625001,37.309014074275915,-108.0615234374);
  
relation["fixme"="chdr_USA_AZ_name_fixup_required"](31.259769987394286,-116.56494140625001,37.309014074275915,-108.0615234374);
);
// print results
out meta;/*fixed by auto repair*/
>;
out meta qt;/*fixed by auto repair*/



> On Oct 18, 2017, at 12:28 PM, Greg Morgan  wrote:
> 
> 
> 
> On Oct 10, 2017 8:13 AM, "Tod Fitch"  wrote:
> I have started trying to clean up some of the redactions in Arizona, starting 
> with the town of Maricopa. As Ian pointed out, these were “pre-redacted” and 
> rather than deleting the road name, the name was changed to 
> chdr_USA_AZ_name_fixup_required.  
> 
> I did not see that the redaction was finished. I will work on any of the 
> remaining names. The chdr changes were focused on various new subdivisions at 
> time of the changes.
> 
> 
> The problem is there are some roads that do not have names on the Tiger 2017 
> overlay. At this time I have left those untouched.
> 
> My worry is that there does not seem to be a lot of local mappers working in 
> the area so it may be a while before the remaining 
> name=chdr_USA_AZ_name_fixup_required roads get fixed. In the meantime data 
> consumers will be giving confusing information to end users. I can see (or 
> mentally hear) lots of routing guidance with “turn right at churdr usa az 
> name fixup required”.
> 
> I am inclined to simply delete the name if Tiger 2017 has no name. That will 
> do two things: 1. Make the map and routing less wrong. And 2. Allow the 
> normal QA tools we have indicate an issue (residential road with no name).
> 
> Thoughts?
> 
> Tod
> 
> > On Oct 9, 2017, at 12:21 PM, Ian McEwen  
> > wrote:
> >
> > AZ has none because of https://www.openstreetmap.org/changeset/51502902
> > rather than an actual absence of things to fix from this (that changeset
> > essentially pre-redacted the names, so they no longor appear in
> > Frederick's list of redactions). I've fixed those I could find in the
> > Tucson & Pima County areas, but there's still lots to be gone over in
> > AZ.
> >
> > Just mentioning this so if anyone's doing anything like tasking manager
> > work, they'll know they need to special-case AZ.
> >
> > On Mon, Oct 09, 2017 at 09:21:59AM -0700, Tod Fitch wrote:
> >> FYI,
> >>
> >> No redactions in Oregon, Arizona or Utah. I’ve added Tiger 2017 names to 
> >> the ways in the list located in California and Nevada. Later today I’ll do 
> >> New Mexico and Colorado.
> >>
> >> I’ve got to restrain myself from correcting geometry, adding surface, 
> >> lanes, turn lanes, etc. while I do this. :)
> >>
> >> Tod
> >>
> >>> On Oct 9, 2017, at 9:01 AM, Tod Fitch  wrote:
> >>>
> >>> Looks like there are about 6600 redactions in the US. Did a quick sort of 
> >>> the list by country and state and it looks like Texas has the most (by 
> >>> eyeing the list rather than counting). Most states have a very manageable 
> >>> number. There were about 42 in California and I was able to apply Tiger 
> >>> 2017 names to 38 of those. Most states will be that easy.
> >>>
> >>> All I did was take the list, extract out the ones for California, do a 
> >>> edit to add "https://www.openstreetmap.org/way/“ in front of the way ID 
> >>> and then do a “Load Location” in JOSM for each. Looked at them with the 
> >>> Tiger 2017 overlay imagery to see if there was a name I could apply. Took 
> >>> maybe 1/2 hour to do all of California.
> >>>
> >>> Not sure this is a big enough job to bother putting up a OSM task for it. 
> >>> Just grab the way IDs in your state, and maybe in your neighboring 
> >>> state(s), and do it.
> >>>
> >>> Texas and maybe New York will require more work, so maybe those could be 
> >>> broken into tasks. But for the rest I think it would pretty much be “one 
> >>> state is one task”.
> >>>
>  On Oct 8, 2017, at 3:28 AM, Nick Hocking  wrote:
> 
>  Can someone put up an OSM task so that we can replace these names , from 
>  Tiger 2017?
>  ___
>  Talk-us mailing list
>  Talk-us@openstreetmap.org
>  https://lists.openstreetmap.org/listinfo/talk-us
> >>>
> >>>
> >>> ___
> >>> Talk-us mailing list
> >>> Talk-us@openstreetma

Re: [Talk-us] Redacting 75, 000 street names contributed by user chdr

[Greg Morgan]

On Oct 10, 2017 8:13 AM, "Tod Fitch"  wrote:

I have started trying to clean up some of the redactions in Arizona,
starting with the town of Maricopa. As Ian pointed out, these were
“pre-redacted” and rather than deleting the road name, the name was changed
to chdr_USA_AZ_name_fixup_required.


I did not see that the redaction was finished. I will work on any of the
remaining names. The chdr changes were focused on various new subdivisions
at time of the changes.


The problem is there are some roads that do not have names on the Tiger
2017 overlay. At this time I have left those untouched.

My worry is that there does not seem to be a lot of local mappers working
in the area so it may be a while before the remaining
name=chdr_USA_AZ_name_fixup_required roads get fixed. In the meantime data
consumers will be giving confusing information to end users. I can see (or
mentally hear) lots of routing guidance with “turn right at churdr usa az
name fixup required”.

I am inclined to simply delete the name if Tiger 2017 has no name. That
will do two things: 1. Make the map and routing less wrong. And 2. Allow
the normal QA tools we have indicate an issue (residential road with no
name).

Thoughts?

Tod

> On Oct 9, 2017, at 12:21 PM, Ian McEwen 
wrote:
>
> AZ has none because of https://www.openstreetmap.org/changeset/51502902
> rather than an actual absence of things to fix from this (that changeset
> essentially pre-redacted the names, so they no longor appear in
> Frederick's list of redactions). I've fixed those I could find in the
> Tucson & Pima County areas, but there's still lots to be gone over in
> AZ.
>
> Just mentioning this so if anyone's doing anything like tasking manager
> work, they'll know they need to special-case AZ.
>
> On Mon, Oct 09, 2017 at 09:21:59AM -0700, Tod Fitch wrote:
>> FYI,
>>
>> No redactions in Oregon, Arizona or Utah. I’ve added Tiger 2017 names to
the ways in the list located in California and Nevada. Later today I’ll do
New Mexico and Colorado.
>>
>> I’ve got to restrain myself from correcting geometry, adding surface,
lanes, turn lanes, etc. while I do this. :)
>>
>> Tod
>>
>>> On Oct 9, 2017, at 9:01 AM, Tod Fitch  wrote:
>>>
>>> Looks like there are about 6600 redactions in the US. Did a quick sort
of the list by country and state and it looks like Texas has the most (by
eyeing the list rather than counting). Most states have a very manageable
number. There were about 42 in California and I was able to apply Tiger
2017 names to 38 of those. Most states will be that easy.
>>>
>>> All I did was take the list, extract out the ones for California, do a
edit to add "https://www.openstreetmap.org/way/“ in front of the way ID and
then do a “Load Location” in JOSM for each. Looked at them with the Tiger
2017 overlay imagery to see if there was a name I could apply. Took maybe
1/2 hour to do all of California.
>>>
>>> Not sure this is a big enough job to bother putting up a OSM task for
it. Just grab the way IDs in your state, and maybe in your neighboring
state(s), and do it.
>>>
>>> Texas and maybe New York will require more work, so maybe those could
be broken into tasks. But for the rest I think it would pretty much be “one
state is one task”.
>>>
 On Oct 8, 2017, at 3:28 AM, Nick Hocking 
wrote:

 Can someone put up an OSM task so that we can replace these names ,
from Tiger 2017?
 ___
 Talk-us mailing list
 Talk-us@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/talk-us
>>>
>>>
>>> ___
>>> Talk-us mailing list
>>> Talk-us@openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/talk-us
>>
>>
>> ___
>> Talk-us mailing list
>> Talk-us@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-us
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us


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

Re: [Talk-us] hydrology Alaska

[Christoph Hormann]

On Wednesday 18 October 2017, Andy Townsend wrote:
>
> https://www.openstreetmap.org/#map=17/69.94271/-152.49898
>
> isn't the result of simplification, though, is it?  You can see the
> pixels...

Like others here i have no practical experience with scanaerial but it 
seems the vectorization algorithm used is very non-sophisticated 
leading to the geometries shown.  Tracing higher resolution images at 
higher resolution and running Douglas-Peucker over it will likely not 
produce good results either (you will get the typical jagged corners).

Those cases where good results were achieved with scanaerial seem to be 
using relatively low resolution images processed at a much higher 
resolution - like here:

http://www.openstreetmap.org/#map=12/68.8084/160.9188

-- 
Christoph Hormann
http://www.imagico.de/

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

[Talk-us] Mapping turn lanes in dual carriageway intersections

[Horea Meleg]

Hello all,
During our editing work on lanes in Detroit and Phoenix we found some 
interesting situations, usually on intersections with dual carriage way, where 
missing turn:lanes tagging can affect the lane connectivity.
So, in this situation: 42.329625, -83.16889
[cid:image005.jpg@01D3481E.54C260C0]
There is no turn:lane info on the middle way, so there will be no connectivity 
between Way 1 and Way 4 and also Way 3 and Way 2.
Our Map Analyst team mapped lane info based on Mapbox 
initiative,
 in brief we mapped only where the marking is present on the road. So, on 
middle way from picture above, we didn't add turn:lanes, therefor will be no 
connectivity to left.
We thought about a solution to resolve this issue, and we think that best 
option is to add there turn:lanes:both_ways=left on middle way like this:
[cid:image006.jpg@01D3481E.54C260C0]
So, in future we will map this cases like this.
We'd love any input and advice from you guys. If you have any questions or 
comments, please let me/us know.
You can add comment and share with us your opinion here: 
https://github.com/TelenavMapping/mapping-projects/issues/36. Also, you can 
find more details on that page.


Thank you,
Horea Meleg,
Telenav

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

Re: [Talk-us] hydrology Alaska

[Andy Townsend]

On 18/10/2017 05:49, ANT Berezhnyi wrote:

+10 to what AlaskaDave said



Simplification creates such a crap, as you led me to an example


https://www.openstreetmap.org/#map=17/69.94271/-152.49898

isn't the result of simplification, though, is it?  You can see the 
pixels...


I'd suggest that, before tracing any more, you revisit the lakes that 
you have added so far (like this one) and make sure that they match the 
best imagery.


Best Regards,

Andy


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