Re: [Talk-ca] can I submit road data?

2020-07-08 Thread Jason Carlson
Thanks James. That's a good idea to create web documentation like that,
obviously learning from the past. With it there is no guessing later down
the road as to what is what if something needs to be modified, where it
came from, etc.

I have a couple of time consuming projects on the go now so will look to do
this later this fall.

*Jason*

On Tue, Jul 7, 2020 at 3:41 PM James  wrote:

> https://wiki.openstreetmap.org/wiki/Import/Guidelines
>
> Usually involves creating a wiki page like
>
> https://wiki.openstreetmap.org/wiki/Ottawa/Import/Plan
>
> outlining that licensing isnt an issue and what tags would be
> used(addr:housenumber and addr:street for address points) as well as
> contigency for conflating against existing data
>
> On Tue., Jul. 7, 2020, 5:11 p.m. Jason Carlson, 
> wrote:
>
>> Okay, I'll scrap the idea of importing roads - mostly because they are
>> already there - just off skew but a dozen or more meters in many places. I
>> wrote software to fix most of our issues in our area - maybe there is an
>> API to do the same with OSM and I can volunteer some skills there.
>>
>> As a side note, what about point data. I have a bunch of rural addresses
>> that I could upload as point data and it would be a lot easier to do the
>> initial import at least if I can get a hold of those guidelines so I can
>> set it up right the first time :) You know where I can find those?
>>
>>
>> *Jason Carlson*
>>
>> IT/GIS Administrator
>>
>> *403.772.3793*
>>
>> *Starland County*
>> *Morrin, AB  *
>> *(403) 772-3793*
>> *www.starlandcounty.com *
>>
>> *Our organization accepts no liability for the content of this email, or
>> for the consequences of any actions taken on the basis of the information
>> provided, unless that information is subsequently confirmed in writing. The
>> content of this message is confidential. If you have received it by
>> mistake, please inform us by an email reply and then delete the message. It
>> is forbidden to copy, forward, or in any way reveal the contents of this
>> message to anyone. *
>>
>>
>> On Tue, Jul 7, 2020 at 2:16 PM stevea  wrote:
>>
>>> > Imports are quite the pain to try and do - there's a whole process in
>>> place now to do them. It stems from the experience in the States of an
>>> import more than a decade ago of the TIGER data (from the Census Bureau)
>>> that is still being fixed after pretty large amounts of time working
>>> through it.
>>>
>>> Major components of the USA's TIGER import included both road
>>> (highway=*) and rail (railway=*).  This took place in 2007-8 with
>>> early-to-mid-2000s data and resulted in OSM data which were (and still are
>>> in places) quite problematic.  There have been many strategies and even
>>> renderers which aim to address helping fix the massive amount of TIGER data
>>> that were imported, yet it will likely take another decade (three?) to
>>> complete these improvements — that's a lot of work.  This sort of "ongoing
>>> work to improve an import" is common with earlier / older imports
>>> (especially when OSM had little to no "official" guidelines to doing
>>> imports well).  Our Import Guidelines go a long way towards remedying
>>> common problems associated with imports from "lessons learned" in earlier
>>> ones, but imports are still both controversial and often problematic.
>>> However, there are excellent examples of well done imports, usually with
>>> very carefully written Import Guidelines, a good deal of community buy-in
>>> and consensus and often the guidance of OSM volunteers who have experience
>>> with imports and can steer the process in better directions if they begin
>>> to go awry.  I don't need to say it, but Kevin is correct:  let TIGER be a
>>> lesson to OSM about imports, especially those done at very wide (national)
>>> scales in large geographic areas like Canada or USA.  They are challenging
>>> to do well, but shouldn't be completely prohibited, but rather done quite
>>> carefully and slowly.
>>>
>>> SteveA
>>> California
>>
>> ___
>> Talk-ca mailing list
>> Talk-ca@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-ca
>>
>
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] can I submit road data?

2020-07-07 Thread James
https://wiki.openstreetmap.org/wiki/Import/Guidelines

Usually involves creating a wiki page like

https://wiki.openstreetmap.org/wiki/Ottawa/Import/Plan

outlining that licensing isnt an issue and what tags would be
used(addr:housenumber and addr:street for address points) as well as
contigency for conflating against existing data

On Tue., Jul. 7, 2020, 5:11 p.m. Jason Carlson, 
wrote:

