[Talk-us] Whole-US Garmin Map update - 2014-07-07
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-07-07 Map to visualize what each file contains: http://daveh.dev.openstreetmap.org/garmin/Lambertus/2014-07-07/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-07-07 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
[Talk-us] Beach routing
OSM US: I've been using some routing engines to map fitness routes (e.g. Strava) that use OSM data. Along our US coasts, there are beaches. The beaches I'm familiar with are popular with walkers and joggers to go up and down the shore, since access is generally open to anyone along the water's edge. I'm considering adding a `highway=path` along the beach to facilitate this. I'd add the connections to the walking paths between parking lots and the beach as well. For uninterrupted strips of sandy beach, would a path be appropriate to indicate walkability? How the map looks now in iD: http://i.imgur.com/2EQ06BR.jpg What I'd propose to do (note the connections): http://i.imgur.com/i8dj6lQ.jpg Area of the examples: http://www.openstreetmap.org/#map=18/38.45143/-75.04957 Thanks, -- Elliott Plack http://about.me/elliottp ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] NJ Orthoimagery
Ian,
I can put you in contact with the people in charge of the map servers at
the USGS. There has been some turnover in the position recently, so things
have been a bit mixed up. In the meantime, The National Map uses the
following link:
http://basemap.nationalmap.gov/arcgis/rest/services/USGSImageryOnly/MapServer
Bryan,
Thanks for this NJ data, it may come in handy!
--
Jim
On Tue, Jul 8, 2014 at 2:26 PM, Bryan Housel br...@7thposition.com wrote:
Hey Ian that’s cool, I didn’t know this service was available.
Would you consider proxying the New Jersey high res orthos too from
2012-2013?
More info:
https://njgin.state.nj.us/NJ_NJGINExplorer/jviewer.jsp?pg=2012_OrthoImagery
Metadata for this layer is here:
https://njgin.state.nj.us/NJ_NJGINExplorer/ShowMetadata.jsp?docId={DF49386A-73AC-4A1A-B6DC-13B769E176A4}
(their page indicates that there are no constraints on access or use,
though a source acknowledgment is appreciated)
Their WMS server is here:
http://njwebmap.state.nj.us/njimagery?REQUEST=GetCapabilitiesSERVICE=WMSVERSION=1.1.1
On Jul 7, 2014, at 2:54 PM, Ian Dees ian.d...@gmail.com wrote:
Note that the OSM US server tiles and caches the USGS NAIP and High Res
Orthos and more information can be found here:
http://wiki.openstreetmap.org/wiki/Foundation/Local_Chapters/United_States/Servers/Imagery
...but the upstream USGS server that used to host this imagery seems to be
broken (it's throwing 500's). I'm working on finding someone to talk to
about that, but until then we'll have to find something else.
On Mon, Jul 7, 2014 at 1:34 PM, Bryan Housel br...@7thposition.com
wrote:
The project for the common imagery sources is here:
https://github.com/osmlab/editor-imagery-index
You could enter an issue there to include this source so that it will be
available in the various OSM editors. Before including it in the index,
they will want to ensure that the source is properly licensed and has a
bounding polygon around where the imagery is valid.
On Jul 6, 2014, at 9:28 AM, Saikrishna Arcot saiarcot...@gmail.com
wrote:
Hi all,
I noticed that there is a wiki page on the USGS High Resolution
Orthoimagery
https://wiki.openstreetmap.org/wiki/USGS_High_Resolution_Orthoimagery,
but that the link is outdated. The new resource to use is likely one of
these http://isse.cr.usgs.gov/ArcGIS/rest/services/Orthoimagery
folders. I've looked at the 1-foot imagery, and this seems to be sharper or
equal quality than the Bing imagery in at least two areas. In addition,
according to this http://cumulus.cr.usgs.gov/listofortho.php page,
only Canada and the border data is marked as View only; all other
counties are public domain.
Is there any reason this imagery can't be used in OSM, and perhaps even
be added as one of the pre-existing imagery sources in JOSM?
--
Saikrishna Arcot
___
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] Seattle is Celebrating OpenStreetMap's 10th Anniversary
OpenStreetMap Seattle invites you to the Tenth Anniversary of OpenStreetMap Celebration, August 9th at Tableau Software in Seattle's Fremont neighborhood. Join us to help celebrate OpenStreetMap's Birthday Event. Signup for the event at http://www.meetup.com/OpenStreetMap-Seattle/events/186048572/ OpenStreetMap Seattle invites you to submit a presentation proposal for a presentation, a panel discussion or a session of lightning talks for the event. We are seeking presentations on mapping and creating maps for mappers of all experience levels. Below is a suggested list of potential topics participants would like to see. All submissions are welcome. Proposals are due by July 25th, 2014. POI - especially unique features roads relationships turn restrictions coastlines highways, .i.e I5 bus data multipolygons addressing boundaries traffic circles Using drones to map Georeferencing images from aerial imagery Quality tools Submit your proposal to cliff...@snowandsnow.us and include a title, short description, and time required. We are looking for additional sponsors to help offset the cost of the event, including food and drinks for the participants. Contact me at cliff...@snowandsnow.us if interested. Clifford Snow -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] NJ Orthoimagery
Good Afternoon,
I’ve been passively following this thread, as well as the thread for “USGS
Orthoimagery”.
http://gis.apfo.usda.gov/arcgis/rest/services/NAIP
I’ve been using the USDA NAIP imagery services for nearly a year now with no
problems. But today, I’m getting errors when trying to use their WMS in JOSM. I
should also add that the www.usda.gov site is down.
Just passing observations along.
Best,
Kristen
---
Kristen Kam
OSM Profile -- http://www.openstreetmap.org/user/KristenK
From: Jim McAndrew [mailto:j...@loc8.us]
Sent: Wednesday, July 09, 2014 1:34 PM
To: Bryan Housel
Cc: Ian Dees; OSM US Talk
Subject: Re: [Talk-us] NJ Orthoimagery
Ian,
I can put you in contact with the people in charge of the map servers at the
USGS. There has been some turnover in the position recently, so things have
been a bit mixed up. In the meantime, The National Map uses the following
link:
http://basemap.nationalmap.gov/arcgis/rest/services/USGSImageryOnly/MapServer
Bryan,
Thanks for this NJ data, it may come in handy!
--
Jim
On Tue, Jul 8, 2014 at 2:26 PM, Bryan Housel
br...@7thposition.commailto:br...@7thposition.com wrote:
Hey Ian that’s cool, I didn’t know this service was available.
Would you consider proxying the New Jersey high res orthos too from 2012-2013?
More info:
https://njgin.state.nj.us/NJ_NJGINExplorer/jviewer.jsp?pg=2012_OrthoImagery
Metadata for this layer is here:
https://njgin.state.nj.us/NJ_NJGINExplorer/ShowMetadata.jsp?docId={DF49386A-73AC-4A1A-B6DC-13B769E176A4}https://njgin.state.nj.us/NJ_NJGINExplorer/ShowMetadata.jsp?docId=%7BDF49386A-73AC-4A1A-B6DC-13B769E176A4%7D
(their page indicates that there are no constraints on access or use, though a
source acknowledgment is appreciated)
Their WMS server is here:
http://njwebmap.state.nj.us/njimagery?REQUEST=GetCapabilitiesSERVICE=WMSVERSION=1.1.1
On Jul 7, 2014, at 2:54 PM, Ian Dees
ian.d...@gmail.commailto:ian.d...@gmail.com wrote:
Note that the OSM US server tiles and caches the USGS NAIP and High Res Orthos
and more information can be found here:
http://wiki.openstreetmap.org/wiki/Foundation/Local_Chapters/United_States/Servers/Imagery
...but the upstream USGS server that used to host this imagery seems to be
broken (it's throwing 500's). I'm working on finding someone to talk to about
that, but until then we'll have to find something else.
On Mon, Jul 7, 2014 at 1:34 PM, Bryan Housel
br...@7thposition.commailto:br...@7thposition.com wrote:
The project for the common imagery sources is here:
https://github.com/osmlab/editor-imagery-index
You could enter an issue there to include this source so that it will be
available in the various OSM editors. Before including it in the index, they
will want to ensure that the source is properly licensed and has a bounding
polygon around where the imagery is valid.
On Jul 6, 2014, at 9:28 AM, Saikrishna Arcot
saiarcot...@gmail.commailto:saiarcot...@gmail.com wrote:
Hi all,
I noticed that there is a wiki page on the USGS High Resolution
Orthoimageryhttps://wiki.openstreetmap.org/wiki/USGS_High_Resolution_Orthoimagery,
but that the link is outdated. The new resource to use is likely one of
thesehttp://isse.cr.usgs.gov/ArcGIS/rest/services/Orthoimagery folders. I've
looked at the 1-foot imagery, and this seems to be sharper or equal quality
than the Bing imagery in at least two areas. In addition, according to
thishttp://cumulus.cr.usgs.gov/listofortho.php page, only Canada and the
border data is marked as View only; all other counties are public domain.
Is there any reason this imagery can't be used in OSM, and perhaps even be
added as one of the pre-existing imagery sources in JOSM?
--
Saikrishna Arcot
___
Talk-us mailing list
Talk-us@openstreetmap.orgmailto:Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
___
Talk-us mailing list
Talk-us@openstreetmap.orgmailto:Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
___
Talk-us mailing list
Talk-us@openstreetmap.orgmailto:Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
___
Talk-us mailing list
Talk-us@openstreetmap.orgmailto: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] Follow up on destination= and destination:ref=
Hi, I posted about destination= and destination:ref= a few days ago, linking to my diary entry. I have since received a lot of useful comments. I just wanted to bump this topic because all the discussion has been going on there and not on the list: http://www.openstreetmap.org/user/mvexel/diary/22419#comment27109 Here at Telenav, we have now adopted destination= and destination:ref= for signpost information. We have two people adding information about signposts where they don't exist, prioritizing corridors that are of particular importance to us. You can follow their work here: http://www.openstreetmap.org/user/Dami_D/history http://www.openstreetmap.org/user/ChrisZontine/history We are not removing or replacing existing exit_to tagging. We are focusing on exits that don't have signpost information at all yet. We are also building support for this convention into our OSM model, retaining the existing support for exit_to for now. From the comment thread on my diary entry I get the feeling that there is some sense of agreement that we can move towards finally deprecating exit_to. As much as I would love to, that would require more discussion around what we will do with the existing exit_to tags, support in editors, etc. I would like to start talking about these things, but not before I am comfortable that we want this as a community. -- Martijn van Exel OSM data specialist Telenav http://www.osm.org/user/mvexel http://wiki.openstreetmap.org/wiki/User:Mvexel http://hdyc.neis-one.org/?mvexel ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
