|
|
IFXAuthorLineSet Class ReferenceThis is the main interface for IFXAuthorLineSet.
More...
Inheritance diagram for IFXAuthorLineSet:
List of all members.
|
Public Member Functions |
| virtual IFXRESULT IFXAPI | Allocate (const IFXAuthorLineSetDesc *pLineDesc)=0 |
| virtual IFXRESULT IFXAPI | Reallocate (const IFXAuthorLineSetDesc *pLineDesc)=0 |
| virtual IFXRESULT IFXAPI | Deallocate ()=0 |
| virtual IFXRESULT IFXAPI | Copy (IFXREFIID interfaceID, void **ppNewAuthorLineSet)=0 |
virtual IFXAuthorLineSetDesc
*IFXAPI | GetLineSetDesc ()=0 |
| virtual IFXRESULT IFXAPI | SetLineSetDesc (const IFXAuthorLineSetDesc *pLineSetDesc)=0 |
virtual IFXAuthorLineSetDesc
*IFXAPI | GetMaxLineSetDesc ()=0 |
| virtual IFXRESULT IFXAPI | GetNumAllocatedTexLineLayers (U32 *pLayers)=0 |
| virtual IFXRESULT IFXAPI | GetPositionLines (IFXU32Line **ppPositionLine)=0 |
| virtual IFXRESULT IFXAPI | GetNormalLines (IFXU32Line **ppNormalLine)=0 |
| virtual IFXRESULT IFXAPI | GetDiffuseLines (IFXU32Line **ppDiffuseLine)=0 |
| virtual IFXRESULT IFXAPI | GetSpecularLines (IFXU32Line **ppSpecularLine)=0 |
| virtual IFXRESULT IFXAPI | GetTexCoordsLines (IFXU32Line **ppTexCoordLines)=0 |
| virtual IFXRESULT IFXAPI | GetMaterialsLines (U32 **ppMaterialLines)=0 |
| virtual IFXRESULT IFXAPI | GetPositionLine (U32 index, IFXU32Line *pPositionLine)=0 |
| virtual IFXRESULT IFXAPI | SetPositionLine (U32 index, const IFXU32Line *pPositionLine)=0 |
| virtual IFXRESULT IFXAPI | GetNormalLine (U32 index, IFXU32Line *pNormalLine)=0 |
| virtual IFXRESULT IFXAPI | SetNormalLine (U32 index, const IFXU32Line *pNormalLine)=0 |
| virtual IFXRESULT IFXAPI | GetDiffuseLine (U32 index, IFXU32Line *pDiffuseLine)=0 |
| virtual IFXRESULT IFXAPI | SetDiffuseLine (U32 index, const IFXU32Line *pDiffuseLine)=0 |
| virtual IFXRESULT IFXAPI | GetSpecularLine (U32 index, IFXU32Line *pSpecularLine)=0 |
| virtual IFXRESULT IFXAPI | SetSpecularLine (U32 index, const IFXU32Line *pSpecularLine)=0 |
| virtual IFXRESULT IFXAPI | GetMaterials (IFXAuthorMaterial **ppMaterials)=0 |
| virtual IFXRESULT IFXAPI | GetLineMaterials (U32 **ppLineMaterials)=0 |
| virtual IFXRESULT IFXAPI | GetMaterial (U32 index, IFXAuthorMaterial *pMaterial)=0 |
| virtual IFXRESULT IFXAPI | SetMaterial (U32 index, const IFXAuthorMaterial *pMaterial)=0 |
| virtual IFXRESULT IFXAPI | GetTexLines (U32 index, IFXU32Line **ppTexLines)=0 |
| virtual IFXRESULT IFXAPI | GetPositions (IFXVector3 **ppPositions)=0 |
| virtual IFXRESULT IFXAPI | GetNormals (IFXVector3 **ppNormals)=0 |
| virtual IFXRESULT IFXAPI | GetTexCoords (IFXVector4 **ppTexCoords)=0 |
| virtual IFXRESULT IFXAPI | GetDiffuseColors (IFXVector4 **ppDiffuseColors)=0 |
| virtual IFXRESULT IFXAPI | GetSpecularColors (IFXVector4 **ppSpecularColor)=0 |
| virtual IFXRESULT IFXAPI | GetPosition (U32 index, IFXVector3 *pVector3)=0 |
| virtual IFXRESULT IFXAPI | SetPosition (U32 index, const IFXVector3 *pVector3)=0 |
| virtual IFXRESULT IFXAPI | GetNormal (U32 index, IFXVector3 *pVector3)=0 |
| virtual IFXRESULT IFXAPI | SetNormal (U32 index, const IFXVector3 *pVector3)=0 |
| virtual IFXRESULT IFXAPI | GetDiffuseColor (U32 index, IFXVector4 *pColor)=0 |
| virtual IFXRESULT IFXAPI | SetDiffuseColor (U32 index, IFXVector4 *pColor)=0 |
| virtual IFXRESULT IFXAPI | GetSpecularColor (U32 index, IFXVector4 *pColor)=0 |
| virtual IFXRESULT IFXAPI | SetSpecularColor (U32 index, IFXVector4 *pColor)=0 |
| virtual IFXRESULT IFXAPI | GetTexLine (U32 layer, U32 index, IFXU32Line *pTextureLine)=0 |
| virtual IFXRESULT IFXAPI | SetTexLine (U32 layer, U32 index, const IFXU32Line *pTextureLine)=0 |
| virtual IFXRESULT IFXAPI | GetTexCoord (U32 index, IFXVector4 *pVector4)=0 |
| virtual IFXRESULT IFXAPI | SetTexCoord (U32 index, const IFXVector4 *pVector4)=0 |
| virtual IFXRESULT IFXAPI | GetLineMaterial (U32 index, U32 *pLineMaterial)=0 |
| virtual IFXRESULT IFXAPI | SetLineMaterial (U32 index, U32 lineMaterialID)=0 |
| virtual IFXVector4 IFXAPI | CalcBoundSphere ()=0 |
Detailed Description
This is the main interface for IFXAuthorLineSet.
Provides high-level information about a line set; namely, what attributes are present in the LineSet and how many elements can be found in each attribute array.
- Note:
- The associated IID is named IID_IFXAuthorLineSet.
Member Function Documentation
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::Allocate |
( |
const IFXAuthorLineSetDesc * |
pLineDesc |
) |
[pure virtual] |
|
|
|
Allocates all the necessary space required by the fully-populated IFXAuthorLineSet.
- Parameters:
-
| pLineDesc | The IFXAuthorLineSet data structure describing the properties of the line set. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pLineDesc was NULL |
| IFX_E_INVALID_RANGE | The number of materials or positions was less than one. |
| IFX_E_OUT_OF_MEMORY | There was insufficiant memory to allocate the line set. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXVector4 IFXAPI IFXAuthorLineSet::CalcBoundSphere |
( |
|
) |
[pure virtual] |
|
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::Copy |
( |
IFXREFIID |
interfaceID, |
|
|
void ** |
ppNewAuthorLineSet |
|
) |
[pure virtual] |
|
|
|
Creates a complete copy of the IFXAuthorLineSet and returns it with the specified interface.
- Parameters:
-
| interfaceID | The IID of the desired LineSet interface |
| ppNewAuthorLineSet | - a pointer to the new AuthorLineSet copy. |
- Returns:
- An IFXRESULT value.
- Return values:
-
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::Deallocate |
( |
|
) |
[pure virtual] |
|
|
|
Frees all data associated with the LineSet.
- Returns:
- An IFXRESULT value.
- Return values:
-
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetDiffuseColor |
( |
U32 |
index, |
|
|
IFXVector4 * |
pColor |
|
) |
[pure virtual] |
|
|
|
Retrieves a specific Diffuse vertex color from this lineset.
- Parameters:
-
| index | The index of the Diffuse vertex color to return |
| pColor | The requested color |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pColor was NULL |
| IFX_E_INVALID_RANGE | index is larger than the number of diffuse vertex colors stored in the lineset. |
- Note:
- Colors are represented in BGRA order.
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetDiffuseColors |
( |
IFXVector4 ** |
ppDiffuseColors |
) |
[pure virtual] |
|
|
|
Returns the pointer to the array of Diffuse Vertex Colors for this line set.
- Parameters:
-
| ppDiffuseColors | The array of IFXVector4s containing the diffuse vertex colors used by this line set. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppDiffuseColors was NULL. |
| IFX_E_INVALID_RANGE | The line set does not contain this attribute. m_numDiffuseColors in the IFXAuthorLineSetDesc is equal to zero(0). |
- Note:
- Colors are represented in BGRA order.
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetDiffuseLine |
( |
U32 |
index, |
|
|
IFXU32Line * |
pDiffuseLine |
|
) |
[pure virtual] |
|
|
|
Retrieves a specific Diffuse vertex color Line index.
- Parameters:
-
| index | The index of the diffuse Line to return |
| pDiffuseFace | The diffuse line containing the diffuse vertex color indices. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pDiffuseLine was NULL |
| IFX_E_INVALID_RANGE | The index is greater than the number of diffuse vertex color Line in the LineSet. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetDiffuseLines |
( |
IFXU32Line ** |
ppDiffuseLine |
) |
[pure virtual] |
|
|
|
Returns the pointer to the LineSet Diffuse index array.
- Parameters:
-
| ppDiffuseLine | The array of IFXLine specifying the indices of the diffuse colors used by each vertex on each line. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppDiffuseLine was NULL. |
| IFX_E_INVALID_RANGE | The LineSet does not contain this attribute. NumDiffuseColors in the IFXLine is equal to zero(0). |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetLineMaterial |
( |
U32 |
index, |
|
|
U32 * |
pLineMaterial |
|
) |
[pure virtual] |
|
|
|
Retrieves a specific Material line ID.
- Parameters:
-
| index | The index of the Line for which we want the material ID |
| puFaceMaterial | The returned material ID. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | puFaceMaterial was NULL |
| IFX_E_INVALID_RANGE | index was larger than the number of lines in the LineSet. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetLineMaterials |
( |
U32 ** |
ppLineMaterials |
) |
[pure virtual] |
|
|
|
Returns the pointer to the Line Material index array.
- Parameters:
-
| ppLineMaterials | The array of U32es specifying the material index to use on each line of the lineset |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppFaceMaterials was NULL. |
| IFX_E_INVALID_RANGE | The lineset does not contain this attribute. NumMaterials in the IFXAuthorLineDesc is equal to zero(0). |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetMaterial |
( |
U32 |
index, |
|
|
IFXAuthorMaterial * |
pMaterial |
|
) |
[pure virtual] |
|
|
|
Retrieves a specific material by index.
- Parameters:
-
| index | The index of the material to return |
| pMaterial | A pointer to the material. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pMaterial was NULL. |
| IFX_E_INVALID_RANGE | The index is invalid |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetMaterials |
( |
IFXAuthorMaterial ** |
ppMaterials |
) |
[pure virtual] |
|
|
|
Returns the pointer to the Material Definition Array.
- Parameters:
-
| ppMaterials | The pointer to the material definition array |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppMaterials was NULL. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetMaterialsLines |
( |
U32 ** |
ppMaterialLines |
) |
[pure virtual] |
|
|
|
Returns the pointer to the LineSet Materials index array.
- Parameters:
-
| ppMaterialLines | The array of IFXLine specifying the indices of the materials used by each vertex on each line. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppTexCoordLines was NULL. |
| IFX_E_INVALID_RANGE | The LineSet does not contain this attribute. NumMaterials in the IFXLine is equal to zero(0). |
Implemented in CIFXAuthorLineSet. |
|
|
Returns the maximum resolution LineSet description.
- Returns:
- A pointer to an IFXAuthorLineSetDesc structure describing the full-resolution representation of the LineSet.
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetNormal |
( |
U32 |
index, |
|
|
IFXVector3 * |
pVector3 |
|
) |
[pure virtual] |
|
|
|
Retrieves a specific Normal from this lineset.
- Parameters:
-
| index | The index of the normal to return |
| pVector3 | The requested normal |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pVector3 was NULL |
| IFX_E_INVALID_RANGE | index is larger than the number of normals stored in the lineset. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetNormalLine |
( |
U32 |
index, |
|
|
IFXU32Line * |
pNormalLine |
|
) |
[pure virtual] |
|
|
|
Retrieves a specific Normal Line index.
- Parameters:
-
| index | The index of the normal Line to return |
| pNormalLine | The returned line containing normal indices |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pNormalLine was NULL |
| IFX_E_INVALID_RANGE | The index is greater than the number of normal Line in the lineset. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetNormalLines |
( |
IFXU32Line ** |
ppNormalLine |
) |
[pure virtual] |
|
|
|
Returns the pointer to the LineSet Normal index array.
- Parameters:
-
| ppNormalLine | The array of IFXLine specifying the indices of the normals used by each vertex on each line. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppNormalLine was NULL |
| IFX_E_INVALID_RANGE | The LineSet does not contain this attribute. NumNormals in the IFXAuthorLineSetDesc is equal to zero(0). |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetNormals |
( |
IFXVector3 ** |
ppNormals |
) |
[pure virtual] |
|
|
|
Returns the pointer to the Normal array for this line set.
- Parameters:
-
| ppNormals | The array of IFXVector3s containing all the normals used in this line set. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppNormals was NULL. |
| IFX_E_INVALID_RANGE | The mesh does not contain this attribute. m_numNormals in the IFXAuthorLineSetDesc is equal to zero(0). |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetNumAllocatedTexLineLayers |
( |
U32 * |
pLayers |
) |
[pure virtual] |
|
|
|
Returns the number of texline layers, where texLines layers are allocated on demand to save memory.
- Parameters:
-
| pLayers | The number of layers allocated |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pLayers was NULL |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetPosition |
( |
U32 |
index, |
|
|
IFXVector3 * |
pVector3 |
|
) |
[pure virtual] |
|
|
|
Retrieves a specific vertex position from the Line Set.
- Parameters:
-
| index | The index of the vertex position to return |
| pVector3 | The position of the specified vertex |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pVector3 was NULL |
| IFX_E_INVALID_RANGE | index is larger than the number of vertex positions stored in the line set. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetPositionLine |
( |
U32 |
index, |
|
|
IFXU32Line * |
pPositionLine |
|
) |
[pure virtual] |
|
|
|
Retrieves a specific Position line index.
- Parameters:
-
| index | The index of the position line to return |
| pPositionLine | The returned line containing position indices |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pPositionLine was NULL |
| IFX_E_INVALID_RANGE | The index is greater than the number of position line segm in the lineset. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetPositionLines |
( |
IFXU32Line ** |
ppPositionLine |
) |
[pure virtual] |
|
|
|
Returns the pointer to the Line Position index array.
- Parameters:
-
| ppPositionLine | The array of IFXLine specifying the indices of the positions for each vertex on each line. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppPositionLine was NULL. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetPositions |
( |
IFXVector3 ** |
ppPositions |
) |
[pure virtual] |
|
|
|
Returns the pointer to the Position Array for this line set.
- Parameters:
-
| ppPositions | The array of IFXVector3s containing all the vertex positions used in this line set. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppPositions was NULL. |
| IFX_E_INVALID_RANGE | The line set does not contain this attribute. m_numPositions in the IFXAuthorLineSetDesc is equal to zero(0). |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetSpecularColor |
( |
U32 |
index, |
|
|
IFXVector4 * |
pColor |
|
) |
[pure virtual] |
|
|
|
Retrieves a specific Specular vertex color from this lineset.
- Parameters:
-
| index | The index of the specular vertex color to return |
| pColor | The requested color value |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pColor was NULL |
| IFX_E_INVALID_RANGE | index is larger than the number of specular vertex colors stored in the lineset. |
- Note:
- Colors are represented in BGRA order.
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetSpecularColors |
( |
IFXVector4 ** |
ppSpecularColor |
) |
[pure virtual] |
|
|
|
Returns the pointer to the array of Specular Vertex Colors for this line set.
- Parameters:
-
| ppSpecularColor | The array of IFXVector4s containing the specular vertex colors used by this line set. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppSpecularColors was NULL. |
| IFX_E_INVALID_RANGE | The line set does not contain this attribute. m_numSpecularColors in the IFXAuthorLineSetDesc is equal to zero(0). |
- Note:
- Colors are represented in BGRA order.
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetSpecularLine |
( |
U32 |
index, |
|
|
IFXU32Line * |
pSpecularLine |
|
) |
[pure virtual] |
|
|
|
Retrieves a specific Specular line index.
- Parameters:
-
| index | The index of the specular Line to return |
| pSpecularFace | The specular Line containing the specular vertex color indices. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pSpecularLine was NULL |
| IFX_E_INVALID_RANGE | The index is greater than the number of specular vertex color Line in the LineSet. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetSpecularLines |
( |
IFXU32Line ** |
ppSpecularLine |
) |
[pure virtual] |
|
|
|
Returns the pointer to the LineSet Specular index array.
- Parameters:
-
| ppSpecularFaces | The array of IFXLine specifying the indices of the specular colors used by each vertex on each line. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppSpecularFaces was NULL. |
| IFX_E_INVALID_RANGE | The LineSet does not contain this attribute. NumSpecularColors in the IFXLine is equal to zero(0). |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetTexCoord |
( |
U32 |
index, |
|
|
IFXVector4 * |
pVector4 |
|
) |
[pure virtual] |
|
|
|
Retrieves a specific Texture Coordinate from this lineset.
- Parameters:
-
| index | The index of the texture coordinate to return |
| pVector4 | The requested texture coordinate |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pVector4 was NULL |
| IFX_E_INVALID_RANGE | index is larger than the number of texture coordinates stored in the lineset. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetTexCoords |
( |
IFXVector4 ** |
ppTexCoords |
) |
[pure virtual] |
|
|
|
Returns the pointer to the array of Texture Coordinates for this line set.
- Parameters:
-
| ppTexCoords | The array of IFXVector4s containing the texture coordinates used by this line set. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppTexCoords was NULL. |
| IFX_E_INVALID_RANGE | The mesh does not contain this attribute. m_numTexCoords in the IFXAuthorLineSetDesc is equal to zero(0). |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetTexCoordsLines |
( |
IFXU32Line ** |
ppTexCoordLines |
) |
[pure virtual] |
|
|
|
Returns the pointer to the LineSet Texture Coordinates index array.
- Parameters:
-
| ppTexCoordLines | The array of IFXLine specifying the indices of the texture coords used by each vertex on each line. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppTexCoordLines was NULL. |
| IFX_E_INVALID_RANGE | The LineSet does not contain this attribute. NumTextureCoords in the IFXLine is equal to zero(0). |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetTexLine |
( |
U32 |
layer, |
|
|
U32 |
index, |
|
|
IFXU32Line * |
pTextureLine |
|
) |
[pure virtual] |
|
|
|
Retrieves a specific Texture line index.
- Parameters:
-
| layer | The texture coordinate layer this line is from |
| index | The index of the texture line to return |
| pTextureLine | The texture line containing the texture coordinate indices |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pTextureFace was NULL |
| IFX_E_INVALID_RANGE | index is greater than the number of texture coordinate lines in the line set, the line set has no texture coordinates, or layer is greater than IFXMAX_TEX_COORD_LAYERS. |
| IFX_E_OUT_OF_MEMORY | We were not able to allocate memory for a new texture layer. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::GetTexLines |
( |
U32 |
index, |
|
|
IFXU32Line ** |
ppTexLines |
|
) |
[pure virtual] |
|
|
|
Returns the pointer to the Face Texture index array.
- Parameters:
-
| index | The index of the texture layer to recover |
| ppTexLines | The array of IFXU32Lines specifying the indices of the texture coordinates used by each vertex on each line for the specified texture layer. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | ppTexLines was NULL. |
| IFX_E_INVALID_RANGE | The Texture Layer index is invalid. The value specified for index may be out of range. This parameter cannot be less than zero(0) or greater than IFXMAX_TEX_COORD_LAYERS. |
| IFX_E_INVALID_RANGE | The mesh does not contain this attribute. m_numTexCoords in the IFXAuthorLineSetDesc is equal to zero(0). |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::Reallocate |
( |
const IFXAuthorLineSetDesc * |
pLineDesc |
) |
[pure virtual] |
|
|
|
Reallocates the LineSet based on the new LineSet description.
- Parameters:
-
| pLineDesc | The new properties of the LineSet. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pLineDesc was NULL |
| IFX_E_INVALID_RANGE | The number of materials or positions was less than one. |
| IFX_E_OUT_OF_MEMORY | There was insufficient memory to allocate the LineSet. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::SetDiffuseColor |
( |
U32 |
index, |
|
|
IFXVector4 * |
pColor |
|
) |
[pure virtual] |
|
|
|
Sets a specific Diffuse vertex color for this lineset.
- Parameters:
-
| index | The index of the diffuse vertex color to set |
| pColor | The new diffuse vertex color to store |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pColor was NULL |
| IFX_E_INVALID_RANGE | index is larger than the number of diffuse vertex colors stored in the lineset. |
- Note:
- Colors are represented in BGRA order.
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::SetDiffuseLine |
( |
U32 |
index, |
|
|
const IFXU32Line * |
pDiffuseLine |
|
) |
[pure virtual] |
|
|
|
Set a specific Diffuse Line index.
- Parameters:
-
| index | The index of the diffuse Line to set |
| pDiffuseFace | The diffuse Line containing the diffuse vertex color index data to set |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pDiffuseLine was NULL |
| IFX_E_INVALID_RANGE | The index is greater than the number of diffuse vertex color Line in the LineSet. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::SetLineMaterial |
( |
U32 |
index, |
|
|
U32 |
lineMaterialID |
|
) |
[pure virtual] |
|
|
|
Sets a specific Line Material ID.
- Parameters:
-
| index | The index of the line on which we want to set the material ID. |
| faceMaterialID | The material ID to set on the line. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_RANGE | index was larger than the number of lines in the LineSet. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::SetLineSetDesc |
( |
const IFXAuthorLineSetDesc * |
pLineSetDesc |
) |
[pure virtual] |
|
|
|
Sets the current IFXLineSetDesc description (as opposed to the "MaxLineSetDesc," which is set when the LineSet is allocated).
- Parameters:
-
| pLineSetDesc | The new IFXLineSetDesc description |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_RANGE | One of the values in pLineSetDesc is larger than the IFXLineSetDesc used to allocate the LineSet, and/or the number of materials is not the same as when the LineSet was allocated. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::SetMaterial |
( |
U32 |
index, |
|
|
const IFXAuthorMaterial * |
pMaterial |
|
) |
[pure virtual] |
|
|
|
Sets a specific material line.
- Parameters:
-
| index | The index of the material to set |
| pMaterial | A pointer to the material to assign to this index. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pMaterial was NULL |
| IFX_E_INVALID_RANGE | The index is greater than the number of materials used by the lineset. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::SetNormal |
( |
U32 |
index, |
|
|
const IFXVector3 * |
pVector3 |
|
) |
[pure virtual] |
|
|
|
Sets a specific Normal for this lineset.
- Parameters:
-
| index | The index of the normal to set |
| pVector3 | The new value of the normal |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pVector3 was NULL |
| IFX_E_INVALID_RANGE | index is larger than the number of normals stored in the lineset. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::SetNormalLine |
( |
U32 |
index, |
|
|
const IFXU32Line * |
pNormalLine |
|
) |
[pure virtual] |
|
|
|
Set a specific Normal Line index.
- Parameters:
-
| index | The index of the normal line to return |
| pNormalLine | The normal Line containing the normal index data to set. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pNormalLine was NULL |
| IFX_E_INVALID_RANGE | The index is greater than the number of normal Line in the LineSet. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::SetPosition |
( |
U32 |
index, |
|
|
const IFXVector3 * |
pVector3 |
|
) |
[pure virtual] |
|
|
|
Sets a specific vertex position for this Lineset.
- Parameters:
-
| index | The index of the vertex position to set |
| pVector3 | The new position value for this vertex |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pVector3 was NULL |
| IFX_E_INVALID_RANGE | index is larger than the number of vertex positions stored in the lineset. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::SetPositionLine |
( |
U32 |
index, |
|
|
const IFXU32Line * |
pPositionLine |
|
) |
[pure virtual] |
|
|
|
Sets a specific Position Line index.
- Parameters:
-
| index | The index of the position line to set |
| pPositionLine | The position Line containing the position index data to set. |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pPositionLien was NULL |
| IFX_E_INVALID_RANGE | The index is greater than the number of position lines in the lineset. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::SetSpecularColor |
( |
U32 |
index, |
|
|
IFXVector4 * |
pColor |
|
) |
[pure virtual] |
|
|
|
Sets a specific Specular vertex color of this lineset.
- Parameters:
-
| index | The index of the specular vertex color to set |
| pColor | The new specular vertex color to store |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pColor was NULL |
| IFX_E_INVALID_RANGE | index is larger than the number of specular vertex colors stored in the lineset. |
- Note:
- Colors are represented in BGRA order.
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::SetSpecularLine |
( |
U32 |
index, |
|
|
const IFXU32Line * |
pSpecularLine |
|
) |
[pure virtual] |
|
|
|
Set a specific Specular Line index.
- Parameters:
-
| index | The index of the specular Line to set |
| pSpecularFace | The specular line containing the specular vertex color index data to set |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pSpecularLine was NULL |
| IFX_E_INVALID_RANGE | The index is greater than the number of specular vertex color Line in the LineSet. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::SetTexCoord |
( |
U32 |
index, |
|
|
const IFXVector4 * |
pVector4 |
|
) |
[pure virtual] |
|
|
|
Sets specific Texture Coordinate for this lineset.
- Parameters:
-
| index | The index of the texture coordinate to set |
| pVector4 | The new texture coordinate value to store |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pVector4 was NULL |
| IFX_E_INVALID_RANGE | index is larger than the number of texture coordinates stored in the lineset. |
Implemented in CIFXAuthorLineSet. |
| virtual IFXRESULT IFXAPI IFXAuthorLineSet::SetTexLine |
( |
U32 |
layer, |
|
|
U32 |
index, |
|
|
const IFXU32Line * |
pTextureLine |
|
) |
[pure virtual] |
|
|
|
Sets a specific Texture Line index.
- Parameters:
-
| layer | The texture coordinate layer into which to place the line |
| index | The index of the texture line to set |
| pTextureLine | The texture line containing the texture coordinate indices to set in the line set |
- Returns:
- An IFXRESULT value.
- Return values:
-
| IFX_OK | No error. |
| IFX_E_INVALID_POINTER | pTextureFace was NULL |
| IFX_E_INVALID_RANGE | index is greater than the number of texture coordinate lines in the line set, the line set has no texture coordinates, or layer is greater than IFXMAX_TEX_COORD_LAYERS. |
| IFX_E_OUT_OF_MEMORY | We were not able to allocate memory for a new texture layer. |
Implemented in CIFXAuthorLineSet. |
© 1999 - 2006 Intel Corporation. All rights reserved.
* Other names and brands may be claimed as the property of others.
|
|


