Re: [Talk-us] Whole-US Garmin Map update - NOW working for me

2012-10-02 Thread Alan Millar

On 9/29/2012 2:18 PM, Alan wrote:

Anyone else have problems with recent versions of these no longer working for 
them?


Um, sorry, false alarm.  After completely clearing out my SD card, and 
making sure there were no left over recycle bin or hidden files, I tried 
it all again and it worked.  Looks like just stupid user error on my 
part :-(


(I do wonder if there was a more subtle explanation in the VFAT 
filesystem on the sd card, where the Nuvi may only read the DOS 8.3 
short filename.  I wonder if there is a scenario where one might copy a 
file to the card and then rename it, ending with a long name of 
gmapsupp.img and a short name of GMAPSU~1.IMG or something.  Always 
looking for someone to blame other than me :-)


Thanks for everyone's advice anyways!

- Alan


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


Re: [Talk-us] railway crossing id

2012-10-02 Thread Dale Puch
The level crossings sound pretty straight forward.  The exception being the
single ID applying to all crossings on private property.  Many of those may
still only be a single crossing though.

Grade separated sounds like it requires a judgment call.  Just place a node
with only the ref# where the ways cross?  Make it a crossing (I don't like
this)  Tag the overpass or tunnel (or this)?  As those are not crossings in
any sense that we care about, I say just a ref number in a node only on the
train track way and forgo any railway tag.  The main use for us might be to
make sure there is an overpass or tunnel there.

Dale

On Tue, Oct 2, 2012 at 4:55 PM, Frederik Ramm  wrote:

> Hi,
>
>
> On 02.10.2012 22:29, Charlie Smothers wrote:
>
>> How do folks think
>> that this should be tagged? Just use a railway=level_crossing, ref= on a
>> node near the crossing?
>>
>
> railway=level_crossing would usually be reserved to tag the crossing
> itself, not to annotate it from a distance.
>
>
>  Should it have a special tag so that it is clear
>> that it is in fact a USDOT ID number?
>>
>
> People sometimes use tags like "namespace:ref" to indicate whose number it
> is, so that would make "usdot:ref=...". (A "fdot:ref" seems to be in common
> use on Florida highways.)
>
>
>  Tag the node at the intersection
>> of the highway and the railway?
>>
>
> Yes - of course if it really is a level crossing and not grade separated.
> Grade separated is more difficult because there will not necessarily be a
> node at the precise intersection.
>
> Bye
> Frederik
>
> --
> Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09" E008°23'33"
>
> __**_
> Talk-us mailing list
> Talk-us@openstreetmap.org
> http://lists.openstreetmap.**org/listinfo/talk-us
>



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


Re: [Talk-us] railway crossing id

2012-10-02 Thread Frederik Ramm

Hi,

On 02.10.2012 22:29, Charlie Smothers wrote:

How do folks think
that this should be tagged? Just use a railway=level_crossing, ref= on a
node near the crossing?


railway=level_crossing would usually be reserved to tag the crossing 
itself, not to annotate it from a distance.



Should it have a special tag so that it is clear
that it is in fact a USDOT ID number?


People sometimes use tags like "namespace:ref" to indicate whose number 
it is, so that would make "usdot:ref=...". (A "fdot:ref" seems to be in 
common use on Florida highways.)



Tag the node at the intersection
of the highway and the railway?


Yes - of course if it really is a level crossing and not grade 
separated. Grade separated is more difficult because there will not 
necessarily be a node at the precise intersection.


Bye
Frederik

--
Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09" E008°23'33"

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


[Talk-us] railway crossing id

2012-10-02 Thread Charlie Smothers
I posted this to Talk:Railways:  
http://wiki.openstreetmap.org/wiki/Talk:Railways
I'm interested in finding out what folks think about how to tag these.
 
In the USA, the US Department of Transportation has adopted a highway 
railcrossing inventory program. Unique numbers are assigned to each crossing. 
They include grade separated, level crossings, and pedestrian crossings. Here 
is a link to the their website. US DOT National Highway-Rail Crossing Inventory 
Program. I think that it would be valuable to include nodes with this unique ID 
on or near crossings. There are lots of bits of information in their database 
about each crossing, including longitude/latitude, signal type. How do folks 
think that this should be tagged? Just use a railway=level_crossing, ref= on a 
node near the crossing? Should it have a special tag so that it is clear that 
it is in fact a USDOT ID number? Tag the node at the intersection of the 
highway and the railway? What if there are several tracks or if it is a divided 
highway; tag each intersection? --Charles_Smothers 18:15, 2 October 2012 (BST) ___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Remap-a-tron level 2 complete! Suggestions for level 3?

2012-10-02 Thread Alex Barth

As the Remap-a-Tron is expanding its scope beyond remapping, I'll submit "Map 
Roulette" as a new name. In case you're looking for a new name, that is :)

On Oct 1, 2012, at 1:52 AM, Martijn van Exel  wrote:

> Also a good one. I will make a list of all the suggestions some time
> this week. There's some low hanging fruit here, and some more complex
> ideas. I don't know when I will have time to implement the next level,
> I hope to have something up before Portland. Any help is appreciated!
> 
> Martijn
> 
> On Sun, Sep 30, 2012 at 11:46 PM, Alexander Jones  wrote:
>> Alan Millar wrote:
>> 
>>> Another suggestion: motorways and trunks without lanes=number tags
>>> 
>>> - Alan
>> 
>> I'd help out with that.
>> 
>> Alexander
>> 
>> 
>> ___
>> Talk-us mailing list
>> Talk-us@openstreetmap.org
>> http://lists.openstreetmap.org/listinfo/talk-us
> 
> 
> 
> -- 
> martijn van exel
> http://oegeo.wordpress.com
> 
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-us