> Okay, I'll scrap the idea of importing roads - mostly because they are
> already there - just off skew but a dozen or more meters in many places. I
> wrote software to fix most of our issues in our area - maybe there is an
> API to do the same with OSM and I can volunteer some skills there.
>
> As a side note, what about point data. I have a bunch of rural addresses
> that I could upload as point data and it would be a lot easier to do the
> initial import at least if I can get a hold of those guidelines so I can
> set it up right the first time :) You know where I can find those?
>
>
> *Jason Carlson*
>
> IT/GIS Administrator
>
> *403.772.3793*
>
> *Starland County*
> *Morrin, AB  *
> *(403) 772-3793*
> *www.starlandcounty.com *
>
> *Our organization accepts no liability for the content of this email, or
> for the consequences of any actions taken on the basis of the information
> provided, unless that information is subsequently confirmed in writing. The
> content of this message is confidential. If you have received it by
> mistake, please inform us by an email reply and then delete the message. It
> is forbidden to copy, forward, or in any way reveal the contents of this
> message to anyone. *
>
>
> On Tue, Jul 7, 2020 at 2:16 PM stevea  wrote:
>
>> > Imports are quite the pain to try and do - there's a whole process in
>> place now to do them. It stems from the experience in the States of an
>> import more than a decade ago of the TIGER data (from the Census Bureau)
>> that is still being fixed after pretty large amounts of time working
>> through it.
>>
>> Major components of the USA's TIGER import included both road (highway=*)
>> and rail (railway=*).  This took place in 2007-8 with early-to-mid-2000s
>> data and resulted in OSM data which were (and still are in places) quite
>> problematic.  There have been many strategies and even renderers which aim
>> to address helping fix the massive amount of TIGER data that were imported,
>> yet it will likely take another decade (three?) to complete these
>> improvements — that's a lot of work.  This sort of "ongoing work to improve
>> an import" is common with earlier / older imports (especially when OSM had
>> little to no "official" guidelines to doing imports well).  Our Import
>> Guidelines go a long way towards remedying common problems associated with
>> imports from "lessons learned" in earlier ones, but imports are still both
>> controversial and often problematic.  However, there are excellent examples
>> of well done imports, usually with very carefully written Import
>> Guidelines, a good deal of community buy-in and consensus and often the
>> guidance of OSM volunteers who have experience with imports and can steer
>> the process in better directions if they begin to go awry.  I don't need to
>> say it, but Kevin is correct:  let TIGER be a lesson to OSM about imports,
>> especially those done at very wide (national) scales in large geographic
>> areas like Canada or USA.  They are challenging to do well, but shouldn't
>> be completely prohibited, but rather done quite carefully and slowly.
>>
>> SteveA
>> California
>
> ___
> Talk-ca mailing list
> Talk-ca@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca
>
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] can I submit road data?

2020-07-07 Thread Jason Carlson
Okay, I'll scrap the idea of importing roads - mostly because they are
already there - just off skew but a dozen or more meters in many places. I
wrote software to fix most of our issues in our area - maybe there is an
API to do the same with OSM and I can volunteer some skills there.

As a side note, what about point data. I have a bunch of rural addresses
that I could upload as point data and it would be a lot easier to do the
initial import at least if I can get a hold of those guidelines so I can
set it up right the first time :) You know where I can find those?


*Jason Carlson*

IT/GIS Administrator

*403.772.3793*

*Starland County*
*Morrin, AB  *
*(403) 772-3793*
*www.starlandcounty.com *

*Our organization accepts no liability for the content of this email, or
for the consequences of any actions taken on the basis of the information
provided, unless that information is subsequently confirmed in writing. The
content of this message is confidential. If you have received it by
mistake, please inform us by an email reply and then delete the message. It
is forbidden to copy, forward, or in any way reveal the contents of this
message to anyone. *


On Tue, Jul 7, 2020 at 2:16 PM stevea  wrote:

