[Imports] Municipality of Örebro, Sweden

2014-10-30 Thread Karl Wettin
Örebro municipality of Sweden release GIS-data as CC0. 

This data can be harvested and post processed to produce a couple of hundred 
thousand nodes with a couple of class tag values:

name, place:halmet,
addr:city, addr:place, addr:street, addr:housenumber, 
name, addr:city, addr:place, highway=road
name, amenity=school, isced:level,
name, amenity=social_facility, social_facility= assisted_living, 
social_facility:for,
name, leisure=park
etc.

Output is one osm.xml-file per class. 

https://github.com/OpenStreetMap-Sverige/import-orebro-osm-xml/tree/master/osm.xml
 
https://github.com/OpenStreetMap-Sverige/import-orebro-osm-xml/tree/master/osm.xml
https://github.com/OpenStreetMap-Sverige/import-orebro-osm-xml/archive/master.zip
 
https://github.com/OpenStreetMap-Sverige/import-orebro-osm-xml/archive/master.zip

Also attempts to find OSM-duplicates in a radius of 500-5000 meters, which 
seems to work really well but could probably be improved by allowing a bit of 
Levenshtein distance, whitespace- and \p{Punct} normalization. Not sure how 
much this would help though, everything looks pretty great when inspecting 
manually.

Duplicates from source data are written to a common osm.xml (rather than 
written to their individual class-osm.xml) and the duplicates from OSM are 
written (with recursed children) to yet another osm.xml-file.



Script:

https://github.com/OpenStreetMap-Sverige/import-orebro-harvester/blob/master/src/main/java/se/kodapan/osm/orebro/Orebro.java
 
https://github.com/OpenStreetMap-Sverige/import-orebro-harvester/blob/master/src/main/java/se/kodapan/osm/orebro/Orebro.java

See line 335 and down to see exactly what classes there are and how the 
duplication detection mechanism works. (And sorry for all the Swedish language 
comments and names.)



We are now considering the workflow. 

Consensus on #osm...@irc.oftc.net mailto:osm...@irc.oftc.net is along the way 
the data looks great, let's just commit it and then get started working on it 
as usual. The reaction on #osm has been quite the opposite make sure any work 
is in the one single commit of the import account.

I've been considering asking all that can help with manual burdon och checking 
all points to do it at github, add any new things to OSM in a per 
user-changes.osm.xml  to avoid inverted identity conflicts and then to a merge 
before we committ it. If I understand everything correct then that would 
satisfy the people I spoke with on #osm.

That might be too much to ask of the users. And the data is really clean. We 
really want to just push it in the way it is and start working with it in the 
database as normal using a task project. 



karl___
Imports mailing list
Imports@openstreetmap.org
https://lists.openstreetmap.org/listinfo/imports


Re: [Imports] [Imports-us] New Orleans: importing buildings and addresses

2014-10-30 Thread Johan C
I don't have any programming skills, but I tested the plugin after Gertjan
programmed it: an example of this splitting of 'nodes on top of each other'
can be seen in the Vermeertoren in Delft:
http://www.openstreetmap.org/?mlat=52.01280mlon=4.33795#map=19/52.01280/4.33795
(opening it in JOSM shows all nodes)

In the Dutch import we wanted to keep all address points within the
building and this method worked quite well. Though aligning them parallel
to the nearest street with the same name might also work

Cheers, Johan

2014-10-30 21:47 GMT+01:00 Eric Ladner eric.lad...@gmail.com:

 On Wed, Oct 29, 2014 at 5:29 AM, Gertjan Idema g.id...@zonnet.nl wrote:

  Matt,

 The principle dividing up multiple addresses on the same location within
 the building is quite simple.
 If there are multiple addresses on one location within a building I do
 the following.

 1. Sort the addresses by postcode, street, house number.
 2. Determine the angle of the line pointing from the address location to
 the center of the building.
 3. From the angle and the desired distance between the address nodes,
 calculate a delta x an a delta y. Either or both may be negative.
 4. Iterate over the address nodes and add  (i * delta x) to the x
 coordinate an (i * delta y) to the y coordinate.

 If the address location is at the center of the building, I set the angle
 to 0.


 I'm having problems visualizing that in my head...  Picture?

 If it's doing what I think it's doing, whouldn't it make more sense to
 align the address nodes parallel to the nearest street with the same name?
 --
 Eric Ladner

___
Imports mailing list
Imports@openstreetmap.org
https://lists.openstreetmap.org/listinfo/imports


Re: [Imports] [Imports-us] New Orleans: importing buildings and addresses

