Add a scale for reference

[agareau-zz]

No description provided.

[smathermather]

scale on a world Mercator map would be begging for trouble...

[danavery]

It's certainly bad at large scales--maybe it'll work at the scales we're
using here? I'm not sure what the distortion is from top-to-bottom of the
viewable area at this scale. I've checked one in on trailsy-dev just for
fun.

On Wed, Nov 13, 2013 at 2:43 PM, Stephen Mather [email protected]:

scale on a world Mercator map would be begging for trouble...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/238#issuecomment-28441781
.

[smathermather]

30+ % difference W/E vs. N/S, if memory serves me....

Just the cost of being able to use anyone's tiles.

Dan Avery [email protected] wrote:

It's certainly bad at large scales--maybe it'll work at the scales we're
using here? I'm not sure what the distortion is from top-to-bottom of the
viewable area at this scale. I've checked one in on trailsy-dev just for
fun.

On Wed, Nov 13, 2013 at 2:43 PM, Stephen Mather [email protected]:

scale on a world Mercator map would be begging for trouble...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/238#issuecomment-28441781
.

—
Reply to this email directly or view it on GitHub.

[danavery]

Whoa, really? At these scales? OK, I'll remove it.

On Wed, Nov 13, 2013 at 2:50 PM, Stephen Mather [email protected]:

30+ % difference W/E vs. N/S, if memory serves me....

Just the cost of being able to use anyone's tiles.

Dan Avery [email protected] wrote:

It's certainly bad at large scales--maybe it'll work at the scales we're
using here? I'm not sure what the distortion is from top-to-bottom of the
viewable area at this scale. I've checked one in on trailsy-dev just for
fun.

On Wed, Nov 13, 2013 at 2:43 PM, Stephen Mather [email protected]:

scale on a world Mercator map would be begging for trouble...

—
Reply to this email directly or view it on GitHub<
https://github.com/codeforamerica/trailsy/issues/238#issuecomment-28441781>

.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/238#issuecomment-28442315
.

[danavery]

Oh wait, I get it now. N/S vs E/W. I was thinking just the difference in
E/W from top to bottom of the visible area.

I suppose it still might be useful for just the E/W part of things. The
GMaps one is at least fun to watch while moving the map around at
continent-level scales.

On Wed, Nov 13, 2013 at 3:07 PM, Dan Avery [email protected]:

Whoa, really? At these scales? OK, I'll remove it.

On Wed, Nov 13, 2013 at 2:50 PM, Stephen Mather [email protected]:

30+ % difference W/E vs. N/S, if memory serves me....

Just the cost of being able to use anyone's tiles.

Dan Avery [email protected] wrote:

It's certainly bad at large scales--maybe it'll work at the scales we're
using here? I'm not sure what the distortion is from top-to-bottom of
the
viewable area at this scale. I've checked one in on trailsy-dev just for
fun.

On Wed, Nov 13, 2013 at 2:43 PM, Stephen Mather <
[email protected]>wrote:

scale on a world Mercator map would be begging for trouble...

—
Reply to this email directly or view it on GitHub<
https://github.com/codeforamerica/trailsy/issues/238#issuecomment-28441781>

.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/238#issuecomment-28442315
.

[agareau-zz]

I think I must have been misunderstood on GitHub regarding my scale
question. Since there is not a measuring tool on the application, I was
speaking purely as a cartographer and end user at that point. It would be
nice if there was some type of static scale bar or ratio.. This can be
done by knowing your scale factor. I know when I have developed web maps
in the past I would have to set some type of scale factor for each static
map tile I would incorporate in my application. In our case it would be
the scale factor for each click of the (+) plus zoom in and (-) negative
zoom out buttons. Also, there seems to be a threshold in place that
selects an object (point or line) within a certain tolerance or distance.
Most likely because you have set a minimum scale or zoom in level that make
selecting those points on a line very difficult. This makes me believe
that you can not select points very well that intersect a line. If a
point is part of or intersects a line it may cause the wrong trail line to
be selected in the vicinity. I would recommend all points should be placed
off all lines and should not intersect any lines. Am I correct?

On Wed, Nov 13, 2013 at 5:43 PM, Stephen Mather [email protected]:

scale on a world Mercator map would be begging for trouble...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/238#issuecomment-28441781
.

GIS Specialist, Anthony Gareau
Cuyahoga Valley National Park
15610 Vaughn Road
Brecksville, Ohio 44141
Phone: (440) 546-5978
Fax: (440) 546-5982

[smathermather]

Hi @agareau, I think @danavery and I understood you correctly, but the weird thing about Google Mercator is that the map is a different scale horizontally than vertically, so a single scale bar can be misleading.

[alanjosephwilliams]

@agareau just a heads up that I edited the headers of this issue, to more clearly mark the issue as related to a potential enhancement.