Using custom background knowledge¶
One of the key novelties of autoBOT is the use of triplet-based graph databases as background knowledge (i.e. knowledge graphs). As shown in the examples, when doing the initialization:
autoBOTLibObj = autoBOTLib.GAlearner(
train_sequences, # input sequences
train_targets, # target space
memory_storage=
"./memory", # tripled base for concept features
representation_type="neurosymbolic") # or symbolic or neural
There is a dedicated parameter called memory_storage, which is a path that links to a file that contains the triplets like the following few examples:
/a/[/r/CapableOf/,/c/en/context/,/c/en/matter_lot/] /r/CapableOf /c/en/context /c/en/matter_lot {"dataset": "/d/conceptnet/4/en", "license": "cc:by/4.0", "sources": [{"activity": "/s/activity/omcs/omcs1_possibly_free_text", "contributor": "/s/contributor/omcs/comdotatdotcom"}], "surfaceEnd": "matter a lot", "surfaceStart": "context", "surfaceText": "[[context]] can [[matter a lot]]", "weight": 1.0} /a/[/r/DerivedFrom/,/c/de/context/,/c/de/tex/n/] /r/DerivedFrom /c/de/context /c/de/tex/n {"dataset": "/d/wiktionary/de", "license": "cc:by-sa/4.0", "sources": [{"contributor": "/s/resource/wiktionary/de", "process": "/s/process/wikiparsec/2"}], "weight": 1.0} /a/[/r/DerivedFrom/,/c/en/acontextual/,/c/en/contextual/] /r/DerivedFrom /c/en/acontextual /c/en/contextual {"dataset": "/d/wiktionary/en", "license": "cc:by-sa/4.0", "sources": [{"contributor": "/s/resource/wiktionary/en", "process": "/s/process/wikiparsec/2"}], "weight": 1.0}
The database is formatted according to the conceptnet. Note that you only need the first few columns of this file (subject-predicate-object). To use your own knowledge, simply provide a custom triplet database.


