[Xastir-dev] Proposal for eliminating the .osm files;

[Jerry Dunmire]

I agree that the Map Chooser is the right place. The problem that I'm
seeing is that the code in the Map Chooser is structured around file
names, not file contents. That makes the code fast. However, things
like projections, zoom levels, copyright notices, etc. should, in my
opinion, be specified in the file. I don't think trying to come up
with a lot of new extensions, nor having to parse file names, is a
particularly good way to go. (Though I do admit it is easy!)

...jerry


On Thu, Jun 17, 2010 at 3:03 PM, Curt, WE7U <curt.we7u at gmail.com> wrote:
> On Thu, 17 Jun 2010, Paul J. Morris wrote:
>
>> The Map Chooser feels like a very plausible (and general) place to warn
>> the user about non-standard map behavior associated with the inclusion
>> of particular layers.
>
> The more I think about it the more I agree.  We don't currently have
> any way to warn the users about odd projections or changes in
> operation based on map selections now.  If a general method could be
> implemented it could help with other things that come up in the
> future.  Even copyright notices for datasets that require it.
>
> Tigermap had an odd projection and it would have been nice to warn
> the users about that.  A moot point now.
>
> --
> Curt, WE7U.                         <http://www.eskimo.com/~archer>
>   APRS:  Where it's at!                    <http://www.xastir.org>
>  Lotto:  A tax on people who are bad at math. - unknown
> Windows:  Microsoft's tax on computer illiterates. - WE7U.
> The world DOES revolve around me:  I picked the coordinate system!"
> _______________________________________________
> Xastir-dev mailing list
> Xastir-dev at lists.xastir.org
> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
>