[OSM-dev] OGC standards / Sql Server 2008 / OSM... help?
shogunz0r at gmail.com
Thu Feb 19 09:12:11 GMT 2009
Thanks guys. I've managed to narrow the problems down to 9 coastlines
for Australia (one of which Dermot fixed last night). I'm fixing them
manually. In total there are just under 50 "invalid" ways in the
Aussie export. I'll see if I can get to them all. Some of them are not
easy to figure out why they're invalid, but i'll ask for help on those
if need be.
On Thu, Feb 19, 2009 at 2:39 AM, Frederik Ramm <frederik at remote.org> wrote:
> Dermot McNally wrote:
>> JOSM is the tool I usually use, and the validator is indeed excellent
>> at finding these cases (it's what I used to investigate this issue).
>> However, Even though the outstanding errors are a lot milder than I
>> had to fix in Ireland (where I had to reverse the directions of all
>> island ways), there's an awful lot of coast around Australia and
>> unless you can get an army of volunteers to carve it up I think you'll
>> be working on it for quite some time.
> The whole of the Australian coastline, in OSM XML, is roughly 110 MB. JOSM
> can open this file in one go - I hesitate to say "with ease", that would
> perhaps be too much on the marketing side ;) you will require a fast machine
> with 2GB+ of RAM and/or some patience but if the problems you see are of a
> kind that can be fixed by the Validator, then this might be the way to go.
> You could attempt to get a current version of the coastline data through
> XAPI, or else grab a (very current) Aussie extract and run osm-excerpt-tags
> on it to reduce it to coastline only. (Opening the whole of Australia in
> JOSM would not work.)
> Merkaartor is likely to be quicker with large files but I don't know if it
> has an error detection/fixing facility like the Validator plugin for JOSM.
> Frederik Ramm ## eMail frederik at remote.org ## N49°00'09" E008°23'33"
More information about the dev