> > Imports are quite the pain to try and do - there's a whole process in
> place now to do them. It stems from the experience in the States of an
> import more than a decade ago of the TIGER data (from the Census Bureau)
> that is still being fixed after pretty large amounts of time working
> through it.
>
> Major components of the USA's TIGER import included both road (highway=*)
> and rail (railway=*).  This took place in 2007-8 with early-to-mid-2000s
> data and resulted in OSM data which were (and still are in places) quite
> problematic.  There have been many strategies and even renderers which aim
> to address helping fix the massive amount of TIGER data that were imported,
> yet it will likely take another decade (three?) to complete these
> improvements — that's a lot of work.  This sort of "ongoing work to improve
> an import" is common with earlier / older imports (especially when OSM had
> little to no "official" guidelines to doing imports well).  Our Import
> Guidelines go a long way towards remedying common problems associated with
> imports from "lessons learned" in earlier ones, but imports are still both
> controversial and often problematic.  However, there are excellent examples
> of well done imports, usually with very carefully written Import
> Guidelines, a good deal of community buy-in and consensus and often the
> guidance of OSM volunteers who have experience with imports and can steer
> the process in better directions if they begin to go awry.  I don't need to
> say it, but Kevin is correct:  let TIGER be a lesson to OSM about imports,
> especially those done at very wide (national) scales in large geographic
> areas like Canada or USA.  They are challenging to do well, but shouldn't
> be completely prohibited, but rather done quite carefully and slowly.
>
> SteveA
> California
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] can I submit road data?

2020-07-07 Thread stevea
> Imports are quite the pain to try and do - there's a whole process in place 
> now to do them. It stems from the experience in the States of an import more 
> than a decade ago of the TIGER data (from the Census Bureau) that is still 
> being fixed after pretty large amounts of time working through it.

Major components of the USA's TIGER import included both road (highway=*) and 
rail (railway=*).  This took place in 2007-8 with early-to-mid-2000s data and 
resulted in OSM data which were (and still are in places) quite problematic.  
There have been many strategies and even renderers which aim to address helping 
fix the massive amount of TIGER data that were imported, yet it will likely 
take another decade (three?) to complete these improvements — that's a lot of 
work.  This sort of "ongoing work to improve an import" is common with earlier 
/ older imports (especially when OSM had little to no "official" guidelines to 
doing imports well).  Our Import Guidelines go a long way towards remedying 
common problems associated with imports from "lessons learned" in earlier ones, 
but imports are still both controversial and often problematic.  However, there 
are excellent examples of well done imports, usually with very carefully 
written Import Guidelines, a good deal of community buy-in and consensus and 
often the guidance of OSM volunteers who have experience with imports and can 
steer the process in better directions if they begin to go awry.  I don't need 
to say it, but Kevin is correct:  let TIGER be a lesson to OSM about imports, 
especially those done at very wide (national) scales in large geographic areas 
like Canada or USA.  They are challenging to do well, but shouldn't be 
completely prohibited, but rather done quite carefully and slowly.

SteveA
California
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] can I submit road data?

2020-07-07 Thread Jason Carlson
Thanks Kevin, That would make sense if there were attribute changes but if
all the basics are the same they are still split. There is odd fields in
the data likely left over from an import years ago that just was never
cleaned up. With GIS databases, it would have been so easy to do a merge on
roads that connect and have the same attributes. Perhaps that query was not
so simple back when it was imported and anything was better than nothing at
that time.

