[mapguide-users] AGG vs GD rendering
I have put some screenshots on my blog contrasting the results of using AGG and GD renderers http://zacster.blogspot.com/2008/02/mapguide-20-agg-versus-gd-renderers.html The AGG lines seem to be too thick? z -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
[mapguide-users] Use of GDAL 3.2.2 in mgos2.0
Hi all, I wonder if i can use of GDAL 3.2.2 in MGOS 2.0, because it doesnt work with my tiled pictures. And if is posible what should i do? Klemen ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] Mapguide Trac is down
Zac Spitzer wrote: Running a report gives the following error: Report execution failed: database is locked Zac, I did a quick check and it seems to be working now. Best regards, -- ---+-- I set the clouds in motion - turn up | Frank Warmerdam, [EMAIL PROTECTED] light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush| President OSGeo, http://osgeo.org ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] MG 2.0 RC4 selection ALMOST working
Is that just for PostGIS, or is it happening for other feature providers too?
Currently Tom has moved that RC4 be tagged as release, so if this is something
that is not specific to the PostGIS provider and it is critical, you should
make sure to create a ticket in Trac with enough information (data, MGP
package, operating system, web server, which viewer you're using) to replicate
the problem.
If it is PostGIS-specific, then it likely won't be fixed in MapGuide. Bruno
Scott is doing a bunch of work on the PostGIS provider currently, so hopfully
it will be fixed through his efforts.
Jason
From: J Manafi
Subject: [mapguide-users] MG 2.0 RC4 selection ALMOST working
I was previously having issues with selection
(http://www.nabble.com/Postgis-Selection-Problem-%28additional%29-tt15466067s16610.html)
where it looked like my objects were selected, but nothing actually was, and
RC4 has made great strides to remedy this. However, my current situation is
this:
I can use the selection tool to make selections on the map. But, they don't
show up unless I click the 'Refresh Map' button. And even then, the statusbar
still shows No features selected. But when I run our script, the output is
correct and formatted accordingly. Yet, If I make a selection programmatically
like stated in the linked post, the selection is highlighted, and the statusbar
reads {0} features selected on {1} layers, yet shows that two layers are
selected in the selection panel, wells and blocks. And, no matter which block I
select--even if the block has nothing inside--the selection panel always shows
the same two wells selected. Also, if I make a selection with the tool, I
cannot use the 'Clear Selection' tool, but it is available when objects are
selected programmatically.
I don't know what is causing this behavior, but these are my observations so
far. If I come across anything new, I will update here. At least the selections
are working enough to use and test our scripts, and for that, I am glad.
winmail.dat___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] MG 2.0 RC4 selection ALMOST working
Oh, looking at your contribution to that thread, it looks like that problem is
Fusion-specific, which is different than ary's problem (which is
PostGIS-specific).
I'm seeing this Fusion selection problem myself on Windows2k3, IIS installation.
Jason
From: [EMAIL PROTECTED] on behalf of Jason Birch
Sent: Thu 2008-02-21 8:32 AM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] MG 2.0 RC4 selection ALMOST working
Is that just for PostGIS, or is it happening for other feature providers too?
Currently Tom has moved that RC4 be tagged as release, so if this is something
that is not specific to the PostGIS provider and it is critical, you should
make sure to create a ticket in Trac with enough information (data, MGP
package, operating system, web server, which viewer you're using) to replicate
the problem.
If it is PostGIS-specific, then it likely won't be fixed in MapGuide. Bruno
Scott is doing a bunch of work on the PostGIS provider currently, so hopfully
it will be fixed through his efforts.
Jason
From: J Manafi
Subject: [mapguide-users] MG 2.0 RC4 selection ALMOST working
I was previously having issues with selection
(http://www.nabble.com/Postgis-Selection-Problem-%28additional%29-tt15466067s16610.html)
where it looked like my objects were selected, but nothing actually was, and
RC4 has made great strides to remedy this. However, my current situation is
this:
I can use the selection tool to make selections on the map. But, they don't
show up unless I click the 'Refresh Map' button. And even then, the statusbar
still shows No features selected. But when I run our script, the output is
correct and formatted accordingly. Yet, If I make a selection programmatically
like stated in the linked post, the selection is highlighted, and the statusbar
reads {0} features selected on {1} layers, yet shows that two layers are
selected in the selection panel, wells and blocks. And, no matter which block I
select--even if the block has nothing inside--the selection panel always shows
the same two wells selected. Also, if I make a selection with the tool, I
cannot use the 'Clear Selection' tool, but it is available when objects are
selected programmatically.
I don't know what is causing this behavior, but these are my observations so
far. If I come across anything new, I will update here. At least the selections
are working enough to use and test our scripts, and for that, I am glad.
winmail.dat___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] MG 2.0 RC4 selection ALMOST working
Yeah, we use no PostGIS data; all of our files are SDF, and some are SDF
converted from Oracle. When we make a selection in Fusion, nothing is
highlighted until we click 'Refresh Map', and then our selection shows
up. It isn't a huge deal to us, but none of our selection properties
show up in the Selection Panel, even once highlighted.
Jason Birch wrote:
Oh, looking at your contribution to that thread, it looks like that problem is
Fusion-specific, which is different than ary's problem (which is
PostGIS-specific).
I'm seeing this Fusion selection problem myself on Windows2k3, IIS installation.
Jason
From: [EMAIL PROTECTED] on behalf of Jason Birch
Sent: Thu 2008-02-21 8:32 AM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] MG 2.0 RC4 selection ALMOST working
Is that just for PostGIS, or is it happening for other feature providers too?
Currently Tom has moved that RC4 be tagged as release, so if this is something that is not specific to the PostGIS provider and it is critical, you should make sure to create a ticket in Trac with enough information (data, MGP package, operating system, web server, which viewer you're using) to replicate the problem.
If it is PostGIS-specific, then it likely won't be fixed in MapGuide. Bruno Scott is doing a bunch of work on the PostGIS provider currently, so hopfully it will be fixed through his efforts.
Jason
From: J Manafi
Subject: [mapguide-users] MG 2.0 RC4 selection ALMOST working
I was previously having issues with selection
(http://www.nabble.com/Postgis-Selection-Problem-%28additional%29-tt15466067s16610.html)
where it looked like my objects were selected, but nothing actually was, and
RC4 has made great strides to remedy this. However, my current situation is
this:
I can use the selection tool to make selections on the map. But, they don't
show up unless I click the 'Refresh Map' button. And even then, the statusbar
still shows No features selected. But when I run our script, the output is
correct and formatted accordingly. Yet, If I make a selection programmatically
like stated in the linked post, the selection is highlighted, and the statusbar
reads {0} features selected on {1} layers, yet shows that two layers are
selected in the selection panel, wells and blocks. And, no matter which block I
select--even if the block has nothing inside--the selection panel always shows
the same two wells selected. Also, if I make a selection with the tool, I
cannot use the 'Clear Selection' tool, but it is available when objects are
selected programmatically.
I don't know what is causing this behavior, but these are my observations so far. If I come across anything new, I will update here. At least the selections are working enough to use and test our scripts, and for that, I am glad.
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] MG 2.0 RC4 selection ALMOST working
Note that if you are testing with the fusion/samples/mapguide/standard
example, the SelectionPanel and SelectionInfo widgets aren't enabled in
the ApplicationDefinition.xml file as shipped. You have to uncomment
those widgets in the file. We should probably change that so those
widgets are included by default.
In RC4 with the Sheboygan map, the selection should be appearing
highlighted as soon as it is selected.
Mike
Jason Birch wrote:
Oh, looking at your contribution to that thread, it looks like that problem is
Fusion-specific, which is different than ary's problem (which is
PostGIS-specific).
I'm seeing this Fusion selection problem myself on Windows2k3, IIS installation.
Jason
From: [EMAIL PROTECTED] on behalf of Jason Birch
Sent: Thu 2008-02-21 8:32 AM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] MG 2.0 RC4 selection ALMOST working
Is that just for PostGIS, or is it happening for other feature providers too?
Currently Tom has moved that RC4 be tagged as release, so if this is something that is not specific to the PostGIS provider and it is critical, you should make sure to create a ticket in Trac with enough information (data, MGP package, operating system, web server, which viewer you're using) to replicate the problem.
If it is PostGIS-specific, then it likely won't be fixed in MapGuide. Bruno Scott is doing a bunch of work on the PostGIS provider currently, so hopfully it will be fixed through his efforts.
Jason
From: J Manafi
Subject: [mapguide-users] MG 2.0 RC4 selection ALMOST working
I was previously having issues with selection
(http://www.nabble.com/Postgis-Selection-Problem-%28additional%29-tt15466067s16610.html)
where it looked like my objects were selected, but nothing actually was, and
RC4 has made great strides to remedy this. However, my current situation is
this:
I can use the selection tool to make selections on the map. But, they don't
show up unless I click the 'Refresh Map' button. And even then, the statusbar
still shows No features selected. But when I run our script, the output is
correct and formatted accordingly. Yet, If I make a selection programmatically
like stated in the linked post, the selection is highlighted, and the statusbar
reads {0} features selected on {1} layers, yet shows that two layers are
selected in the selection panel, wells and blocks. And, no matter which block I
select--even if the block has nothing inside--the selection panel always shows
the same two wells selected. Also, if I make a selection with the tool, I
cannot use the 'Clear Selection' tool, but it is available when objects are
selected programmatically.
I don't know what is causing this behavior, but these are my observations so far. If I come across anything new, I will update here. At least the selections are working enough to use and test our scripts, and for that, I am glad.
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] MG 2.0 RC4 selection ALMOST working
We realized about the Selection widgets, and we went ahead and included
those in the ApplicationDefinition.xml files that we used. We also noted
that the selection does indeed work with the Sheboygan maps, and as soon
as you select parcels, the map refreshes to indicate your selection, as
well as the SelectionInfo widget shows your selected objects. However,
we used the included Aqua ApplicationDefinition.xml template and only
changed the .MapDefinition files to reflect our maps instead of
Sheboygan and added our custom scripts/urls as widgets to test, and we
are having the selection issues. I even removed everything external to
the initial Aqua template except for one of our maps to load, and the
same thing occurs.
Also of note:
I used the FireBug extension to see the GET and POST commands, and when
running the Sheboygan sample, the selection command issues a POST of
.../fusion/MapGuide/php/Query.php followed by POST
.../fusion/MapGuide/php/Selection.php, whereas our maps only issue POST
of .../fusion/MapGuide/php/Query.php. I don't know if that has anything
to do with the SelectionInfo showing selected objects for Sheboygan and
not for us, or if all of these issues are just interrelated.
Jonathan
Mike Adair wrote:
Note that if you are testing with the fusion/samples/mapguide/standard
example, the SelectionPanel and SelectionInfo widgets aren't enabled
in the ApplicationDefinition.xml file as shipped. You have to
uncomment those widgets in the file. We should probably change that
so those widgets are included by default.
In RC4 with the Sheboygan map, the selection should be appearing
highlighted as soon as it is selected.
Mike
Jason Birch wrote:
Oh, looking at your contribution to that thread, it looks like that
problem is Fusion-specific, which is different than ary's problem
(which is PostGIS-specific).
I'm seeing this Fusion selection problem myself on Windows2k3, IIS
installation.
Jason
From: [EMAIL PROTECTED] on behalf of Jason Birch
Sent: Thu 2008-02-21 8:32 AM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] MG 2.0 RC4 selection ALMOST working
Is that just for PostGIS, or is it happening for other feature
providers too?
Currently Tom has moved that RC4 be tagged as release, so if this is
something that is not specific to the PostGIS provider and it is
critical, you should make sure to create a ticket in Trac with enough
information (data, MGP package, operating system, web server, which
viewer you're using) to replicate the problem.
If it is PostGIS-specific, then it likely won't be fixed in
MapGuide. Bruno Scott is doing a bunch of work on the PostGIS
provider currently, so hopfully it will be fixed through his efforts.
Jason
From: J Manafi
Subject: [mapguide-users] MG 2.0 RC4 selection ALMOST working
I was previously having issues with selection
(http://www.nabble.com/Postgis-Selection-Problem-%28additional%29-tt15466067s16610.html)
where it looked like my objects were selected, but nothing actually
was, and RC4 has made great strides to remedy this. However, my
current situation is this:
I can use the selection tool to make selections on the map. But, they
don't show up unless I click the 'Refresh Map' button. And even then,
the statusbar still shows No features selected. But when I run our
script, the output is correct and formatted accordingly. Yet, If I
make a selection programmatically like stated in the linked post, the
selection is highlighted, and the statusbar reads {0} features
selected on {1} layers, yet shows that two layers are selected in the
selection panel, wells and blocks. And, no matter which block I
select--even if the block has nothing inside--the selection panel
always shows the same two wells selected. Also, if I make a selection
with the tool, I cannot use the 'Clear Selection' tool, but it is
available when objects are selected programmatically.
I don't know what is causing this behavior, but these are my
observations so far. If I come across anything new, I will update
here. At least the selections are working enough to use and test our
scripts, and for that, I am glad.
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] MG 2.0 RC4 selection ALMOST working
What response are you getting from Query.php for your maps?
Mike
Jonathan Manafi wrote:
We realized about the Selection widgets, and we went ahead and
included those in the ApplicationDefinition.xml files that we used. We
also noted that the selection does indeed work with the Sheboygan
maps, and as soon as you select parcels, the map refreshes to indicate
your selection, as well as the SelectionInfo widget shows your
selected objects. However, we used the included Aqua
ApplicationDefinition.xml template and only changed the .MapDefinition
files to reflect our maps instead of Sheboygan and added our custom
scripts/urls as widgets to test, and we are having the selection
issues. I even removed everything external to the initial Aqua
template except for one of our maps to load, and the same thing occurs.
Also of note:
I used the FireBug extension to see the GET and POST commands, and
when running the Sheboygan sample, the selection command issues a POST
of .../fusion/MapGuide/php/Query.php followed by POST
.../fusion/MapGuide/php/Selection.php, whereas our maps only issue
POST of .../fusion/MapGuide/php/Query.php. I don't know if that has
anything to do with the SelectionInfo showing selected objects for
Sheboygan and not for us, or if all of these issues are just
interrelated.
Jonathan
Mike Adair wrote:
Note that if you are testing with the
fusion/samples/mapguide/standard example, the SelectionPanel and
SelectionInfo widgets aren't enabled in the ApplicationDefinition.xml
file as shipped. You have to uncomment those widgets in the file.
We should probably change that so those widgets are included by default.
In RC4 with the Sheboygan map, the selection should be appearing
highlighted as soon as it is selected.
Mike
Jason Birch wrote:
Oh, looking at your contribution to that thread, it looks like that
problem is Fusion-specific, which is different than ary's problem
(which is PostGIS-specific).
I'm seeing this Fusion selection problem myself on Windows2k3, IIS
installation.
Jason
From: [EMAIL PROTECTED] on behalf of Jason Birch
Sent: Thu 2008-02-21 8:32 AM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] MG 2.0 RC4 selection ALMOST working
Is that just for PostGIS, or is it happening for other feature
providers too?
Currently Tom has moved that RC4 be tagged as release, so if this is
something that is not specific to the PostGIS provider and it is
critical, you should make sure to create a ticket in Trac with
enough information (data, MGP package, operating system, web server,
which viewer you're using) to replicate the problem.
If it is PostGIS-specific, then it likely won't be fixed in
MapGuide. Bruno Scott is doing a bunch of work on the PostGIS
provider currently, so hopfully it will be fixed through his efforts.
Jason
From: J Manafi
Subject: [mapguide-users] MG 2.0 RC4 selection ALMOST working
I was previously having issues with selection
(http://www.nabble.com/Postgis-Selection-Problem-%28additional%29-tt15466067s16610.html)
where it looked like my objects were selected, but nothing actually
was, and RC4 has made great strides to remedy this. However, my
current situation is this:
I can use the selection tool to make selections on the map. But,
they don't show up unless I click the 'Refresh Map' button. And even
then, the statusbar still shows No features selected. But when I run
our script, the output is correct and formatted accordingly. Yet, If
I make a selection programmatically like stated in the linked post,
the selection is highlighted, and the statusbar reads {0} features
selected on {1} layers, yet shows that two layers are selected in
the selection panel, wells and blocks. And, no matter which block I
select--even if the block has nothing inside--the selection panel
always shows the same two wells selected. Also, if I make a
selection with the tool, I cannot use the 'Clear Selection' tool,
but it is available when objects are selected programmatically.
I don't know what is causing this behavior, but these are my
observations so far. If I come across anything new, I will update
here. At least the selections are working enough to use and test our
scripts, and for that, I am glad.
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
___
mapguide-users mailing list
Re: [mapguide-users] MG 2.0 RC4 selection ALMOST working
This is the response from a query:
Object not foundERROR: The specified object was not found.
The specified object was not found.
Exception occurred in method GetItem at line 117 in file
d:\buildforgeprojects\mapguide_open_source_v2
.0\build_22.4\mgdev\common\foundation\Data/NamedCollection.cpp
- GetItem line 117 file
d:\buildforgeprojects\mapguide_open_source_v2.0\build_22.4\mgdev\common\foundation
\Data/NamedCollection.cpp
general exceptiongeneral
exception{hasSelection:true,extents:{minx:-1841749.109647,miny:10697190
.314625,maxx:-1611134.1984211,maxy:10745845.651758},layers:[obstructions,platforms,wellbores
,pipelines,blocks],obstructions:{featureCount:1},platforms:{featureCount:3},wellbores:
{featureCount:15},pipelines:{featureCount:6},blocks:{featureCount:4}}
Mike Adair wrote:
What response are you getting from Query.php for your maps?
Mike
Jonathan Manafi wrote:
We realized about the Selection widgets, and we went ahead and
included those in the ApplicationDefinition.xml files that we used.
We also noted that the selection does indeed work with the Sheboygan
maps, and as soon as you select parcels, the map refreshes to
indicate your selection, as well as the SelectionInfo widget shows
your selected objects. However, we used the included Aqua
ApplicationDefinition.xml template and only changed the
.MapDefinition files to reflect our maps instead of Sheboygan and
added our custom scripts/urls as widgets to test, and we are having
the selection issues. I even removed everything external to the
initial Aqua template except for one of our maps to load, and the
same thing occurs.
Also of note:
I used the FireBug extension to see the GET and POST commands, and
when running the Sheboygan sample, the selection command issues a
POST of .../fusion/MapGuide/php/Query.php followed by POST
.../fusion/MapGuide/php/Selection.php, whereas our maps only issue
POST of .../fusion/MapGuide/php/Query.php. I don't know if that has
anything to do with the SelectionInfo showing selected objects for
Sheboygan and not for us, or if all of these issues are just
interrelated.
Jonathan
Mike Adair wrote:
Note that if you are testing with the
fusion/samples/mapguide/standard example, the SelectionPanel and
SelectionInfo widgets aren't enabled in the
ApplicationDefinition.xml file as shipped. You have to uncomment
those widgets in the file. We should probably change that so those
widgets are included by default.
In RC4 with the Sheboygan map, the selection should be appearing
highlighted as soon as it is selected.
Mike
Jason Birch wrote:
Oh, looking at your contribution to that thread, it looks like that
problem is Fusion-specific, which is different than ary's problem
(which is PostGIS-specific).
I'm seeing this Fusion selection problem myself on Windows2k3, IIS
installation.
Jason
From: [EMAIL PROTECTED] on behalf of Jason Birch
Sent: Thu 2008-02-21 8:32 AM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] MG 2.0 RC4 selection ALMOST working
Is that just for PostGIS, or is it happening for other feature
providers too?
Currently Tom has moved that RC4 be tagged as release, so if this
is something that is not specific to the PostGIS provider and it is
critical, you should make sure to create a ticket in Trac with
enough information (data, MGP package, operating system, web
server, which viewer you're using) to replicate the problem.
If it is PostGIS-specific, then it likely won't be fixed in
MapGuide. Bruno Scott is doing a bunch of work on the PostGIS
provider currently, so hopfully it will be fixed through his efforts.
Jason
From: J Manafi
Subject: [mapguide-users] MG 2.0 RC4 selection ALMOST working
I was previously having issues with selection
(http://www.nabble.com/Postgis-Selection-Problem-%28additional%29-tt15466067s16610.html)
where it looked like my objects were selected, but nothing actually
was, and RC4 has made great strides to remedy this. However, my
current situation is this:
I can use the selection tool to make selections on the map. But,
they don't show up unless I click the 'Refresh Map' button. And
even then, the statusbar still shows No features selected. But when
I run our script, the output is correct and formatted accordingly.
Yet, If I make a selection programmatically like stated in the
linked post, the selection is highlighted, and the statusbar reads
{0} features selected on {1} layers, yet shows that two layers are
selected in the selection panel, wells and blocks. And, no matter
which block I select--even if the block has nothing inside--the
selection panel always shows the same two wells selected. Also, if
I make a selection with the tool, I cannot use the 'Clear
Selection' tool, but it is available when objects are selected
programmatically.
I don't know what is causing this behavior, but these are my
observations so far. If I
RE: [mapguide-users] AGG vs GD rendering
Antialiased lines of width 1 pixel do generally look a bit thicker than they should, when compared to non-AA lines. This is because exact pixel coverage is computed, and neighboring pixels are also affected a little bit. Some more in-depth explanations can be found here: http://www.antigrain.com/tips/line_alignment/line_alignment.agdoc.html#PAGE_LINE_ALIGNMENT http://www.antigrain.com/doc/introduction/introduction.agdoc.html#toc0002 That said, it may be possible to play around with gamma correction values to make the lines less visually thick, but they would still look fuzzy. However, a different gamma would be necessary for dark vs. light background colors, so it would not be a universal solution. Traian -Original Message- From: [EMAIL PROTECTED] [mailto:mapguide-users- [EMAIL PROTECTED] On Behalf Of Zac Spitzer Sent: Thursday, February 21, 2008 4:23 AM To: MapGuide Users Mail List Subject: [mapguide-users] AGG vs GD rendering I have put some screenshots on my blog contrasting the results of using AGG and GD renderers http://zacster.blogspot.com/2008/02/mapguide-20-agg-versus-gd- renderers.html The AGG lines seem to be too thick? z -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] AGG vs GD rendering
hi! What is faster AGG vs GD? What are yours experience? macieksk ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] AGG vs GD rendering
Depends on the data. In general I expect AGG to be faster in text-heavy maps and GD to be faster in polygon heavy maps. Line-heavy maps would be a tossup, depending on line width. YMMV. Traian From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Maciej Skorczewski [EMAIL PROTECTED] Sent: Thursday, February 21, 2008 4:05 PM To: MapGuide Users Mail List Subject: Re: [mapguide-users] AGG vs GD rendering hi! What is faster AGG vs GD? What are yours experience? macieksk ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
[mapguide-users] MGOS 2 RC4 Observations
Finally got around to testing RC4 a little and here are my observations. The test platform is a VMWare instance running Windows XP, using the .NET web extensions, and testing with IE and Firefox. Testing was difficult due to instability and crashing issues with Autodesk MapGuide Studio 2009 beta, but I tried to make the best of it. - Tooltips do not work for any flexible layout with any layer source, including the Sheboygan samples. They work for normal layouts. - With flexible layouts, when using the selection tool, no attributes for the selected object (which always highlighted properly) were visible in the Selection Panel, although the layer and number of selected objects were properly displayed. This was the case for any layer source, including the Sheboygan samples. Selection attributes work fine in the properties pane in standard layouts still. Other than that, everything seemed to work okay in my informal testing and Fusion is beyond cool. I have not tried to migrate any custom 1.2 apps over yet, so cannot comment on that aspect at this time. Andy Morsell, P.E. Spatial Integrators, Inc. http://www.SpatialGIS.com ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] MG 2.0 RC4 selection ALMOST working
The exception is corrupting the json formatted response so when
Query.php returns there is a (likely suppressed) javascript error that
prevents Fusion from processing the selection and hence other widgets
from responding to it to load the selection.
Mike, we should be able to reproduce this with some of Jason's data.
Cheers
Paul
On 21-Feb-08, at 3:14 PM, Jonathan Manafi wrote:
This is the response from a query:
Object not foundERROR: The specified object was not found.
The specified object was not found.
Exception occurred in method GetItem at line 117 in file d:
\buildforgeprojects\mapguide_open_source_v2
.0\build_22.4\mgdev\common\foundation\Data/NamedCollection.cpp
- GetItem line 117 file d:\buildforgeprojects
\mapguide_open_source_v2.0\build_22.4\mgdev\common\foundation
\Data/NamedCollection.cpp
general exceptiongeneral exception{hasSelection:true,extents:
{minx:-1841749.109647,miny:10697190
.314625,maxx:-1611134.1984211,maxy:10745845.651758},layers:
[obstructions,platforms,wellbores
,pipelines,blocks],obstructions:{featureCount:1},platforms:
{featureCount:3},wellbores:
{featureCount:15},pipelines:{featureCount:6},blocks:
{featureCount:4}}
Mike Adair wrote:
What response are you getting from Query.php for your maps?
Mike
Jonathan Manafi wrote:
We realized about the Selection widgets, and we went ahead and
included those in the ApplicationDefinition.xml files that we
used. We also noted that the selection does indeed work with the
Sheboygan maps, and as soon as you select parcels, the map
refreshes to indicate your selection, as well as the SelectionInfo
widget shows your selected objects. However, we used the included
Aqua ApplicationDefinition.xml template and only changed
the .MapDefinition files to reflect our maps instead of Sheboygan
and added our custom scripts/urls as widgets to test, and we are
having the selection issues. I even removed everything external to
the initial Aqua template except for one of our maps to load, and
the same thing occurs.
Also of note:
I used the FireBug extension to see the GET and POST commands, and
when running the Sheboygan sample, the selection command issues a
POST of .../fusion/MapGuide/php/Query.php followed by POST .../
fusion/MapGuide/php/Selection.php, whereas our maps only issue
POST of .../fusion/MapGuide/php/Query.php. I don't know if that
has anything to do with the SelectionInfo showing selected objects
for Sheboygan and not for us, or if all of these issues are just
interrelated.
Jonathan
Mike Adair wrote:
Note that if you are testing with the fusion/samples/mapguide/
standard example, the SelectionPanel and SelectionInfo widgets
aren't enabled in the ApplicationDefinition.xml file as shipped.
You have to uncomment those widgets in the file. We should
probably change that so those widgets are included by default.
In RC4 with the Sheboygan map, the selection should be appearing
highlighted as soon as it is selected.
Mike
Jason Birch wrote:
Oh, looking at your contribution to that thread, it looks like
that problem is Fusion-specific, which is different than ary's
problem (which is PostGIS-specific).
I'm seeing this Fusion selection problem myself on Windows2k3,
IIS installation.
Jason
From: [EMAIL PROTECTED] on behalf of Jason
Birch
Sent: Thu 2008-02-21 8:32 AM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] MG 2.0 RC4 selection ALMOST working
Is that just for PostGIS, or is it happening for other feature
providers too?
Currently Tom has moved that RC4 be tagged as release, so if
this is something that is not specific to the PostGIS provider
and it is critical, you should make sure to create a ticket in
Trac with enough information (data, MGP package, operating
system, web server, which viewer you're using) to replicate the
problem.
If it is PostGIS-specific, then it likely won't be fixed in
MapGuide. Bruno Scott is doing a bunch of work on the PostGIS
provider currently, so hopfully it will be fixed through his
efforts.
Jason
From: J Manafi
Subject: [mapguide-users] MG 2.0 RC4 selection ALMOST working
I was previously having issues with selection (http://www.nabble.com/Postgis-Selection-Problem-%28additional%29-tt15466067s16610.html
) where it looked like my objects were selected, but nothing
actually was, and RC4 has made great strides to remedy this.
However, my current situation is this:
I can use the selection tool to make selections on the map. But,
they don't show up unless I click the 'Refresh Map' button. And
even then, the statusbar still shows No features selected. But
when I run our script, the output is correct and formatted
accordingly. Yet, If I make a selection programmatically like
stated in the linked post, the selection is highlighted, and the
statusbar reads {0} features selected on {1} layers, yet shows
that two
Re: [mapguide-users] MG 2.0 RC4 selection ALMOST working
ahhh ajax. the secret deadly ninja of web apps.
On Thu, Feb 21, 2008 at 7:34 PM, Paul Spencer [EMAIL PROTECTED] wrote:
The exception is corrupting the json formatted response so when
Query.php returns there is a (likely suppressed) javascript error that
prevents Fusion from processing the selection and hence other widgets
from responding to it to load the selection.
Mike, we should be able to reproduce this with some of Jason's data.
Cheers
Paul
On 21-Feb-08, at 3:14 PM, Jonathan Manafi wrote:
This is the response from a query:
Object not foundERROR: The specified object was not found.
The specified object was not found.
Exception occurred in method GetItem at line 117 in file d:
\buildforgeprojects\mapguide_open_source_v2
.0\build_22.4\mgdev\common\foundation\Data/NamedCollection.cpp
- GetItem line 117 file d:\buildforgeprojects
\mapguide_open_source_v2.0\build_22.4\mgdev\common\foundation
\Data/NamedCollection.cpp
general exceptiongeneral exception{hasSelection:true,extents:
{minx:-1841749.109647,miny:10697190
.314625,maxx:-1611134.1984211,maxy:10745845.651758},layers:
[obstructions,platforms,wellbores
,pipelines,blocks],obstructions:{featureCount:1},platforms:
{featureCount:3},wellbores:
{featureCount:15},pipelines:{featureCount:6},blocks:
{featureCount:4}}
Mike Adair wrote:
What response are you getting from Query.php for your maps?
Mike
Jonathan Manafi wrote:
We realized about the Selection widgets, and we went ahead and
included those in the ApplicationDefinition.xml files that we
used. We also noted that the selection does indeed work with the
Sheboygan maps, and as soon as you select parcels, the map
refreshes to indicate your selection, as well as the SelectionInfo
widget shows your selected objects. However, we used the included
Aqua ApplicationDefinition.xml template and only changed
the .MapDefinition files to reflect our maps instead of Sheboygan
and added our custom scripts/urls as widgets to test, and we are
having the selection issues. I even removed everything external to
the initial Aqua template except for one of our maps to load, and
the same thing occurs.
Also of note:
I used the FireBug extension to see the GET and POST commands, and
when running the Sheboygan sample, the selection command issues a
POST of .../fusion/MapGuide/php/Query.php followed by POST .../
fusion/MapGuide/php/Selection.php, whereas our maps only issue
POST of .../fusion/MapGuide/php/Query.php. I don't know if that
has anything to do with the SelectionInfo showing selected objects
for Sheboygan and not for us, or if all of these issues are just
interrelated.
Jonathan
Mike Adair wrote:
Note that if you are testing with the fusion/samples/mapguide/
standard example, the SelectionPanel and SelectionInfo widgets
aren't enabled in the ApplicationDefinition.xml file as shipped.
You have to uncomment those widgets in the file. We should
probably change that so those widgets are included by default.
In RC4 with the Sheboygan map, the selection should be appearing
highlighted as soon as it is selected.
Mike
Jason Birch wrote:
Oh, looking at your contribution to that thread, it looks like
that problem is Fusion-specific, which is different than ary's
problem (which is PostGIS-specific).
I'm seeing this Fusion selection problem myself on Windows2k3,
IIS installation.
Jason
From: [EMAIL PROTECTED] on behalf of Jason
Birch
Sent: Thu 2008-02-21 8:32 AM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] MG 2.0 RC4 selection ALMOST working
Is that just for PostGIS, or is it happening for other feature
providers too?
Currently Tom has moved that RC4 be tagged as release, so if
this is something that is not specific to the PostGIS provider
and it is critical, you should make sure to create a ticket in
Trac with enough information (data, MGP package, operating
system, web server, which viewer you're using) to replicate the
problem.
If it is PostGIS-specific, then it likely won't be fixed in
MapGuide. Bruno Scott is doing a bunch of work on the PostGIS
provider currently, so hopfully it will be fixed through his
efforts.
Jason
From: J Manafi
Subject: [mapguide-users] MG 2.0 RC4 selection ALMOST working
I was previously having issues with selection (
http://www.nabble.com/Postgis-Selection-Problem-%28additional%29-tt15466067s16610.html
) where it looked like my objects were selected, but nothing
actually was, and RC4 has made great strides to remedy this.
However, my current situation is this:
I can use the selection tool to make selections on the map. But,
they don't show up unless I click the 'Refresh Map' button. And
even then, the statusbar still shows No features selected. But
when I run our script, the output is correct
Re: [mapguide-users] MG 2.0 RC4 selection ALMOST working
Ok, I found Jason's problem but it was in code that is not in the
general release so I don't know where the other problem is coming from
even though it has the same exception. In Jason's case, there was a
layer being programmatically created that had an incorrect property
mapping (it referred to a field in the feature source that didn't
exist).
Is it possible to get an mpg of your map/layer/data or a subset enough
to reproduce the problem? You can send directly to me.
Cheers
Paul
On 21-Feb-08, at 7:43 PM, Ryan Northcott wrote:
ahhh ajax. the secret deadly ninja of web apps.
On Thu, Feb 21, 2008 at 7:34 PM, Paul Spencer [EMAIL PROTECTED]
wrote:
The exception is corrupting the json formatted response so when
Query.php returns there is a (likely suppressed) javascript error that
prevents Fusion from processing the selection and hence other widgets
from responding to it to load the selection.
Mike, we should be able to reproduce this with some of Jason's data.
Cheers
Paul
On 21-Feb-08, at 3:14 PM, Jonathan Manafi wrote:
This is the response from a query:
Object not foundERROR: The specified object was not found.
The specified object was not found.
Exception occurred in method GetItem at line 117 in file d:
\buildforgeprojects\mapguide_open_source_v2
.0\build_22.4\mgdev\common\foundation\Data/NamedCollection.cpp
- GetItem line 117 file d:\buildforgeprojects
\mapguide_open_source_v2.0\build_22.4\mgdev\common\foundation
\Data/NamedCollection.cpp
general exceptiongeneral exception{hasSelection:true,extents:
{minx:-1841749.109647,miny:10697190
.314625,maxx:-1611134.1984211,maxy:10745845.651758},layers:
[obstructions,platforms,wellbores
,pipelines,blocks],obstructions:{featureCount:
1},platforms:
{featureCount:3},wellbores:
{featureCount:15},pipelines:{featureCount:6},blocks:
{featureCount:4}}
Mike Adair wrote:
What response are you getting from Query.php for your maps?
Mike
Jonathan Manafi wrote:
We realized about the Selection widgets, and we went ahead and
included those in the ApplicationDefinition.xml files that we
used. We also noted that the selection does indeed work with the
Sheboygan maps, and as soon as you select parcels, the map
refreshes to indicate your selection, as well as the SelectionInfo
widget shows your selected objects. However, we used the included
Aqua ApplicationDefinition.xml template and only changed
the .MapDefinition files to reflect our maps instead of Sheboygan
and added our custom scripts/urls as widgets to test, and we are
having the selection issues. I even removed everything external to
the initial Aqua template except for one of our maps to load, and
the same thing occurs.
Also of note:
I used the FireBug extension to see the GET and POST commands, and
when running the Sheboygan sample, the selection command issues a
POST of .../fusion/MapGuide/php/Query.php followed by POST .../
fusion/MapGuide/php/Selection.php, whereas our maps only issue
POST of .../fusion/MapGuide/php/Query.php. I don't know if that
has anything to do with the SelectionInfo showing selected objects
for Sheboygan and not for us, or if all of these issues are just
interrelated.
Jonathan
Mike Adair wrote:
Note that if you are testing with the fusion/samples/mapguide/
standard example, the SelectionPanel and SelectionInfo widgets
aren't enabled in the ApplicationDefinition.xml file as shipped.
You have to uncomment those widgets in the file. We should
probably change that so those widgets are included by default.
In RC4 with the Sheboygan map, the selection should be appearing
highlighted as soon as it is selected.
Mike
Jason Birch wrote:
Oh, looking at your contribution to that thread, it looks like
that problem is Fusion-specific, which is different than ary's
problem (which is PostGIS-specific).
I'm seeing this Fusion selection problem myself on Windows2k3,
IIS installation.
Jason
From: [EMAIL PROTECTED] on behalf of Jason
Birch
Sent: Thu 2008-02-21 8:32 AM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] MG 2.0 RC4 selection ALMOST
working
Is that just for PostGIS, or is it happening for other feature
providers too?
Currently Tom has moved that RC4 be tagged as release, so if
this is something that is not specific to the PostGIS provider
and it is critical, you should make sure to create a ticket in
Trac with enough information (data, MGP package, operating
system, web server, which viewer you're using) to replicate the
problem.
If it is PostGIS-specific, then it likely won't be fixed in
MapGuide. Bruno Scott is doing a bunch of work on the PostGIS
provider currently, so hopfully it will be fixed through his
efforts.
Jason
From: J Manafi
Subject: [mapguide-users] MG 2.0 RC4 selection ALMOST working
I was previously having issues with selection
Re: [mapguide-users] MGOS 2 RC4 Observations
My observations so far: - Feature Joins are now working properly again (took 3 RCs to get there), but performance has somewhat degraded as a result. - There are lots of minor bugs/annoyances/usability problems with Fusion and/or the 5 example templates. Case in point: the number of Fusion related bugs I've filed on Trac. My view as a result is to stay w/ 1.2 for a bit longer, and use 2.0 as a testbed for new Fusion-driven designs, with full migration on the next 2.x point release. - Jackie Andy Morsell wrote: Finally got around to testing RC4 a little and here are my observations. The test platform is a VMWare instance running Windows XP, using the .NET web extensions, and testing with IE and Firefox. Testing was difficult due to instability and crashing issues with Autodesk MapGuide Studio 2009 beta, but I tried to make the best of it. - Tooltips do not work for any flexible layout with any layer source, including the Sheboygan samples. They work for normal layouts. - With flexible layouts, when using the selection tool, no attributes for the selected object (which always highlighted properly) were visible in the Selection Panel, although the layer and number of selected objects were properly displayed. This was the case for any layer source, including the Sheboygan samples. Selection attributes work fine in the properties pane in standard layouts still. Other than that, everything seemed to work okay in my informal testing and Fusion is beyond cool. I have not tried to migrate any custom 1.2 apps over yet, so cannot comment on that aspect at this time. Andy Morsell, P.E. Spatial Integrators, Inc. http://www.SpatialGIS.com ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users -- View this message in context: http://www.nabble.com/MGOS-2-RC4-Observations-tp15624277s16610p15628228.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
