Hi,
As Massachusetts slowly migrates back into winter, here is the status
update on the address import for Boston, MA.
License: As it turns out, all public City of Boston data is licensed CC
BY 4.0, which requires attribution. I have sent additional
clarification questions on whether the
Hi all,
Just an update on the current status.
1. I am waiting for a response from Boston GIS regarding the license
terms (MassGIS != Boston GIS, as I recently realized).
2. At this point the code will only be minimally tweaked as I have
implemented everything I originally planned:
- Standalone
Hi Jason, all.
I added the addr:city to the tags to use w/o confirming first - what is
the balance between adding the address information directly on the
building as opposed to using the boundaries?
I suppose that for the ease of processing the building will need to
have as much information as
Jason Remillard writes:
> The licensing link says the following, it is kind of weird.
indeed.
> "The City of Boston recognizes the value and benefit gained by sharing
> GIS data. Although the City has made reasonable efforts to provide
> accurate data, the City
Hi Jason,
On Mon, 2016-03-21 at 20:42 -0400, Jason Remillard wrote:
> Hi Roman,
>
> The city of Boston building data set for buildings has address.
>
> http://bostonopendata.boston.opendata.arcgis.com/datasets/492746f09dd
> e475285b01ae7fc95950e_1
Interesting, so that's where the tax parcel
Hi Roman,
The city of Boston building data set for buildings has address.
http://bostonopendata.boston.opendata.arcgis.com/datasets/492746f09dde475285b01ae7fc95950e_1
It seems like they have already figured out what address goes on what
building. Should this data set be used rather than the
On Sun, Mar 20, 2016 at 11:52 AM, Roman Yepishev
wrote:
> * Some of the addresses from MassGIS point to parks, monuments, or
> buildings are located a few feet away. While it may possible to assign
> the marker to the building nearby, I'd prefer not to do the guess work
>
Hi, all! Going back to the point...
I stopped linking to the .osn files in order to minimize the confusion.
Instead, every neighborhood gets their .gpx file with the details of
the issues encountered at that particular address:
- Building is missing.
- Building has more than one address.
-
I should point out that I'm not opposed to this import or address
imports in general; generally, I am supportive. But, I think the doing
an import right is vastly harder than someone who hasn't been through
one thinks, and that it's good to iterate on approach and data quality,
and not rush or
Hi Greg, all.
I'd like to provide some information on the import I did not share
initially to make my intentions clear (so far I may be seen as dumping
the data into OSM and running away).
TL;DR
=
* I believe in an iterative approach to any project.
* I want to make as many useful things as
Hi Roman ,
- The source addresses uses abbreviations (RD, ST,etc) are you expanding them?
- The source addresses are capitalized, are you fixing that?
- How are you dealing with multiple addresses per building
- How are you dealing with multiple buildings per address.
- Unless you are working
Quick followup as I may have had the Tax Parcel 2015 dataset in mind.
On Wed, 2016-03-16 at 08:57 -0400, Roman Yepishev wrote:
>
> > - The source data contains the building heights, you might want to
> > import that in too.
> Only number of floors is provided (which can be 2.5), not the height
>
Roman Yepishev writes:
> The wiki now contains updated files that set the postcode and add
> a fixme tag to a building in case it already had the number that does
> not match the official information from SAM.
How many fixme tags would there be?
How many of these fixme
Clifford Snow writes:
> 4) Is it really necessary to upload that many notes during the import? if a
> building is missing, can you add a node with the address information
> instead of leaving a note?
I am opposed to adding notes from bulk data. There are already a
Hi Jason,
Thanks for you message. Replies are inline.
On Wed, 2016-03-16 at 08:02 -0400, Jason Remillard wrote:
> Hi Roman ,
>
> - The source addresses uses abbreviations (RD, ST,etc) are you
> expanding them?
There are only around 240 SAM streets that did not map to OSM streets
exactly, these
Hi Clifford, thank you for the message. The answers are inline below.
On Tue, 2016-03-15 at 13:40 -0700, Clifford Snow wrote:
> 1.) Automatically updating the street name to match the address
> records is not advisable. My experience doing address imports, the
> address information may not match
Glad to see someone adding more addresses to OSM.
I have some questions/comments for you.
1.) Automatically updating the street name to match the address records is
not advisable. My experience doing address imports, the address information
may not match the street signs. There may be two
17 matches
Mail list logo