{% extends 'main-documentation-layout.html' %} {% block documentation-body %}
Problems may have one or more languages which usually define:
Code examples:


{% extends "generic.html" %} {% block header %} {{ entry.title }} {% endblock %} {% load static %} {% if error_message %}
{{ error_message }}
{% endif %} {% block content %}This entry describes the basic setup for an Nvidia Jetson Nano. The Nano is only connected using micro USB and uses a micro SD; however a keyboard, mouse, and HDMI were used to configure initial board bring up.
https://developer.nvidia.com/jetson-nano-sd-card-image-r3231
https://www.balena.io/etcher/
cd ~/Downloads/
unzip balena-etcher-electron-1.5.71-linux-x64.zip
./balenaEtcher-1.5.71-x64.AppImage
select storage device
select flash
May require a reboot and then verify ubuntu bootup and perform initial configuration.
Test the setup by pinging and ssh'ing in.
ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.836 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.809 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.907 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=64 time=0.899 ms
64 bytes from <IP_ADDRESS>: icmp_seq=5 ttl=64 time=1.00 ms
ssh<EMAIL_ADDRESS><EMAIL_ADDRESS>password:
Welcome to Ubuntu 18.04.3 LTS (GNU/Linux 4.9.140-tegra aarch64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
This system has been minimized by removing packages and content that are
not required on a system that users do not log into.
To restore this content, you can run the 'unminimize' command.
215 packages can be updated.
114 updates are security updates.
Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings
Last login: Sun Jan 28 11:05:23 2018 from <IP_ADDRESS>
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.
{% endblock %}


Widely regarded as one of the best Formula One drivers of all time, German-born Michael Schumacher is probably best known for his eleven-year stint at Ferrari, where he won five consecutive F1 titles between 2000 and 2004.
Despite
being retired since 2012, Schumacher still holds many of Formula One's driver records, including most championships, race victories, fastest laps, pole positions and most races won in a single season.
On 29 December 2013, Schumacher was skiing with his 14-year-old son Mick descending the Combe de Saulire below the Dent de Burgin above Méribel in the French Alps. While crossing an unsecured off-piste area between Piste Chamois and Piste Mauduit
he fell and hit his head on a rock, sustaining a head injury despite wearing a ski helmet.
According to his physicians, he would most likely have died had he not been wearing a helmet. Schumacher was put into a medically induced
coma because of traumatic brain injury; his doctors reported on 7 March 2014 that his condition was stable.
On 4 April 2014, Schumacher's agent reported that he was showing "moments of consciousness" as he was gradually withdrawn
from the medically induced coma, adding to reports by relatives of "small encouraging signs" over the preceding month. In mid-June he was moved from intensive care into a rehabilitation ward.
By 16 June 2014, Schumacher had regained
consciousness and left Grenoble Hospital for further rehabilitation at the University Hospital (CHUV) in Lausanne, Switzerland. On 9 September 2014, Schumacher left CHUV and was brought back to his home for further rehabilitation.
In November 2014, it was reported that Schumacher was "paralysed and in a wheelchair"; he "cannot speak and has memory problems". In a video interview released in May 2015, Schumacher's manager Sabine Kehm said that his condition is slowly
improving "considering the severeness of the injury he had".
In September 2016, Felix Damm, Schumacher's lawyer, told a German court that his client "cannot walk", in response to false reports from December 2015 in German publication
Die Bunte that he could "walk a couple of steps".


Transparency data
Academies project update: Weald of Kent and Valley Invicta
EFA letters to Weald of Kent Academy Trust and Valley Invicta Academy Trust with a decision on proposals for a grammar school in Kent.
Details
On 13 December 2013, Education Funding Agency (EFA) wrote to Weald of Kent Academy Trust and Valley Invicta Academy Trust with a decision on their proposals for grammar school provision in Sevenoaks, Kent.
The assessment is that the proposals do not represent an expansion of the existing schools and therefore cannot be approved.


Doesn't have authorization to see this page
If you found this page get back
If nothing works call André but don't wake him
Click here to login


KRIB specification
Basics
A
B
C
D
Indent with tab represent tree structure intuitively. A has a child B. B has a child C and D.
A
B
C
D
E
F
All the leaves of the tree are regarded as objects and others are regarded as predicates in RDF. In the KRIB representation above, C, D and F is the objects.
Interpretation of objects
Description
Thatching is the craft of building a roof with dry vegetation such as straw, water reed, sedge (Cladium mariscus), rushes, heather, or palm fronds, layering the vegetation so as to shed water away from the inner roof.
Object with no bracket is regarded as a literal. So, the predicate and object in turtle is like below:
ont:Description "Thatching is the craft of building a roof with dry vegetation such as straw, water reed, sedge (Cladium mariscus), rushes, heather, or palm fronds, layering the vegetation so as to shed water away from the inner roof.";
If the object is with bracket, and has the corresponding entry in the dictionrary, that object is regarded as a IRI reference. The example in KRIB and turtle is like below:
References
[Thatching]
ont:References <https://dbpedia.org/resource/Thatching>;
The label information is provided by the dictionary also.
<https://dbpedia.org/resource/Thatching> rdfs:label "Thatching".
If the object includes bracheted word, multiple graphs are output.
Examples
[Roundhouse], Iron Age European
ont:Examples "Roundhouse, Iron Age European";
ont:Examples <https://dbpedia.org/resource/Roundhouse_(dwelling)>;
This interpretation makes the predicate an annotation property. Because that cannot be ObjectProperty or DataProperty anymore. Therefore, the semantics of the predicate is automatically weakened. See discussion in OWL documentation for the detail.
For annotations properties note that annotations are not "semantic-free" under the OWL 2 RDF-Based Semantics. Just like every other triple or set of triples occurring in an RDF graph, an annotation is assigned a truth value by any given OWL 2 RDF-Based interpretation. Hence, although annotations are meant to be "semantically weak", i.e., their formal meaning does not significantly exceed that originating from the RDF Semantics specification, adding an annotation may still change the meaning of an ontology. A similar discussion holds for statements that are built from ontology properties, such as owl:imports, which are used to define relationships between two ontologies.
Bracketed object in the middle of the branch
A
B
[C]
D
E
F
G
[H]
I
J
K
L
M
N
Bracket is only allowed to object, in other words, a bracketed word is regarded as object even if that appears in the middle of the branch. This allows you to describe complecated data, as much as JSON.
common.ttl
common.ttl placed in the same directory with KRIB file is regarded as a common additional prefixes and triples. `entry:` and `prop:` prefix are the mandatory in KRIB. Subjects and Objects of instances are in the `entry:` namespace and Predicates are in the `prop:` namespace.Comments
There is no comment notation available in KRIB.Templating(beta)
Each class, which is the value of Type can have a template for its instance.Type
Map
Title
Kuala Lumpur
Latitude
3.1412
Longitude
101.68653
Type
Class
Title
Map
EJS
<iframe src="https://maps.google.com/maps?q=<?= Latitude ?>,<?= Longitude ?>&hl=en&z=6&output=embed" width="600" height="450" frameborder="0" style="border:0" allowfullscreen></iframe>
Entity Linking
You can implemant your own logic to resolve entity mentions, which task is called "Entity linking" in NLP (Natural Language Processing, one of computer science domains).
Addition to the surface string of entity mention, you can make use of (1) the path to it and (2) the list of all the object literal in the item.


3 items
China
UK
US
DE
ES
Login
Home
Products
Technique
Product1
Product2
Product3
Product4
Consumers
Blog
About us
Our·Team
Latest·News
eShop
Contact·Us
What would you think about
When you are walking in the dark night in a rainy day?
If you feel afraid
You may need an umbrella which could show you the way.
It is not an ordinary umbrella
It will shine at dark night.
1
2
3
Create
high-quality
brand, cast
first-class
credit.
With a
conscience
to do business, with
good faith
to create the future.
love
Dreaming
, strive for
Innovation
, pursue
Artistry
, down to
Earth
.


Mechanical Parts:
Castings
Aluminium and High Pressure Diecasting
Alumium Gravity Diecasting
Sand and Permanent Mould Castings
Investment Castings (Lost wax)
Metal Working
Pressings and Stampings
Fabrications and Assemblies
Precision CNC machined parts
Turned parts
Cold Formed Parts
Forgings
Open/Closed Die. Forgings
Aluminium Forgings
Steel Forgings
Stainless Steel Forgings
Example: Mechanical Parts
Tooling:
Plastic Injection Moulds
Stamping Tools
Gears & Gearboxes
Ceramics & Composites
Plastics
Rubber Products
Rapid Prototyping
Selective Laser Sintering (SLS)
Urethane/Vacuum Casting
Rapid Injection Molding
Example: Tooling
Electrical & Electronics Parts:
Design & Layout Services
PCB/PCBA
Cable Assemblies
Box Build/Integration
Magnets/Motors/Stators
Example: Electrical & Electronics Parts
Testing Services and Turnkey Systems:
Materials Testing
Components Testing
Castings Testing
Gears/Gearboxes Testing
Assemblies & TurnkeySystems
Subassemblies
Electromechanical Assemblies
Turnkey Systems
Factory Automation
Test Equipment
Example: Testing Services and Turnkey Systems


When to self-isolate
Advice about when you should self-isolate and when it becomes a legal requirement
- You know someone who has Covid symptoms or who has tested positive for Covid-19
- You have symptoms that might mean you have Covid-19 or have got it again
- You have requested or taken a Covid-19
- You have been told to self-isolate by NHS Test and Trace
- You have been told to self-isolate by the NHS Covid-19 app
- You have been received an NHS Covid-19 app venue alert
Cross links
Page last reviewed: 21 December 2020
Next review due: 21 December 2020


false
FireFTP
'
Nature Boy
'
designed by
Mime Čuvalo
in
Croatia
SSH component is ported from
Paramiko
<IP_ADDRESS>,
created by
Robey Pointer


Full Stack Developer
A motivated adaptable and responsible Mathematics and computing graduate,currently at Moringa school pursuing software engineering,am looking forward seeking position which will utilize the professional and technical skills developed through the past work experiences in this field. I have a methodical, customer-focused approach to work and a strong drive to see thing to completion.
The pet project is a site which contains my favorite pet,which is a German Shepherd dog and more details about it together with it characteristics. Also contains the subscription button to the newsletter via the email where one can inquire more details.The Programming languages used to make the application are HTML and CSS
My favorite band ia a project that is featuring Sauti sol band with there collection of music which can be downloaded and also each member of the band biography. The Programming languages used to make the application are HTML and CSS
J.N.K Dairy farm is a farm that deal with the milk production in large quantity we have various type of breeds that are able to give us high quantity of milk.We have four shed for our cows where each shed produces it amount of milk in term of litter have. We a land where we grow our fodders in order to feed our cows and also our veterinary who help in the looking of the health of all animals and providing them with the required nutrients so that they cannot lower the production and the quality of the milk.The programming languages used are HTML,CSS and Javascript.
The three above program have used HTML for the structuring of the pages and the CSS to style the pages.
Coordinator marketing and communication
I enrolled in Meru University of Science and Technology to pursue Mathematics and Computer Science where I specialized in Applied Mathematics. After graduation I realized I had a lot of gaps on my side of computing and had to work on it. I was looking forward to solving various applied Mathematics problem using various programs and software that inspired me to enroll in computing program at Moringa School. Through my volunteer in the Nairobi City County Youth Center I realized that most Youths have passions and desire to pursue the tech related fields but lack capital resource was a challange. Due to my inadequate experience in the field could not be able to introduce some programs like web development for free so as to enlighten the youth,this inspired me to have the passion to learn the same.
To work in a busy organization that allows for creativity and innovation on provision of quality services by application of the Mathematical and IT knowledge and skills acquired. To become an expert in analysis and able to bring out solutions that can solve todays real life challenges. To continually develop and use my skills to provide the best service delivery to the organization and to the society. To be a leader and role model in upholding the professional ethics and integrity.
Meeting and socializing with new friends and travelling to new places in search of new ideas.
Reading magazines.
Playing and watching football.


BEFORE THE NATIONAL GREEN TRIBUNAL (WESTERN ZONE) BENCH, PUNE M.A.NO.65/2014 IN APPLICATION NO.13/2014 CORAM : HON'BLE SHRI JUSTICE V.R. KINGAONKAR (JUDICIAL MEMBER) HON'BLE DR. AJAY A.DESHPANDE (EXPERT MEMBER) B E T W E E N: AMIT MARU, 22, Opp.Block No.4/5, BhanjibhaiRathod Marg, Tardeo,Tulsiwadi, Mumbai-400 034. ....APPLICANT AND 1. Secretary, Ministry of Environment & Forest ParyavaranBhavan,CGO Complex, Lodi Road, New Delhi-110003. 2. MEMBER SECRETARY, National Coastal Zone Management Authority, ParyavaranBhavan,CGO Complex, Lodi Road, New Delhi-110003. Page 1 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) 3. SECRETARY, Environment Department, Room No. 217, 2nd Floor, Mantralaya Mumbai-400032. 4. MEMBER SECRETARY MaharashtraCoastal Zone Management Authority, New Administrative Bldg. Opp. Mantralaya, Mumbai-400 032. 5. THE REGIONAL DIRECTOR Central Groundwater Board, Central Region, N.S.Bldg. Civil Lines, Nagpur-440 001.(Maharashtra). 6. CENTRAL GRONDWATE BOARD State Unit Office, 217/11, KendriyaSadan, 'B' Wing, GPOA, First Floor, Akurdi, Pune-411 044. 7. MEMBER SECRETARY THE MAHARASHTRA POLLUTION CONTROL BOARD Mumbai. 8. THE EXECUTIVE ENGINEER, Building Proposal Department (Western Suburbs) Municipal Corporation of Greater Mumbai, PurskritiBhawan, 90-feet road, Kandivli (E), Mumbai-400 101. 9. WINDSOR REALITY PVT. LTD Off CST Road, Near BandraKurla Complex, Santacruz( E) Mumbai-400 098. .........RESPONDENTS Counsel for Applicant(s) Mr. Aditya Pratap, a/w A.B.Walunj Advocates Page 2 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) Counsel for Respondent(s): Ms. Shweta Busar, Advocate, holding for Ranjan Nehru Advocate for Respondent No.1. Mr. D.M.Gupte a/w Supriya Dangare Advocates for Respondent Nos.2 to 4. Mrs.Ujwala Pawar, DGP/ Mr.A.S.Mulchandani AGP, S.S.P.Mishra, CCo, for Respondent Nos.5, 6. Mr. Saurabh Kulkarni, a/w Supriya Dangare Advocates for Respondent No.7. Mr. Sameer Khale,a/w Rahul Garg, Chirag Chavan, Makarand Rodge Advocates for Respondent No.8 Mr. T. N. Subramoniam a/w Saket Mone, Suresh D. Shettiyar, Sunil Bhat Advocates i/b Vidhi Partners for Respondent No.9. Date: October 1st, 2014 J U D G M E N T
1. This is an Application filed by Project Proponent, raising preliminary objection regarding maintainability of Main Application (Application No.13 of 2014), on the ground that said Application is barred by Limitation as well Applicant has no locus to file it, and hence the same is liable to be dismissed. Secondly, that Original Applicant (Amit Maru) is not an 'aggrieved person' and, therefore, such Application under Section 14(1) (2) read with Page 3 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) Sections 15 and 18 of the National Green Tribunal Act, 2010, is not maintainable at his behest.
2. The Project Proponent (M/s Windosor Reality Pvt Ltd), has come out with a case that the plans for construction of commercial building were issued by the Planning Authority on 7.7.1993. The project work was started long back. The construction work was going on for about a period almost over and above 8/10 years. The Project Proponent alleges that the building having 28 floors, 3 level podium and 2 voids, in total 33 floors, have been constructed and that by itself must be deemed to be a notice to the Applicant. So, it is not open for the Applicant now to raise such a dispute under false and frivolous allegations that 'cause of action' to file the Application has arisen first on 23rd October, 2013. The Applicant cannot raise such a dispute at a belated stage by giving goby to the specific provisions of Section 14 (3) read with Section 18 of the National Green Tribunal Act, 2010. The Hon'ble Bombay High Court and Hon'ble Supreme Court interpreted the special enactments like the Arbitration Act, 1998, the Electricity Act, 2003 and held that where a statute prescribes shorter period of limitation and different scheme of limitation is provided under such a Statute, the provisions of the Limitation Act, 1963, are excluded and the Tribunal must apply the period of Page 4 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) limitation as prescribed under the special enactment while exercising its powers. So, when the special provision is set out under Section 14(3) of the NGT Act, then time cannot be extended any more by Application of Section 5 of the Limitation Act, 1963, or any such analogues provision.
3. The jurisdiction exercised by the NGT is not equivalent to writ jurisdiction available to the Hon'ble High Court under Article 226 of the Constitution and as such declaratory relief sought by the original Applicant (Amit Maru) cannot be granted since he is not 'aggrieved person' as such and hence, cannot maintain the Application for want of locus standi. For this reason also, the Application is liable to be dismissed.
4. The Project Proponent would submit that the plans of the construction were sanctioned by the Planning Authority on 7.7.1993 and the construction work was undertaken before about ten (10) years of filing of the Application. It is stated that the construction work of the building was very much going on within sight of the Applicant since he is resident of nearby locality and could have knowledge of the same. It is stated that the Application is filed with ill-motive to pressurize the Project Proponent in order to shell out certain amount without any reason. In other words, it is stated that the Page 5 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) Application is filed with a view to blackmail the Project Proponent or for some other consideration.
5. According to the Respondent No.9, (Project Proponent) the 'cause of action' 'first arose' on 7.7.1993, when the plans for construction of commercial building were sanctioned by Municipal Corporation of Greater Mumbai. The time cannot be extended by the Tribunal beyond the prescribed period, as provided under Section 14(3) of the National Green Tribunal Act, 2010. It is alleged that the Applicant without having any locus standi has filed the Application by way of making fishing inquiry in the matter. On these premises, the Respondent No.9 sought dismissal of the Main Application.
6. The Original Applicant resisted the Misc. Application. On behalf of the original Applicant, written submission is filed, in addition to the oral arguments. It is contended that the concept of 'limitation' is alien to the Environment (Protection) Act, 1986. It is further contended that the violation of Environment (Protection) Act, 1986, can be dealt with at any point of time by giving suitable directions. It is further averred that Section 5 of the Environment (Protection) Act, 1986, may be invoked by the competent Authority, as and when violation of the Environment (Protection) Act, 1986, is brought to the notice of the competent Authority. According to the Page 6 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) original Applicant, the construction work of the Respondent No.9, is carried out in violation of the Coastal Regulation Zone (CRZ), Notification, 2011, as well as the Environment (Protection) Act, 1986. The MCZMA has taken due action on basis of the complaint made by him on 23rd October, 2013, against gross violation of the CRZ Notification, 2011, by the Respondent No.9. The original Applicant would submit that view taken by the Hon'ble Principal Bench, New Delhi, in Goa Foundation vs Secretary, MoEF and ors (MA No.49/2013 in Application No.26/2012), is applicable to the facts of present case. It is further contended that the Application involves 'substantial question, relating to environment' and first 'cause of action' challenging illegality of construction work, first arose when legality of such construction work came to the notice of the Applicant. According to the Applicant, mere fact that the construction is of large scale and the building is of substantial height, will not give due notice about legality of the construction to any common man. The Applicant alleges that when the Developer makes construction in the private premises, concealing such activity from public eyes, by surrounding the site by steel sheets/shutters and get guarded it around the clock, and there is no access for inspection of the property nor any information is available Page 7 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) about violation of Law. It is further stated that view taken by the Hon'ble Principal Bench in 'J. Mehta vs Union of India and ors' (Misc Application Nos.507,595,644,649 of 2013, in Application No.88/2013), is applicable to the facts of the present case. In view of such submissions, the original Applicant sought dismissal of the Misc. Application, whereby preliminary objections are raised by the Respondent No.9 (Developer).
7. We have heard learned counsel for contesting parties. We have also perused the written submissions filed by them. We have carefully gone through the case laws cited by them.
8. In view of these rival submissions, following questions need to be answered:
i) Whether the Original Application is maintainable at the instance of the Applicant or liable to be dismissed, due to absence of locus standi?
ii) Whether the Original Application is barred by Limitation?
9. As far as question of locus standi is concerned, the Respondent No.9, would submit that the original Applicant has filed the Application only with a view to seek fishing inquiry in the matter, without bonafides. The averments made by the Respondent No.9, may be Page 8 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) reproduced for the purpose of understanding the main plank of submissions in this behalf. They are:
"The Respondent No.9 states that the Applicant has no locus standi to file the present Application as this Tribunal cannot deal with the matters as if it is public interest litigation. The Applicant is not affected by any of the acts of the Respondent No.9, while carrying out the construction activities on the said property and hence, he is not a person aggrieved within the meaning of Section 18 of the said Act and hence has no locus to file the same. This Hon'ble Tribunal is a creation of statute for adjudicating dispute specifically provided under the said Act and cannot and does not have the power of constitutional Courts exercising their powers under Articles 226 and 32 of the Constitution of India. The Respondent No.9 therefore, states that the Applicant is not having any locus to file the present Application."
10. Perusal of the original Application, reveals that grievance of the original Applicant is that the impugned construction activity is carried out in violation of CRZ Notification, 2011. Not only that but the competent Authority issued stop work order of which copy is annexed along with the Application. The original Applicant may not be personally affected, being a neighbor or resident of very same locality. Still, however, the original Applicant may demonstrate as to how he has interest in the environment of maintaining the coastal stretches of Mumbai. The violation of CRZ Notification, 2011, if at all is found to have been done by the Respondent No.9 that would give certain reasons to the Applicant to raise the Page 9 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) environmental issues. He may not have personal cause of action. However, as a Member of the society, he may agitate the environmental issues about violation of the Laws like CRZ, in the interest of environment. At this juncture, it is not necessary to go into the details of merits of the Application. However, from the affidavit of Shri. Raju Vasave, In-charge Regional officer of the MPCB, it appears that the prosecution is initiated against the Respondent No.9, under Section 15 of the Environment (Protection) Act, 1986, read with Environment Impact Assessment (EIA) Notification,2006. So also the affidavit of Ajay Fulmali filed on behalf of the Respondent Nos.3 and 4, shows that the impugned construction work prima facie is not in keeping with the environmental norms. Considering the prima facie material available on record, it is difficult to say that the Application is totally bereft of any reason and without locus standi.
11. Now, the term 'environment' has to be interpreted liberally. The environmental dispute cannot be cribbed, cabined or put in the small compass of 'personal disputes' or 'property disputes' or "disputed rights between two groups" or "individual rights". The damage caused to environment has to be looked from holistic angle. Any person may raise environmental dispute irrespective of his being personally affected due to the act of wrong Page 10 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) doer/polluter or violater of environmental Law/Norms. The only barrier is that such a person shall not file the Application with malafide intention. Secondly, he shall not be totally alien. In other words, if it is demonstrated that the Applicant is a person interested in protection of environment, or at least restitution of environment, then prima facie, he has locus standi to maintain the Application.
12. We may reproduce, for the purpose of ready reference, Section 14 (1) and (2) of the National Green Tribunal Act, 2010.
14. Tribunal to settle the dispute:-
(1) The Tribunal shall have the jurisdiction over all civil cases where a substantial question relating to environment (including enforcement of any legal right relating to environment), is involved and such question arises out of the implementation of the enactments specified in Schedule I.
(2) The Tribunal shall hear the disputes arising from the questions referred to in sub section (1) and settle such disputes and pass order thereon.
13. On behalf of the Respondent No.9, it is argued that the Application cannot be termed as 'person aggrieved', so as to entertain the Application. We may point out that the expression 'person aggrieved' is used only in context of Section 16 of the NGT Act, 2010. Obviously, when any Appeal is required to be filed, then it has to be filed by a Page 11 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) 'person aggrieved'. But, an Application can be entertained at the behest of any person, who is interested in protection, restitution or otherwise securing maintenance of environment. In any case, mere technical approach in such a case will not be appropriate. The person even though he has a legal grievance pertaining to probable adverse impact on environment, or probable adverse impact on environment, is entitled to approach the Tribunal, with such an Application, inasmuch as Section 14 (1) (2) of the NGT Act, 2010 will have to be read along with Section 15 and Section 20 of the NGT Act, 2010. He/she will come within ambit of Section 2(1) (j) of the NGT Act, 2010. In our opinion, protection of environment, is related to the fundamental right guaranteed under Article 21 of the Constitution and as such, anyone who has bonafide intention to protect environment can approach the Tribunal for the purpose of protection of such right.
14. In our opinion, prima facie, excessive construction without having EC, does amount to violation of the Environmental norms, at least, of the procedure to follow the Environmental norms. Section 14(1) of the National Green Tribunal Act, 2010, provides jurisdiction to the Tribunal to deal with 'substantial questions relating to environment' which also has to be read with Section 20 of Page 12 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) the National Green Tribunal Act, 2010, even anticipated action ought to be considered as 'substantial question relating to environment'. In the present case, without EC beyond permissible limits, undertaking of huge construction involves environmental issues like use of groundwater, illegality/impermissibility of high rise building in a particular area, violation of C.R.Z. Regulations, violation of provisions of the Air Act and Water Act. The issues pertaining to car parking, use of RG area, sitting etc. which need to be thrashed out and answered appropriately. The expression 'environment' is wide enough to encompass within its fold many such things.
15. On behalf of the Respondent No.9, learned Advocate invited our attention to the observations in case of "Rana Sen Gupta vs (1) Union of India (2) State of West Bengal (3) M/s Rashmi metaliks Ltd (4) West Bengal Pollution Control Board" (Appeal No.54/2012). True, in the given case the Appellant was held to be a person having no locus standi to prefer the Appeal. It was held that "the Appellant was not the 'aggrieved person' to challenge the order, which was impugned before the NGT (Principal Bench)". However, the said case can be distinguished on the facts. Appellant Rana Sen Gupta was a person residing in village, which was allegedly impacted on account of so called activity. The allegations basically were that Rana Page 13 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) Sen Gupta was a public spirited citizen. It was noticed, however, that there was absolutely no tangible material to start such a proclaimed status by Rana Sen Gupta. It was also noted that his previous Appeal No.32/2011, had been dismissed. Therefore, his locus standi was found to be dubious. Another case relied upon by the Respondent No.9, is of 'Ankur vs Maharashtra State Environment Impact Assessment Authority' (Application No.32/2012). The facts of that case are also on different footings. The Applicant alleged in the said Application that the Project Proponent had encroached upon the agricultural field of the farmers and other common land of the village. So called encroachment was in respect of agricultural land situated at village Kalane (district Sindhudurg), whereas, the Applicant's address was of Pen (district Raigad). Both these two (2) places were at a distance of 300/400 km away from each other. There was material on record to show that the Application was ill-motivated. Nothing of that sort is found on record of the present case.
16. The issue of locus standi of the Applicant and bar of limitation, to file the Application, will have to be considered on basis of prima facie material.
This Application is filed under Section 14(1), 15 and 18 of the National Green Tribunal Act, 2010. The contention of Respondent No.9 that such huge Page 14 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) construction could have been ordinarily noticed by any passerby is prima facie acceptable. The height of construction went on and on, above the average level and became so notorious that any prudent person could have noticed the same, being a sky rise construction. What the Applicant alleges in the present case is that the Respondent No.9 made excessive construction beyond limits of the Environmental Clearance (EC) and that was not known due to lack of information in respect of original E.C.
17. In 'Goa Foundation & Anr vs Union of India & Ors' (In Misc Application No.49 of 2013, Application No. 26/2012) decided on July, 18th, 2013, five(5) Members Bench of the Principal Bench, headed by the Hon'ble Chairperson, it is held that:
"25. Aggrieved is a person who has suffered a legal grievance, against whom a decision has been pronounced or who has been refused something. This expression is very generic in its meaning and has to be construed with reference to the provisions of a statute and facts of a given case. It is not possible to give a meaning or define this expression with exactitude and precision."
18. According to the Respondent No.9, reliance of the original Applicant on case of 'Goa Foundation vs Union of India' decided by the Hon'ble Principal Bench, is misplaced. It is argued that Judgment in 'Goa Foundation' case (supra) may not be followed. On behalf of the Page 15 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) Respondent No.9, it is further contended that the commercial building having 28 floors, 3 level podium, 2 voids, in all 33 floors and over a period of 8/10 years is constructed, which itself could be treated as deemed notice to the Applicant and, therefore, it is not open to him now to raise such a dispute, which is nothing but proclamation of omission and an attempt to extract easy money from the Respondent. The Respondent No.9, therefore urges to dismiss the main Application on the ground that the Application is not maintainable for want of locus standi. It is contended that view taken by Hon'ble Principal Bench in "Goa Foundation vs Union of India" may be deviated from by This Bench inasmuch as it is not a binding precedent to be followed by this Bench. We do not agree. Whether it is a binding precedent or not is not the question which needs to be addressed at this juncture. It is well settled principle that Judgment of a co-ordinate Bench must be duly respected by another Bench. This basic jurisprudential discipline shall be maintained to follow principle of 'stair desists'. Hence, we are unable to accept the contention of learned Counsel for the Respondent No.9.
19. We cannot brush aside the purposive interpretation of expression "any person aggrieved" as used in Section 18 (2) (e) of the National Green Tribunal Act, 2010. It is not Page 16 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) referable to any person aggrieved by any kind of order as such, but may be a person aggrieved due to loss of environment, breach of environmental norms or like causes. Only barrier is that his action shall not be baseless, ill-motivated or that outcome of vendetta nor shall he be a person disinterested in such cause of environment but wants to take garb thereof for extraneous reasons. In latter cases the Application may be dismissed and the Tribunal will have to be on guard.
20. Learned Counsel for the Respondent No.9, strenuously argued that the Application is barred by limitation, in view of the fact that 'cause of action' for filing of the Application 'first arose' on 7.7.1993, when plans for construction of commercial building were sanctioned by the MCGM. The Respondent No.9, states that after twenty (20) years from the date of sanctioning the plan, now, filing of such Application will open up unwarranted issues, therefore the Application is totally misconceived. The Respondent No.9, seeks to rely on the wording of Sections 14 and 15 of the National Green Tribunal Act, 2010, as well as the special provisions of Limitation provided there under. Learned counsel for the Respondent No.9, would submit that general provision of the Limitation Act, are excluded in view of the special enactment, which provides specific provision in respect of Page 17 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) the limitation clause and, therefore, there will be no scope for extension of limitation. It is argued that "the plain and simple language of Section 14(3) of the NGT Act, i.e. "unless it is made within a period of six months from the date, on which the cause of action for such dispute first arose", negates the principle of continuing cause of action. If the plea of continuing cause of action is accepted within the limitation, the statute would be eschewed of the important and vital words "first arose".
21. Reliance is placed on the observations in "Aradhana Bhargav & Ors. V. MoEF & Ors" [Application No.11 of 2013], decided by the Hon'ble Bench of NGT on 12.8.2013. The observations in relevant paragraphs of the said Judgment are as below:
"23. From the very reading, it would be quite clear that the Tribunal has jurisdiction over all civil cases only where a substantial question relating to the environment including enforcement of any legal right related to environment is involved and also the said substantial question should also arise out of the implementation and is included in one of the seven enactments specified under the Schedule - I. Even, if the applicant is able to satisfy the above requisites, the Tribunal can adjudicate the disputes only if it is made within a period of six months from the date on which the cause of action in such dispute first arose and the Tribunal for sufficient cause can condone the delay for a period not exceeding 60 days in making the application.
24. Under Section 15 of the Act, an application for relief and compensation to the victims of pollution and other environmental damage under the enactments specified in Schedule-I or for restitution of the property damage or for restitution of environment for such area or areas, the applicant could be filed within a period of five years from the date of which the cause of action for such Page 18 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) compensation or reliefs first arose. Also, if sufficient cause was shown, the Tribunal is empowered to condone the delay for a period not exceeding 60 days. Significant it is to note that the expression "cause of action for such dispute first arose" is employed. By employing the above expression, the legislative intent indicating that the period of limitation would commence only from the date on which the first event constituting the dispute arose, is explicit. This is not only an indication but also the caution that the later dates on which subsequent events arose should not be taken into account for computing the period of limitation.
28. Traite law it is that the special law of limitation, in any given enactment, will always exclude the general law of limitation. The NGT Act, 2010, a special enactment specifically provides period of limitation under Section 14(2) and 15(3), as stated supra. The Principal Bench, NGT has already held in Jesurethinam & Ors Vs. Ministry of Environment, Union of India &Ors, reported in 2012 (2) FLT 811 NGT that, when a specific provision for limitation is provided under the special statute, the general provisions of the Limitation Act, 1963 are inapplicable. Hence, the Tribunal is afraid whether the theory of continuing cause of action can be made applicable to the present factual position of the case for which the specific period of limitation is available under the NGT Act, 2010.
30. A person who wishes to invoke the jurisdiction of the Tribunal or Court has to be vigilant and conscious of his rights and should not let the time to go by not taking appropriate steps. It is true that the provisions of law of limitation have to be construed liberally but the same cannot be applied to the present facts of the case for the reasons stated above. It is true that the Tribunal must adopt a practical approach which is in consonance with the provisions of the Act providing limitation. In the instant case, the period of limitation has begun to run long back. The period of limitation once commences operating; it does not stop but continues to operate with its rigour. An interpretation accepting the continuing cause of action would frustrate the very object of the Act and the purpose Page 19 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) of prescription of limitation. In the instant case, it is contended by the respondent project proponent that nearly 600 crores have been spent and more than 50% of the work is over, hence, the project proponent who obtained the environmental clearance in the year 1986 and has completed not less than 50% of the work by spending hundreds crores of rupees would be thrown to jeopardising his project at the long lapse of years. Needless to say, if it is allowed, it would be against the very intent of the law. Even it may be true that the applicants are aggrieved persons and it may even be true that there was violations of provisions of law but action should have been initiated within the prescribed period of limitation. In view of all the above, it can be well stated that the contentions put forth by the Learned Counsel for the applicants that the application was within time have to be rejected."
22. In case of "Aradhana Bhargava" (Supra) the challenge was to EC. That was an Appeal under Section 16 of the NGT Act, 2010. Herein, the challenge is mainly to the violations of the EC conditions. Both these matters are on different footings. We do not find parallels between them. Hence, Judgment in "Aradhana Bhargava" case is not applicable to the facts of the present case.
23. The Counsel further seeks to rely upon observation in 'Nikunj Developers & anr vs State of Maharashtra Environment Department and Ors' (MA No.347/2012, arising out of Appeal No.76/2012) decided on 14.3.2012, by the Hon'ble Principal Bench of the NGT. It has been held :
"19. From language of the above provision it is clear that the Tribunal loses jurisdiction to condone the delay if the delay is Page 20 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) of more than 90 days. Every appeal has to be filed within 30 days from the date of communication of the order. That is, what an applicant is required to ensure before the appeal is heard on merits. However, the Tribunal has been vested with the jurisdiction to entertain the appeal which is filed after 30 days from the date of communication of an order. This power to condone the delay has a clear inbuilt limitation as it ceases to exist if the appeal is filed in excess of 60 days, beyond the prescribed period of limitation of 30 days from the date of communication of such order. To put it simply, once the period of 90 days lapses from the date of communication of the order, the Tribunal has no jurisdiction to condone the delay. The language of the provision is clear and explicit. It admits of no ambiguity and the legislative intent that Tribunal should not and cannot condone the delay in excess of 90 days in all, is clear from the plain language of the provision.
20. As stated in the cases Hiralal RatanLal and India Houses (supra) the period of limitation statutorily prescribed, has to be strictly adhered to and cannot be relaxed and or departed from, on equitable consideration. Further, in construing a statutory provision, the first and the foremost rule of construction is that of literary construction. We do not see any reason to expand the scope of the provision and interpret the proviso to Section 16 in the manner that Tribunal can be vested with the power of condoning the delay beyond 90 days. Such interpretation would be contrary to the specific language of the Section and would defeat the very legislative intent and object behind this provision. "
24. So far as the question of limitation is concerned, we will have to examine the averments of the Applicant. The averments may or may not be proved in final analysis. Still, however, it cannot be overlooked that the construction activity is stopped by the MCGM, after the complaint was filed by the Applicant, as per order dated January 6th, 2014. According to him, the construction Page 21 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) activity cannot be carried out in CRZ-I, area and the competent authority ought to have issued directions under Section 5 of the Environment (Protection) Act, 1986. He submits that since the competent authority, did not give any EC and the Respondent No.9, did not obtain any permission from the MCZMA, for impugned construction for the project in question, illegal construction is ongoing activity, and can be challenged, because the 'cause of action' is still continuing. He alleges that when he got knowledge that the impugned construction was being carried out without permission of the statutory authority, though it falls in CRZ-I, area, he immediately filed complaint dated 23rd October, 2013, but no action was initiated by the MCZMA. It is for such a reason that he filed the Application and claims that it is within limitation.
25. It may be stated that originally, the MCZMA granted permission for the construction of commercial building in 1993. The sanction certificate was issued on 18.9.1997. In or about 2000, the Respondent No.9, came into possession of land in question. On 26th December, 2001, the plans for residential building were approved by the MCGM. In October, 2005, development rights were issued for development of the property. The Respondent No.9, obtained conveyance of the entire land and his name was mutated in the Property Register Card. The Page 22 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) construction activity, no doubt, started long back. But the real question is whether the conditions for continuation of construction activity were followed by the Respondent No.9?. The Respondent No.9, relied upon the case of "Munnilal Girijanand v. State and others" (Application No. 45/2014). It was a case of Slum Rehabilitation Area (SRA) project which had commenced in 2002, when it was not governed by EIA Notification, 2006. The facts of that case are of altogether different from the present case. Secondly, it was found that the Applicants (Munnilal and others) were litigating before different Forums, including the City Civil Court, Hon'ble High Court and Apex Court in respect of identical issue, before filing of the Application in the Tribunal under Section 14 of the NGT Act, 2010. So, it was a case of going from one Court to another for the same the same kind of relief. In "J. Mehta vs Union of India and Ors" (M.A.Nos.507,509,644 and 649/2013, in Application No.88/2013) of the National Green Tribunal (PB), considered the question of limitation in following way:
"53. Thus, it is clear that the cause of action should have a direct nexus with the matters relating to environment. In the present case, the respondents can hardly be heard to contend that since they have been flouting with impunity, the law, the terms and conditions of the EC for long, and therefore, every person is expected to know such violations or unauthorized use, and as such, the application would be barred by limitation. Respondent No. 9 has not come to the Page 23 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) Tribunal with clean hands and disclosed complete details, which were exclusively within their knowledge and possession. In the normal course of business, Respondent No. 9 would have first entered into agreements with other persons for providing these premises, either on sale or lease, as the case may be. Then such buyers/lessees would start making constructional changes and provide infrastructure necessary for using the parking and services area for commercial purposes. Then alone, such persons would have started using the premises for such purposes. All these facts have been withheld by Respondent No. 9. Therefore, the Tribunal would be entitled to draw adverse inference against Respondent No. 9 in that behalf. In any case, Respondent No. 9 and other private respondents have converted the user of the premises contrary to the specified purpose and in violation of law and terms and conditions of the EC. Thus, even such an approach would support the case of the applicant and in any case the respondents cannot be permitted to take advantage of their own wrong or default.
54. The cause of action is not restricted to 'in personam' but is an action available to any person in terms of Section 14 of the NGT Act. It empowers any person aggrieved to raise a substantial question relating to environment including enforcement of any legal right relating thereto. Every citizen is entitled to a clean and decent environment in terms of Article 21 of the Constitution and the term 'cause of action first arose' must be understood in that sense and context. The applicant has been able to establish that he first came to know about the misuser and change of user, particularly with regard to adverse environmental impact, only in the middle of December, 2012 and immediately thereafter, he took steps retuning the authorities concerned to take action as per law but to no avail. Then 'he filed the present application within the prescribed period of six months. The respondents have not been able to rebut successfully the factual matrix stated by the applicant. As already stated, they have withheld relevant facts and information from the Tribunal.
Page 24 (J) M.A. No.65/2014 in Application No.13/2014 (WZ)
55. A cause of action is a bundle of facts which should give, in its composite form, right to a plaintiff against the defendant to approach a court or Tribunal for a legal remedy or redressed of his grievance. Thus, the existence of a legal remedy to the plaintiff is a sine qua non for an actionable cause of action. In view of the above reasoning, we have no hesitation in concluding that the present application is not barred by time.
56. Lastly but most importantly, now we have to deal with the question as to whether the breach of conditions of EC is likely to cause environmental and health hazards or not. We have already held that Respondent No. 9 has not only violated the specific terms and conditions of the EC dated 27th November, 2006 but has also miserably failed to submit an application for reappraisal of the project. Furthermore, the said Respondent No. 9 has committed breach of the bye laws, fire safety measures, Corporation laws, etc. All the public authorities have specifically taken the stand that at no point of time, did they accord any permission or sanction for conversion of the parking area for commercial purposes and its misuser or unauthorized construction. In fact, according to them, they have taken appropriate steps against Respondent No. 9 in accordance with law. We have already noticed that this Tribunal is not concerned with the violations and breaches committed by Respondent No. 9 with regard to other laws in force but for environmental laws in terms of Schedule I to the NGT Act and its adverse impact on environment and public health.
57. It has come on record that approximately 59 of commercial area has been increased by such unauthorized conversion and misuser. The terms and conditions of the EC have specifically provided that in the event of any change in the scope of the project, Respondent No.9 was expected to take steps for reappraisal of the project and take fresh EC, which admittedly, has not been done by Respondent No. 9 despite lapse of considerable time. These violations would consequently have a direct impact on traffic congestion, ambient air quality, contamination of underground water, sewage disposal and municipal solid waste disposal besides Page 25 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) other adverse impact on population density in the area. With the significant change of commercial area by 59, the EC itself would be substantially affected and it would be for the authorities concerned to examine whether the EC can be continued or requires to be recalled. There is a drastic change in PSY with change in sq.ft. area as the EC was not intended for such area to which Respondent No. 9 has now expanded its activity. Furthermore, assessment of water requirement is based upon the number of users and other services in the area and this substantial change has fundamentally been altered and would have drastic and adverse effects on all these aspects. The EIA Report submitted by Respondent No. 9 itself shows that these are the various aspects, the variation of which is bound to alter the entire basis for grant of the EC. For instance, the parking for 1772 cars was to be provided in the project in terms of EIA report. For this purpose, the basement, lower ground floor in one block and the multi-level car parking in the Block 2P had been provided. Major part of this area had been converted and used by Respondent No. 9 and other private respondents for commercial purposes. It is not even the case of Respondent No. 9 that the required number of cars can be parked in that building. The cars which could have been parked in the building now would have to be parked on the public roads/places leading to lowering the road capacity resulting in lowering the average speed of the vehicle, consequently increasing the air pollution."
(Emphasis by Us)
26. The term 'cause of action' is a bundle of facts. There cannot be two opinion about legal position that once the 'cause of action' starts running, then it cannot be stopped. In case of violation of Law, particularly, like CRZ Notification, violation continues, when the construction activity goes on without hindrance. As stated before, the competent authority directed the Page 26 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) Respondent No.9, to stop construction activity and therefore, the construction work now has come to halt. It appears prima facie that the question regarding alleged violation of CRZ, Notification, is yet to be determined by MCZMA. Under the circumstances, the Application cannot be held as totally barred by limitation, inasmuch as the 'cause of action' is continuous and still remains unabated. In our opinion, question of locus as well as question of limitation ought to be decided on case to case basis.
27. What is meaning of expression 'such disputes' in relation to Section 14 (2) of the NGT Act, 2010, would depend upon facts of a particular case. One cannot be oblivious of the fact that the Legislature has purposefully used the expression 'such disputes' which imply plurality of nature of dispute, which may be raised in various kind of environmental litigations. Needless to say, it will not be possible to accept straight jacket formula for applicability of sub-section (3) of Section 14. Unless it can be clearly gathered that the dispute has origin, which could be referable to a fixed time of period due to its nature itself, counting of time will not begin from the day one of fixed staring point. Nobody will deny that once limitation period commences, then it will not be arrested in the midst thereof. Close scrutiny of sub-clause (3) of Section 14, will Page 27 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) make it amply clear that period of limitation will commence from the 'date of cause of action' for such dispute when it 'first arose'. If this sub-clause, is properly bisected, the legal position which emerges, may be stated in following way:
a) Filing of Application can be allowed within six months from the date of 'commencement of cause of action' for "such dispute" and,
b) From "first date of arising of cause" of action.
28. We cannot overlook the material fact that 'first cause of action' in respect of present dispute arose when CRZ Notification's violation was noticed by the Applicant and he made complaint to the concerned Authority. It is important to note that though the MCZMA, is the Authority to take action in the matter on its own, yet failure to take such action by itself, would give rise to 'cause of action', because it is the breach of mandate under the Environment (Protection) Act, 1986, and the order issued thereunder by the MoEF, that will trigger cause of action. A copy of order dated 6th March, 2012, issued by the MoEF, shows that MCZMA, is the Authority created by MoEF, under Section 3 of the Environment (Protection) Act, 1986, to exercise powers and take certain measures for protecting and improving quality of coastal environment and preventing, abating and controlling Page 28 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) environmental pollution in the areas of the State of Maharashtra. The relevant part of Notification dated 6th March, 2012, may be reproduced for ready reference:
II. The Authority shall have the power to take the following measures for protecting and improving the quality of the coastal environment and preventing, abating and controlling environmental pollution in areas of the State of Maharashtra; namely :-
(i) Examination of proposals for changes or modifications in classification of Coastal Regulation Zone areas and in the Coastal Zone Management Plan (CZMP) received from the Maharashtra State Government and making. Specific recommendations from Coastal Regulation Zone point of view as per the provisions of Coastal Regulation Zone notification, 2011;
(ii) (a) inquiry into cases of alleged violation of the provisions of the said Act or the rules made there under or any other law which. is relatable to the objects of the said Act and, if found necessary in a specific case, issuing directions under Section 5 of the said Act, insofar as such directions are not inconsistent with any direction issued in that specific case by the National Coastal Zone Management Authority or by the Central Government;
(b) Review of cases involving violations of the provisions of the 'said Act and the rules made thereunder or under any other law which is relatable to the objects of the said Act, and if found necessary referring such cases, with comments for review to the National Coastal Zone Management Authority:
Provided that the cases under sub-paragraphs (ii)
(a) and (ii) (b) of paragraph II only be taken up suo motu on the basis of complaint made by an individual or an representative body or an organization;
(iii) filing complaints under Section 19 of the said Act, in cases of non-compliance of the directions issued by it under sub-paragraphs (i) and (ii) of paragraph II of this Order; (iv) to take action under Section 10 of the said Act Page 29 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) so as to verify the facts concerning the issues arising from sub-paragraphs (i) and (ii) of paragraph II of this Order.
29. A plain reading of above Notification reveals that the Authority is empowered to take action including issuing directions under Section 5 of the Environment (Protection) Act, 1986. It is obvious, therefore, that when the Authority failed to take suitable action, when CRZ violation was complained and brought to the notice of the competent Authority, the 'first cause of action' had arisen to file the present Application. Apart from that, we cannot overlook the fact that the Applicant could not have knowledge of particulars of the EC granted in favour of the Project Proponent and, therefore, could have no reason to file such Application before verification of the fact that enormous construction was carried out in breach of the EC conditions and within CRZ area.
30. Considered from the standpoint of above view, we are of the opinion that "such disputes" in the present Application arose when the MCZMA failed to issue directions under Section 5 of the Environment (Protection) Act, 1986, irrespective of knowledge that the construction activity was in breach of the CRZ Notification. We are of the opinion that the Applicant could have knowledge of the nature of initial EC granted in favour of the project Proponent. Secondly, initial construction activity was Page 30 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) below 20,000 sq mtrs and, therefore, the Applicant might be under impression that no EC was required. However, project activity increased by leaps and bounds and, therefore, he gathered knowledge that certain illegal activity was going on. It is in the wake of such 'subsequent event' that he raked up the dispute in question. Obviously, the cause of action 'first arose' for such a dispute when knowledge of excessive project activity was gained and that Competent Authority failed to exercise powers under Section 5 of the Environment (Protection) Act,1986, because 'cause of action' triggered for the purpose of filing this Application and hence it is within limitation.
31. In the final analysis, we hold that the present Application, in the given circumstances, is not barred by limitation, nor can be dismissed for want of 'locus standi'. Under the circumstances, Misc Application No.65/204, is dismissed with no order as to costs.
The Main Application scheduled for hearing on next date.
..............................................., JM (Justice V. R. Kingaonkar) .............................................., EM (Dr.Ajay A. Deshpande) Date: October 1st, 2014 Page 31 (J) M.A. No.65/2014 in Application No.13/2014 (WZ) Page 32 (J) M.A. No.65/2014 in Application No.13/2014 (WZ)


