[Talk-us] Whole-US Garmin Map update - 2014-08-13
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@ list, others can benefit. Downloads: http://daveh.dev.openstreetmap.org/garmin/Lambertus/2014-08-13 Map to visualize what each file contains: http://daveh.dev.openstreetmap.org/garmin/Lambertus/2014-08-13/kml/kml.html FAQ Why did you do this? I wrote scripts to joined them myself to lessen the impact of doing a large join on Lambertus's server. I've also cut them in large longitude swaths that should fit conveniently on removable media. http://daveh.dev.openstreetmap.org/garmin/Lambertus/2014-08-13 Can or should I seed the torrents? Yes!! If you use the .torrent files, please seed. That web server is in the UK, and it helps to have some peers on this side of the Atlantic. Why is my map missing small rectangular areas? There have been some missing tiles from Lambertus's map (the red rectangles), I don't see any at the moment, so you may want to update if you had issues with the last set. Why can I not copy the large files to my new SD card? If you buy a new card (especially SDHC), some are FAT16 from the factory. I had to reformat it to let me create a 2GB file. Does your map cover Mexico/Canada? Yes!! I have, for the purposes of this map, annexed Ontario in to the USA. Some areas of North America that are close to the US also just happen to get pulled in to these maps. This might not happen forever, and if you would like your non-US area to get included, let me know. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
Sounds like you fixed this quickly. Would you mind explaining the steps in detail you took to achieve this? Thanks On Thu, Aug 14, 2014 at 9:04 PM, Nick Hocking nick.hock...@gmail.com wrote: stevea wrote, though there are problems in the west, like Las Vegas Ok - I think I've fixed all of these in Las Vegas (there were a few thousand). It's amazing how simple they are to find using the overpass api (and overpass turbo). Nick ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Fwd: Western state vacation - counties and street names
Midwestern area mappers take note: My friend Mike (OSM: mdroads), owner of mdroads.com, is out west and has been dropping lots of notes out there. -- Forwarded message -- From: Mike Date: Thu, Aug 14, 2014 at 10:50 AM Subject: Western state vacation - counties and street names To: Elliott Plack Elliott, I have a whole string of OSM notes posted across South Dakota, Wyoming, Kansas and Nebraska, for street name variances with Tiger and also confirmation of county/secondary numbering. Every county has its own way of signing things and handling their street grid system, changed since the last Tiger for E911 purposes. At each county line, going the NS street will have two names, one for each county's grid usually the 1st in the county to the east and also the 31st to the west. Most counties are fixed grid size under the PLSS. Most EW roads are lettered; the main highway was often P Road since that was the 16th in the middle of the county. Other counties reverse this whole number/letter business. Other counties use all letters or numbers, and differ by road type for direction. I can't reliably do GPS tracks, nor paper notes, so I'm tracing in JOSM from imagery. Should be back in town for next week. Mike -- Elliott Plack http://about.me/elliottp ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
Keith wrote
Sounds like you fixed this quickly. Would you mind explaining the steps in
detail you took to achieve this? Thanks
I decided to use a set of common abbreviations of
Ct
St
Ave
Dr
Ln
Pl
Pkwy
Cl
Cir
Rd
In Australia I'd propably add Cct (Circuit) to the list.
Then for the first Ct which is Court I went to overpass-turbo.eu and
ran the query of
query type=way
has-kv k=name regv= [Cc][Tt]$/
bbox-query {{bbox}}/!--this is auto-completed with the
current map view coordinates.--
/query
union
item/
recurse type=down/
/union
print/
This shows all the ways whose name ends in a space followed by ct (in any
capitalization).
With this map in one window and JOSM in another window, I then located the
first Ct in the Josm window and edited it manually to be Court
Often there was a *nest* of abbreviations (St Ln Pl etc...) in the same
neighbourhood, so having fixed one way I would hav a quick look around that
area. and fix any other abbreviations I found. Then on to the next Ct.
I generally worked my way west to east and north to south.
Once I had cleared up all the Ct (rerunning the operpass query verifies
this) I then started on the St (Streets). About30 or 40 hours later Las
Vegas was fixed.
What I will now do I export to CSV all the Las Vegas Road names, then grep
out all the good ones (I.E Court, Street, Road) and see what's left.
Any typos I've made while editing (E.G Ctourt) and any ways without
suffixes will be left and I can investigate if they can be improved or not
(from TIGER 2013).
You'll notice that no bots were run in the making of these fixes. This is
for two reasons. Firstly I'm not a fan of bots since they make assumptions
which may not always be true. Secondly, manual editing in JOSM with the
TIGER 2013 and OSM data showing, means that I found quite a few missing
road names in OSM. Also I found quite a few missing roads and If both TIGER
and Bing imagery agreed about the road then I added in the road.
I also found a few typos along the way which I could fix as well.
Ie always found that desk checking against another source (like TIGER) and
entire city results in massive improvements. Any city I've mapped I always
desk check against another source and inevitably find lots of typos to fix.
Nick
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
Nick,
I have been following the discussion about road name abbreviations and wanted
to chime in.
I agree with you that bots miss stuff AND goof up in silly ways. A CLASSIC
example of a bot mistake is “Street Joseph Street”. This example has been fixed
by a participant in a MapRoulette name fixing challenge. But as you can see
below, a bot updated the street name from “St Joseph St” to “Street Joseph
Street”. Example below:
http://www.openstreetmap.org/way/13597392/history
For sure fixing names automatically can save time. But you can only correct so
much with the implemented bot logic and sometimes make mistakes (what you’re
analyzing might not be what you’re expecting). As my co-worker has said,
humans are the best pattern, spelling error catchers.
It’s pleasing to know you’re taking the time to expand abbreviations and
correct other data errors along the way. Keep it up!
Best,
Kristen
---
Kristen Kam
OSM Profile -- http://www.openstreetmap.org/user/KristenK
From: Nick Hocking [mailto:nick.hock...@gmail.com]
Sent: Friday, August 15, 2014 2:14 PM
To: talk-us@openstreetmap.org
Subject: Re: [Talk-us] Road abbreviations
Keith wrote
Sounds like you fixed this quickly. Would you mind explaining the steps in
detail you took to achieve this? Thanks
I decided to use a set of common abbreviations of
Ct
St
Ave
Dr
Ln
Pl
Pkwy
Cl
Cir
Rd
In Australia I'd propably add Cct (Circuit) to the list.
Then for the first Ct which is Court I went to
overpass-turbo.euhttp://overpass-turbo.eu and ran the query of
query type=way
has-kv k=name regv= [Cc][Tt]$/
bbox-query {{bbox}}/!--this is auto-completed with the
current map view coordinates.--
/query
union
item/
recurse type=down/
/union
print/
This shows all the ways whose name ends in a space followed by ct (in any
capitalization).
With this map in one window and JOSM in another window, I then located the
first Ct in the Josm window and edited it manually to be Court
Often there was a *nest* of abbreviations (St Ln Pl etc...) in the same
neighbourhood, so having fixed one way I would hav a quick look around that
area. and fix any other abbreviations I found. Then on to the next Ct. I
generally worked my way west to east and north to south.
Once I had cleared up all the Ct (rerunning the operpass query verifies this)
I then started on the St (Streets). About30 or 40 hours later Las Vegas was
fixed.
What I will now do I export to CSV all the Las Vegas Road names, then grep out
all the good ones (I.E Court, Street, Road) and see what's left.
Any typos I've made while editing (E.G Ctourt) and any ways without suffixes
will be left and I can investigate if they can be improved or not (from TIGER
2013).
You'll notice that no bots were run in the making of these fixes. This is for
two reasons. Firstly I'm not a fan of bots since they make assumptions which
may not always be true. Secondly, manual editing in JOSM with the TIGER 2013
and OSM data showing, means that I found quite a few missing road names in OSM.
Also I found quite a few missing roads and If both TIGER and Bing imagery
agreed about the road then I added in the road.
I also found a few typos along the way which I could fix as well.
Ie always found that desk checking against another source (like TIGER) and
entire city results in massive improvements. Any city I've mapped I always
desk check against another source and inevitably find lots of typos to fix.
Nick
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
