Re: [Talk-us] [Imports] Import WestCOG building footprints in south-west Connecticut

no hurry, I’d check in again with the contact on Monday. It > would be nice to have the buildings with addresses on them. > > > > Joe > > > > *From:* Yury Yatsynovich > *Sent:* Saturday, August 29, 2020 5:05 PM > *To:* Julien Lepiller > *Cc:* impo...@openstreetmap.o

Re: [Talk-us] [Imports] Import WestCOG building footprints in south-west Connecticut

From: Yury Yatsynovich Sent: Saturday, August 29, 2020 5:05 PM To: Julien Lepiller Cc: impo...@openstreetmap.org; talk-us@openstreetmap.org Subject: Re: [Talk-us] [Imports] Import WestCOG building footprints in south-west Connecticut Hi Julien, Unfortunately, I have limited knowledge

Re: [Talk-us] [Imports] Import WestCOG building footprints in south-west Connecticut

Hi Julien, Unfortunately, I have limited knowledge on the data quality as I wasn't able to download it (the server returns error). I let the CT point of contact (Scott) know about the problem -- he mentioned in our communication that he forwarded the issue to the tech support team, but I haven't

Re: [Talk-us] [Imports] Import WestCOG building footprints in south-west Connecticut

So, it's been a week since that last message. Do you think we should import addresses and buildings at the same time? Should we import the buildings first and care about addresses later? Yury, what are your thoughts about the data source quality? Do you think it's a good idea to import from

Re: [Talk-us] [Imports] Potential Import of Addresses for Thurston County, WA, USA

; that import, although how much so I am not certain. > > > > > > Also @Clifford Snow if you see this I would appreciate whatever you > > have to teach about imports. > > > > Sincerely, > > Raven > > > > > >

Re: [Talk-us] [Imports] Import WestCOG building footprints in south-west Connecticut

Thank Julien for pushing this forward! yeah, I tried to get addresses from here: http://geodata-ctmaps.opendata.arcgis.com/datasets/bfa7da83da384c2aa809882179369dc4_0/features/305004 and add them on top of the westCOG buildings. The data is a big mess because it's a join_table of like 30

Re: [Talk-us] [Imports] Import WestCOG building footprints in south-west Connecticut

Le Sat, 22 Aug 2020 13:30:02 -0400, Yury Yatsynovich a écrit : > Hi Julien, > The following communication that I've had recently with a CT official > might be of interest to you: > > Oh, great! I think we already saw this data (I tried to contact them too, but never got a reply :/). From what

Re: [Talk-us] [Imports] Import WestCOG building footprints in south-west Connecticut

Hi Julien, The following communication that I've had recently with a CT official might be of interest to you: * Hi Yury, At this point, yes, I think that’s correct. Obviously, we’d like if you cite the state, but we don’t have set guidelines for that. I forwarded the other issue with

Re: [Talk-us] [Imports] Import of Orange County, California Buildings and Addresses

Tod, You might want to look into Paul Norman's ogr2osm.py [1] python tool which can translate shapefiles into .osm files that can be uploaded using JOSM. It's simple to use, just need to create a translation file for shapefile fields to OSM tag. I'm in the process of doing an import of building

Re: [Talk-us] [Imports-us] Interested in importing address points in New York State

On 16/07/2020 00.44, Skyler Hawthorne wrote: Reading up on the import guidelines, I can see that the license is important. However, I am not able to see anything that explicitly states one way or another what kind of license the data sets are distributed under, and this whether or not it is

Re: [Talk-us] [Imports] Preliminary Import/Organized Mapping Effort Idea

I asked the Jamestown S'Klallam Tribe, near Sequim, WA for updated boundaries. The state boundaries did not match what was on the tribes website. They provided me with an update - the same one they just sent the Census Bureau. With the 2020 census my guess is that TIGER might have some good

Re: [Talk-us] [Imports] Preliminary Import/Organized Mapping Effort Idea

On Fri, Dec 20, 2019 at 7:18 PM Clifford Snow wrote: > I've reached out to a couple of the nearby reservations, one with a small > parcel of off reservation land trust, the other with only a small > reservation but a very large off reservation land trust. I don't expect > answers until possibly