I looked at the ESRI imagery and it is a lot more accurate (although more
dated so I guess new areas wouldn't be in it). I looked at a couple of
villages (which I have aerials for just because those tiles were partly
rural). I noticed the OSM road data matches perfectly with the Bing aerials
but not with my aerials or ESRI at all. ESRI is insanely close to lining up
with ours. The good news is the Bing tile skews are isolated and
variant only to each tile so theoretically a person could highlight all
points and move them all to correct. The bad news is because Bing is the
default viewer, some future editor is just going to think they need to fix
it to align with Bing not realizing it is inaccurate and all the work will
be undone. Too bad OSM does not have an option to flag flawed
background tiles for an area so users are at least alerted that the tile
they are using as a guide is not accurate.

*Jason Carlson*

IT/GIS Administrator

*403.772.3793*

*Starland County*
*Morrin, AB  *
*(403) 772-3793*
*www.starlandcounty.com *

*Our organization accepts no liability for the content of this email, or
for the consequences of any actions taken on the basis of the information
provided, unless that information is subsequently confirmed in writing. The
content of this message is confidential. If you have received it by
mistake, please inform us by an email reply and then delete the message. It
is forbidden to copy, forward, or in any way reveal the contents of this
message to anyone. *


On Tue, Jul 7, 2020 at 12:13 PM Kevin Farrugia 
wrote:

> Hey Jason,
>
> Imports are quite the pain to try and do - there's a whole process in
> place now to do them. It stems from the experience in the States of an
> import more than a decade ago of the TIGER data (from the Census Bureau)
> that is still being fixed after pretty large amounts of time working
> through it.
>
> There could be multiple reasons for all of the road splits you're seeing-
> one is that in most import data sources roads are split at traversable
> intersections (as you would find in most GIS datasets), another reason is
> that in OSM streets are split wherever there is a change in attributes, for
> example where speed limits change, turn lanes appear/disappear, surface
> types changes, or there's a bridge.
>
> It might be worth trying Esri imagery.  I've noticed in the municipality I
> work for, as well as others in the Toronto area, that they buy the aerial
> imagery that we commission them to fly every spring. It might not be the
> freshest available, but I've found the accuracy to be more accurate than
> other commercial imagery available.
>
> ---
> Kevin F
>
> On Tue., Jul. 7, 2020, 1:02 p.m. Jason Carlson, 
> wrote:
>
>> While waiting for a response I think if I import roads that already exist
>> (albeit incorrectly) it will possibly be just as much work to fix. I tried
>> editing changes but the aerial photos by Bing are horribly inaccurate in
>> some places. I think they must pay for accuracy based on the amount of
>> population in an area. For example, one rural road comes to the right edge
>> of a Bing aerial tile and stops as on the adjacent tile the road abruptly
>> starts 30 meters to the south. I just noticed however I can load other
>> aerial backgrounds including my own which is very accurate. The only thing
>> that sucks is I have a lot of data that is missing such as road width, lane
>> numbers, surface type, road name aliases (like historical or common local
>> names), speed limits, even signage locations (like yield or stops). With my
>> 3300+ roads (of which OpenStreetMap has split into a heck of lot more
>> unnecessarily probably from the initial import) this is going to take some
>> time to fix but hopefully after I do some mapping programs that use
>> OpenStreetMaps will help people navigate to rural addresses in our region
>> as right now GPS units are pretty much useless out here.
>>
>>
>> On Fri, Jun 26, 2020 at 11:53 AM Jason Carlson 
>> wrote:
>>
>>> I noticed a number of roads in our county are incorrect in our area (as
>>> are most rural areas with next to no population). I recently rebuilt all
>>> our GIS road data and submitted it to an organization that then
>>> redistributes it to emergency dispatch services and about 25
>>> organizations/companies. I did not see OpenStreetMap as one of the ones
>>> they send data too so I was wondering if I could submit that data myself to
>>> them?
>>>
>>> Jason
>>>
>> 

Re: [Talk-ca] can I submit road data?

2020-07-07 Thread Kevin Farrugia
Hey Jason,

Imports are quite the pain to try and do - there's a whole process in place
now to do them. It stems from the experience in the States of an import
more than a decade ago of the TIGER data (from the Census Bureau) that is
still being fixed after pretty large amounts of time working through it.

There could be multiple reasons for all of the road splits you're seeing-
one is that in most import data sources roads are split at traversable
intersections (as you would find in most GIS datasets), another reason is
that in OSM streets are split wherever there is a change in attributes, for
example where speed limits change, turn lanes appear/disappear, surface
types changes, or there's a bridge.

It might be worth trying Esri imagery.  I've noticed in the municipality I
work for, as well as others in the Toronto area, that they buy the aerial
imagery that we commission them to fly every spring. It might not be the
freshest available, but I've found the accuracy to be more accurate than
other commercial imagery available.

---
Kevin F

On Tue., Jul. 7, 2020, 1:02 p.m. Jason Carlson, 
wrote:

> While waiting for a response I think if I import roads that already exist
> (albeit incorrectly) it will possibly be just as much work to fix. I tried
> editing changes but the aerial photos by Bing are horribly inaccurate in
> some places. I think they must pay for accuracy based on the amount of
> population in an area. For example, one rural road comes to the right edge
> of a Bing aerial tile and stops as on the adjacent tile the road abruptly
> starts 30 meters to the south. I just noticed however I can load other
> aerial backgrounds including my own which is very accurate. The only thing
> that sucks is I have a lot of data that is missing such as road width, lane
> numbers, surface type, road name aliases (like historical or common local
> names), speed limits, even signage locations (like yield or stops). With my
> 3300+ roads (of which OpenStreetMap has split into a heck of lot more
> unnecessarily probably from the initial import) this is going to take some
> time to fix but hopefully after I do some mapping programs that use
> OpenStreetMaps will help people navigate to rural addresses in our region
> as right now GPS units are pretty much useless out here.
>
>
> On Fri, Jun 26, 2020 at 11:53 AM Jason Carlson 
> wrote:
>
>> I noticed a number of roads in our county are incorrect in our area (as
>> are most rural areas with next to no population). I recently rebuilt all
>> our GIS road data and submitted it to an organization that then
>> redistributes it to emergency dispatch services and about 25
>> organizations/companies. I did not see OpenStreetMap as one of the ones
>> they send data too so I was wondering if I could submit that data myself to
>> them?
>>
>> Jason
>>
> ___
> Talk-ca mailing list
> Talk-ca@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca
>
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] can I submit road data?

