[Talk-us] Importing County Data
Mike N
niceman at att.net
Sat Dec 18 00:48:01 UTC 2021
Interesting ... they do set a "Custom license" on the roads and address
that does not exclude OSM usage. That might be acceptable when
combined with the Email.
Mike
On 12/17/2021 7:41 PM, Steven W wrote:
> That was one of my concerns as well. This is the response I got from asking about that:
> "We have no licensing restrictions or guarantees on our data found on our Open Data Site. (https://opendata-linncounty-gis.opendata.arcgis.com/) Feel free to use however you want to use it. The more that have access or use for it the better in our thought process.
>
> We do not update any planimetric data or topo data on a set schedule, but most other layers are updated nightly."
>
> I'm not certain if that should be interpreted as 'unlicensed' or something else, and if that would cause any issues on the OSM side.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On Friday, December 17th, 2021 at 6:29 PM, Mike N <niceman at att.net> wrote:
>
>> One thing to check is for a compatible license. For example there are
>>
>> 2 counties near me with "open data" - that is, data freely available for
>>
>> download from the ESRI data portal. However I cannot use the data
>>
>> because there is no license specified. I tried to talk one of them
>>
>> through how to set the an "Open data commons" license over the phone,
>>
>> but we couldn't find the setting.
>>
>> If their license is not compatible, it is also acceptable for them
>>
>> to issue a waiver to allow use in OSM, but in practice this is difficult
>>
>> to obtain.
>>
>> Mike
>>
>> On 12/17/2021 6:17 PM, Steven W via Talk-us wrote:
>>
>>> Hi,
>>>
>>> Hopefully this is the right place to ask, otherwise please direct me
>>>
>>> elsewhere as I've never done this before.
>>>
>>> I asked about this on reddit and was directed here. I've found that many
>>>
>>> US county assessor maps are open data (and at the very least I've
>>>
>>> confirmed that my county is) and I'd like to import building outlines
>>>
>>> and addresses to OSM. My current ideal plan would be to import the data
>>>
>>> into JOSM, remove duplicates with current OSM data taking precedence and
>>>
>>> resolve other warned/errors that crop up, then import.
>>>
>>> My main blind spots are scripting since it's such a large area, and
>>>
>>> proper due process (which I will say is nicely outlined in the wiki
>>>
>>> (which I've been looking at here
>>>
>>> https://wiki.openstreetmap.org/wiki/Import/Guidelines))
>>>
>>> Here is the reddit post with about the same amount of detail:
>>>
>>> https://old.reddit.com/r/openstreetmap/comments/rimngy/importing_county_data/
>>>
>>> https://old.reddit.com/r/openstreetmap/comments/rimngy/importing_county_data/
>>>
>>> Any thoughts, suggestions, or other ideas?
>>>
>>> Thanks!
>>>
>>> Steve
>>
>> Talk-us mailing list
>>
>> Talk-us at openstreetmap.org
>>
>> https://lists.openstreetmap.org/listinfo/talk-us
More information about the Talk-us
mailing list