Re: [Talk-us] [Imports] Preliminary Import/Organized Mapping Effort Idea

(Conversational quoting, please) On Fri, Dec 20, 2019 at 6:42 PM David Bartecchi wrote: > All of these concerns must be weighed against the fact that the current > absence of Native lands in OSM only contributes to the erasure Native > Americans and their lands from the American collective

Re: [Talk-us] [Imports] Preliminary Import/Organized Mapping Effort Idea

I've reached out to a couple of the nearby reservations, one with a small parcel of off reservation land trust, the other with only a small reservation but a very large off reservation land trust. I don't expect answers until possibly after the new year. Unlike Oklahoma, Washington reservations

Re: [Talk-us] [Imports] Preliminary Import/Organized Mapping Effort Idea

Content warning: Aboriginal abuse mention On Fri, Dec 20, 2019 at 2:08 PM Clifford Snow wrote: > I do have Washington State tribal lands available [1] as a background > layer for JOSM. There is also a vector tile layer [2] of the same > background available for iD users. > > The data contains

Re: [Talk-us] [Imports] Preliminary Import/Organized Mapping Effort Idea

On Thu, Dec 19, 2019 at 3:03 PM Mike Thompson wrote: > > I've avoided BIA because their data doesn't seem accurate > We have gotten some additional feedback off list also suggesting that the > BIA data may not be as accurate as some other sources. Perhaps we should > create a wiki page listing

Re: [Talk-us] [Imports] Preliminary Import/Organized Mapping Effort Idea

Clifford, Thanks for your feedback. > I've avoided BIA because their data doesn't seem accurate We have gotten some additional feedback off list also suggesting that the BIA data may not be as accurate as some other sources. Perhaps we should create a wiki page listing every reservation, its

[Talk-us] [Imports] Preliminary Import/Organized Mapping Effort Idea

Hi all, Looking to get more people/groups involved in OSM is always a challenge. One place I might start would be to reach out to those mappers who have last edited the current boundaries and ask them their thoughts on this project. If you are using JOSM editor you can use ‘Ctrl + h’ to find

Re: [Talk-us] [Imports] Preliminary Import/Organized Mapping Effort Idea

Mike, Thanks to you, David and Paul for taking the initiative to mapping Natiive American Reservations. On and off for the last few years I've been attempting to reservations mapped in Washington State. My first choice for boundary information has always been from the reservation then the state.

Re: [Talk-us] [Imports] City of Portsmouth, Virginia Building/Address Import

; > <https://wiki.openstreetmap.org/wiki/City_of_Portsmouth_Buildings/Address_Import> > > > This message has been cross-posted in Talk-US, Imports-US, & Imports. > > Also please rememberer SOTMUS is around the corner

Re: [Talk-us] [Imports] Grand Junction, CO Fire Hydrant Import

Just a quick thought, but have you checked out the Conflation plug-in in JOSM? Assuming the hydrant number that will go in your ref tag is unique, that would be an easy way to match or use a search radius on already mapped hydrants and then merge tags. The only other issue I could see is that

Re: [Talk-us] [Imports] [Imports-us] Spartanburg County SC road centerlines import

On 10/22/2018 2:56 PM, Rory McCann wrote: Hi Mike. Thanks for the answers, that clears things up. Bt On 10/22/2018 5:00 AM, Rory McCann wrote: >> I'm a little unclear about one big question: What are you doing with the existing data in OSM? Existing OSM data seems to have nearly

Re: [Talk-us] [Imports-us] Spartanburg County SC road centerlines import

Thank you for your comments. Answers inline. On 10/22/2018 5:00 AM, Rory McCann wrote: On 22/10/2018 05:20, Mike N wrote: This is a proposed import of road centerlines for Spartanburg County SC, based on county GIS data.   This will include a systematic review of all roads in the county and

Re: [Talk-us] [Imports] Bing Building Import

Hi all- Have there been any ideas about how we want to handle the import process? My thoughts are that this could be treated as a unified project for "simple" imports that will not be conflating the footprints with other data (e.g. address points). My thought is we could adopt a streamlined

