Forum   |   Links    


Forum Home   Start New Topic   Edit Profile   Register  

1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16   17   18   19   20   21   22   23   24   25   26   27   28   29   30   31   32   33   34   35   36   37   38   39   40   41   42   43   44   45   46   47   48   49   50   51   52   53   54   55   56   57   58   59   60   61   62   63   64   65   66   67   68   69   70  


Show Profile  Michael Posted: 27 August 2017, 4:56 PM  
The LINZ Data Service is doing some renaming of url's on Tuesday 29 Aug. I don't think it have any effect on my use of the site, except that it will be unavailable 8-11pm that day. Read about it at Whew, that's a pretty long url...

Show Profile  Rolf Posted: 2 October 2017, 11:16 AM  
How about the mapping at the Sprint events in Australia. Nearly all trees/bush were mapped as semi-open.

I should think it made the mapping a lot simpler.

What did competitors think?

Show Profile  Bryan Posted: 3 October 2017, 5:23 AM  
Just checked the map against google maps and the vegetation is very generalised - areas which I would probably have classed as open run, individual trees or copses, one very distinctive tree or bush have all been classed as semi-open - all quite easy to map with the full range of symbols (bush, tree, white) and to show with clarity at 1:4000. I can also see areas which are shown as semi-open but the aerial clearly shows grass. I would have mapped this differently.

Show Profile  Michael Posted: 9 October 2017, 4:35 AM  
We all map a bit differently:-))

When you have one tree in an open area, its a tree. When you have two trees, its probably two trees. When you have 50 trees its probably open with scattered trees. Within an open/scattered area, all mappers would pick out Tane Mahuta and make it a "tree" but as to whether any of the other 49 would stand out, that's subjective. So is drawing the boundary round it, and whether you pick out clearings within it.

I ran in Oz, it wasn't an issue.

It may be an issue the way we are adding more and more detail to sprint maps. The spec says that most areas should be done at 1:5000 with 4000 the exception.

Show Profile  fraser Posted: 10 October 2017, 10:53 AM  
I would say on the whole New Zealand maps are at the other end of the spectrum and the use of single trees is probably over done. I am probably guilty of that anyway.

What is technically wrong on the aussie map is there are a few areas of semi-open that are below the minimum size of 10 square millimetres. In this case they should be mapped as open or as single trees.

I have drawn what 10 square millimetres looks like, using green, next to a couple of the areas which are below the minimum size.

Show Profile  Michael Posted: 4 November 2017, 1:47 PM  
Mapping conundrum #1234:

I'm using the ISSOM tramway for model railways in parks, largely on a yellow background, and you can hardly see it. The obvious answer is to beef up the lines from 50% to 100% black. Any downside in that? Any other suggestions?

Show Profile  fraser Posted: 7 November 2017, 1:29 AM  
Wouldn't it be better to just use the railway symbol?

Show Profile  Michael Posted: 13 November 2017, 11:02 AM  
It would certainly stand out better. I thought I had found a good way of distinguishing big railways from tiny little ones that you step over without breaking stride. Maybe an almost-invisible line is perfect:-)

Show Profile  Michael Posted: 18 January 2018, 2:37 PM  
Experience with Greater Wellington LiDAR coverage. It was like all my Christmases at once when LiDAR coverage of the Lower North Island (up to Otaki and Eketahuna) became available on the LINZ website. All those areas which had no or dodgy contours could be fixed (although it takes some effort to preserve what fieldworkers have observed).

I have now done three areas and find that quality is variable. A small area in the Hutt Valley , and Tukutuku on the Kapiti coast seemed quite good. The former covered by mature exotic trees was formerly based on 5m city council-supplied contours and I could tell what corresponded to what. Some wiggles were spurious and that's completely understandable. The latter in native bush was formerly based on topo contours interpolated twice down to 5m, the new contours put spurs and valleys in different places but they were mainly wrong where vegetation or steepness meant there had been no fieldwork. It wasn't too hard to blend them in.

