 |
|
|
May 4, 2009 -
Ref#:5411360
|
Please confirm whether the FSPTS will automatically approve an amendment that does not require approval when stocking standards are being entered to get new SSID's (or does this amendment have to be submitted as one requiring approval). The stocking standards were approved as a variance in the original FSP text but licensee would prefer to address this variance with separate SSID's rather than the approved variation method in results. |
-
Jul 14, 2009 -
When stocking standards are being entered to create a new SSID, even for stocking standards that had already been approved as a variance in FSP, then the new SSID's have to be submitted for approval in FSP. It is not an automatic approval as it must be reviewed by the MOF.
|
 |
|
|
Apr 29, 2009 -
Ref#:429104959
|
For FSP #134, amendment #7 requiring approval was initiated in 2008 and approved on Jan 12/09. It is still showing in draft status in FSPTS because we are working on the shape file submission.
Amendment #8 did not require approval and took effect on Nov 18/08 (while #7 was still being reviewed). It included a minor change to an FDU boundary. The spatial change was in a different location than the changes to #7.
My question is: does the boundary change to #8 need to show up in the shape file for amendment 7 since it was in effect before #7 was approved?
|
|
|
 |
|
|
Nov 4, 2008 -
Ref#:11413826
|
When submitting a proposed Stocking Standard, I inadvertently associated it with the wrong FSP Amendment. Can I change this before I submit the Standard proposal? |
|
|
 |
|
|
Aug 18, 2008 -
Ref#:818201342
|
How can a licensee/BCTS expire a stocking standard in their FSP? |
-
Aug 18, 2008 -
FSP stocking standards should not be automatically set to expire with the FSP as they may be administered at the SU level long after the FSP expires. If a licensee/BCTS wishes to expire a stocking standard(s) in an approved FSP, they may do so by submitting a request to expire to MFR staff. The stocking standards may be expired by entering an expiry date in the stocking standard record in the FSPTS. This can be done by an MFR user with FSP decision maker or system admin roles or may be done via data fix. Licensees/BCTS users should always leave the expiry date field blank in their stocking standards when submitting their FSP.
NOTE: licensees/BCTS who have submitted stocking standards with an expiry date do not need to edit their FSPs in the FSPTS to remove the expiry date. A data fix will be applied to remove the expiry dates.
|
 |
|
|
Aug 1, 2008 -
Ref#:81163756
|
How are forest development units in an approved FSP amended? |
-
Aug 1, 2008 -
Licensees and BCTS can submit an amendment to the FSP Tracking System to add and/or change their forest development units (FDUs) in an approved FSP. The amendment can be made through either the ESF or directly in the FSP Tracking System. The amendment must include the spatial information for the new and/or changed FDUs. This can be either as part of the XML/GML file that is submitted through ESF; or as a zip folder containing the shape files attached to the amendment in the FSP Tracking System.
The MFR must ensure the FDU layers in the LRDW are updated with the new and/or changed FDUs. If the licensee/BCTS submits the spatial information as an attachment in the FSP Tracking System, then the MFR must download, unzip and load this information into the LRDW (as an XML/GML submission through the ESF). Once the FDU layers in the LRDW are updated with the new spatial information, the MFR can review and approve/reject the amendment.
The Amending an Approved FSP User Guide contains more information on amending FDUs. The user guide can be obtained from the FSP Tracking Website at: http://www.for.gov.bc.ca/his/fsp/userGuides/.
|
 |
|
|
Jul 10, 2008 -
Ref#:71081520
|
Can I declare a road as a line in my spatial submission? |
-
Jul 10, 2008 -
No. Declared areas must be submitted as polygons, not lines. Roads are typically submitted as polygons ranging in width from 20-75 metres. The size of the polygon can be as large an area as necessary to provide flexibility to move the road location a bit to address any issues during construction.
The necessary assessments must be complete before an area can be declared. Declaring a larger area requires more assessment effort. Declaring a smaller area may not give you enough planning protection if you need to change the location of the road during construction.
|
 |
|
|
Jul 9, 2008 -
Ref#:791745
|
How do you know what amendments require approval? |
|
|
 |
|
|
Jul 9, 2008 -
Ref#:7917255
|
Are you able to amend an approved stocking standard, or do you have to create a new one? |
|
|
 |
|
|
Jul 9, 2008 -
Ref#:7917219
|
Is there any requirement to submit a consolidated version of an FSP with every amendment? |
|
|
 |
|
|
Jul 9, 2008 -
Ref#:7917129
|
Why is the status of an amendment "draft" (before I submit) even if the amendment does not have to be approved? |
-
Jul 9, 2008 -
All FSPs and amendments are initially assigned a status of "draft" when they are created in the FSP Tracking System. The "draft" status is used to indicate that the plan or amendment is not ready for submission to the MFR.
When the amendment is successfully submitted, it will be assigned a status of "submitted" (for amendments requiring approval) or "approved"(for amendments not requiring approval).
|