P 72
GIS Experience
Having said the term 'Requirement Identification Process' , let us see what it is and how it got set-in and the process we followed.
If one goes back to GIS set-up origination in May,2000, the whole thing started at the back ground of launching Reliance Telecommunication for Mobile phone services! The management was looking for business potential mark-ups in identified zone/areas, detailed occupation of potential customers and their communication requirement needs etc. Also there was need of mapping the National Hi-way and State Hi-way when it came to cross country back bone cabling. Business group used to bring in market survey and convey to the management the priority cities in descending order.
The listing started with Metro cities and other 6 large potential cities- termed as top 10. As GIS team we had the task of mapping these cities in that order by digitizing the Ikonas satellite imagery for respective city and place them in overall India map & then incorporate the Hi way co-ordinates joining them. So it virtually became drawing the India map for us. As usual, even before understanding and estimating the involved task for the top 10 cities,, there came next listing of 48 cities . So literal crowding effect took place. Later another 212 got added.
When it came to indenting the image , SI(Space Imaging) was looking for edge co-ordinates for each city in terms of Lat/Long at each corner. This was more for keeping track and accounting the supplies.Also RSR was keen to ensure the quality of shoot of the imagery before dispatch. That forced us to source complete Indian satellite imagery for entire India- exclusively to mark the boundaries of the respective cities and determine the Lat/Long of our needs. But that additional sourcing came as handy and very useful in the end, which I shall address later. The entire GIS team including the agency staff got really charged and functioned as well oiled machinery. Our indent to SI was getting conveyed as flash and they responded effectively. In that loop even Antrix members cooperated very well.
That made the distribution of imagery for digitization to engaged agencies became Auto mode.
As the back bone cabling was a long drawn affair, the engineering planning group was looking for digitized Road maps urgently. So we put another team led by Bhoyer and Badri to undertake that challenge. Using TTK maps and AAI maps, they initiated that task and then superimposed them in Indian satellite imagery to align the lat long of contours. By that they fine tuned the alignment and we could get fairly accurate routing and cable length requirement. The end customer- National Long Distance Backbone Planning team were too happy with that output!
So far I have been covering only Digitization of imagery, But there is another important segment in developing GIS in general and some special aspects when it comes to Telecommunication in particular! How we went ahead in that respect is really a Dream! I owe my regards to Don. Michael and my Network team.
Contd....
Key Aspects :- Incident analysis, Planning, Technical issue, Team building
GIS Experience
Having said the term 'Requirement Identification Process' , let us see what it is and how it got set-in and the process we followed.
If one goes back to GIS set-up origination in May,2000, the whole thing started at the back ground of launching Reliance Telecommunication for Mobile phone services! The management was looking for business potential mark-ups in identified zone/areas, detailed occupation of potential customers and their communication requirement needs etc. Also there was need of mapping the National Hi-way and State Hi-way when it came to cross country back bone cabling. Business group used to bring in market survey and convey to the management the priority cities in descending order.
The listing started with Metro cities and other 6 large potential cities- termed as top 10. As GIS team we had the task of mapping these cities in that order by digitizing the Ikonas satellite imagery for respective city and place them in overall India map & then incorporate the Hi way co-ordinates joining them. So it virtually became drawing the India map for us. As usual, even before understanding and estimating the involved task for the top 10 cities,, there came next listing of 48 cities . So literal crowding effect took place. Later another 212 got added.
When it came to indenting the image , SI(Space Imaging) was looking for edge co-ordinates for each city in terms of Lat/Long at each corner. This was more for keeping track and accounting the supplies.Also RSR was keen to ensure the quality of shoot of the imagery before dispatch. That forced us to source complete Indian satellite imagery for entire India- exclusively to mark the boundaries of the respective cities and determine the Lat/Long of our needs. But that additional sourcing came as handy and very useful in the end, which I shall address later. The entire GIS team including the agency staff got really charged and functioned as well oiled machinery. Our indent to SI was getting conveyed as flash and they responded effectively. In that loop even Antrix members cooperated very well.
That made the distribution of imagery for digitization to engaged agencies became Auto mode.
As the back bone cabling was a long drawn affair, the engineering planning group was looking for digitized Road maps urgently. So we put another team led by Bhoyer and Badri to undertake that challenge. Using TTK maps and AAI maps, they initiated that task and then superimposed them in Indian satellite imagery to align the lat long of contours. By that they fine tuned the alignment and we could get fairly accurate routing and cable length requirement. The end customer- National Long Distance Backbone Planning team were too happy with that output!
So far I have been covering only Digitization of imagery, But there is another important segment in developing GIS in general and some special aspects when it comes to Telecommunication in particular! How we went ahead in that respect is really a Dream! I owe my regards to Don. Michael and my Network team.
Contd....
Key Aspects :- Incident analysis, Planning, Technical issue, Team building
No comments:
Post a Comment