2020-07-07 Thread John Marshall
Hi Jason,

I am happy to help. Sounds like a fun project.

John

On Tue, Jul 7, 2020 at 1:02 PM Jason Carlson 
wrote:

> While waiting for a response I think if I import roads that already exist
> (albeit incorrectly) it will possibly be just as much work to fix. I tried
> editing changes but the aerial photos by Bing are horribly inaccurate in
> some places. I think they must pay for accuracy based on the amount of
> population in an area. For example, one rural road comes to the right edge
> of a Bing aerial tile and stops as on the adjacent tile the road abruptly
> starts 30 meters to the south. I just noticed however I can load other
> aerial backgrounds including my own which is very accurate. The only thing
> that sucks is I have a lot of data that is missing such as road width, lane
> numbers, surface type, road name aliases (like historical or common local
> names), speed limits, even signage locations (like yield or stops). With my
> 3300+ roads (of which OpenStreetMap has split into a heck of lot more
> unnecessarily probably from the initial import) this is going to take some
> time to fix but hopefully after I do some mapping programs that use
> OpenStreetMaps will help people navigate to rural addresses in our region
> as right now GPS units are pretty much useless out here.
>
>
> On Fri, Jun 26, 2020 at 11:53 AM Jason Carlson 
> wrote:
>
>> I noticed a number of roads in our county are incorrect in our area (as
>> are most rural areas with next to no population). I recently rebuilt all
>> our GIS road data and submitted it to an organization that then
>> redistributes it to emergency dispatch services and about 25
>> organizations/companies. I did not see OpenStreetMap as one of the ones
>> they send data too so I was wondering if I could submit that data myself to
>> them?
>>
>> Jason
>>
> ___
> Talk-ca mailing list
> Talk-ca@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca
>
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] can I submit road data?

2020-07-07 Thread Jason Carlson
While waiting for a response I think if I import roads that already exist
(albeit incorrectly) it will possibly be just as much work to fix. I tried
editing changes but the aerial photos by Bing are horribly inaccurate in
some places. I think they must pay for accuracy based on the amount of
population in an area. For example, one rural road comes to the right edge
of a Bing aerial tile and stops as on the adjacent tile the road abruptly
starts 30 meters to the south. I just noticed however I can load other
aerial backgrounds including my own which is very accurate. The only thing
that sucks is I have a lot of data that is missing such as road width, lane
numbers, surface type, road name aliases (like historical or common local
names), speed limits, even signage locations (like yield or stops). With my
3300+ roads (of which OpenStreetMap has split into a heck of lot more
unnecessarily probably from the initial import) this is going to take some
time to fix but hopefully after I do some mapping programs that use
OpenStreetMaps will help people navigate to rural addresses in our region
as right now GPS units are pretty much useless out here.


On Fri, Jun 26, 2020 at 11:53 AM Jason Carlson 
wrote:

> I noticed a number of roads in our county are incorrect in our area (as
> are most rural areas with next to no population). I recently rebuilt all
> our GIS road data and submitted it to an organization that then
> redistributes it to emergency dispatch services and about 25
> organizations/companies. I did not see OpenStreetMap as one of the ones
> they send data too so I was wondering if I could submit that data myself to
> them?
>
> Jason
>
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] can I submit road data?

2020-06-29 Thread Jason Carlson
Okay, I've heard back, The original data I built on and all the data I
added has no licensing restrictions for distributions and is allowed for
public use. In fact the non-profit organization AMDSP.ca
 has locally maintained data from a
number of municipalities/urban areas in Alberta. They got back to me that
their road data in Alberta is open for public use and freely to be shared.
Municipalities actually have to pay to be a member with them before they
can submit their local data to be shared and they have strict rules to make
sure the data maintains integrity.

So now that I know there are no licensing issues, how should I submit my
data and what fields of data do you need for roads?

*Jason Carlson*

IT/GIS Administrator

*403.772.3793*

*Starland County*
*Morrin, AB  *
*(403) 772-3793*
*www.starlandcounty.com *

