#2340 closed defect (wontfix)
MgCooker using scaleindexes backwards while rendering tiles
Reported by: | Gyufi | Owned by: | jng |
---|---|---|---|
Priority: | high | Milestone: | Maestro-5.0-maintenance |
Component: | Maestro | Version: | |
Severity: | major | Keywords: | |
Cc: | Gyufi | External ID: |
Description
Using
- MapGuide Open Source 2.5.0.7449
- Installed MapGuide Maestro 5.0.0.7213 and MapGuide Maestro 5.0.0.7698
on a Windows Server 2008 R2 Enterprise SP1 x64 server.
I tried to prerender tiles with MgCooker with these scales: 1:90000, 1:45000, 1:25000, 1:15000, 1:8000, 1:4000, 1:2000, 1:1000, 1:500, 1:250. (10 scales)
When I using MgCooker to render tiles in 1:90000 scale, it creates tiles to subdirectories of Repositories/TileCache/<FolderName>_<MapName>/S0 directory.
When I using (Ajax or Fusion) Viewer to render tile on-the fly, it creates tiles to subdirectories of Repositories/TileCache/<FolderName>_<MapName>/S9 directory.
BaseMap FiniteDisplayScales are fine, but MapGuide waiting scaleindexes backwards when calling mapguide.fcgi with GETTILEIMAGE operation.
I made some modifications in
- OSGeo.MapGuide.MaestroAPI/Tile/BatchSettings.cs
- MgCooker/SetupRun.cs
files.
With these modifications tile rendering working fine, but I don't think this is the best way to solve the problem.
Attachments (8)
Change History (18)
by , 11 years ago
Attachment: | SetupRun.cs added |
---|
by , 11 years ago
Attachment: | BatchSettings.2.cs added |
---|
by , 11 years ago
Attachment: | Modifications.zip added |
---|
by , 11 years ago
Attachment: | Modifications.2.zip added |
---|
by , 11 years ago
Attachment: | BatchSettings.cs added |
---|
comment:1 by , 11 years ago
Cc: | added |
---|
follow-up: 4 comment:2 by , 11 years ago
Can you put these up as diffs? It makes it easier for me to see what has changed and makes applying the changes much easier.
comment:3 by , 11 years ago
Component: | Tile Service → Maestro |
---|---|
Milestone: | → Maestro-5.0-maintenance |
Owner: | set to |
Type: | task → defect |
Version: | 2.5.0 |
comment:4 by , 11 years ago
Replying to jng:
Can you put these up as diffs? It makes it easier for me to see what has changed and makes applying the changes much easier.
Thank you to reply so quickly. I attached the 2 diffs.
follow-up: 6 comment:5 by , 11 years ago
Is the issue basically when going through the "pyramid" of tiles to generate, MgCooker is starting from the bottom instead of the top?
comment:6 by , 11 years ago
Replying to jng:
Is the issue basically when going through the "pyramid" of tiles to generate, MgCooker is starting from the bottom instead of the top?
I don't understand exactly what you mean. If I understand you, then this is the answer:
It doesn't matter where MgCooker starting the generation, bottom or top.
With the above example
With 1:90000 scale:
With 1:250 scale:
Another example:
I generate tiles with MgCooker in 1:8000 scale (and only this scal), it generates tiles with scaleindex=4. MapGuide using scaleindex=5 for 1:8000 scale.
Therefore when I view the Map in 1:4000 in Viewer (Fusion), it drawing 1:8000 tiles to the left-top corner (of the entire map) and start to generate the remaining tiles in 1:4000 scale (which are not found in the TileCache). (I will attach a picture about it soon.)
comment:7 by , 11 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Sorry I cannot accept this patch.
I compared the tile directories that the AJAX Viewer and MgCooker (without this patch) produces. They are identical in directory structure and content.
I then compared the AJAX viewer tile directory against the one produced by MgCooker with this patch. The directory structure is radically different, and the MgCooker one has way more blank tiles generated.
I then noticed the version of Maestro you're using. 5.0.0.7213 is beta 5. Final release is 5.0.0.7698. There have been many changes and fixes to MgCooker in the time between these releases.
I'm certain your issue would be solved by just upgrading your beta 5 installation of Maestro 5.0 to the final release.
comment:10 by , 11 years ago
Now we find the solution. Does matter the order of scales in MapDefinition in Finite Display Scales section.
We defined the scales in this order: 90000, 45000, 25000, 15000, 8000, 4000, 2000, 1000, 500, 250. But the right order of scales is 250, 500, 1000, 2000, 4000, 8000, 15000, 25000, 45000, 90000.
Until now it wasn't clear for us.
Best regards, Gyufi
Sorry for too much attachments. I have not received feedback after add attachment. Relevant files are SetupRun.cs and BatchSettings.cs