Re: [Talk-us] [Imports] Durham and Chatham County Address Imports (North Carolina, USA)

Point taken. In this case, they are the center of property polygons, so not on buildings, conflated with buildings nor at entrances. I don't mind if they are reasonably placed as nodes, but these are not quite there, yet. James On Sat, 2018-07-21 at 15:34 -0400, Nathan Mills wrote: > To the

Re: [Talk-us] [Imports] Durham and Chatham County Address Imports (North Carolina, USA)

To the extent that the address points are not duplicates of existing address nodes, unconflated address nodes are a perfectly legitimate means of mapping and do not need to be "fixed." Even if the address exists on a poly, it's still fine as long as the node is marking something meaningful,

Re: [Talk-us] [Imports] Bing Building Import

The damage done by the "foot shot" is the damage to the community. At least one researcher found a way to study this (because of inadvertent import quality issues with TIGER) and found that the areas with better import quality wound up more poorly mapped over time. I'm convinced that there are

Re: [Talk-us] [Imports-us] Importing Addresses in Orange County North Carolina

On Sat, Jun 23, 2018 at 2:50 PM Greg Morgan wrote: > > > On Wed, Jun 20, 2018, 2:34 PM Clifford Snow > wrote: > >> A couple of things First you have two tags that are not needed, >> addr:state and addr:country. >> > I have a different opinion on this subject. I always add these two tags. > We

Re: [Talk-us] [Imports-us] Importing Addresses in Orange County North Carolina

On Sat, Jun 23, 2018 at 2:57 PM, Tommy Bruce wrote: > I agree I don't see anything wrong with keeping the state and country tag. > > 2018-06-23 14:50 GMT-07:00 Greg Morgan : > >> >> >> On Wed, Jun 20, 2018, 2:34 PM Clifford Snow >> wrote: >> >>> A couple of things First you have two tags that

Re: [Talk-us] [Imports-us] Importing Addresses in Orange County North Carolina

On Wed, Jun 20, 2018, 2:34 PM Clifford Snow wrote: > A couple of things First you have two tags that are not needed, > addr:state and addr:country. > I have a different opinion on this subject. I always add these two tags. We are an international map. If he has the data already, I don't see

Re: [Talk-us] [Imports-us] Importing Addresses in Orange County North Carolina

Hi Tommy, Yes, I agree that existing addresses should be kept. When I wrote that I removed duplicates, what I actually meant was that I removed duplicates of existing addresses from the addresses that I am planning to add. That is to say that only missing addresses will be added. Sorry about

Re: [Talk-us] [Imports] US Sports Fields Import

Hi Jason, I mentioned this in your repo but thought I would also mention it to this list. The Microsoft legal team reviewed this particular scenario and determined that it is consistent with the current terms of the imagery as it relates to contributing to OSM. You're welcome to use the Bing

[Talk-us] [Imports-us] New to lists and would like to suggest some imports

I would add that the guidance of an OSM volunteer with some experience with importing can be quite helpful. It is easy to be eager to complete an import. It can be challenging, especially for novice mappers or those unexperienced with "medium-sized" projects like this to do one for the first

Re: [Talk-us] [Imports-us] New to lists and would like to suggest some imports

first things first. the import guidelines are here: https://wiki.openstreetmap.org/wiki/Import/Guidelines second, the licensing is critical. make absolutely sure that the state has a clear statement of public domain, CC0 or equivalent license. probably the most valuable import would be

Re: [Talk-us] [Imports] Integrating our open source data into OSM

On 2017.11.10. 00:11, Sean Lindsey wrote: > It seems that it's going to be hard to come up with a mass import > solution that every one can agree on. I would suggest that you take > name, address, phone number, website and category then try and > re-geocode the data, but it seems there is

Re: [Talk-us] [Imports] Integrating our open source data into OSM

It seems that it's going to be hard to come up with a mass import solution that every one can agree on. I would suggest that you take name, address, phone number, website and category then try and re-geocode the data, but it seems there is opposition to this method as well. Another approach - as

Re: [Talk-us] [Imports] Integrating our open source data into OSM

