Changes between Version 25 and Version 26 of MapGuideRfc14
- Timestamp:
- 02/02/07 14:02:14 (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MapGuideRfc14
v25 v26 4 4 More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page. 5 5 6 = Status=6 == Status == 7 7 8 8 ||RFC Template Version||(1.0)|| … … 20 20 ||-1|| || 21 21 22 = Overview=22 == Overview == 23 23 24 24 This document describes a proposal for adding a cartographic styling engine to !MapGuide. The main goal is to be able to handle point, line, and fill styles as sophisticated as AutoCAD as well as being able to represent all symbols described in … … 29 29 Note: the FGDC standard goes beyond line styles, fill styles, and point styles – we are ignoring anything else in that document. 30 30 31 = Motivation=31 == Motivation == 32 32 33 33 Most GIS applications are in need of very sophisticated symbolization. In many countries published maps must adhere to high standards that are often even written into law. This RFC introduces a high quality symbolization engine for !MapGuide. … … 35 35 The new engine will also support using point symbols as labels. This addresses a long standing !MapGuide request for being able to create maps that use highway symbolization as part of labeling. 36 36 37 = Proposed Solution=37 == Proposed Solution == 38 38 39 39 The proposal is to create one engine that will satisfy the requirements of all three symbolizations (point, line, and area). This engine will use as input a new XML resource, parameters, and geometry, and will use the rendering interface of !MapGuide to perform high quality stylization from those inputs. The resource format and the engine will ultimately be able to handle all three symbolization types. … … 281 281 The upper / lower dashing has zero start offset, whereas the cross tick has a 28 mm offset. This horizontally positions the first cross tick at the center of the first long dash in the second cycle of upper / lower dashing. 282 282 283 = Implications=283 == Implications == 284 284 285 285 The new symbol definitions and cartographic engine will obviously have an impact on the !LayerDefinition XML schema. Those changes will be proposed in a subsequent RFC. That RFC will discuss any potential compatibility issues, however non are anticipated at this time. 286 286 287 = Test Plan=287 == Test Plan == 288 288 289 289 Unit tests will be written to verify the new cartographic styling engine. In addition we will also create a sample symbol library to use for testing. 290 290 291 = Funding/Resources=291 == Funding/Resources == 292 292 293 293 Autodesk will provide resources to implement the core symbolization engine and detailed implementation for point symbols and label symbols. If time allows we will also implement some portion of the line symbolization. In the future we plan to finish the symbolization engine to also include area symbolization. Timing for this has yet to be determined. 294 294 295 = Appendix A=295 == Appendix A == 296 296 297 297 Here are links to the symbolization schema (xsd) and to a zip file containing generated HTML documentation for the schema.
