My WebLink
|
Help
|
About
|
Sign Out
Home
CC_Minutes_1981_0810
Roseville
>
City Council
>
City Council Meeting Minutes
>
198x
>
1981
>
CC_Minutes_1981_0810
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/17/2007 8:59:23 AM
Creation date
2/2/2005 5:27:28 AM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Minutes
Meeting Date
8/10/1981
Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
37
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
<br />MR. HONCHELL: One thing to remember is that any change you <br />make in a lot or a formula is going to affect all the other lots <br />in this particular case, especially because it's 100% assessed. <br />The money will come from those lots you see up on the screen in <br />some manner or other. As you consider changes, you might want to <br />at least keep in mind what these changes will do to the other <br />lots. I don't know what that would mean on your specific alter- <br />natives. One of the other approaches I guess we were thinking <br />of, after talking to the property owner, would be to, as best <br />possible, if the Council did want to make a change, would be to <br />follow the odd lot formula because it may be an imperfect system, <br />but it is at least tried and true for the most part. Rather than <br />start changing dimensions and areas and methods of assessment on <br />several other lots or all of them if you use acreage or square <br />footage, would be to simply say the Council, in this case, would <br />make an interpretation that the side lot for Lot 6 would be <br />105.3 feet on the north and 124 plus 100 feet on the south. I <br />guess I would say that's more of a flexible interpretation of <br />what is the side lot than simply throwing the side lot formula <br />out. I say this knowing that doing something like that would <br />make a total impact for the watermain assessment and.the paving <br />assessment of approximately $3,000 to that Lot 6. Correspondingly, <br />all the other lots adjacent to the shaded area would more or less <br />pick up a couple of hundred dollars each. If we reduce one by <br />$3,000, the others go up. All of those adjacent to the water <br />line, namely on the cul-de-sac, would go up by another approxi- <br />mately $100 each. In quick numbers you're looking at the lots <br />on the cul-de-sac being $300 higher each lot and those along <br />Fernwood being approximately $200, if this were done. This is <br />just another way. <br /> <br />COUNCILMAN JOHNSON: How would the assessment on number 6 <br />then compare to expanded lot 3 or expanded lot 5? <br /> <br />MR. HONCHELL: Lot 6 would be slightly over $9,000, Lot 5 <br />would be $12,600, and Lot 3-4 would be around $14,000. I gues's <br />I would say that by square footage, it would be in much closer <br />proportion to the total assessment. Some of those also have some <br />other things - they have some extra water services - but still, <br />in general, that's the way it would end up. <br /> <br />COUNCILMAN JOHNSON: I have a feeling that that adjustment <br />(inaudible). It loads unfairly on all the rest of the owners <br />some of the assessment that should probably more properly be <br />on Lot 6. <br /> <br />MR. HONCHELL: That's what I'm saying. There's no easy way. <br />I guess as a reaction to the two proposals. the one of average <br />square footage, my reaction would be that you probably would end up <br />loading an awful lot on the other side of Fernwood - namely, <br />7, 8, 9, 6, etc. 5, in that they're some areas - they have an <br />odd lot formula in reverse. They're wide at the street and <br />narrow in the back. But if you just take total square footage, <br /> <br />4 <br />
The URL can be used to link to this page
Your browser does not support the video tag.