Creates a striped list with alternating background colors. - Use the `:nth-child(odd)` or `:nth-child(even)` pseudo-class selectors to apply a different `background-color` to elements that match based on their position in a group of siblings. - **Note:** You can use it to apply different styles to other HTML elements like `
`, `


Overall, image classification is prevalent in the world of Machine Learning. Problems can be solved in multiple ways, specifically using Supervised and Unsupervised Methods. Below is a small snippet of the ideas I have been putting together.
Supervised Methods Considered
Unsupervised Methods Considered
Datasets


Used by more than a million people, Finans is a very usefull tool to manage your money
Available for
With Finans, you organize all your bills and savings with simple charts.
Always forget due date? Finans remeber you!
Finans goes beyond the basic
In a matter of seconds you can control your money
Our client support helps you with any question 24/7


I am a self-taught developer with a degree in kinesiology. While I still enjoy this field I felt there was more out there to challenge me. Throughout the pandemic year I gained the necessary skillset required to pursue a career in web development. The challenges that programming generates has enabled me to utilize the tools I learned. I enjoy problem solving and collaborating with others to help achieve my goals. Please look around at these projects and feel free to contact me.
See My ProjectsThis website was created for a company called ServingU. The companys main goal is to help people, specifically college students, find jobs within the service industry. A user can sign up to a mailing list and enter what university is closest to them. The information taken is used to match with potential employers and find a match quickly.
The app is programmed to search any stock data by searching its ticker symbol. I used react to create this app because it offers the simplicity of HTML layout while using javascript all in one language. Class components were used along with react hooks to build the program. Once ticker is searched the app will pull up a card that shows important data about that company: name, symbol, percent change (red=loss, green=gain), year high and year low. To see project in action click download link (either fast or slow speed), click download now. Once downloaded enter npm install in your text editor to install dependencies, then run npm start to run application.
The program was created using react.js. This helps with the simplicity of putting all the files together. As opposed to the stock search, I used functional components to create robofriends. This app has a list of cards pulling from a set list of users. Each card has a picture of a robot, a name, and email address. There is a search bar at the top used to filter out the cards on the page. The webpage filters as you enter letters or erase them. If you would like to scroll the page to see the users on it, the search bar at the top is meant to scroll with the user. To see project in action click see live.
CONTACT ME


Other Projects
dancey.dance
dancey.dance provides guides, checklists, and technical tools such as ticketing and housing systems for lindy hop and blues dance exchanges and workshops. The goal is to make these events easier, faster, cheaper, and most importantly more fun to create. The first project launched was ATLX 2018
Novel Monkey
Novel Monkey is a highly conceptual, experimental site designed for speed-writing, specifically for NaNoWriMo. It was built in 2014, on top of Meteor. It’s a bit buggy and the age shows, but people still use it. Plans are in the works for a simpler serverless, and perhaps even offline-mode version of this writing tool.
Freelance for Good
Work in Progress. Freelance for Good, formerly BuildATL, was an attempt to build a small jobs matching system for nonprofits and public good projects who need design and web projects with freelancers, students, and those who want to do some good or beef up their portfolio. This project is still in the planning stages, and has received previous support from General Assembly.
bullWatch
Work in Progress. bullWatch is an investment tracking and diary project that helps retail investors track and focus their investment efforts on long-term investments. It employs tools to help users filter the nonsense of short-term, pump and dump-y media news, and focus on what matters most—long term trends and helping users stick to their strategies. This project is still in the early planning and prototyping stages


--- layout: post title: Happy Birthday RFC! date: 2009-04-08 18:49:19.000000000 -07:00 categories: - general news tags: [] status: publish type: post published: true meta: _edit_last: '1' author: login: ckelty email<EMAIL_ADDRESS>display_name: ckelty first_name: Christopher last_name: Kelty excerpt: !ruby/object:Hpricot::Doc options: {} ---
40 years.
There was a very nice editorial in the NYT this week by Steve Crocker, author of the first, and many subsequent RFCs.