So this is very nice project. I could participate but I did not had time… Anyway don’t expect any map with layers:-).
http://tree-nation.com/
So this is very nice project. I could participate but I did not had time… Anyway don’t expect any map with layers:-).
http://tree-nation.com/
Yeah, it is a pain, especially when you have more layers. But it is not MapServer’s fault, since you have to put a lot of information in there!
For WMS and probably for other services, if you don’t put in LAYER’s tag METADATA line “ows_extent”, mapserver keeps computing the extent every time you make a getcapabilities request. You cannot put EXTENT tag into the LAYER only, because strange things happen – seems that depends on the datasource, when the LatLonBoundingBox tag appears. With “ows_extent” this everything OK. Mapserver 4.10
Next time I will have to write some .map manually I will generate it with some simple script!
Italian people do go on!
The answer is, I don’t know, except using gdaltindex. But, I know place where they know:
http://labs.metacarta.com/wms-c/
I hope to add some comments later and hope this helps out there.
Lately I have searched hard something I had in front of my eyes: I wanted to convert WKT text to proj4 definition. Search for “wkt2proj” didn’t really made it:-) But I found it, it’s name is testepsg and is part of gdal/ogr. It is not present in default build, but i.e. FWTools has it.
It basically converts WKT stored in .prj file into more formats: formated WKT, simplified WKT, old WKT and finally proj4 text.
testepsg ESRI::tmp/mywkt.prj
Hope it helps!