Glen wrote:
> # Merge ways that are < 2000 nodes combined to a single way.
After dealing with cleaning up the horrible mess of ways that went
over the 2000 limit a number of times, I'd strongly argue to keep the
polylines at a starting point of ~495 nodes each. It gives you (i.e.
not really you, but some helpful 3rd party who doesn't know about the
limit) a bit of leeway to mix and match and combine without being too
splintered, but not too close to going over the cliff either.
> I would prefer to make a relation with that name and add all the LINZ objects to it before
> deleting it.
ok
Hamish
On 1/29/13, Glen Barnes <
barnacl...@gmail.com> wrote:
>
>
> On Tuesday, 29 January 2013 17:34:02 UTC+13, Hamish wrote:
>>
>> Glen:
>> > I've run into a few issues with having duplicate nodes where different
>> polygons
>> > share that same outline and are part of a relation.
>>
>> Do you mean the Validator complaining that there are two overlapping
>> ways, typically an inner hole in some relation and an area of bush or
>> something in that hole?
>>
>
> Yes.
>
>
>>
>> > I'm thinking there is probably some for of script we could run that
>> would deal with these
>> > issues and I will probably show Stephen and Rob to see what they think.
>> >
>>
>> I've just been leaving them for now, along with the overlapping
>> coastline/bush "duplicate nodes on unclosed way" which won't auto-fix
>> in bulk. I figure a tool within the Validator will come around in
>> time.
>>
>
> Right - The actual 'proper' solution is to:
>
>
> - Merge ways that are < 2000 nodes combined to a single way.
> - Move the tags to a relation if they are > 2000 nodes combined. This
> way you don't get an unclosed way issue.
>
>
>> > There is also a job to get rid of the big forest up north and make a
>> relation of all the LINZ
>> > data. I'm still trying to find the LINZ layer which 'fills in' the other
>> >
>> parts of the forest but
>> > have yet to find it. I wonder what the best way is to find "All the
>> layers that cover this area"?
>>
>>
nztopomaps.com is pretty good to let you glance at the topo50 sheet,
>> and you can do the same by adding a custom WMS layer in JOSM linking
>> to the LINZ data service.
>>
>> for big forests often there's a single green "node" describing the
>> whole thing, you need to checkout the rectangle containing that green
>> dot, many of the rectangles around it turn up as 0 features even if
>> there is coverage from the neighboring rectangle.
>>
>> Just having a peek at the topo50 sheets for northland, 90 mile beach
>> seems to be all exotic_poly, but you've already completed those
>> workslices. South of there the bush seems pretty well broken up and
>> about half pine trees, so the areas shouldn't get too huge.
>> So actually I'm not really sure where you are looking. URL?
>>
>>
> <
https://www.evernote.com/shard/s2/sh/cedc6f54-8811-4912-8145-23b2d3fe42c9/2aa734310d8eb415357369cba40474c5>
> --
> You received this message because you are subscribed to the Google Groups
> "nzopengis" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
nzopengis+...@googlegroups.com.
> To post to this group, send email to
nzop...@googlegroups.com.
> Visit this group at
http://groups.google.com/group/nzopengis?hl=en.
> For more options, visit
https://groups.google.com/groups/opt_out.
>
>
>