Strict Standards: Declaration of AuthPriv::doAuthByCookie() should be compatible with Auth::doAuthByCookie($name) in /home4/smith/public_html/faq/admin/lib/eleontev/Auth/AuthPriv.php on line 28

Strict Standards: Declaration of AuthPriv::authToCookie() should be compatible with Auth::authToCookie($name, $period = , $data = , $path = ) in /home4/smith/public_html/faq/admin/lib/eleontev/Auth/AuthPriv.php on line 28

Strict Standards: Declaration of AuthPriv::removeCookie() should be compatible with Auth::removeCookie($name) in /home4/smith/public_html/faq/admin/lib/eleontev/Auth/AuthPriv.php on line 28

Strict Standards: Declaration of AuthPriv::isPriv() should be compatible with Auth::isPriv() in /home4/smith/public_html/faq/admin/lib/eleontev/Auth/AuthPriv.php on line 28

Strict Standards: Declaration of AuthPriv::checkPrivAction() should be compatible with Auth::checkPrivAction() in /home4/smith/public_html/faq/admin/lib/eleontev/Auth/AuthPriv.php on line 28

Strict Standards: Non-static method PHP_Compat::loadFunction() should not be called statically in /home4/smith/public_html/faq/admin/common_share.inc.php on line 21

Strict Standards: Non-static method PHP_Compat::loadFunction() should not be called statically in /home4/smith/public_html/faq/admin/lib/Pear/PHP/Compat.php on line 95

Strict Standards: Non-static method PHP_Compat::loadFunction() should not be called statically in /home4/smith/public_html/faq/admin/lib/Pear/PHP/Compat.php on line 95

Strict Standards: Non-static method PHP_Compat::loadFunction() should not be called statically in /home4/smith/public_html/faq/admin/lib/Pear/PHP/Compat.php on line 95

Strict Standards: Declaration of SettingModel::getRecords() should be compatible with & AppModel::getRecords($limit = , $offset = ) in /home4/smith/public_html/faq/admin/modules/setting/setting/inc/SettingModel.php on line 17

Strict Standards: Declaration of SettingModel::save() should be compatible with AppModel::save(&$obj) in /home4/smith/public_html/faq/admin/modules/setting/setting/inc/SettingModel.php on line 17

Strict Standards: Declaration of KBClientView::stripVars() should be compatible with & BaseView::stripVars($values, $skip_keys = , $server_check = ) in /home4/smith/public_html/faq/client/inc/KBClientView.php on line 13

Strict Standards: Non-static method Registry::instance() should not be called statically in /home4/smith/public_html/faq/client/inc/common.inc.php on line 79

Strict Standards: Non-static method DBUtil::connect() should not be called statically in /home4/smith/public_html/faq/client/inc/common.inc.php on line 92

Strict Standards: Non-static method KBClientBaseModel::getSettings() should not be called statically in /home4/smith/public_html/faq/index.php on line 38

Strict Standards: Non-static method KBClientLoader::getManager() should not be called statically in /home4/smith/public_html/faq/index.php on line 62

Strict Standards: Non-static method AuthPriv::isAuth() should not be called statically in /home4/smith/public_html/faq/client/inc/KBClientLoader.php on line 69

Strict Standards: Non-static method Auth::_isAuth() should not be called statically in /home4/smith/public_html/faq/admin/lib/eleontev/Auth/AuthPriv.php on line 126

Strict Standards: Non-static method AuthPriv::getUserId() should not be called statically in /home4/smith/public_html/faq/client/inc/KBClientLoader.php on line 70

Strict Standards: Non-static method AuthPriv::getPrivId() should not be called statically in /home4/smith/public_html/faq/client/inc/KBClientLoader.php on line 71

Strict Standards: Non-static method AuthPriv::getRoleId() should not be called statically in /home4/smith/public_html/faq/client/inc/KBClientLoader.php on line 72

Strict Standards: Non-static method KBClientLoader::getView() should not be called statically in /home4/smith/public_html/faq/index.php on line 63
Stripe removal and groove-inlay recessing of intersection markings: I am looking to purchase the SMITH SPS10 Surface Preparator, designed for your intended application of removing thermoplastic and paint markings and replacing it with a flame applied preform tape marking.

Stripe removal and groove-inlay recessing of intersection markings: I am looking to purchase the SMITH SPS10 Surface Preparator, designed for your intended application of removing thermoplastic and paint markings and replacing it with a flame applied preform tape marking.

The use of the SMITH SPS10 with the Flail-it medium set-up is ideal, and should achieve an SP 5 - 7 profile with proper up-cut use, best for hot-tape type application on asphalt or concrete. You indicated that you will be removing the stripe and installing it in the same location. If you require a finer profile, it is recommended to have a second cutter drum outfitted with the Strip-it fine pattern that can be used following the Flail-it application to clean out the initial cut.

If you are removing markings and re-applying in a new location, it is recommended to use the LNX8 rotary eraser to prevent sharp-edge permanent grooving where the prior stripe will re-appear as a false ghost line during wet conditions. 

It is a best practice to always purchase a wear parts kit and cutter drum assembly or rebuild kit with your new equipment to reduce downtime, and to qualify for the SMITH lifetime chassis warranty. Your account manager, Lauren, can assist you with best pricing.



Article ID: 356
Last updated: 27 Feb, 2015
Removal Equipment -> LNX8 Traffic Line Remover -> Stripe removal and groove-inlay recessing of intersection markings: I am looking to purchase the SMITH SPS10 Surface Preparator, designed for your intended application of removing thermoplastic and paint markings and replacing it with a flame applied preform tape marking.
http://www.smithmfg.com/faq/entry/356/