[Talk-us] Bulk upload from sql server 2008 (via shapefile?)

[Ian Dees]

On Fri, Sep 4, 2009 at 10:19 AM, Lord-Castillo, Brett <
BLord-Castillo at stlouisco.com> wrote:

>  Sounds good. Should I use any particular projection, or export out to
> unprojected WGS84?
>
All of the shp -> osm options can reproject to the appropriate projection,
so pick whichever makes the most sense for your locality.

> One of the major problems is that there are an awful lot of domains tied to
> the sql server tables. Going to take a while to convert the domain codes to
> domain descriptions.
>
The domain descriptions probably don't need to end up in the shapefiles --
if you have a description of what the domain codes are as a textfile or
metadata file, we can use that to assist in conversion.

> I also have to deal with losing topologies and z-values as well as
> converting field names to a dbf compatible form. So, the conversion will
> take a while, but it’s doable J
>
>
>
> I’ll start with street centerlines. Once I get those to shapefile, what’s
> the next step?
>
It might be more impactful (and easier to merge with existing OSM data) if
you start with a data domain that hasn't made it into OSM yet. Something
like structure outlines, school locations, parks, etc. Since OSM data
already has the street centerlines (even if they're crummy), it'll be tons
more work to merge the existing data with your new data. ... but that's just
my opinion.

Next step would be to convert to OSM. Depending on your skills, you have
three options. 1) use crschmidt's shp2osm Python script [0], 2) use my
shp-to-osm Java application [1], or 3) ask someone else to do it. [2]

[0] http://crschmidt.net/blog/2009/01/05/polyshp2osm/
[1] http://redmine.yellowbkpk.com/projects/show/geo
[2] I'd be happy to convert for you. Just ship the zipped-up .shp/.dbf/.prj
files over to me.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20090904/ab06cd4e/attachment.html>