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 RCL Shapefile, there are any number of ways in
> OSM that make up that segment, with varying attributes. The reverse is
> possible as well. Merging this won't be easy by any means. However
> there's no reason we couldn't start importing (sooner) in areas that
> haven't been edited since the TIGER import
>
> As for RoadMatcher, though I haven't played with it yet, I don't see
> how OSM attributes are lost, it's just that you have to map from
> OSM->Shapefile->OSM.
>
> Remember, I'm just broadcasting my interest, I have a lot of learning to do.
>
> Regards,
> -Josh
>
> On Mon, Feb 21, 2011 at 12:01 PM, Mike N <nice...@att.net> wrote:
>>> 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 database is best used only for adding new
>> roads that don't exist in the OSM database.  As part of the upload process,
>> plan on stitching them into existing roads, perhaps using JOSM.
>>
>>  It would also be handy to be able to project the improved geometry onto
>> existing roads of the same name, while preserving attributes and driveway /
>> footpath / bridges that have already been added to the OSM data.    That
>> will preserve user's contributions and history.  This would require some
>> new, yet-to-be developed tool to work directly with OSM data.  There is much
>> interest in this because of the TIGER 2010 data and Arkansas state data
>> sets.   It is not certain when there will be developer resources to develop
>> such a tool.
>>
>>  The limitation of Roadmatcher is that it works only with shapefiles, thus
>> OSM attributes are lost when exporting to shapefiles.
>>
>> _______________________________________________
>> Talk-us mailing list
>> Talk-us@openstreetmap.org
>> http://lists.openstreetmap.org/listinfo/talk-us
>>
>
> _______________________________________________
> Imports mailing list
> impo...@openstreetmap.org
> http://lists.openstreetmap.org/listinfo/imports
>

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

Reply via email to