help.openstreetmap.org >> <https://help.openstreetmap.org/questions/60508/submit-open-source-poi-data>, >> and was referred to these mailing lists >> >> Regards, >> -- >> Sean Lindsey >> Cybo Company >> LinkedIn <https://www.linkedin.com/in/se

Re: [Talk-us] [Imports] Integrating our open source data into OSM

/60508/submit-open-source-poi-data>, > and was referred to these mailing lists > > Regards, > -- > Sean Lindsey > Cybo Company > LinkedIn <https://www.linkedin.com/in/sean-lindsey/> > 541-912-2505 <(541)%20912-2505> > > > ____

Re: [Talk-us] [Imports] Fort Worth, Texas import

Daniel- Thanks for the heads up! It looks like their footprints cover an area of the city that I've already imported, but the height data would certainly be useful. I think it would make sense to add this in to the import project. Thanks! Andrew Matheny On Jun 21, 2017 11:56 PM, "Daniel

Re: [Talk-us] [Imports] Fort Worth, Texas import

Hey Joe, Andrew, With regard to this import moving ahead, we have decided to archive the project in the tasking manager [0] to avoid community working on these tasks and digitize data. [0] - https://lists.openstreetmap.org/pipermail/talk-us/2017-May/017373.html Cheers, Jinal Foflia On Sat,

Re: [Talk-us] [Imports] Fort Worth, Texas import

Andrew, Looks good to me and a great follow up to the Dallas project. I would suggest contacting the project lead for project 95, they appear to work at mapbox. I contacted the mapbox user that created a digitizing project that overlapped my import project and they changed the status on the

Re: [Talk-us] [Imports] Dakota County, MN Building and Address Import

> What I need help with is: > • I can export the data out into the chunks in Shp format fairly > easily, I know how to script that. And I have decent polygons for doing so. > I need a good tool for converting that to OSM, in bulk. Hi Joe: I think you are on the right track here, but I

Re: [Talk-us] [Imports] Dakota County, MN Building and Address Import

On Wed, Mar 15, 2017 at 10:48 AM, wrote: > What I need help with is: > >1. I can export the data out into the chunks in Shp format fairly >easily, I know how to script that. And I have decent polygons for doing >so. I need a good tool for converting that

Re: [Talk-us] [Imports-us] OSM-Colorado Mappy Hour Denver Buildings Import Discussion

The data here: http://gis.drcog.org/datacatalog/content/planimetrics-2014-building-roofprints Doesn't seem to match the description on the wiki. Perhaps it has already been converted partly to the OSM tagging (e.g. sheds and garages are separate)? On Tue, Jan 24, 2017 at 6:20 PM, Mike

Re: [Talk-us] [Imports-us] OSM-Colorado Mappy Hour Denver Buildings Import Discussion

Russ, This is very exciting to see this coming along. Let me know how I can help. Hopefully we can use its success to convince other government bodies in Colorado to allow us to import their data into OSM! Here are a few comments. re: "The Denver Regional Council of Governments (DRCOG), in

Re: [Talk-us] [Imports] Proposing import of sidewalk data Seattle, WA, USA

On Tue, Aug 2, 2016 at 10:59 AM, Clifford Snow wrote: > > On Tue, Aug 2, 2016 at 6:01 AM, Frederik Ramm wrote: > >>sidewalk tagging in OSM is a complex issue. The fact that sidewalks >> are not tagged as individual geometries is not purely a

Re: [Talk-us] [Imports] Proposing import of sidewalk data Seattle, WA, USA

On Sun, Aug 7, 2016 at 5:04 AM, Marc Gemis wrote: > On Sun, Aug 7, 2016 at 12:40 AM, Greg Morgan wrote: >> look at the recent turn lane work that MapBox is performing. They >> have done a wonderful job of finding issues and developing use cases >>

Re: [Talk-us] [Imports] Proposing import of sidewalk data Seattle, WA, USA

> Again this seems to be is the "I'm waiting for someone else to do something" > line. If you want a map rendering that shows stop signs, create one, like I I am not standing in any line. If I find an issue that I don't think has been addressed or the original author did not understand is an

Re: [Talk-us] [Imports] Proposing import of sidewalk data Seattle, WA, USA

