Table of contents
    No headers


    There some rough code for downloading and merging data for the yukon and surround at, eventually the resultant processed and merged data will be placed online. No idea when I'll get around to that though. If you get to it first, please let me know, I have a place to host it. -- MattWilkie - 2008-01-24


    >Someone at AAFC in Ottawa said that they use the Canvec base for all
    >their maps. Is this the same as the NTDB base in the Yukon? Do you use it?

    In the Yukon canvec is derived from the 50k ntdb, and thus similar. The main difference at this time lies in naming of the layers and their attribute structure. The geometry is nearly identical -- provided you are using the free ntdb from and not the 50k ntdb from Yukon Government (including us). The 50k ntdb we are using, edition 2.x (might be ed3.0), is behind the current release, edition 3.1.

    The main change from ed2 to ed3.1 is horizontal correction. Ed3.1 will align more closely to GPS and Landsat7 data. The attributes are unchanged.

    So the bottom line is: if you are working with GPS and remote sensing data, use Canvec. If you are working with Yukon Government, use our 50k ntdb. If you have to do both, flip a coin and explain to the project manager what is lost by choosing one or the other.

    I apologise for a complicated answer to a straightforward question, and for the state of ambiguity it places everyone who works with us in.

    -- MattWilkie


    > the feature catalogue does not have code "LX_2030019" listed in the appendix, yet 105p15
    > has this layer in both the GML and SHP distribution archives. Is the specification in error or is the datafile isnamed?

    2-The CanVec codification will be modified in the next release in January 2008. Camp: Modify LX_2030019 to LX_2030009 Parabolic Antenna: Modify BS_2000059 to BS_2000009





        Send feedback