Do the latest NGS topographical maps show the city limits properly? Those
are public domain
On Sun, Jan 27, 2019 at 10:16 AM OSM Volunteer stevea <
stevea...@softworkers.com> wrote:
> On Jan 26, 2019, at 4:00 AM, Andy Townsend wrote:
> > A mapper has recently changed this to "cut the corner off" north of the
> 880 between San Jose airport and Stevens Creek Mall / Westfield Valley
> Fair. You can see the change at
> http://overpass-api.de/achavi/?changeset=66619223=18=37.33883=-121.93327=B0TTTFT
> .
> >
> > Some of this mapper's previous changes have had to be undone, so I did
> check the node change made here to see if it might be one of them.
> However, according to the node history
> https://www.openstreetmap.org/node/373647840/history#map=13/37.3600/-121.9066
> the original source of this node was a changeset quite a while ago with a
> description "adjust boundaries based on san jose city map, bing, and common
> sense ". It therefore would be great if a local could check it if possible.
>
> I'm fairly local (SJC is my "home airport") yet I'm not finding
> easily-available San José City Limit boundaries in an ODbL-compatible
> format which I could use to relatively quickly repair the damage. (The
> user mk408 has a history of "making it up as he sees fit" OSM data entry
> which many have disputed or redacted, for example, many years ago he made
> MANY roads in the entire South Bay region — Campbell, Los Gatos, Monte
> Sereno, southern San José —into highway=tertiary roads, and that remained
> very questionable until it slowly but surely "healed itself," again, this
> took months-to-years). There are some geo data at
> http://csj-landzoning.appspot.com/index.html which indicate the present
> OSM data are "largely correct," the exception being that the area directly
> over the northern part of the airport do not include the "leg" that
> "covers" runway 12L/30R and that the acute angle over taxiways V, W and W1
> is more like "aligned with these taxiways, rather than cutting across
> them." You really have to see them rather than expect that I can describe
> them with text. They are, again, "mostly correct" but could use some
> rather minor correction.
>
> As I bumped into somebody on a plane on my way back from SOTM-US Seattle
> (2016) who works in the San José City Hall and when she met me was bowled
> over at the coincidence that I was the very person sitting next to her
> drinking gin and tonic who entered into OSM most of Santa Clara County's
> bikeways/bicycle infrastructure and network=lcn routing (which the city
> office found "extremely helpful" — her words), it's conceivable that I
> might be able to use that to sway release of some data which could be
> forthcoming. While I don't know quite who to call, exactly, if somebody
> wants to "release to me" ODbL-compatible data which need to be harmonized
> with what are now in OSM, I'll volunteer to be the "nexus of citizen entry"
> to assure they find their way into our wonderful map. Send me a pointer to
> the data, assure me they are ODbL-OK and I'll "merge" these into OSM.
>
> SteveA
> California
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
