I've been in contact with VITA, the agency responsible for GIS for the
state of Virginia, USA. They are interested in OSM utilizing their
road centerline data. VITA coordinates with all the localities in
Virginia to obtain this information, though most of it is sourced from
the Virginia Base
Josh,
Are you on the regular talk list?
There's been a long discussion about the dangers of importing on that
list. Since you're new to importing, I'd suggest reading that thread
so you're familiar with the pitfalls.
Where in Virginia are you? If you're near the DC area, a few of us
have been
Serge,
I am, and am aware there are dangers, though I'm sure I'm not aware of
all of them, which is why I'm going slowly. :) I'm in Fairfax County,
so it would be good for me to attend that meeting.
I've linked to the data on the wiki (Virginia [1] and Fairfax County
[2]). Please let me know what
I'm totally new to importing, so I first wanted to see if anyone else
is interested in this project, though I am willing to take the time to
learn the process myself. Is the process used for importing the
Canadian database [1] the best method for doing this?
The process for the Canadian
On Mon, Feb 21, 2011 at 12:04 PM, Peter Budny pet...@gatech.edu wrote:
Josh, this sounds great! Unfortunately, you're headed in to really new
territory. As far as I can tell, OSM doesn't have any methods in place
for merging data in any meaningful sense, which sounds like what you
need to
Hi,
Katie Filbert wrote:
How about just converting the data to OSM format. Break it up by small,
manageable chunks such as census tracts. Post the files somewhere.
Maybe OSM-US can help provide a place for them.
I hear that Potlatch2 already has a mode where you can load a shape file
as a
Richard Weait rich...@weait.com writes:
On Mon, Feb 21, 2011 at 12:04 PM, Peter Budny pet...@gatech.edu wrote:
Josh, this sounds great! Unfortunately, you're headed in to really new
territory. As far as I can tell, OSM doesn't have any methods in place
for merging data in any meaningful
On Mon, 2011-02-21 at 19:25 +0100, Frederik Ramm wrote:
What I like most about it is that you have a forced visual feedback -
there is no way you can copy something into OSM without seeing what is
actually there before you do.
It would be really nice to add some JOSM layer functionality like
On Mon, Feb 21, 2011 at 12:31 PM, Dave Hansen d...@sr71.net wrote:
On Mon, 2011-02-21 at 19:25 +0100, Frederik Ramm wrote:
What I like most about it is that you have a forced visual feedback -
there is no way you can copy something into OSM without seeing what is
actually there before you
Hi,
Ian Dees wrote:
I think this is a great first step towards a merging/importing
toolkit. A shapefile reading and rendering plugin for JOSM would be
extremely nice to have and was the original intention of my shp-to-osm code.
... as long as we make absolutely sure nobody can simply hit
On Mon, 2011-02-21 at 19:59 +0100, Frederik Ramm wrote:
Ian Dees wrote:
I think this is a great first step towards a merging/importing
toolkit. A shapefile reading and rendering plugin for JOSM would be
extremely nice to have and was the original intention of my shp-to-osm code.
... as
Hi Josh,
I've done a couple imports with varying levels of success. I live in
Virginia (in Arlington) and would like to help.
-Kate
On Mon, Feb 21, 2011 at 12:40 PM, Josh Doe j...@joshdoe.com wrote:
I absolutely agree about preserving user contributions. For any given
segment in the Virginia
Josh,
I like Katie's idea of breaking the data up into manageable chunks
(counties?) and importing in incrementally. I'd be interested in helping
with a few chunks. I'm in Arlington, too. Perhaps we'll meet at a DC area
event?
SEJ
A serious and good philosophical work could be written
13 matches
Mail list logo