*Our organization accepts no liability for the content of this email, or
for the consequences of any actions taken on the basis of the information
provided, unless that information is subsequently confirmed in writing. The
content of this message is confidential. If you have received it by
mistake, please inform us by an email reply and then delete the message. It
is forbidden to copy, forward, or in any way reveal the contents of this
message to anyone. *


On Fri, Jun 26, 2020 at 12:16 PM Jarek Piórkowski 
wrote:

> The limitation is generally licensing.
>
> Openstreetmap can accept an import of data that is freely licensed, but
> the criteria for "freely" are fairly strict - most Canadian cities' "open
> data" don't meet it. If you're familiar with Creative Commons, the license
> will likely have to be as free or more free as cc-by-sa. In particular, a
> lot of Canadian open data licenses have indemnification clauses which rule
> them out as sources.
>
> Otherwise, if you're familiar with the area you can try editing the roads
> manually - there is a number of satellite imagery sources which has been
> approved for tracing in OSM, and you can use personal knowledge as source
> for things like road surfaces or widths.
>
> --Jarek
>
> On Fri, Jun 26, 2020, 13:55 Jason Carlson, 
> wrote:
>
>> I noticed a number of roads in our county are incorrect in our area (as
>> are most rural areas with next to no population). I recently rebuilt all
>> our GIS road data and submitted it to an organization that then
>> redistributes it to emergency dispatch services and about 25
>> organizations/companies. I did not see OpenStreetMap as one of the ones
>> they send data too so I was wondering if I could submit that data myself to
>> them?
>>
>> Jason
>> ___
>> Talk-ca mailing list
>> Talk-ca@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-ca
>>
>
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] can I submit road data?

2020-06-26 Thread Jason Carlson
There are 3032 roads I've entered so that would take a long time to do it
manually. I'm just looking up licensing - it was all created by me,
however, I downloaded a shapefile to get the end points for roads I needed
to line up with outside our county. It also had parameter fields that they
also needed. Because I built mine on top of that I figured I better check.

*Jason Carlson*

IT/GIS Administrator

*403.772.3793*

*Starland County*
*Morrin, AB  *
*(403) 772-3793*
*www.starlandcounty.com *

*Our organization accepts no liability for the content of this email, or
for the consequences of any actions taken on the basis of the information
provided, unless that information is subsequently confirmed in writing. The
content of this message is confidential. If you have received it by
mistake, please inform us by an email reply and then delete the message. It
is forbidden to copy, forward, or in any way reveal the contents of this
message to anyone. *


On Fri, Jun 26, 2020 at 3:15 PM Bernie Connors 
wrote:

> Jason,
>
>   If it's just a few roads I too would recommend you just use one of
> the OSM editors to correct the roads yourself.
>
> Bernie.
>
> On Fri, Jun 26, 2020, 2:55 PM Jason Carlson, 
> wrote:
>
>> I noticed a number of roads in our county are incorrect in our area (as
>> are most rural areas with next to no population). I recently rebuilt all
>> our GIS road data and submitted it to an organization that then
>> redistributes it to emergency dispatch services and about 25
>> organizations/companies. I did not see OpenStreetMap as one of the ones
>> they send data too so I was wondering if I could submit that data myself to
>> them?
>>
>> Jason
>> ___
>> Talk-ca mailing list
>> Talk-ca@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-ca
>>
>
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] can I submit road data?

2020-06-26 Thread Jarek Piórkowski
The limitation is generally licensing.

Openstreetmap can accept an import of data that is freely licensed, but the
criteria for "freely" are fairly strict - most Canadian cities' "open data"
don't meet it. If you're familiar with Creative Commons, the license will
likely have to be as free or more free as cc-by-sa. In particular, a lot of
Canadian open data licenses have indemnification clauses which rule them
out as sources.

Otherwise, if you're familiar with the area you can try editing the roads
manually - there is a number of satellite imagery sources which has been
approved for tracing in OSM, and you can use personal knowledge as source
for things like road surfaces or widths.

--Jarek

On Fri, Jun 26, 2020, 13:55 Jason Carlson,  wrote:

> I noticed a number of roads in our county are incorrect in our area (as
> are most rural areas with next to no population). I recently rebuilt all
> our GIS road data and submitted it to an organization that then
> redistributes it to emergency dispatch services and about 25
> organizations/companies. I did not see OpenStreetMap as one of the ones
> they send data too so I was wondering if I could submit that data myself to
> them?
>
> Jason
> ___
> Talk-ca mailing list
> Talk-ca@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca
>
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca