[Talk-us] Address data for Miami Florida United States

Levente Juhász jlevente89 at gmail.com
Fri Sep 14 20:28:57 UTC 2018


Great stuff, Leif! I will catch up with this project over the weekend and
will provide some input.

I have access to a few workstations with a bunch of memory so I can help
out with converting/processing the input data if needed. Just let me know.
I don't think of the size of these datasets as an issue in terms of
processing (not even the buildings). As you said, splitting them up into
smaller chunks or using a totally different toolset would also work.

Finding enough people to review and put the data on the map will be a
bigger issue in Miami, imho. You guys are planning to implement an entirely
manual approach, correct?

Cheers,
Levente



On Fri, Sep 14, 2018, 4:06 PM Leif Rasmussen <354lbr at gmail.com> wrote:

> Update on the address data:
> I tried transforming the small data file (550,000 addresses) to OSM
> format, but my computer ran out of memory.  I will try using a more
> powerful computer later.  The transformation worked perfectly on a smaller
> file of 8000 addresses in Miami Beach, however.  I uploaded that sample
> file to a google drive folder
> <https://drive.google.com/open?id=1DJGNdONqdTXMlA0e550ghsmpotqc4QM4>.
> Simply download the file and drag and drop it into JOSM to view that
> addresses.  The address data source only had "addr:city" for some of the
> addresses, so that tag will have to be added manually based on postcode
> later.
> Thanks,
> Leif Rasmussen
>
> Also, the addresses with numbered street names (4th Street) have not been
> expanded (to eg. "Fourth Street").  The roads in OSM currently have the
> numbered versions (4th Street), so I will just leave the addresses like
> they are now.
>
> On Thu, Sep 13, 2018 at 10:42 AM mangokm40 <mangokm40 at protonmail.com>
> wrote:
>
>> Mr. Rasmussen,
>>
>> Thanks for the offer!  I definitely need help. :)
>>
>> I looked, and failed to find, the layer without unit#.  That's what I
>> thought would be preferred.  Thanks
>> for spotting it.  I don't see why we would search for a specific unit on
>> a map.  When I navigate, I would
>> just want directions to "1234 NW 33rd Ct", not "1234 NW 33rd Ct Apt 6".
>> If you know
>> of a good reason for the unit #s, let me know.  It doesn't matter to me,
>> since I don't need navigation in
>> Miami.  :D
>> If you think 600k points is big, imagine the building footprints. :)
>>  It's available, if required.  Heck, they
>> even make a 3d building layer available.  But I don't think we'll enjoy
>> the size.
>>
>> I knew the license is not a problem.  However, I saved that email just in
>> case it comes up.
>>
>> I'm going to read the info Mr. Juhász provided.  Unfortunately, I'm way
>> behind here.
>> Also, I replied to all b/c I think that's what I'm supposed to do.
>> However, I don't want to 'bug' people on
>> the list.  Hopefully, someone will let me know if this needs to go
>> off-list.
>>
>>
>> (_8'()
>>
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> On Wednesday, September 12, 2018 4:17 PM, Leif Rasmussen <
>> 354lbr at gmail.com> wrote:
>>
>> Hi Mango,
>> I have quite a lot of experience with address imports, and would love to
>> help with Miami.  I have visited Miami several times, and have grown a
>> liking for it.  Adding addresses there would be a real pleasure.
>> There appears to be two address data sets - one with "addr:unit", and one
>> without.  The one with "addr:unit" addresses
>> <https://gis-mdc.opendata.arcgis.com/datasets/address-with-condo?geometry=-80.369%2C25.708%2C-80.365%2C25.709> has 1,166,445
>> points, and the one without
>> <https://gis-mdc.opendata.arcgis.com/datasets/eef6b33da60d47c0964387960c840eea_0?geometry=-80.274%2C25.715%2C-80.272%2C25.715>
>> has 586,171 points.  Both of these should be considered.  I would suggest
>> importing the one with condos, or "addr:unit" features if the quality is
>> good.  Otherwise, I think that the dataset without addr:unit should be
>> imported.
>> Also, the license seems OK.  According to the Miami-Dade County
>> Buildings Import
>> <https://wiki.openstreetmap.org/wiki/Miami-Dade_County_Large_Building_Import#Import%20Data>,
>> the license is public domain, which they claim is true of all government
>> produced data in Florida.
>> The only issue I see with the data is the size.  My laptop took 5 minutes
>> to open the address points (including addr:unit, so 1,166,445 nodes) and
>> more than 20 minutes to edit a single key.  This could be worked around,
>> though, by splitting up the data.
>> I created a wiki page for the import
>> <https://wiki.openstreetmap.org/wiki/Miami-Dade_County_Address_Import>,
>> which is a step of the Import Guidelines
>> <https://wiki.openstreetmap.org/wiki/Import/Guidelines>. Sending a
>> proposal to the local community and imports mailing list will also be
>> needed.
>> I hope that this import will end up working out!
>> Leif Rasmussen
>>
>>
>>
>>
>> (_8'()
>>
>> Sent with ProtonMail <https://protonmail.com> Secure Email.
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>
> On Wednesday, September 12, 2018 4:17 PM, Leif Rasmussen <354lbr at gmail.com>
>> wrote:
>>
>> Hi Mango,
>> I have quite a lot of experience with address imports, and would love to
>> help with Miami.  I have visited Miami several times, and have grown a
>> liking for it.  Adding addresses there would be a real pleasure.
>> There appears to be two address data sets - one with "addr:unit", and one
>> without.  The one with "addr:unit" addresses
>> <https://gis-mdc.opendata.arcgis.com/datasets/address-with-condo?geometry=-80.369%2C25.708%2C-80.365%2C25.709> has 1,166,445
>> points, and the one without
>> <https://gis-mdc.opendata.arcgis.com/datasets/eef6b33da60d47c0964387960c840eea_0?geometry=-80.274%2C25.715%2C-80.272%2C25.715>
>> has 586,171 points.  Both of these should be considered.  I would suggest
>> importing the one with condos, or "addr:unit" features if the quality is
>> good.  Otherwise, I think that the dataset without addr:unit should be
>> imported.
>> Also, the license seems OK.  According to the Miami-Dade County
>> Buildings Import
>> <https://wiki.openstreetmap.org/wiki/Miami-Dade_County_Large_Building_Import#Import%20Data>,
>> the license is public domain, which they claim is true of all government
>> produced data in Florida.
>> The only issue I see with the data is the size.  My laptop took 5 minutes
>> to open the address points (including addr:unit, so 1,166,445 nodes) and
>> more than 20 minutes to edit a single key.  This could be worked around,
>> though, by splitting up the data.
>> I created a wiki page for the import
>> <https://wiki.openstreetmap.org/wiki/Miami-Dade_County_Address_Import>,
>> which is a step of the Import Guidelines
>> <https://wiki.openstreetmap.org/wiki/Import/Guidelines>. Sending a
>> proposal to the local community and imports mailing list will also be
>> needed.
>> I hope that this import will end up working out!
>> Leif Rasmussen
>>
>>
>> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
-- 
Levente Juhasz
https://blog.jlevente.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20180914/6a9bc199/attachment-0001.html>


More information about the Talk-us mailing list