Alex Barth
http://twitter.com/lxbarth
tel (+1) 202 250 3633





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


Re: [Talk-us] Remap-a-tron level 2 complete! Suggestions for level 3?

2012-10-02 Thread Mike N

On 10/2/2012 11:15 AM, the Old Topo Depot wrote:

Regarding TIGER county connectivity; since the last OSMI update GA, AL
and northern MS have had county boundary issues cleaned.

What's left is KY, LA, AR, southeastern TX, and portions of VA, TN, and
KS.  States such as ME and southeastern MA also have scattered
boundaries that have not been addressed, but the first four states
listed here now comprise the bulk of the outstanding county boundary issues.


 Add SC to the list - it had been previously fixed, but many counties 
have been marooned, courtesy of the redaction bot.  I fixed up a few 
around me, but that's as far as I got.



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


Re: [Talk-us] Remap-a-tron level 2 complete! Suggestions for level 3?

2012-10-02 Thread the Old Topo Depot
Regarding TIGER county connectivity; since the last OSMI update GA, AL and
northern MS have had county boundary issues cleaned.

What's left is KY, LA, AR, southeastern TX, and portions of VA, TN, and KS.
 States such as ME and southeastern MA also have scattered boundaries that
have not been addressed, but the first four states listed here now comprise
the bulk of the outstanding county boundary issues.

Best,

On Mon, Oct 1, 2012 at 8:04 PM, Dale Puch  wrote:

> Well as a start is I put a section into the QA tools page
> http://wiki.openstreetmap.org/wiki/Quality_assurance#Remap-a-Tron
> Several projects there that ideas/code/SQL might be borrowed from.
>
> Well your obviously familiar with this :) did the issues found by this
> query all get resolved?
> http://oegeo.wordpress.com/2012/04/07/detecting-highway-trouble-in-openstreetmap/
>
> Also some SQL from a bot http://wiki.openstreetmap.org/wiki/OSM_Fixerthat 
> might be of use in building other queries.
>
> Dale
>
>
> On Mon, Oct 1, 2012 at 4:04 PM, Martijn van Exel  wrote:
>
>> The setup involves designing the SQL queries and the initial database,
>> and tweaking the front end for different types of problems. Up until
>> now, we have been able to get away with just displaying the
>> non-remapped way as a vector element on the leaflet map, but for
>> example forfolding ways that may not be enough, as the folds may be
>> really tiny and not visible without also displaying the offending
>> piece of the way in a kind of magnifying glass (or in the popup
>> balloon). That would mean significant front-end tweaking as well as
>> partial re-engineering of the webservices that transmit the geojson.
>> (these are really really simple things[1] so that should not be hard
>> to do for someone with a little python / json experience). For the
>> connectivity errors, which are as high on my list as anything to fix,
>> we'd need to transmit both ways involved and find a way to display the
>> issue effectively. Maybe just the two ways in different colors. Nice
>> extra would be if the popup would say 'hey, there are x more
>> connectivity errors within a mile, do you just want to go ahead and
>> edit all of them?'
>>
>> A wiki page is an excellent idea, who has time to set that up?
>>
>> [1] https://github.com/mvexel/remapatron/blob/master/service/get.py
>>
>> On Mon, Oct 1, 2012 at 1:59 AM, Dale Puch  wrote:
>> > For setting up the runs, is it all SQL queries or are there other items
>> > involved?  Perhaps start a wiki page for useful queries to identify
>> problems
>> > (for this or other projects), or even just collaboration on plain text
>> > criteria ideas for future runs and build what is needed from there.
>> >
>> > Dale
>> >
>> >
>> > On Mon, Oct 1, 2012 at 1:52 AM, Martijn van Exel  wrote:
>> >>
>> >> Also a good one. I will make a list of all the suggestions some time
>> >> this week. There's some low hanging fruit here, and some more complex
>> >> ideas. I don't know when I will have time to implement the next level,
>> >> I hope to have something up before Portland. Any help is appreciated!
>> >>
>> >> Martijn
>> >>
>> >> On Sun, Sep 30, 2012 at 11:46 PM, Alexander Jones > >
>> >> wrote:
>> >> > Alan Millar wrote:
>> >> >
>> >> >> Another suggestion: motorways and trunks without lanes=number tags
>> >> >>
>> >> >> - Alan
>> >> >
>> >> > I'd help out with that.
>> >> >
>> >> > Alexander
>> >> >
>> >> >
>> >> > ___
>> >> > Talk-us mailing list
>> >> > Talk-us@openstreetmap.org
>> >> > http://lists.openstreetmap.org/listinfo/talk-us
>> >>
>> >>
>> >>
>> >> --
>> >> martijn van exel
>> >> http://oegeo.wordpress.com
>> >>
>> >> ___
>> >> Talk-us mailing list
>> >> Talk-us@openstreetmap.org
>> >> http://lists.openstreetmap.org/listinfo/talk-us
>> >
>> >
>> >
>> >
>> > --
>> > Dale Puch
>>
>>
>>
>> --
>> martijn van exel
>> http://oegeo.wordpress.com
>>
>
>
>
> --
> Dale Puch
>
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-us
>
>


-- 
John Novak
585-OLD-TOPOS (585-653-8676)
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us