2014-10-30 Thread Gertjan Idema
For an extreme example, you can have a look at Europaplein 360 - 398 in
Utrecht (With an editor).
Our reason for this solution is that we want to make sure that the
addresses stay within the building contour. The imported dataset only
guarantees that the addresses are within the building. When aligning the
addresses parallel to the street, the address nodes could easily end up
in a neighboring building. Also you would want to make sure the address
numbers get aligned in the right direction along the street. And in The
Netherlands, the addresses might be in different streets.
The algorithm would get quite complex if you wanted to solve all these
issues.

Gertjan


On Thu, 2014-10-30 at 15:47 -0500, Eric Ladner wrote:
 On Wed, Oct 29, 2014 at 5:29 AM, Gertjan Idema g.id...@zonnet.nl
 wrote:
 
 Matt,
 
 The principle dividing up multiple addresses on the same
 location within the building is quite simple.
 If there are multiple addresses on one location within a
 building I do the following.
 
 1. Sort the addresses by postcode, street, house number.
 2. Determine the angle of the line pointing from the address
 location to the center of the building.
 3. From the angle and the desired distance between the address
 nodes, calculate a delta x an a delta y. Either or both may be
 negative.
 4. Iterate over the address nodes and add  (i * delta x) to
 the x coordinate an (i * delta y) to the y coordinate.
 
 If the address location is at the center of the building, I
 set the angle to 0.
 
 
 
 
 
 I'm having problems visualizing that in my head...  Picture?
 
 
 If it's doing what I think it's doing, whouldn't it make more sense to
 align the address nodes parallel to the nearest street with the same
 name?
 
 -- 
 Eric Ladner

___
Imports mailing list
Imports@openstreetmap.org
https://lists.openstreetmap.org/listinfo/imports


[Imports] Marin County data license

2014-10-30 Thread Nathan Mixter
Hi,

The County of Marin in California has buildings and addresses available to
download from their website. The data appears to be high quality and covers
the whole county. It would be great to be able to conflate the two files,
merging the points and areas that have a direct one-to-one relationship.


The website doesn't have anything specific about the license. It just has
vague disclaimer info - county cannot be held liable ...blah blah blah. I
contacted them to ask if the data was public domain and if it could be used
in OSM. This is their response:


You may download public domain data from the MarinMap GIS data download
site.

You do not need a license to use public domain data.

You may acknowledge “MarinMap” as the original source, but you MUST state
that MarinMap has no responsibility or warranty regarding data after they
have entered the public domain.

You may use the legalese from the disclaimer web page to facilitate writing
a disclaimer.
URL of the disclaimer page:
http://www.marinmap.org/dnn/Pages/LegalNoticeDisclaimer.aspx;
http://www.marinmap.org/dnn/Pages/LegalNoticeDisclaimer.aspx

Since the data is public domain, is there any way to accommodate their
request to include the disclaimer? There have been other imports that have
had this requirement I think and included it on the wiki or someplace
similar. Can it be included on the changeset tag somewhere?

Anyone had any experience with this type of data? Any ideas on how to make
it work?

Thanks,
Nathan Mixter
___
Imports mailing list
Imports@openstreetmap.org
https://lists.openstreetmap.org/listinfo/imports


Re: [Imports] Marin County data license

2014-10-30 Thread Daniel O'Connor
A wiki entry describing the data, the import, etc and the attributions may
be sufficient.

On Fri, Oct 31, 2014 at 2:57 PM, Nathan Mixter nmix...@gmail.com wrote:

 Hi,

 The County of Marin in California has buildings and addresses available to
 download from their website. The data appears to be high quality and covers
 the whole county. It would be great to be able to conflate the two files,
 merging the points and areas that have a direct one-to-one relationship.


 The website doesn't have anything specific about the license. It just has
 vague disclaimer info - county cannot be held liable ...blah blah blah. I
 contacted them to ask if the data was public domain and if it could be used
 in OSM. This is their response:


 You may download public domain data from the MarinMap GIS data download
 site.

 You do not need a license to use public domain data.

 You may acknowledge “MarinMap” as the original source, but you MUST state
 that MarinMap has no responsibility or warranty regarding data after they
 have entered the public domain.

 You may use the legalese from the disclaimer web page to facilitate
 writing a disclaimer.
 URL of the disclaimer page:
 http://www.marinmap.org/dnn/Pages/LegalNoticeDisclaimer.aspx;
 http://www.marinmap.org/dnn/Pages/LegalNoticeDisclaimer.aspx

 Since the data is public domain, is there any way to accommodate their
 request to include the disclaimer? There have been other imports that have
 had this requirement I think and included it on the wiki or someplace
 similar. Can it be included on the changeset tag somewhere?

 Anyone had any experience with this type of data? Any ideas on how to make
 it work?

 Thanks,
 Nathan Mixter





 ___
 Imports mailing list
 Imports@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/imports


___
Imports mailing list
Imports@openstreetmap.org
https://lists.openstreetmap.org/listinfo/imports