[Talk-us] Unpaved streets

2009-09-03 Thread Nakor
 Hello,

In my neighborhood there are some unpaved residential streets. How should
those be tagged?

highway=track

highway=residential
surface=unpaved

BTW does highway=residential imply surface=paved?

 Thanks in advance,

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


Re: [Talk-us] Unpaved streets

2009-09-03 Thread Paul Fox
ian wrote:
  On Thu, Sep 3, 2009 at 9:13 AM, Nakor nakor...@gmail.com wrote:
  
Hello,
  
   In my neighborhood there are some unpaved residential streets. How should
   those be tagged?
  
   highway=track
  
   highway=residential
   surface=unpaved
  
  
  That's how I've been doing it.
  

do you have a way of rendering those unpaved streets distinctively?

paul 
=-
 paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 61.7 degrees)

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


Re: [Talk-us] Unpaved streets

2009-09-03 Thread Alex Mauer
On 09/03/2009 09:17 AM, Ian Dees wrote:
 No tag should ever imply any other tag. It's always better to be more
 verbose than not.

No it's not.  Are you seriously putting oneway=no (just to name one
example) on every street you tag?

-Alex Mauer hawke



signature.asc
Description: OpenPGP digital signature
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


[Talk-us] TopOSM Colorado

2009-09-03 Thread Lars Ahlzen
Hi All!

It's been a while since the last TopOSM update, but I haven't been
resting. After Massachusetts, I decided to pick a state with somewhat 
more interesting topography: Colorado.

http://toposm.com/co/

There are still a few rough edges and things that are missing (like the
map legend), so consider it a preview.

TopOSM-CO has a few important differences from TopOSM-MA:

* Color-by-elevation in base layer.

* Contour lines and hillshading generated from NED [1].

* Hydrography (lakes, rivers, wetlands etc) from NHD [2].

* The hillshading, contour lines and map features are on separate
layers. Use the layer switcher (top right +) to toggle.

Since the data is nationwide, the same technique could (theoretically)
be used to generate a complete TopOSM map of the US, or even the world 
by using e.g. SRTM for elevation and OSM for hydrography.

I'll update the TopOSM wiki page [3] with the changes in this version as
soon as I can.

- Lars



[1] National Elevation Dataset. Available for the entire US.
http://ned.usgs.gov/

[2] National Hydrography Dataset. Available for the entire US. There is
some effort to import this into OSM, but we're not there yet.
http://nhd.usgs.gov/

[3] http://wiki.openstreetmap.org/wiki/TopOSM

-- 
Lars Ahlzen
l...@ahlzen.com


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


Re: [Talk-us] TopOSM Colorado

2009-09-03 Thread Bill Ricker
 TopOSM-CO has a few important differences from TopOSM-MA:

What, MASSGIS doesn't cover Aspen?

 * Color-by-elevation in base layer.

interesting

 * Contour lines and hillshading generated from NED [1].

does that mean you're interpolating lines from a grid?

 * Hydrography (lakes, rivers, wetlands etc) from NHD [2].

which will eventually be in OSM

 * The hillshading, contour lines and map features are on separate
 layers. Use the layer switcher (top right +) to toggle.

AWESOME. that's beautiful.

 Since the data is nationwide, the same technique could (theoretically)
 be used to generate a complete TopOSM map of the US, or even the world
 by using e.g. SRTM for elevation and OSM for hydrography.

requiring only a render farm plus some config ?

Use any perl in ingesting or anything?


-- 
Bill
n1...@arrl.net bill.n1...@gmail.com

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