I've been playing with the DeepEarth BlueMarble and noticed that the web version tile pyramid is coming out of the AWS S3. Is this one of Amazon's public data sets or is someone paying for the use of the S3? Also does anyone know what pyramid builder was
used to create the tile sets? I have a few data sets currently behind Geoserver WMS that I'd like to handle in a similar way for performance reasons.
Thanks for an impressive tool. I'm trying to stack layers from several WMS sources over the base options and can see that DeepEarth makes a fantastic OWS viewer.
Jan 8, 2009 at 1:06 AM
Edited Jan 8, 2009 at 1:12 AM
what SRS=EPSG:XXXX are the WMS maps you have
"SRS=EPSG:4326" has a tilelayer in the project but the projection is not quite right
I also made another WMS TileLayer that uses "SRS=EPSG:3395" or "SRS=EPSG:900913", these are basically yhr same projection that deepearth is using by default, I have not uploaded this TileLayer
I use "SRS=EPSG:4326." On PostGIS backed datasets I can convert to any EPSG required. Imagery data is more problematic, for example NAIP counties are UTM and would need to be warped
I see 3395 in my spatial_ref_sys table and I can add the google projection 900913:
Would the new EPSG:3785 Mercator be the same as 900913?
new "web mapping crs" (EPSG:3785):
PROJCS["Popular Visualisation CRS / Mercator",
GEOGCS["Popular Visualisation CRS",
DATUM["Popular Visualisation Datum",
SPHEROID["Popular Visualisation Sphere",6378137,0,
I'm still curious about the best way to produce static TileLayers. Are you using DeepZoom and renaming the tiles?
'..\DeepZoomProjectWeb\ClientBin\GeneratedImages\dzc_output_images' contains jpg tiles, but the tiles generated by DeepZoomComposer are not 256x256. I notice that the ImageTools.exe commandline is no longer in the DeepZoom project.
Is it better to use gdal scripts to create the image pyramid for local or S3 use?
Jan 9, 2009 at 12:55 AM
from what I have read EPSG:3785 Mercator is basically the same as EPSG:900913
HELLO DEEPZOOMTOOLS.DLL : DEEP ZOOM IMAGE TILE GENERATION MADE EASY
In our most recent release of Deep Zoom Composer, one of the major changes we made was to change how we generated the image tiles both for designing as well as exporting your Deep Zoom Content. In the past, ever since our first release
at MIX, our image encoding was done using a combination of SparseImageTool.exe and
ImageTool.exe command line tools. Starting with this release, we have retired those tools and have shifted to a preview version of a .NET based DLL that provides image generation capabilities.
If you look inside your Deep Zoom Composer installation folder, which is by default, [Program Files]\Microsoft Expression\Deep Zoom Composer, you will see a file called DeepZoomTools.dll: