[Imports] Importing Buildings and Addresses for Austin, Texas

[Clifford Snow]

On Mon, Nov 9, 2015 at 5:32 PM, Paul Norman <penorman at mac.com> wrote:

> - There seems to be inconsistency in how height is being handled. The wiki
> says cm, but the github repo is saying it's to the nearest 10cm. Meanwhile,
> the data that was inadvertently imported early has stuff like
> height=3.9099999999999997
>
> - There's no mention of merging with existing POIs, e.g.
> osm.org/way/379207894 and osm.org/node/368164079
>
> - How has the accuracy of the city data been assessed?
>

It would help if you could describe how the city's data was validated.  The
height could be given in feet, for the above example, change it to
height=13'10".

>
>
> - You're proposing using a coa:place_id tag. There are four issues with
> this. The first is that there seems no confirmation of stability from the
> city, only uniqueness. I've seen a number of cases where an ID that people
> thought was relatively stable turned out not to be.
>
> I like the use of the source id. I believe that we will use these at a
later date. Not including them when they are available just because no one
has used them before is short sighted in my opinion.

I'd like to see addr:city and addr:postcode added to the address
information. Census has boundaries for zipcodes. Is it possible that that
City of Austin has the information? Or possibly Travis County? County
Assessors obviously need the information to send out property taxes. (I'm
assuming Travis County has property taxes.)

Do you have addr:unit information? If not, how are you handling buildings
and mobile home parks with the same address but multiple units?

Clifford

-- 
@osm_seattle
osm_seattle.snowandsnow.us
OpenStreetMap: Maps with a human touch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20151109/bf1bfeba/attachment-0001.html>