[Carto] RE: Sample MRI File - Version 0.12

[Landon Blake]

Bob,

I just read your questions this morning. I need some time to think about them before I respond.

Thanks,

Landon
Office Phone Number: (209) 946-0268
Cell Phone Number: (209) 992-0658
 
 
________________________________________
From: Bob Basques [mailto:Bob.Basques at ci.stpaul.mn.us] 
Sent: Monday, May 03, 2010 11:41 AM
To: Landon Blake; carto at lists.osgeo.org; Tyler Mitchell (OSGeo)
Subject: Re: Sample MRI File - Version 0.12

All, 

Ok, looking through it. . . .BTW, I'm looking at things with respect to PDF output (Including 3D models eventually). 

Comments on Spec: 

*  Should "DPI" be considered a valid INIT type for resolution?  Wouldn't px, em or ?? fit better? 
*  Should "width / height" really be "X / Y / (Z)" ? 
*  Don't know that the "mapframes" container is needed.  Just process each "mapframe" inside of "mapframes" no matter what. 
*  Are unique "SECTION name=" defaulted to requiring unique values, should NAME be moved out of PARAM status?  For more than one Section of type "LAYOUT" for example. 
*  Mapframe Stacking isn't accounted for (z order) for more than one MapFrame, might want to display on mapframe partial over another.  Could get away with sending a polygon instead of width / height - X / Y, although that would get messy quick  Might have to bite the bullet there though.  Another use for this, would be to print out a result on top of a template that might already contain a MAPFRAME of the same name.  The stacking would become needed in this situation too I think.  Over or under the template? 
*  I'm lost on the mapframe>scale value, what to what, relative to what?  Should the unit size be passed in for the Model_space_position as well to make this work? 
*  Should mapframe properties be referenced to a mapframe  like : <map_frame_properties mapframe="Main Map Frame"> 

Suggested additions: 

*  Set up more than one Map view in this example . . . Will help with referencing question I have above. 
*  Captioning for Mapframes. 
*  Stat's block, for outputting in text form, the descriptive elements of the print. 
*  There was mention of adding in the Time of day to the date, I would second this. 
*  Add metadata sub section to each layer. 

bobb 



>>> "Landon Blake" <lblake at ksninc.com> wrote:
I don't think that is the most current XML file. Try the attached.

Landon
Office Phone Number: (209) 946-0268
Cell Phone Number: (209) 992-0658


________________________________________
From: carto-bounces at lists.osgeo.org [mailto:carto-bounces at lists.osgeo.org] On Behalf Of Bob Basques
Sent: Monday, May 03, 2010 11:02 AM
To: carto at lists.osgeo.org; Tyler Mitchell (OSGeo)
Subject: Re: [Carto] Requesting Tentative Consensus on MRI FileFormat- Version 0.12

Is this the latest stuff being talked about?

http://lists.osgeo.org/pipermail/carto/attachments/20100412/a894c7f6/mri_stripped_version_0-11-0001.xml

http://lists.osgeo.org/pipermail/carto/attachments/20100412/a894c7f6/MRI_Changes-0001.obj  (really a PDF . . .)


>>> "Tyler Mitchell (OSGeo)" <tmitchell at osgeo.org> wrote:
On 05/03/2010 10:23 AM, Landon Blake wrote:
> We could certainly define "dynamic" components using proportions and
> anchoring, but that will increase the complexity of the map rendering
> engine quite a bit. I'd prefer to see that done in the prior step by
> a nother program in the tool chain.
>
> That just my opinion though.

I sure agree.  Anything that has a user interface can be considered
slightly off-topic for now at least.  The hope is to solidify an XML
specification and then let others build to the specification.

Of course, once we have it settled, then I'm sure several of us will
want to try various approaches and report back here :)
_______________________________________________
Carto mailing list
Carto at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/carto


Warning:
Information provided via electronic media is not guaranteed against defects including translation and transmission errors. If the reader is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this information in error, please notify the sender immediately.