And, I was hoping that OSM
volunteers would take heed to "Map Your Train Ride!" to get more platform/stop
data into OSM's passenger train routes. But, there is more than one way to do
all of these things, of course.
Fantastic there are so much good data "out there&q
On Sep 2, 2018, at 9:52 PM, OSM Volunteer stevea
wrote:
>
> I "found something rectangular" and sketched in
> http://wiki.osm.org/wiki/Colorado/Railroads which we might agree (as a
> useful, communicative wiki) is "alpha-1" or so.
Following up to my own post
nk you for your thoughts and hopefully the answers will clarify what sort
> of assistance I'm after.
You are welcome, and I'll be curious to watch what happens. As I saw your
request for feedback is to be off-list, we who are on-list (I speak f
mentation.
Have fun,
SteveA
California
> On Sep 12, 2018, at 10:39 AM, john whelan wrote:
(a lot about how hard it is to query our data).
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
On Sep 6, 2018, at 4:30 PM, john whelan wrote:
> The pilot project itself did manage to get a fair amount of accurate data
> into OSM. That data is still there and can be used. It was instrumental in
> supporting the HOT summit in Ottawa. It managed to raise awareness within
> local
On Sep 6, 2018, at 1:14 PM, john whelan wrote (replying
to me, stevea):
> > Hm, we tried to revive the wiki, a tried-and-true OSM methodology for doing
> > EXACTLY that. Is there something wrong with that idea?
>
> No this project was initiated by Stats Canada, but without
ot;
(it DOES mention Active Monitoring tools) and "what tags are of interest" (it
DOES mention Tag Standardization" and "The data that could be mapped"), then
HOW? The answer: (or at least an excellent one): use our already-built,
well-establishe
This strategy works: Portland TriMet, meet
California/Railroads, meet Miami/BrightLine, meet San Francisco BART, meet
Denver RTD...and so on.
Rail mapping feels like solving a crossword, good for the mind and then there's
that volunteer spirit par
solve in weeks or months or a year what it might have taken us ten years (or
15) to get to "about here." I'd say we're doing fine, even as we do have some
climbing ahead. OK, I'm fine with that. I'm being a bit rough and fast here,
no do
cation of the codebase), or we will
self-destruct in endless discussions like this. I'd much rather take what is
known to be a proven successful path. So, let's improve our render-defect
fixing pipeline, as it is rather broken. No judgement there, rather
identification of problems needing
her for dominance: OSM loses (big
time) in the long-run as we continue to fool ourselves with the folly of these
contradictions.
The bottom line, "easy as cake, simple as pie:" FIX WHAT IS BROKEN. Is this
difficult software development? That'
l-to-humanity,
feels-good-in-your-bones volunteer activities you might do right now. Maybe
that's just me, but I sincerely doubt that.
SteveA
California
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
be too surprised. Whether this is legal or ethical or has
anything to do with maps (OSM or otherwise), I'll refrain from saying anything
about here and now. Except that as more and more telescopes are pointed at
everybody everywhere, we shouldn't lament the disappearance of
eaning up NE2 messes (as I find them) since about 2011 (even
after he would rudely swear at me in my polite emails to him); good riddance to
NE2. His horrific sense of bicycle routing turned into me and others first
tearing out our hair in frustration, then we began our USBRS WikiProject. So:
issues, we are people making a
map, we both agree and disagree and we do the best we can.
SteveA
California
> On Aug 16, 2018, at 2:52 PM, talk-us-requ...@openstreetmap.org wrote:
>
> Send Talk-us mailing list submissions to
> talk-us@openstreetmap.org
>
> To subscr
, but they are
comprehensive, especially for getting a Forest Service boundary (whether forest
or wilderness, two separate legal designations) "conflated" with data already
existing in OSM. I would be happy to send them to you, just reply and ask me
for my "USFS Import ten-step" document
t?"
We can be both bold and careful, but it isn't easy. Ask. Dialog. Read.
Discuss. It is getting better.
SteveA
California
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
of government resources wisely
spent and our volunteer spirit working for the highest good of awesome
geography, OSM continues to rock the mapping world. Yeah!
Keep up the great work, everybody. I know I am seriously dedicated to this
project long term.
SteveA
California
> On Aug 14, 2
r d’OSM et
continueraient d’atteindre cet objectif.
Bonne journée,
Etienne
Californie
> On Aug 12, 2018, at 4:59 PM, James wrote:
>
> Résumé très facile: Paris ou la france ≠ Le Québec.
> Le Québec fait les chose très différente de la France.
>
> On Sun., Aug. 12, 2018, 8:36 p.m. OSM
Ayant embarqué à bord de nombreux trains à Paris (pour choisir l'une des
nombreuses villes que j'ai embarquées dans les trains), OSM aux Halles dit
"operator=RATP" et "name=RER B". Certains disent que la pure consistance est
stupide. Je dis "trouver ce qui fonctionne et rester cohérent".
e's
how WE do it" and "here's how we AND OUR NEIGHBORS do it" makes sense for
trains and bus schedules and bike routes. Or don't. These things really are
international and good dialog makes good protocols. We're simply people
talking on a mailing list; I happen to believe
eally can get the phones to connect and the trains running on time,
the ideas behind "let's agree on good language and tagging..." work, this is
simply being good neighbors. A big human family sharing a map acts like a big
human family sharing a map. We seem to continue to do t
ry good or even excellent and well-thought out and discussed, as are
developing public_transport OSM data in Canada. We're making a great map.
Thank you again for spirited and interesting discussion.
SteveA
California
> On Jul 16, 2018, at 6:06 PM, Damien Riegel wrote:
>
> On 12 July 2018 at
ing this wrong, please chime
in, but I strongly believe this is firm legal ground.
FEDERAL laws are slightly different, and maybe even MORE generous: data
produced by federal agencies are "in the public domain" (unless classified as
Confidential, Secret and Most Secret, which are
iveness
I believe a wider audience's participation can offer greater clarity. Thank
you in advance for taking a look, especially if you participate,
SteveA
California
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
rgely in agreement: if you (and Canada) want to move into the direction of
putting operator=* on freight rail (and maybe sometimes passenger rail), yes,
that seems correct. If you additionally want to use the network=* key for, in
this example, STM, yes, that makes perfect sense to me as well. So
ot;Société de transport de Montréal" exactly
right too (twice), making it a good candidate value for the name=* key.
SteveA
California
> On Jul 10, 2018, at 7:22 PM, Damien Riegel wrote:
>
> Hi everyone,
>
>
> I'm new to this list so please forgive me if this topic h
Hello Volker, old friend:
Thank you for the Garmin history, thank you for the additional links! (I knew
one, didn't know two).
SteveA
> On July 7, 2018 at 6:23:52 AM, Volker Schmidt wrote:
> In fact Garmin started using OSM maps aleady in summer 2013 on the edge
> Touring. This
as as "smart" (and tuned...) as its data are. That's clearly a business
opportunity, too. I appreciate the good discussion. Go OSM!
SteveA
> On Jul 5, 2018, at 2:55 PM, Martijn van Exel wrote:
> Also, if Garmin can sell OSM maps for US
s
Garmin map history, I'm eager to hear it.
SteveA
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
with real world data,
please use the Discussion page built into each wiki to discuss with others any
potential changes to existing wiki. The "right thing" (better written wiki)
usually happens soon after such discussion.
SteveA
California
OSM Volunteer since 2009
lar
workflows, and what works (better, worse) and what doesn't. That should be
ongoing, anyway, so I suppose we can say we're doing OK. I often wish us to do
better, nudge, nudge. Sometimes that begins with good discussion. Look, we
presently have here a rough initial inve
some open-source version of one without
onerous License Terms that MANY (not just me) find offensive.
Is that possible?
Thanks for reading. I mean this in the best interests of OSM longer-term.
SteveA
California
OSM Volunteer since 2009
___
Talk-u
w. Or, we can discuss here.
Happy holiday weekend (perhaps belated as you read this),
SteveA
California
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
now "smarten up" your
phone or GPS with these named trails and very precise geo data.
OSM: what a great project!
SteveA
California
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
as doing so contradicts the workflow we have evolved, no, I do not abide that.
Should we want to improve that workflow, I'm listening. But (politely,
Clifford) I reject that the tiger:reviewed tag has lost all meaning.
We can be more clever, we can be more zealous, but let
dely available.
So if you're in Georgia or Pennsylvania (or even if not!) and want to help
build Earth's largest official cycling route network, check it out and have fun!
SteveA
California
USBRS in OSM guy (among other hats I wear)
___
Talk-us mail
The Spring, 2018 AASHTO ballots for new USBRs are now becoming available. If
you wish to enter data into OSM for USBR 66 in Missouri,
https://www.dropbox.com/sh/46ztv3epkgj5kv9/AABiIcGZILoUnSckJqzD0uNda?dl=0
downloads route data, including turn-by-turns and 30+ pages of rather nice,
Project_United_States_railways if you wish to
participate.
Did you "play with trains" when you were younger? Please help improve OSM's
"national train set" in the US: it's actually rather fun!
SteveA
California
> On Apr 3, 2018, at 11:08 AM, OSM Volunteer steve
I want to
establish network=* tagging as correct, to get ahead of this curve.
Thank you for reading,
SteveA
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
M has grown
statewide rail wikis (now at eight, nine...so, still forty-something to go!)
and I know I'm not the only mapper who wants to keep momentum going to
wiki-document all 50 states' rail infrastructure and passenger routes.
Thanks in advance for any answer/mapping you might offer,
Stev
You're quite welcome.
Steve
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
I should have included:
https://wiki.openstreetmap.org/wiki/WikiProject_United_States_railways
as that is a better starting place (for your flavor of question) than our "at
the top" Amtrak wiki.
There's a lot to grok to become a good OSM rail editor (and don't forget
updating wiki), yet, many
Hi Greg:
Great questions. If you are a rail public_transport:version=2 super-jockey,
hey, polish them up to a firm buff and we'll marvel at their brilliant shine!
However (and this is pedestrian me), I make "better" progress (higher quality
data, at the expense of being slower) following
consensus still
doesn't feel it has fully emerged, so I'll hold off on this minor change until
at least somebody says something!
Rail USA does slowly and surely get better. Nice to be here, everybody.
Remaining in listening mode,
SteveA
___
Talk-us
nning JOSM on a Mac, I hope.
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
and would like
them to all have the same network=Amtrak tag. Does this seem reasonable?
Thanks,
SteveA
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
SM is fantastic, like Rosie the Riveter swinging her fist,
"We can do this."
Curating this discussion to wiki doesn't seem a lengthy task. Might we see a
WikiProject USA/Help fight advertising emerge?
SteveA
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
ot;if you are going to do this, we'll make it EASY for
you to do it the RIGHT way." Awesome, everybody! Let's keep up the good work
and really follow through on these!
SteveA
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
project should you have the honor to offer one and
it accompanies your understanding to cease and desist these practices.
SteveA
OpenStreetMap volunteer
(A little harsh? Maybe. Maybe not.)
___
Talk-us mailing list
Talk-us@openstreetmap.org
https
honest, done in sixty seconds, actionable and now
you know, too.
One down. (Who is going to call Bright Valley and chew their ear off?) I put
some good soul into this project (Frederik), what's the script for next?
SteveA
___
Talk-us mailing list
T
ls do when "paint bombs are being thrown at our canvas." Let's be
those smart people and use those good tools, developing them with good dialog
and documenting what we mean to do.
Happy mapping and have a great day!
SteveA
California
___
Ta
ate boundaries in our
map).
We've already achieved consensus that "CDPs are lesser entities." I'm
suggesting we go ahead and delete them as noise (except in truly useful
circumstances absent any "better" data, as in Alaska). Superseding them with
better data: I'm all for
re to blame. This makes the bottom line straightforward: US Census
Bureau census boundary data as polygons do not belong in OSM (except in Alaska,
where they remain distinctly useful), since a node with a place=* tag delivers
OSM's proper mapping of these semantics.
SteveA
California
Cont
of this I'm spouting about
"Township" can be ignored, as it is effectively another word to describe an
admin_level=8 entity and you seem to be fine leaving things that way.
Regards,
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
is not a standard well kept.
And we make our point: OSM doesn't always follow its own rules. Crowdsourcing
can be messy, yet we try to improve day by day. Thanks to all for getting here!
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
Thank you, Matthew. As I said, "slavishly follow rules," no, not necessarily.
"Understand the issues," yes, through good dialog. I like what I see here, it
allows good consensus to emerge, tedious and perhaps even a bit annoying as it
may be. :-)
SteveA
On Feb 19, 2018,
alue to yes. BTW, I agree with the consensus that sometimes
an actual human on-the-ground survey is the only way to do this sufficient to
delete the tiger_reviewed=no tag, as Bing or other imagery is most certainly
not always sufficient.
SteveA
California
___
-up/thumbs-down, need a
touch-up.
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
uot; to "Sainte" in the Ontario version). Some (many? most?)
"Sainte-Quelque Chose" names have hyphens, too. So, hm.
That would be my approach, as it is OSM's approach. This is OSM, yet it is
Canada, too, of course. It's not always easy or clear, is it?
SteveA
_
We call it TALK-ca for a reason! We call it OPENStreetMap for a reason!
Consensus doesn't always come easy! Thanks to everyone for good discussion.
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo
I stand corrected, thank you everybody.
BTW I do my best not to abbreviate thinks like "DC" for District of Columbia,
but I now better understand that "St." in many cases has now truly become the
official name, abbreviation included.
SteveA
We (the USA) has many sources which "say" St. Louis (Missouri) but OSM has
name=Saint Louis. The latter is correct in an OSM context. Following our
wiki, CAN the name be spelled without an abbreviation?" If yes, then please do
so.
Thanks,
SteveA
> On Feb 16, 2018,
f (trade off?) of "well,
let's capture the data we consider deleting by adding them into OSM using OSM
methods."
This isn't required, more like a "recycle the scraps on the cutting room floor
into nice, correct data." I do that where I can, certainly not always! Great
discussion.
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
r, Kevin Farrugia says something different.
We listen, we consider, we allow consensus to emerge and the bold pull
triggers. By that I mean "clean up what we now agree needs correcting."
OSM is so delightfully human and organic. I'm so glad we so widely speak
amongst ourselves.
SteveA
ional tags). BTW another wiki of ours,
https://wiki.osm.org/wiki/TIGER_Edited_Map gives a nice overview/documentation
of the Ito map.
We might create a new thread or keep it in this one: but even as a seasoned
TIGER cleanup volunteer, I don't know what to do with additional TIGER tags,
and I
k a year as to when the US will "finish fixing TIGER," it
might be decades. But that's OK, it will be worth it, as our map gets better
every day.
Happy mapping,
SteveA
California
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.op
tart small, document it. That seems a fairly
low bar to step over.
Later,
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
Please see https://wiki.osm.org/wiki/Key:level
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
e more difficulties.
It is getting better. (As my tone hews closer to honey than vinegar, it will
get better). Again, I've said it and said it and said it. So please: do it.
The good intentions to do so are clearly there, that is a terrific place to be
to continue onto the next steps.
SteveA
and transparent, not (exclusively) "fail fast." In fact, OSM
insists upon this.
Please install pilots in your large, jet aircraft. If it is to fly and land at
its destination (years into the future), it not only deserves, it simply must
have an experienced flight crew.
nd with maybe a eight or ten rules, (reasonable
for a parser extracting machine-dialble phone numbers, if necessary), you're
either done or at or above 99%, I'd be willing to wager (and I'm not a betting
type, though I do play poker with friends and online).
Nice job.
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
I encourage you to edit wiki, Max, it is an important part of OSM-ing, if you
are one who does, fantastic. Honest updates or better data, it's easy to write
and comes naturally to many. Please, go for It!
Steve
___
Talk-us mailing list
On Jan 29, 2018, at 2:35 PM, Stewart C. Russell <scr...@gmail.com> wrote:
> On 2018-01-29 04:37 PM, OSM Volunteer stevea wrote:
>>
>> OSM is delighted to receive building data in Canada, truly we are.
>> (Provided they are high-quality data). I have heard the process o
Um, "dyed-in-the-wool."
Steve
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
eeds the most rudimentary structure of project
management, badly, and right now. Previous experience with national-level/wide
scope projects in OSM is quite helpful, but only died-in-the-wool OSM
volunteers need "apply" (themselves).
Sincerely,
SteveA
OSM Volunteer since 2009
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
OK, I've redacted Halifax changes. From four to three (municipalities with
license now "green.")
Steve
> On Jan 28, 2018, at 7:39 PM, Stewart C. Russell <scr...@gmail.com> wrote:
>
> On 2018-01-28 09:16 PM, OSM Volunteer stevea wrote:
>> Halifax also looks lik
lities, now. Thanks to great teamwork for a productive
weekend, everybody. See you around.
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
And...you're off and running (better and better).
This is a process, everybody. Nobody wants to be slapping anybody around. I
like the way we've been polite and patient with each other here.
Regards,
SteveA
> On Jan 28, 2018, at 4:47 PM, Matthew Darwin <matt...@mdarwin.ca> wrote:
&g
Smiling here, thank you for wiki-ing fresher status in both wikis! (It's quite
doable, yes?).
Steve
> On Jan 28, 2018, at 3:40 PM, Matthew Darwin wrote:
> Great, seems like we have a list of 3 ok ones:
> Ottawa (approved license)
> Gatineau + Montreal (explicit approval
or... are more appropriate.
I'm saying "wiki when wiki is right."
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
erstanding up and down our wiki, toolchains, processes, lines of
communication, etc. A sort of thing that is done on a talk page and via wikis.
It appears to be a national conversation.
Steady ahead.
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
towards
Open Data with the culture of OSM. We have made great progress, but in my
opinion, only in limited contexts and suffering from "stove-piped"
communication blockages. This deeply frustrates further progress.
Please observe all of the moving parts, (perhaps marvel a bit!) and know t
right now. Please!
We seem to be getting somewhere, even if it is determining that "efforts remain
unconfused and confused on a national level." I'll take that as minor progress
— because it can be cleaned up and remedied!
Thank you to all for measured, patient and polite con
ative to move forward with these and I'm left with little to do
from here to push it forward any differently than I have been.
Thank you,
SteveA
California
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
On Jan 26, 2018, at 8:12 PM, Stewart C. Russell <scr...@gmail.com> wrote:
> On 2018-01-26 09:56 PM, OSM Volunteer stevea wrote:
>> What I did was to "back-populate" the list of "approved" (by whom? when?
>> how did these get here?) list of Canadian
main in
motion, dialog to continue and good work to continue. Including the solid task
of planting acorns so that mighty oaks may grow.
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
account) can change these to be more accurate!
Capturing ADDITIONAL status harmonization with whatever might be going on in
OSM-CA-TM is an ongoing bit of work to be done which appears to be only in the
most early of contemplation/discussion.
SteveA
California
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
o toddling to walking:
excellent.
Happy weekend everyone,
SteveA
California
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
nce in OSM, that sounds like a conversation, as we have here in talk-ca.
Yes, so, we're having it. Part in talk-ca, part in the wiki, part in the map,
part in email, part in the real world over coffee and talk.
More in the wiki, please? Thanks, it feels like my work is done here!
SteveA
Califo
ization and project (links, wikis,
mapping work...) connectivity (intra-OSM, as it were) goes a long way. Nice
working with you!
> Keep up the great work.
Thanks, you and BC2020 (and Canadians OSMers and all of OSM and all the little
children...), too.
SteveA
California
_
mebody" or "walled garden."
It's OSM, after all. We use other forms of communication, but on a national
project of scope this large, we can (and should and do) use the wiki.
Zippin' it closed for a while,
SteveA
California
___
seems an appropriate
place to learn that. Yet our wiki updated with those links took me about
twenty seconds of cut-and-paste.
Yeah!
SteveA
California
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
;poof." It birthed as a brilliant flare
and now toddles along.
If I may humbly say to the dear readers here: I see many green lights ahead on
BC2020. There are some pesky obstacles like licensing and a good Import Plan
(the Ottawa seed is a good start) but those do get resolved over the
e locally-modifiable to be successful, MUST "rule" the HOWs of data
importation. This "nationwide/project-wide" Import Plan, flexible enough to
handle multiple scenarios and flavors of building data is ripe (overdue?) for
completion. It is an ambitious project, and I wish you
lanning. Good. OSM is organic, it moves and grows in fits and spurts.
Fantastic project.
Fun, isn't it? (I enjoy this discussion, by the way). Great talking here.
SteveA
California
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
I agree that absolute novices unfamiliar with OSM are not what we might call
"an ideal candidate," for BC2020i but it certainly has been and can be done.
That said, "coming with Java preloaded" is a certain kind of "trigger warning"
that "you have to be this tall to ride the ride." That's
yond. However, nothing ever happens
without a good plan, and good planning and good project management is what will
get you there. The solid backbone and structure of OSM is the vessel, and
Ottawa and Canada are very well on your way to fantastic bicycle geo data and
tools. The rest of the pieces co
shly hesitate to say it puts what we have in the USA
— nothing close! — to a bit of shame). Well done!
Regards,
SteveA
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
Oops, the bicycle router I wanted to refer to in my previous is
http://cycle.travel by Richard Fairhurst (whom I inexplicably confused with
Simon Poole).
SteveA
California
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https
501 - 600 of 963 matches
Mail list logo