On 06/08/2016 23:40, Greg Morgan wrote: Again relevance: I am still waiting for a stop sign to be rendered a year after it was requested. If we wait until a stop sign gets all artsie and fartsie, then it will never be rendered and it will never be mapped or shall I say mappers will become

Re: [Talk-us] [Imports] Proposing import of sidewalk data Seattle, WA, USA

Thank you for your comments Greg! We've been drafting a longer response that we wanted to share, and this seems like a good moment to jump in and do so. Firstly, thank you to everyone for your engaging feedback! We’ve learned a huge amount about the weaknesses and strengths of our proposal. We

Re: [Talk-us] [Imports] Proposing import of sidewalk data Seattle, WA, USA

On Tue, Aug 2, 2016 at 6:01 AM, Frederik Ramm wrote: > Meg, > >sidewalk tagging in OSM is a complex issue. The fact that sidewalks > are not tagged as individual geometries is not purely a shortcoming, it > is a compromise that keeps OSM data editable. Having individual

Re: [Talk-us] [Imports] Proposing import of sidewalk data Seattle, WA, USA

Clifford, On 08/02/2016 05:59 PM, Clifford Snow wrote: > We tell people not to map for the renderer. In the same spirit shouldn't > we tell people not to let the limitations of the editor stop them from > mapping? Usually, when you deal with individual mappers who come up with a tagging scheme,

Re: [Talk-us] [Imports] Proposing import of sidewalk data Seattle, WA, USA

On Tue, Aug 2, 2016 at 6:01 AM, Frederik Ramm wrote: >sidewalk tagging in OSM is a complex issue. The fact that sidewalks > are not tagged as individual geometries is not purely a shortcoming, it > is a compromise that keeps OSM data editable. Having individual >

Re: [Talk-us] [Imports] Kansas City addresses from maps.kcmo.org

On Fri, Jul 29, 2016 at 3:02 PM, Frederik Ramm wrote: > Hi, > > On 07/29/2016 03:42 AM, Clifford Snow wrote: > > Thanks for pointing out my lapse. You are correct. I've used parcel > > boundaries for parks a number of time. > > Nonetheless (in order not to confuse the

Re: [Talk-us] [Imports] Kansas City addresses from maps.kcmo.org

On Thu, Jul 28, 2016 at 5:12 PM, Clifford Snow wrote: > > On Thu, Jul 28, 2016 at 12:02 PM, teslas_moustache < > teslas_mousta...@riseup.net> wrote: > >> >> I'm not sure if property lines and ownership are useful. And I don't >> think that building outlines are included,

Re: [Talk-us] [Imports] Kansas City addresses from maps.kcmo.org

Hi, On 07/29/2016 11:46 PM, Jonathan Schleuss wrote: > I'm kind of curious about this. Why not import those property lines? I'm > not arguing for them, because it seems like a lot of work. But I note > that in cities such as Fresno, they are in the map >

Re: [Talk-us] [Imports] Kansas City addresses from maps.kcmo.org

Hi, I'm kind of curious about this. Why not import those property lines? I'm not arguing for them, because it seems like a lot of work. But I note that in cities such as Fresno, they are in the map as landuse=residential. What if we add all the buildings, all the trees, every bench? Why not

Re: [Talk-us] [Imports] Kansas City addresses from maps.kcmo.org

Hi, On 07/29/2016 03:42 AM, Clifford Snow wrote: > Thanks for pointing out my lapse. You are correct. I've used parcel > boundaries for parks a number of time. Nonetheless (in order not to confuse the original poster) let's reiterate that property lines themselves do not belong in OSM; only

Re: [Talk-us] [Imports] Kansas City addresses from maps.kcmo.org

Clifford Snow writes: > On Thu, Jul 28, 2016 at 12:02 PM, teslas_moustache < > teslas_mousta...@riseup.net> wrote: > >> I'm not sure if property lines and ownership are useful. And I don't >> think that building outlines are included, so I may need to continue >> with

Re: [Talk-us] [Imports] Kansas City addresses from maps.kcmo.org

