Hi,
I checked 20 or so stations in Massachusetts, they all look good.
Jason
On Wed, Mar 7, 2018 at 12:07 PM, Ilya Zverev wrote:
> Hi everyone,
>
> Following the recent UK Shell stations import, I've got ahold of the
> entire NavAds dataset. A major part of it are fuel
://www.openstreetmap.org/user/jharpster
>
>
> -----Original Message-
> From: Jason Remillard [mailto:remillard.ja...@gmail.com]
> Sent: Tuesday, January 2, 2018 7:22 PM
> To: Rory McCann <r...@technomancy.org>
> Cc: Imports OpenStreetMap.org <imports@openstreetmap.org>;
> ta
sting
> OSM data, and would be under the ODbL?
>
> I haven't looked at your data, or tried to run the code myself, but I'd
> like to do it sometime.
>
> Rory
>
> On 30/12/17 20:51, Jason Remillard wrote:
>> Hi,
>>
>> I have trained a neural network to f
Hi,
I have trained a neural network to find baseball, basketball, and
baseball fields in satellite images. It was trained using OSM and bing
tiles. Using the neural network I have mapped 2,800 new fields in the
US northeast, I would like to import the missing fields back into OSM.
Wiki project
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
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
Hi Frederick,
I don't think you should hold off. The data may never come, and having
addresses in by hand will allow us to QA any possible future import...
Jasob
On Sat, May 23, 2015 at 11:18 PM, Frederick Hunter fhunt...@verizon.net
wrote:
Hi Lars,
Thanks for the reply. I hadn't realized
Hi Charles,
tag k='capacity' v='6' /
tag k='socket:tesla_supercharger' v='6' /
tag k='name' v='Tesla Supercharger Harris Ranch' /
tag k='addr:city' v='Coalinga' /
tag k='tesla:ref' v='harrisranchsupercharger' /
Hi Wiktor,
I don't think an address tag is needed or desirable.
The best way of doing this is to compare versions of the official data
(perhaps every 6 months), making a list of things that have changed so
that they can be examined in OSM.
Of coarse the big issue is that the matching is not
...@vink.pl wrote:
2015-01-10 16:44 GMT+01:00 Jason Remillard remillard.ja...@gmail.com:
Hi Wiktor,
I don't think an address tag is needed or desirable.
The best way of doing this is to compare versions of the official data
(perhaps every 6 months), making a list of things that have changed so
Hi Karl,
- You need to setup a wiki page for the import, basically duplicating
the information in this email.
- If you are using your import account, there is no requirement to
have the entire import in one change set. In fact if you upload a
change set that is at the maximum size, it will make
Hi Nathan,
I loaded the data in JOSM. It has some weird tags for an import.
Fixme, n, fixme, gnis:* ,
It looks like this data has been merged with the existing OSM data,
otherwise why have gnis tags?
Some of the buildings that are in OSM overlap with the data. It is all
kind of confusing
Hi Matt,
- It is not clear if including the ids is useful. You should consider
dropping them.
- Why only put the id on the buildings, but not the address nodes.
- Consider figuring out how to capture multiple addresses at the same
node location, rather than dropping them in favor of the primary
Hi Clark,
If you are not interested in importing the data yourself, I would
suggest posting on the Canadian talk list, ask if there are any local
people that can help out. The data set is not too large, if it makes
sense, it should not be to hard to import it.
Thanks
Jason
On Tue, Sep 16, 2014
Hi Rafael,
Everything looks ok except ... you should look at the surface tags on
the OSM ways you are going to keep and it does not have a surface tag,
transfer the imported surface tag, leaving the rest of the way alone.
If the OSM surface tag exists and conflicts, message the osm author
and try
Hi,
This is the best I can do with the online translation to English...
- The source, source:date tags on the node is not needed since it is
in the change-set.
- The process of replacing the existing nodes with the new nodes is
not ideal. The new data should be merged in with the old node so
Hi,
- Paid staff
The question was raised on if paid staff would be used for this. The wiki
says no money is being exchanged for work - does this mean that all work
will be done by volunteers?
- Remote mappers
Will many remote mappers be involved, particularly paid ones?
I believe it
Hi Richard,
Assuming the data quality is good and the existing way does not have a
speed limit, I don't see any reason not do an automated edit.
Leave the MapRoulette for the areas where the data and OSm speed limit
don't match?
Jason
On Tue, Jun 24, 2014 at 4:43 PM, Richard Weait
Hi,
Bike Route 1 on Cape Cod, MA is signed. I saw a bunch of them last
summer biking around on vacation.
In my opinion at this point the new routes should go through the
import process, but given that signs are already up, and over time
more are sure to come, I don't see any problem having the
Hi,
I support fixing imports with automated edits such as this proposal.
Except for the gnis:id, I think it would be Ok to drop the rest of the tags.
Thanks
Jason
On Thu, May 29, 2014 at 3:29 AM, malenki o...@malenki.ch wrote:
On Thu, 29 May 2014 02:52:23 +0200
Martin Koppenhoefer wrote:
Hi David
Given that this is using the same process as the NYC import, what
lessons/changes are planned to avoid the same problems encountered in NYC.
I think NYC had to be paused a couple of times, it was not perfect. It
would be dumb to do everything exactly the same.
NYC importers (Alex ),
Hi Richard,
- Is it possible to get the way version number in the output file?
Otherwise, if the drivers are using older map data, we might overwrite
more recent corrections.
- Will the data have duplicate change requests on the same way id from
different drivers, so we can get some kind of
Hi Richard,
- Is it possible to get the way version number in the output file?
Otherwise, if the drivers are using older map data, we might overwrite
more recent corrections.
- Will the data have duplicate change requests on the same way id from
different drivers, so we can get some kind of
Hi Martin,
It looks like most of the source:maxspeed=massgis were not from an import,
but from a very prolific mapper, NE2. You may want to consider changing the
tags yourself. User NE2 is currently not participating in OSM right now.
Jason
On Thu, Mar 20, 2014 at 11:15 AM, Martin
Hi,
This is a bunch of little imports. This is not a single all of Poland
dataset, but rather a collection of little datasets by region. The data
is similar, of course due to the nature of the data being addresses.
this is true. Data comes form local governaments databases/GIS which are
Hello Everybody,
Each municipality is a different import. Part of the process needs to be
to be validation, for example, which has already been brought up and not
answered.
I have been trying to follow this thread, but I think I missed this part.
Could somebody recap this, if this one
Hi Eduard,
One of the issues that always seems to cause difficulties on public
transportation imports is the ID/ref. ref= is only used if it is visible on
the stops. If the ID is really an SIRI id or GTFS id, then it should use a
different tag. If the ID, is none of the above, then perhaps it
Hi,
- No streets?
- 98% of the addresses in this file could have the building=yes tag applied.
Jason
2014-02-19 13:54 GMT-05:00 Zbigniew Czernik zbign...@openstreetmap.pl:
W dniu 19.02.2014 19:20, Łukasz Gurdek pisze:
Witam,
wspólnie z użytkownikiem 35mariusz proszę o zaimportowanie
Hi,
- 98% of the addresses in this file could have the building=yes tag
applied.
I don't think so. How I can determine which address should have the
building tag? Should I compare every address with imagery?
Yes, put them in by default then remove them before uploading via Bing
images.
Hi,
On second thought, we will ask everybody that wants to help to use their
own import account. Besides the simplifications, and the re-projection
verification does anybody have any other issues?
Thanks
Jason.
On Thu, Dec 13, 2012 at 10:20 AM, Jason Remillard remillard.ja...@gmail.com
wrote
Hello Everybody,
I would like to kick off the MassGIS building import. This following is
copy/paste from the current wiki (
http://wiki.openstreetmap.org/wiki/MassGIS_Buildings_Import). The external
links will work on the wiki.
--
On Dec, 2012 MassGIS
Hi,
I would like to continue the discussion on the simplification of the
MassGIS buildings in a new thread.
In my town, there are 5427 buildings. 43,628 nodes, or 8 nodes per
structure. I did a 0.25 meter simplify on the entire town, and the node
count went down to 41,809. We are looking at an
Hi Paul
On Wed, Dec 12, 2012 at 9:49 PM, Paul Norman penor...@mac.com wrote:
A couple of initial comments:
** **
Has some kind of simplify been run on the data? Although most of the
buildings are quite good some of the curved ones are overnoded (e.g.
Hi Zbigniew,
The technical part looks good to me.
Are you planning on doing all of Poland?
Jason
On Sun, Feb 2, 2014 at 7:48 PM, Zbigniew Czernik
zbign...@openstreetmap.pl wrote:
Hi
I want to import address data in Świdnik.
Import wiki-page:
Hi,
We have talked about this a bunch. It is not about saving space in the
database, it is about putting the source data in the right place. A
physical building, lake, mountain, river, do not have a source. You
can't survey the source of an lake, it is not geo data. Every time an
object is
Hi Tiziano,
First off, I don't know about the license. Somebody else on the import
list should be able to help. Also, you can also talk to the
http://www.osmfoundation.org/wiki/Licensing_Working_Group.
A good place to start is with talking to the Italian mappers (perhaps
the Italian osm mailing
Hi Saikrishna,
Just a quick look.
- The street number tag is addr:housenumber, not addr:houseNumber. OSM
tags don't use CamelCase
- didn't the source data also have zip codes?
- If you are going to dump an address, you should write it out into a
separate file that will be reviewed by hand. These
Hi Clifford,
Building outlines will not be included this time. The original Seattle
Import merged address nodes with the building outlines. When the building is
torn down mappers are removing the outline and but not saving the address
information. Often this address information is reused.
Hi,
I can't recall an address import going forward over the last 1.5 years
that had building outlines and intentionally ignored them. You don't
have building outlines, so really nothing to argue about.
Thanks
Jason
On Sun, Jan 12, 2014 at 6:09 PM, Johan C osm...@gmail.com wrote:
I'm aware that
Hi Saikrishna,
I agree with Serge, we need to be 100% sure the license situation is
straight. Often the data providers say the data is in the public
domain, but in fact, isn't.
Some workflow suggestions
- In general, you should try to script the workflow from start to
finish. You will be
Hi Daniel,
FYI, the wiki page has a link to the full data set. It is ~ 125K buildings.
Probably 125 change sets.
Do you have address data too?
- The tagging seem fine. You might want to put the date the source data in
the changeset comments.
This is a lot of data. You need to break it up,
Hi Satoshi,
I agree with putting the source= tag on the change set. You also might
want to put the date of the source data into source tag.
Any address data?
Otherwise, everything else looks fantastic.
Thanks
Jason.
On Wed, Dec 18, 2013 at 3:27 AM, Satoshi IIDA nyamp...@gmail.com wrote:
Hi Andreas,
This all looks good. I have one more request. Could you update the
public transport wiki pages to include the ref:IFOPT tag. It looks
like you will be the first person using this tag.
Thanks
Jason
On Mon, Dec 16, 2013 at 6:23 AM, Andreas Uller a.ul...@gmx.at wrote:
Dear List,
I
Hi Clifford,
Collaborating with governmental groups (just as long as they have more than
3 letters that start with N) can give us positive press. That positive press
will bring new users to OSM.
I am all for working with the upstream data sources. The technical
argument goes both ways, they
On Fri, Dec 13, 2013 at 11:56 PM, andrzej zaborowski balr...@gmail.com wrote:
On 14 December 2013 00:57, Jason Remillard remillard.ja...@gmail.com wrote:
Hi Andrzej,
Some quick feedback.
Thanks.
First off on process.
- We need to see all of this info pushed into an import wiki project page
Hi Christian,
This is the wiki project page?
https://wiki.openstreetmap.org/wiki/IENC_manual_insertion
I can't really comment on the tagging.
General comments, the email and wiki need the following.
- We would like to see some sample OSM files that are ready for uploading.
- The source data
Hi Randal,
Some comments.
- The alignment matches Bing very closely.
- There are about 100 building inside building, and 2 crossing
buildings errors from the JOSM validator. It looks like the error is
in the source data.
- What is your mapping to the building tag? The source data has all
kinds
Hi Serge,
On Sat, Nov 30, 2013 at 6:29 PM, Serge Wroclawski emac...@gmail.com wrote:
Randal,
Thanks for making this page and engaging in the import process.
Regarding the license, in the United States, only the Federal government can
place something in the Public Domain (it's a very
Hi Andreas,
- ID
We just looked at another bus stop import.
https://wiki.openstreetmap.org/wiki/AltoAdige_-_S%C3%BCdtirol/SASA_Bus_Stops_Import
This issue of the IFOPT/GFS numbers has already came up, without any
good solution so far. These global routing ids are useful and I think
belong in
Hi Ben,
- And last but not least an import-plan:
http://wiki.openstreetmap.org/wiki/AGIV_CRAB_Import
I did not see any handling of abbreviations in your python code. If
the source data has abbreviations, they should get expanded by the
conversion scripts. Regardless, you should talk about
Hi Kurt, Ben,
This is a good point. I've already seen cases where we have the
full name currently in osm but the data we get contains some
abbreviatiated form.
I'll try to look at it. I currently find 970 street names with
a '.' in it.
You should probably go back to your local Belgium
I just read the page again, I am 100% good with your changes Frederik .
Thanks
Jason
On Fri, Nov 8, 2013 at 8:39 PM, Frederik Ramm frede...@remote.org wrote:
Hi,
On 07.11.2013 18:52, Frederik Ramm wrote:
I don't agree with that either and I am planning to revert these two
aspects of your
Hi Andy,
We are getting a bit off topic here. The goal of the modifications is
to clarify the actual policy.
On Thu, Nov 7, 2013 at 4:27 AM, Andy Allan gravityst...@gmail.com wrote:
On 6 November 2013 23:56, Daniel O'Connor daniel.ocon...@gmail.com wrote:
I understand the problem we are
Hi Frederik,
Thank you for reviewing it. Honestly, I am very encouraged that these
two items are the only issues you had. I expected you to be a tough
critic :-)
On Thu, Nov 7, 2013 at 12:52 PM, Frederik Ramm frede...@remote.org wrote:
Hi,
On 07.11.2013 02:31, Jason Remillard wrote:
I just
Hi,
I just made the changes.
http://wiki.openstreetmap.org/wiki/Import/Guidelines
Let me know what you think...
Thanks
Jason.
On Wed, Nov 6, 2013 at 8:23 PM, Glen Barnes barnaclebar...@mac.com wrote:
Realised I only sent this directly to Martin previously:
“should and “must” are very
Hi,
I would like to propose some changes to the import wiki page.
http://wiki.openstreetmap.org/wiki/Import/Guidelines
The actual expectations for imports are firmer than what is suggested
by the wiki page. The goal is to catch the wiki page up with the
actual current expectations...
Stop
Hi Randal,
On Mon, Nov 4, 2013 at 9:39 PM, Randal Hale
rjh...@northrivergeographic.com wrote:
So I guess a question would be where do GIS people go with their GIS issues
in OSM? Talk-us, imports, imports-us, or the new diversity list we just
discovered? Do we belong on the imports list or do
Hi,
After being pointed to changeset 17263910 I think this question needs
re-examination, now that we've seen the data.
For an overview of the data, see
http://pnorman.dev.openstreetmap.org/imports/review/polish_forests/forest_blocks.png.
It seems to be typical of the data this import
Hi
Problems 1, 2, 3, 4, 6, and 9 should have been fixed before the first
file was uploaded. OSM files that are going to be imported, should
100% clean in the JOSM validator. This is a pretty basic thing, right?
7 - Building that already exist in OSM should be skipped, especially
since it looks
Hi Daniel,
Some suggestions
- put a source tag on the changeset set. The comment will be what the
suburb is, and then source tag.
- If you have already QA'ed it, perhaps you could try to find some
help and do an automated upload.
Most important
- It does not look like the adjacent boundaries
Hi Mikel,
Normally, I would ask for 3 weeks of discussion for your
imports/automated edit, look at the code, and would certainly complain
about those tags.
The primary identity of any given object used for automated updates is
by definition a bit fuzzy, nothing can change that.. If many people
Hi Aaron,
Hopefully we can avoid turning this feedback cycle into a big pile of mush
for you!
I would not be against hardcoding conflation logic for the GNIS nodes and
sending everything else to a real editor for conflation. Let the user click
on the node, pull in just the feature id, discard
Hi Peter,
Nothing major.
- For imports, we have been tending to put the source tags on the change
set lately.
- You should document the change set tags in the wiki.
- Any addresses?
Thanks
Jason
On Wed, Oct 2, 2013 at 5:16 PM, Peter Brodersen pe...@ter.dk wrote:
Hi,
I'm preparing an
Hi Mikel (and import list).
This is much better!
- There are bunch of JOSM validation errors in the upload file. Duplicate
nodes, abbreviated street names, self intersecting ways, etc. Most of them
look real issues to me and should be cleaned up first.
- Looks like not all of the broken data
Hi Aaron,
Some quick feedback. Since this is so new to everybody it might be better
to pick one import type so we all can figure out how to use your new
software.
I ran the demo and schools have gnis features that need to be merged. Do
you think it would be possible to merge them in from your
Hi Markus,
Thanks for jumping into this!
Just one question. The SIRI spec is very large and complicated! I am
not sure if you will know.
So far we have decided to not import the SASA reference number for
each stop, generally these ID's are not really useful in OSM. However,
I just wanted to
Hi Brian,
On Mon, Sep 23, 2013 at 6:23 PM, Brian May b...@mapwise.com wrote:
For fully automated - 10k. I experimented with 30k while manually reviewing
in JOSM, and it ran fine. From observing network traffic looks like it bulk
transferred everything right away and then there's processing on
Hi Aaron, Serge
In Aaron defense, before this thread, it would not have have occurred
to me to use Maproulette for an import.
We seem to have two flavors of community imports right now. The first
style, (Seattle, DC and NY city), has the QA, conflation, and
uploading done directly by mappers. It
Hi Bryce,
If you really want to be sure nobody gets confused by some of the
extra tags in the drop tags, you could run an automated edit project
to remove them. I am not 100% sure about this, but putting something
in the JOSM drop list is 50x less work than running an automated edit
project over
Hello,
- Why aren't you using a script for the conflation with OSM?
Jason
On Tue, Sep 10, 2013 at 8:22 AM, Alex Barth a...@mapbox.com wrote:
I'm submitting this import proposal for peer review on this list:
https://github.com/osmlab/nycbuildings/blob/master/PROPOSAL.md
In March 2012, NYC
won't be able to make
it.
But Jason Remillard has agreed to take over for me, so he'll be
running things tonight.
what time tonight? i should know this, but it's slipped my mind.
I hope I see all, or at least most of you this weekend in Birmingham!
wish i could be there. enjoy your trip
Hi,
OK, we will put the NPS import on the agenda tonight.
Thanks
Jason
On Mon, Sep 2, 2013 at 12:57 PM, Thomas Colson thomas_col...@nps.gov wrote:
Any chance we can get the GRSM/NPS import on the agenda?
-Original Message-
From: Jason Remillard [mailto:remillard.ja...@gmail.com
haven't seen in a long while, so I won't be able to make
it.
But Jason Remillard has agreed to take over for me, so he'll be
running things tonight.
I hope I see all, or at least most of you this weekend in Birmingham!
- Serge
___
Imports-us
Hi,
Lars and I have finished QA'ing the MassGIS lake uplaod file, and
would like to do the upload next weekend. Please take a look at the
file if you are interested, let us know if you see any issues.
https://dl.dropboxusercontent.com/u/393787/ponds_missing_from_osm.zip
A new file was generated
Hi Innocensia,
I think before you proceed with the import, you need to learn more
about how normal mapping is done in OSM. For example, what tags are
used for roads (highway, surface, ref, name, ), how routes are
handled, relations, etc. It looks to me like you have not done any
normal mapping
Hi Brain,
- Do you have the OSM file for us to look at? Make sure it is not
over-noded, JOSM validator is happy, etc.
- Some of the USFWS NWR are not open to the public for hunting,
hiking, etc. For example,
http://www.fws.gov/refuges/profiles/index.cfm?id=53516
Which is a NWR, that also
Hi,
I think Paul is correct. The gnis:fcode, and gnis:ftype is a mistake,
taginfo for it.
http://taginfo.openstreetmap.us/keys/gnis:fcode#overview
tag info for nhd:fcode
http://taginfo.openstreetmap.us/search?q=nhd%3Afcode
gnis:fcode - NHD:FCode
Same for ftype
Everything besides the feature
to stop, I will plan on doing the upload in
beginning of September with a fresh set of files giving everybody
minimum of 3 weeks to think about this.
Thanks
Jason
On Wed, Aug 14, 2013 at 7:04 PM, Lars Ahlzen l...@ahlzen.com wrote:
On 08/13/2013 07:46 PM, Jason Remillard wrote:
Hi,
Would
Hi,
Would anybody object to just killing the source tag, and putting it on
the changeset like would be done if it was a current import. It would
save 20 megs on the uncompressed MA snapshot. I 100% agree would be
good to do, but did not propose this on the first go to avoid any
controversy.
will re-run
the process against a daily OSM snapshot when ready for final .osc creation
and upload. Please review and let me know what you think. And a shout out to
Jason Remillard for help with this.
Brian
[1] http://wiki.openstreetmap.org/wiki/Florida_Land_Cover_Import
Hi,
In 2009 user crschmidt imported 290,000 buildings around Boston. An
example changeset
http://www.openstreetmap.org/browse/changeset/727013
Three tags were used.
building=yes
area=yes
source = MassGIS Buildings (http://www.mass.gov/mgis/lidarbuildingfp2d.htm)
The proposal is to run an
Hi Alex,
The JOSM validation on the building file does not look so hot. Lots of
buildings overlapping each other, duplicate nodes, etc. Also, like
Clifford mentioned, the street names need to be expanded.
Jason.
On Sun, Aug 4, 2013 at 11:57 PM, Alex Barth a...@mapbox.com wrote:
Hello everyone
Hi John,
I cc'ed the normal import list too.
- The shapes need to be simplified. I used 1.5 meters.
- There are around 1000 duplicate buildings in the data set (from validation)
- There are some self intersecting way (from validation)
- Roofs on top of building are getting marked as buildings
Hello
Some general thoughts on building imports, since these two issues seem
to keep coming up.
For buildings, the long term maintenance plan is the same. Plan A, is
that in N years time, the area has enough mappers that the data is
being maintained like any other osm data. If Plan A, does not
Hi Thomas,
Some ideas for you
Another way of doing this import is to break it up by feature type.
For example, if the location data is very accurate (say 15 meter
uncertainty), then you can run a fully automated import of the lake
names. For each lake name in the source database, see if we have
Hi Serge,
I don't understand where you are trying to go here?
Why do we care about older imports that are completed and are
basically good enough. It seems like only the ongoing imports (which
should already have wiki pages) and the older imports that we are
thinking about reverting are
Hi David,
I am OK with whatever you decide on the tagging. This is an emerging
feature in OSM. In a couple more years, when we have 100,000 charging
stations mapped the tagging will work itself out. I just don't think
an import should get ahead or deviate from what normal mapping
practice is in
Hi David,
Two small questions on the tagging.
- Why not use name=, instead of brand=*.
- Why not use access=*, instead of car=yes
(http://wiki.openstreetmap.org/wiki/Key:access)
I did not see a link to the code you are using for the import. Since
it is something that is going to be run
to the imported nodes
- what happens if a station is deleted from the source data
Its only 200 nodes, so you could do this by hand every couple of
months. Just some things to think about.
Thanks
Jason.
On Tue, Jul 9, 2013 at 5:47 PM, Jason Remillard
remillard.ja...@gmail.com wrote:
Hi David
that we covered in the previous import?
Mike
On Sun, Jul 7, 2013 at 7:49 PM, Jason Remillard remillard.ja...@gmail.com
wrote:
Hi,
We would like to import the rest of the ponds/lakes into
Massachusetts. The import wiki is below.
http://wiki.openstreetmap.org/wiki
'porjo_tasparks'
Ian.
From: Jason Remillard remillard.ja...@gmail.com
To: IanB porj...@yahoo.com.au
Cc: Imports OpenStreetMap.org imports@openstreetmap.org
Sent: Sunday, 23 June 2013 11:29 PM
Subject: Re: [Imports] Tasmanian Parks
Hi Ian,
On Sun, Jun 23, 2013
?
Ian.
Yes, you might be right. In general that
On 20/06/2013 12:28 AM, Jason Remillard wrote:
Hi Ian,
Thanks for posting to the list.
- Forest Reserve does not seem to be an established value for
protection_title
- Don't include DPIPWE:RES_STATUS, DPIPWE:MANAGE, DPIPWE:ACT
Hi Ian,
Thanks for posting to the list.
- Forest Reserve does not seem to be an established value for protection_title
- Don't include DPIPWE:RES_STATUS, DPIPWE:MANAGE, DPIPWE:ACT,
DPIPWE:IUCN, DPIPWE:ENVIRON,
- Definitely don't include DPIPWE:AREA_HA.
Its not OSM policy, but I suggest that as
Hi,
The NPS state of the map talk from this weekend was very interesting!
I hope you are successful moving over NPS tiles to OSM.
It reminded me of your import email from several weeks ago, I wanted
to give you some feedback on your actual imported data!
!
mamata
On Thu, Jun 13, 2013 at 9:10 AM, Jason Remillard remillard.ja...@gmail.com
wrote:
Hi,
The NPS state of the map talk from this weekend was very interesting!
I hope you are successful moving over NPS tiles to OSM.
It reminded me of your import email from several weeks ago, I wanted
achieve a good, accurate, and authentic public-domain source of park
navigation data.
I'm heading out of town for the weekend, plan on researching/fixing that
way, building, and TIGER tag issue when I get back.
-Original Message-
From: Jason Remillard [mailto:remillard.ja
Hi,
Many of the import/robot guidelines, could be simplified, if we
adopted a new/more general rule.
A good import results in OSM data that is indistinguishable from
normally mapped data.
Generally, normal mappers would not
- put down a node every half meter on a straight line.
- map a
Hi Matthew,
The import proposal looks good! I downloaded the tar file and looked
at the first OSM file.
- There are some duplicate buildings. They were probably added while
you have been processing the data. You may want to proceed anyway and
fix them after if it will be a lot of work redoing
Hi Matthew,
The import proposal looks good! I downloaded the tar file and looked
at the first OSM file.
- There are some duplicate buildings. They were probably added while
you have been processing the data. You may want to proceed anyway and
fix them after if it will be a lot of work redoing
Hi Ian,
- The changeset source tag, shouldn't that be something like - City of
Chicago, data set blablabla. The github link will probably be dead
in 5 years. You could use a website= tag on the change set for the
github repo link.
- The wiki says that you are planning on manually checking for
1 - 100 of 102 matches
Mail list logo