It's a different story at Catchpool Valley in Rimutaka Forest Park - another native bush map. We have city council contours but I don't rate them highly - I suspect their terrain model outside the residential area uses coarser data. The GW LiDAR-based contours show greater detail but I'm not sure that I trust them either. There are strange discrepancies such as significant hills on the flat valley floor. The position of some of the "reentrants" along tracks open to the sky leads me to wonder if they have filled in their model with aerial photo-based data.

So. just as with aerial photos and photogrammetry, there may be good LiDAR, and not-so-good LiDAR.

Show Profile  mcroxford Posted: 20 January 2018, 11:36 PM an interesting tool for getting the declination right.

Show Profile  Michael Posted: 21 January 2018, 3:24 AM  
Hmmm. Gives a different answer for Wgtn than does GNS. Could be that NZTM is different from UTM in this part of the world.

Show Profile  Michael Posted: 9 February 2018, 12:22 AM  
The following, or something like it, will shortly appear in an ONZ Mappers Bulletin

Sprint Mapping Specification

The IOF Mapping Committee has developed a draft revision of the Sprint Mapping Specification ISSOM. It hopes it will be adopted in 2018, which given the last revision project, seems a bit optimistic. It has also published a draft appendix on digital printing.

All federations have the opportunity to comment by 1 May. ONZ wishes to have any possible response submitted to it by 15 April. The primary question is, does NZ wish to make a submission?

So the first step is to read the drafts. They don't appear to be on the IOF website, but Norway has put them up:
ISSOM 201x final draft:

What has changed from ISSOM 2007:

ISOM 2017 Appendix 1- CMYK printing and colour definitions:

The second step is to answer the following questions
1. There are or are not significant issues that NZ needs to make submissions on (the ISSOM or perhaps the digital appendix)
2. I am or I am not interested in discussing a NZ submission on the above (depends on a yes to the above of course)
3. I have time to discuss during March (depends on a yes to the above of course)

Please reply to gmichael (dot) wood (at) by 28 Feb. (There's a problem with the Mapsport address for Xtra senders.) In the meantime, feel free to comment on the draft on the Maptalk mapping thread, issues often crop up or are answered in chat forums. Attackpoint may also hold interesting views.

Show Profile  Michael Posted: 3 March 2018, 8:48 AM  
There's an OCAD12 update which includes a symbol table and CRT file to go from ISSOM2007 (the existing sprint spec) to the draft ISSOM20XX. I imagine it will work fine if you have an absolutely stock standard symbol table with no extensions. Ha ha. I'll shortly develop a crt with comments in it to convert the OHV park/sprint maps to the new spec. Might not match your particular symbols but at least it will have words in it and not just numbers.

BTW the symbol numbers are pretty similar to the old ISSOM, Whereas most of the ISOM2017 symbol numbers have changed. Sigh.

Show Profile  Michael Posted: 11 March 2018, 9:49 AM  
There's one change in the draft ISSOM which is sure to come in, in fact I think it was an oversight last time. That's the size of the small path 507.

With the current ISSOM it is the same size as 1:15,000 ordinary maps. Many of us have older eyes, we deserve and get 1:10,000 maps with symbol sizes at 150%. I suspect that many younger people are also getting 1:10,000 maps and appreciate the larger symbols.

Now MOST of the current sprint symbols are approximately at the 150% level and the new draft brings 507 into line with that. Why not do it now? It would have been quite a help at today's event in a steep green area criss-crossed by MTB tracks, and also last Wednesday's event with a myriad of paths in the olive green of a botanical garden.

Show Profile  The Map Guy Posted: 13 March 2018, 6:50 AM  
I have noticed there is a potential clarity issue with the new NZ water trough symbol (*) using the ISOM2017 default OCAD symbol set.

The asterisk symbol was introduced to give a clear distinction between a tree and water trough on a yellow background. So far, so good, but if a water trough is on a fenceline (shared between two paddocks) the symbol may be hidden by the black fenceline.

A solution is to create a new blue colour (above black) for and use it for water troughs.

See the image on:

1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16   17   18   19   20   21   22   23   24   25   26   27   28   29   30   31   32   33   34   35   36   37   38   39   40   41   42   43   44   45   46   47   48   49   50   51   52   53   54   55   56   57   58   59   60   61   62   63   64   65   66   67   68   69   70  

Ruffneck Productions © Ruffneck Productions