Hi Andrea,
Excellent analysis and some very good prospective optimisations there.
In order to get the fully benefit the styles must not use partial
> transparency, and I had
to fix one of the styles accordingly (believe it was lakes, not 100% sure).
Interesting. Originally I used transparency, but for my re-made styles
(which is what you're using) I got rid of that because I figured it would
slow stuff down and I also realised that I could get the same colour
without it. I'll definitely further-optimise my SLD's.
Then again, Jonathan has this data in Oracle... I did not want to venture
> there: loading
> data there is a pain, the styles need fixing because of the uppercase
> attributes,
> and honestly, why waste an open source developer spare time on closed
> source databases anyways?
Completely concur. And thanks for all your work given it's your free time!
(That said, these styles are completely interchangeable between shapefile
and our Oracle, with just one change - search/replace "ROAD_NO" (shapefile)
to "ROAD_NUMBER" (Oracle)).
Now, this is PostGIS specific (no
> plain simplification in Oracle, only the topology preserving one is
> available, which
> is supposedly more expensive than not doing it, at least, it is in
> PostGIS),
There is plain "simplify" in Oracle:
http://docs.oracle.com/cd/E11882_01/appdev.112/e11830/sdo_util.htm#BJEHCIBF-
that tool is available via Oracle Locator and doesn't require Oracle
Spatial. It's just a simple Douglas-Peucker implementation
*"Topological characteristics of the input geometry might not be maintained
after simplification."*
Spatialite of course has one too -
http://www.gaia-gis.it/gaia-sins/spatialite-sql-4.1.0.html#p6
And with MSSQL Server it seems to be "Reduce" -
http://technet.microsoft.com/en-us/library/bb933814.aspx
I don't know if OGR is used as an input source in GeoServer (shapefile
reading?), but it appears to have a Simplify function too (If I'm looking
in the right place) -
http://www.gdal.org/ogr/classOGRGeometry.html#afd3ea0ffa1e2994427032d0212206ccf
So the ST_Simplify optimisation could potentially be carried over to other
datastores (although that does presume that ST_Simplify is as fast on the
other implementations as it is in PostGIS).
Again, thanks for your free-time work! :-)
Cheers,
Jonathan
--
This transmission is intended for the named addressee(s) only and may
contain sensitive or protectively marked material up to RESTRICTED and
should be handled accordingly. Unless you are the named addressee (or
authorised to receive it for the addressee) you may not copy or use it, or
disclose it to anyone else. If you have received this transmission in error
please notify the sender immediately. All email traffic sent to or from us,
including without limitation all GCSX traffic, may be subject to recording
and/or monitoring in accordance with relevant legislation.
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
