sounds good to me
On Sat, Feb 11, 2023 at 1:17 PM john whelan wrote:
> Sounds wonderful.
>
> John
>
> On Sat, Feb 11, 2023, 12:49 Mateusz Konieczny via talk <
> talk@openstreetmap.org> wrote:
>
>> I propose to replace following surface tags by doing an automated edit:
>>
>> obvious typos:
>>
>>
That is a good summary, though "Once the OSM available satellite imagery
does not show the feature" is perhaps a bit too strict. Some things aren't
always visible or clear from aerial imagery and need to be surveyed in
person. I'm sure the intent of this phrase is not to encourage people to
On Wed, Oct 26, 2022 at 1:11 PM Greg Troxel wrote:
>
> I think people should keep in mind that a culture of deltionism is
> demoralizing to contributors and harms OSM more than a few marginal
> items in the database.
>
This is a fair point, but given how often this comes up, it doesn't seem
On Tue, Oct 25, 2022 at 4:37 AM Frederik Ramm wrote:
> If someone does a
> lot of good work for OSM otherwise and would really like to record an
> ancient former railroad that ran through where their house now sits - I
> shrug and let them do it. Only if someone starts to make it their
> mission
This looks like something that there still is not consensus on.
Here are couple of roads that are not plowed in the winter in my area of
Vermont. Both are tagged differently:
Lincoln Gap Road: https://www.openstreetmap.org/way/19729533
VT 108 through Smugglers Notch:
100% agreed. I'm the other local mapper and I'm certainly not worked up about
it. Andrew just asked my opinion about some changes he was thinking of making
and my opinion didn't line up with his so we figured getting some additional
opinions wouldn't be a bad idea.
-- Zeke
On Thursday,
In my area some of the CDP boundaries do correspond to official
administrative boundaries, and others do not. Deleting them all statewide
would remove some good data. The data is good though, and the ones that
aren't real boundaries usually are real places. For example there are
several
This exact question is the reason why I haven't imported the Green Mountain
National Forest in Vermont (well also the fact that I haven't figured out
how to convert Shapefiles to OSM format yet, but anyhow….). My research
leads me to believe the the National Forest Boundary is simply the area
apologize for bringing up dead topic. I'd be interested to
know what was said though.
Zeke
--
Zeke Farwell
Burlington, VT, USA
On Sat, Sep 4, 2010 at 9:46 AM, Eric Jarvies e...@csl.com.mx wrote:
On Sep 4, 2010, at 6:57 AM, Serge Wroclawski wrote:
On Sat, Sep 4, 2010 at 7:15 AM, Xan
Sure do. Quite useful.
On Sat, Sep 4, 2010 at 12:59 PM, John Smith deltafoxtrot...@gmail.comwrote:
On 5 September 2010 02:04, Zeke Farwell ezeki...@gmail.com wrote:
I've been thinking about layers for a while. In OSM we do not use layers
for different types of features as one would
On Sat, Sep 4, 2010 at 3:32 PM, M∡rtin Koppenhoefer
dieterdre...@gmail.comwrote:
yes, but it get's even harder when the information is split over
several layers and you do edits without even seeing the data, because
it is on a different layer. How could you maintain integrity and
topology?
, Nathan Edgars II nerou...@gmail.comwrote:
On Sat, Aug 28, 2010 at 12:53 AM, Zeke Farwell ezeki...@gmail.com wrote:
As you know, Mapnik will render multipolygons
correctly as long as all the ways form complete rings and are tagged with
outer and inner as needed, but it turns out that Osmarender
Nathan,
I have run into similar issues with complicated multipolygons rendering just
find in Mapnik but not fine in Osmarender. Another mapper (who's area I had
temporarily broken) told me that the member ways of my relations were in the
wrong order. At the time I primarily used Potlatch which
In looking at some of those ways I'd say your simplification is completely
warranted. The curves still look very smooth after you've removed 73% of
the nodes.
I agree with others that storage is cheap and saving space in the DB may not
be that important. More nodes make for smoother, more
On Sun, Jun 20, 2010 at 6:28 AM, Lennard l...@xs4all.nl wrote:
On 20-6-2010 0:53, Val Kartchner wrote:
So, apparently we have to work it out ourselves before they'll even
consider making the change.
The problem is that once we add a tag to the stylesheet, and it starts
rendering, it is
On Thu, Jun 17, 2010 at 11:26 AM, Apollinaris Schoell ascho...@gmail.comwrote:
mentioned earlier already. the ref tag is taken by a standardization in osm
worldwide. sure osm is free and everyone is allowed to change things but
then don't expect to get any useful rendering anywhere. it
On Fri, Jun 18, 2010 at 12:30 AM, Nathan Edgars II nerou...@gmail.comwrote:
You know that nat and int are short for national and international, right?
Yup. If they are needed for something else then those tags can be avoided
and a new one could be created (us_ref?). It just seems better to
On Wed, Jun 16, 2010 at 6:52 PM, Richard Welty rwe...@averillpark.netwrote:
7 instead of US 7, NY 7, (7), etc.
Yes. Thank You. I've never liked putting network prefixes in the ref tag.
The reference number for United States Highway 7 is simply 7 not US 7.
No one calls it US 7 either.
Classifying by runway length does make some sense to me, but I really have
no idea how Mapnik or any other renderer works. Not sure if this would in
fact be easy or not. It also means a renderer needs the runway tagged as a
way or polygon in order to make a decision. What is a renderer to do
Steve,
I like this as a possible solution as well. Perhaps the admin_level tag
could be used? Same as for boundaries. The challenges in my eyes are not
making the tagging scheme overly complicated, and making if verifiable based
on physical characteristics. In my opinion OSM only needs three
at 11:33 PM, Zeke Farwell ezeki...@gmail.com wrote:
Steve,
I like this as a possible solution as well. Perhaps the admin_level tag
could be used? Same as for boundaries. The challenges in my eyes are not
making the tagging scheme overly complicated, and making if verifiable based
The way I see it, any given feature may have many components to it's data.
With a road you've got the geometry, name, classification, surface, etc…. .
These components may all come from one source, or they make come from
several. If the road is unmodified since the TIGER import then the source
Hi everyone,
You may or may not know that currently in OSM there is only one [rendered]
tag to describe the many different types of places where planes can take off
and land (aeroway=aerodrome). I'm trying to figure out how we can tag tiny
airstrips and gigantic international airports
Would something like this work, Val?
Personal Airstrip:
aeroway=aerodrome
aerodrome=airstrip
access=private
RC Airstrip:
aeroway=aerodrome
aerodrome=rc_airstrip
Another possibility for RC Airstrip:
aeroway=aerodrome
aerodrome=airstrip
aircraft_type=radio_controlled
On Sat, Jun 12, 2010 at
Well said.
Zeke
On Mon, May 24, 2010 at 9:42 PM, Richard Welty rwe...@averillpark.netwrote:
i think i have issues with both sides of this argument:
as far as putting layer on a river, there's explicit language about
that here:
http://wiki.openstreetmap.org/wiki/Key:layer
as far as
Yes! I agree 100%.
Zeke
On Mon, Mar 8, 2010 at 5:36 AM, Paul Johnson ba...@ursamundi.org wrote:
It's time to retire ref=* on highway=* ways to describe attributes
of the overlying route instead of the physical attributes of the way
itself. Using the ref= tag on ways to describe routes
Part of Paul's original email:
* Many bridges and tunnels have signed references that would actually be
physical attributes of a way, but with the ref= tag on ways describing the
overlying route instead of the way itself, makes it impossible to properly
describe these attributes if ref= on a
On Thu, Dec 17, 2009 at 10:30 AM, Christopher Covington c...@vt.edu wrote:
I really think we should expand the meaning of the existing restriction
tag. It was originally made for turn restrictions, and currently
supports hours and days of the week, but there's no reason why it
couldn't also
for that matter, there are roads in the Alps that don't get plowed,
are there any european mappers following this list who know
if those get tagged for seasonal closure, and if so, how?
I've seen a variety of discussions about seasonal closures on the wiki, but
none with lasting results.
The Crown Point bridge
(http://www.openstreetmap.org/browse/way/28436071) comes to mind; it's
constructed of non-reinforced concrete and was essentially condemned
recently with only a few hours notice
(
http://www.poststar.com/news/local/article_e77cd748-ba8b-11de-9ff0-001cc4c03286.html
).
something as simple as closed=yes/closed=temporary/closed=indefinite
would seem to suffice.
I like this proposal as it could also encompass regular seasonal closures.
There are many roads through the mountains in Vermont that are generally
closed from Nov 1st through May 30th each year due
Wow, that looks great! I'm psyched to see someone people like you working
on US centric tileservers.
Zeke
On Tue, Apr 28, 2009 at 9:34 PM, Lars Ahlzen l...@ahlzen.com wrote:
Hi OSMappers!
I've been working on a topographic map based on OSM data, somewhat
similar in style to the National
a member of the appropriate relations. Bit of a pain, but
it's mostly done now. For the US/Canada border I've found the Canadian
Geobase data to be more accurate than the TIGER data.
Zeke Farwell
Burlington, VT
On Tue, Mar 31, 2009 at 12:22 PM, Richard Weait rich...@weait.com wrote:
On Tue, 2009-03
.
I think eventually another layer should be created that show the
distinctions between BLM, USFS, NPS State Parks, etc In preparation
for that we should definitely have a wiki page detailing how to tag these
public land types.
Zeke Farwell
Burlington, VT
On Thu, Feb 19, 2009 at 3:50 PM
Chris,
Thanks for putting up that table. Looks great. I have two suggestions:
I think the network identifiers should be simpler. What about this scheme?
Interstate = Interstate signed highway system
US = US signed highway system
[state abbr.] = State signed highway system
TX = Texas
CA =
Yeah we're getting a little ahead of ourselves with the shields. The first
step is tagging the highways in a standard scheme which would give a
renderer sufficient data to draw shields. Then someone has to actually
build a renderer that draws the shields. Thats a whole other can of worms.
I
that
we all start using relations to tag numbered highways in the United States,
and when Mapnik eventually gets around to rendering reference numbers from
relations, we can stop using the ref tag on ways themselves entirely.
Zeke Farwell
Burlington, VT, USA
37 matches
Mail list logo