On Thu, Jul 28, 2016 at 4:51 PM, Kevin Kenny wrote: > Property lines also define the bounds of public areas like parks, > schoolyards, cemeteries, and airfields, which surely do belong in OSM. They > aren't infallible, but they are often more precise than guessing from >

Re: [Talk-us] [Imports] Kansas City addresses from maps.kcmo.org

On Jul 28, 2016 6:14 PM, "Clifford Snow" wrote: > While property lines don't belong in OSM, they can be useful. Having parcel boundaries can be useful to figure out the address of a building. Especially if you can get access to the property, i.e. the owner has no

Re: [Talk-us] [Imports] Updates:LA County building import (Los Angeles, California, USA)

Christoph, Thank you for the observation. Specific to "roads now intersect buildings indicating that mapping is inaccurate - like here:" They are mostly unreviewed TIGER import, I also saw one instance where we have building but no roads. This was already discussed by the import team and will be

Re: [Talk-us] [Imports] Status and progress: NYS DEC Lands reimport

On Tue, Jul 19, 2016 at 8:25 AM, Greg Troxel wrote: > Martin Koppenhoefer writes: >> On this particular issue I believe you should use different tagging. >> Currently there is almost no use of access=permit >>

Re: [Talk-us] [Imports] Status and progress: NYS DEC Lands reimport

Martin Koppenhoefer writes: > On this particular issue I believe you should use different tagging. > Currently there is almost no use of access=permit > http://taginfo.openstreetmap.org/tags/access=permit > Typically if you require a permission for access it is "private"

Re: [Talk-us] [Imports] Proposed import cleanup: NYSDEClands

On 05/19/2016 05:27 AM, Paul Norman wrote: I was debugging some MP issues and came across the NYSDEClands import[1], done in 2010, consisting of natural areas. They have a number of unwanted tags[2], and a couple of other problems with their tags Because there's a relatively small number of

Re: [Talk-us] [Imports] Proposed import cleanup: Olympic peninsula streams

On Thursday 19 May 2016, Paul Norman wrote: > - Simplifies them with JOSM, set to 2.5m threshold That's not a good idea - incidently that is *never* a good idea for a meachanical edit, especially not with an absolute threshold. I also don't see significant meaningless detail in the data so even

Re: [Talk-us] [Imports] RFC: LA County building import (Los Angeles, California, USA)

Hi, We've started the import this during MaptimeLA [0] last April 2. First project focused on Southside LA [1]. For any issues regarding the process and the data please post a ticket in GH [2]. [0] http://www.meetup.com/MaptimeLA/events/229861154/ [1] http://labuildingsimport.com/project/2 [2]

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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 >

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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.  -

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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 >

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports] Boston, MA, USA addr:housenumber Import

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

Re: [Talk-us] [Imports-us] Virginia Beach, Virginia Imports

Hello, Thanks for the questions! > You live an hour away from Virginia Beach, is that correct? Yes! Good detective work - depending on traffic. > Are you > familiar enough with the city to verify the data quality, or will you > enlist the help of local mappers who are? Yes! Virginia Beach

Re: [Talk-us] [Imports-us] Virginia Beach, Virginia Imports

> On Mar 1, 2016, at 11:58 PM, Frederik Ramm wrote: > > > Is there a community that can be counted on to make sure the data > doesn't rot in OSM once imported - or will you commit to that? > Is this really a serious objection? If so then perhaps I should not map areas I

Re: [Talk-us] [Imports-us] Virginia Beach, Virginia Imports

Hi, On 03/02/2016 02:55 AM, Jonah Adkins wrote: > I'd like to propose an import of city-sourced GIS data for the City of > Virginia Beach, Va. The City GIS Office has given the data / license for this > purpose. > Conflation will be done carefully by hand, and attributes copied where needed.

Re: [Talk-us] [Imports-us] RFC: LA County building import

Hi Frederik, > On Feb 12, 2016, at 11:33 PM, Frederik Ramm wrote: > > How many of your team are local to LA, and how are you cooperating with > the OSM community in LA? Of the four of us who have been preparing the data and who will be overseeing the import, two of us

Re: [Talk-us] [Imports-us] RFC: LA County building import

