On Wed, Aug 26, 2009 at 10:23 AM, Richard Weaitrich...@weait.com wrote:
On Wed, Aug 26, 2009 at 8:39 AM, Lennardl...@xs4all.nl wrote:
Richard Weait wrote:
I think the provincial / state borders will continue to be yucky on
the main map until mapnik supports rendering different style sheets
On Wed, Aug 26, 2009 at 10:56 AM, Adam Schreibersa...@clemson.edu wrote:
To make things clear, should the place=state tag be placed on, near
the node for the capital city of the state?
Near the geometric center of the state, I'd think. Looks like:
place=state
name=South Carolina # for
James Ewen wrote:
On Wed, Aug 26, 2009 at 8:23 AM, Richard Weaitrich...@weait.com wrote:
So we USA-ians have a few nodes to move for place=state;
Ooh, yuck... the state name labels end up in the wrong spots... missed
that. Washington looks like it has two labels.
I just cleaned up all
Eww, a bit of a mess right now. Maybe I'm just seeing a wierd snapshot, but
several states are labeled twice, and most are labeled at the lower right
corner of the state (with the state name crossing into its neighbors.)
With only 50 states to worry about, is this something 1 person should take
On Wed, 2009-08-26 at 08:47 -0600, James Ewen wrote:
On Wed, Aug 26, 2009 at 8:23 AM, Richard
Weaitrichard-gnthur35lhcavxtiumw...@public.gmane.org wrote:
So we USA-ians have a few nodes to move for place=state;
Ooh, yuck... the state name labels end up in the wrong spots... missed
that.
On Wed, 2009-08-26 at 10:56 -0400, Adam Schreiber wrote:
To make things clear, should the place=state tag be placed on, near
the node for the capital city of the state?
Why not closer to the geographic center like expected?
signature.asc
Description: This is a digitally signed message part
I'm doing some preliminary work on making the state park data from the
Minnesota DNR available to the map. I've sliced up the state park
boundaries and trails into small enough chunks for JOSM to handle, but I'm
having difficulties with my rules.txt file.
It may be a silly question, but does the
Hi, its
line,TRAIL_USE,B,bicycle,yes
line,TRAIL_USE,C,cars,yes
line,TRAIL_USE,H,horse,yes
it takes a little trial error at 1st.
Btw, also add
attribution,*
and make sure the source allows for copying :)
hope that helps,
Sam
On 8/26/09, Chris Hunter chunter...@gmail.com wrote:
I'm doing some
I was working on those exact same files and accidentally released a version
of shp-to-osm that uses contains instead of equals for string
comparison. Download the 2nd-newest version of shp-to-osm and when your
rules.txt line looks for a certain key, it will pick it up if the shapefile
contains
Thanks,
I'm pretty tired at the moment, but I knew there had to be a reason why SHP2OSM
kept erroring out when I tried to translate the fields instead of copy them.
I'll try and locate the correct version tomorrow.
Chris
Sent via BlackBerry from T-Mobile
-Original Message-
From: Ian
10 matches
Mail list logo
