You should consider using the US Chapter's Tasking Manager. Ian Dees can
give you permissions to add tasks. When setting up task, TM allows you to
specify the changeset comment where the import wiki page can be shown.
On Fri, Feb 7, 2020 at 2:33 PM wrote:
> I've updated the translation
I've updated the translation information on the wiki page, and absent
objections, I intend to slowly go through the addresses (again, I'm
also drawing in buildings/roads where necessary).
I have found some issues with the dataset, most of which I've reported
to the local county GIS.
I will start
I've made some modifications to the script (ME 1/2 is no longer
converted to Me 1/2), and the server now has a naive conflation service
(if any address in the bbox exists on osm inside that bbox, don't send
the address).
The conflation is semi-live (it uses overpass).
On my todo list:
* Go
I did an import of 800K Baltimore County addresses (and buildings, conflated,
like yours) six years ago. You’re welcome to my expansion code, which we did in
SQL when pulling it out of the database. I made a special case for McNames like
McDonalds or McTavern, of which we have quite a few here.
The Mesa County address set has 89,130 addresses.
The Colorado address set has 1,958,082 addresses, of which a bit less
than 89,130 addresses are from Mesa County (the county data is newer).
I was planning on adding it as a default datasource in the JOSM
MapWithAI plugin after I had gotten
Hi,
On 1/25/20 18:42, smocktay...@gmail.com wrote:
> eventually importing the state address
> database
How many addresses are there, and are there any plans to involve more
people? One person importing a whole state sounds quite a burden.
Bye
Frederik
--
Frederik Ramm ## eMail
Thank you for linking that script. I've been making my script a bit
more generic (see
https://wiki.openstreetmap.org/wiki/Import/Colorado_Addresses#Generic_Script
for what it currently looks like), and I wouldn't mind sending in a
pull request sometime for ogr2osm for a generic address parser.
Looks like a great project. I did not dive into the data but since you are
talking about expanding street types, I thought I would share a large
collection of suffixes I collected for our Miami-Dade address import. I
found most of these in a USPS document and also added some missing types on
my
Clifford,
We do have the Colorado Open Records Act, but I can't find anything in it
that states that the records (data) have to be placed in the "public
domain", only that they have to be made "publicly available." Someone with
more training in the law may be able to interpret it better.
Mike.
Mike,
You might want to look at state laws for Colorado regarding open data. My
state has legislation describing the terms that open data should be
licensed. They don't use the term PD but words that mean the same. Part of
the legislation is to make sure they are not releasing information on
On Sat, Jan 25, 2020 at 5:23 PM wrote:
>
> As noted on the wiki page, I have two sources. One is more up-to-date
> in my local area while the other covers the entire state (with the
> latter being a superset of the former).
>
> In my case, I got the data from
>
As noted on the wiki page, I have two sources. One is more up-to-date
in my local area while the other covers the entire state (with the
latter being a superset of the former).
In my case, I got the data from
On Sat, Jan 25, 2020 at 10:44 AM wrote:
> This is a two-phase import project.
>
> I'm going to be updating addresses in Mesa County, Colorado with their
> E911 Address Point data (see https://emap.mesacounty.us/DownloadData/ ,
> updated January 22, 2020) and eventually importing the state
On Sat, 2020-01-25 at 12:15 -0800, Clifford Snow wrote:
> As you get further along, please provide some samples of the data you
> plan to import.
I have uploaded a sample area to GDrive and linked to them from the
wiki here:
Taylor,
On Sat, Jan 25, 2020 at 1:11 PM wrote:
>
> I was missing expansions for PT, SQ, and TRL in the uploaded sample
> file. I did have the Trl expansion in my translation file, but I hadn't
> rerun it. I was not missing an expansion for SW (there is a PREFIX_DIR
> field, but the SW in SW 60
On Sat, 2020-01-25 at 12:15 -0800, Clifford Snow wrote:
> Happy to see more addressing in OSM.
>
> A couple of observations from looking at the Mesa E911 address
> FileGDB.
>
> The expansion of street_type is missing WAY, SQ, LOOP, PT, LNDG and
> RUN. Also missing is expansion for SW.
>
> Mesa
Happy to see more addressing in OSM.
A couple of observations from looking at the Mesa E911 address FileGDB.
The expansion of street_type is missing WAY, SQ, LOOP, PT, LNDG and RUN.
Also missing is expansion for SW.
Mesa county also has building outlines. Have you considered importing them
at
This is a two-phase import project.
I'm going to be updating addresses in Mesa County, Colorado with their
E911 Address Point data (see https://emap.mesacounty.us/DownloadData/ ,
updated January 22, 2020) and eventually importing the state address
database (
18 matches
Mail list logo