Maning, On 02/13/2016 06:45 AM, maning sambale wrote: > We are proposing a building import of the public domain building and > assessor data for LA County [0]. How many of your team are local to LA, and how are you cooperating with the OSM community in LA? What is your estimate about

Re: [Talk-us] [Imports] Importing Buildings and Addresses for Austin, Texas

On Mon, Nov 9, 2015 at 6:40 PM, Andy Wilson wrote: > 3. Efficiency. There are enough buildings in OSM already and as Martin > pointed out, comparing them individually and properly merging tags, etc > would be time consuming. JOSM has a "Replace Geometry" tool found

Re: [Talk-us] [Imports] Importing Buildings and Addresses for Austin, Texas

On Mon, Nov 9, 2015 at 12:59 PM Martin Koppenhoefer wrote: > > > sent from a phone > > > Am 09.11.2015 um 18:07 schrieb Eric Ladner : > > > > Replacing existing hand drawn buildings with imports from the city's GIS > system would probably be

Re: [Talk-us] [Imports] Importing Buildings and Addresses for Austin, Texas

I'll second Paul's bit rot on unique ID's comments. They're all well and good until somebody upgrades their GIS system, then all those unique ID's get flushed down the drain. And actually doing a conflation with hundreds of thousands of buildings which may or may not have the ID's preserved

Re: [Talk-us] [Imports] Importing Tesla Superchargers

In many cases, the sucket:tesla_supercharger is different So Tesla is calling their supercharger sockets suckets? How appropriate. -jack On April 13, 2015 4:24:03 PM EDT, Charles Samuels o...@charles.derkarl.org wrote: On Sunday, April 12, 2015 05:33:02 PM Greg Troxel wrote: You may

Re: [Talk-us] [Imports] Importing Tesla Superchargers

On Sunday, April 12, 2015 05:33:02 PM Greg Troxel wrote: You may actually be right about the likelihood of correctness, and this may lead to an expected value of 0.1 errors per year. However, imports changing data entered by hand is something that crosses a cultural bright line, and I find

Re: [Talk-us] [Imports] Importing Tesla Superchargers

Do you think anybody will do the effort to correct some of the data, when it will be overwritten again with each update ? That's why people ask not to overwrite the data automatically. regards m p.s. it's annoying that this is cross-posted on 2 mailing lists, I'm only subscribed to one of

Re: [Talk-us] [Imports] Importing Tesla Superchargers

Hi, On 04/13/2015 10:23 AM, Greg Morgan wrote: Oh my goodness. Once again we have the alleged notion that imports will drive off mappers without examining any real data. No. It appears that you're going off on a tangent without examining the messages that were written ;) Until now I can't

Re: [Talk-us] [Imports] Importing Tesla Superchargers

Oh my goodness. Once again we have the alleged notion that imports will drive off mappers without examining any real data. If we look at the Buckeye Charger we see that fredo_p, a A Hit-and-Run Mapper, added the original node. He's still a mapper. Theodin a German mapper added something. AndiG88

Re: [Talk-us] [Imports] Importing Tesla Superchargers

Charles Samuels o...@charles.derkarl.org writes: On Sunday, April 12, 2015 01:12:12 AM Andy Allan wrote: Right now, if a tag doesn't match with supercharge.info, I overwrite OSM's. Could you explain this a bit further? For example, if supercharge.info has capacity 6, and I correct this

Re: [Talk-us] [Imports] Importing Tesla Superchargers

On Sunday, April 12, 2015 01:12:12 AM Andy Allan wrote: Right now, if a tag doesn't match with supercharge.info, I overwrite OSM's. Could you explain this a bit further? For example, if supercharge.info has capacity 6, and I correct this to capacity 8, does your script then overwrite my

Re: [Talk-us] [Imports] Importing Tesla Superchargers

* Charles Samuels o...@charles.derkarl.org [150412 22:21]: On Sunday, April 12, 2015 01:12:12 AM Andy Allan wrote: Right now, if a tag doesn't match with supercharge.info, I overwrite OSM's. Could you explain this a bit further? For example, if supercharge.info has capacity 6, and I correct

  1   2   3   4   >