[OSM-dev] OGC standards / Sql Server 2008 / OSM... help?
shogunz0r at gmail.com
Wed Feb 18 22:37:47 GMT 2009
Thanks for the links Jon
I've rolled my own import by reading the planet file XML and inserting
the data into the database, initially into tables that mirror the OSM
database. I then convert the data into SqlGeometry in other tables. I
tried using the Geography data type, but there's just no chance of
compliance there, so for now i'm using the Geometry datatype.
The only error highlighted for Australia on the coastal checker
website is far away from the areas where i'm getting issues.
On Thu, Feb 19, 2009 at 12:25 AM, Jon Burgess
<jburgess777 at googlemail.com> wrote:
> On Thu, 2009-02-19 at 00:08 +0200, brendan barrett wrote:
>> Thanks Dermot
>> Is correcting it inside OSM the only way to deal with this kind of
>> data? If so, i'm thinking of compiling a list of all the ways that do
>> not comply, and then posting them somewhere so that we can all pick
>> them off one by one. There are a lot in Australia alone (using the
>> aussie export to get my testing done). I have a feeling that anyone
>> using Sql Server Spatial will have these issues.
> You don't mention how you are importing the data. Another tool which
> attempts to parse and correct minor issues with the coastlines is the
> coastcheck utiity. This also generates a set of shapefiles containing
> just the final geometries. There may still be problems with these, but
> perhaps a few less than the raw data.
> The problems seen by this tool are highlighted on the coast checker web
>  http://trac.openstreetmap.org/browser/applications/utils/coastcheck
>  http://hypercube.telascience.org/~kleptog/
>  http://tile.openstreetmap.nl/coastlines.html
More information about the dev