How can I get started on editing the project?

[neroute2]

I'd like to start improving Mexican coverage, towards which I've been slowly working on a list. How do I edit files on the project (nobody controls Mexico)? I've seen mention of a waypoint editor; where is this?

[michih]

You can find all tools here: http://travelmapping.net/devel/tools.php It's linked in the footer.
The most important tool is the wpt editor: http://travelmapping.net/wptedit/

Mexico does currently not have a maintainer. Feel free to work on drafting new wpt files but be careful with active systems.
You need to be familar with Github hwy data repository, are you?

[neroute2]

Mexico does currently not have a maintainer. Feel free to work on drafting new wpt files but be careful with active systems.
You need to be familar with Github hwy data repository, are you?

I think I successfully submitted a simple pull request: https://github.com/TravelMapping/HighwayData/pull/3072


Is there any way to import the waypoint list into the editor, or do you have to copy/paste from github?

[mapcat]

The edit looks okay, as does the pull request. In the future you'll want to give the pull request a more descriptive title, of course.

The editor is not set up to import any files afaik. Just copy-paste into the edit window (and into the in-use labels box, if you're considering changing the name of a waypoint).

[neroute2]

Is there a new URL for the manual? http://cmap.m-plex.com/tools/manual.php doesn't work and isn't archived.

[michih]

The old manual is gone for good. @yakra might still have a copy - on a broken drive?

Jim has requested a review of your first modifications. I've checked 2D so far, see my comments  @ https://github.com/TravelMapping/HighwayData/pull/3074

[neroute2]

I replied to 2D.

[yakra]

(and into the in-use labels box, if you're considering changing the name of a waypoint).

http://travelmapping.net/logs/pointsinuse.log

[yakra]

The old manual is gone for good. @yakra might still have a copy - on a broken drive?

Found a copy right here on my main desktop, in an out-of-the-way place I didn't expect to look at first. I'll fix some of the links up to not point to cmap.m-plex.com, and then put it online.

Edit: http://yakra.teresco.org/manual/manual.html
It's chock full of outdated info, but it's a start. Better than having all this just disappear on us.

I'll see about updating some of the info there. Maybe.

[neroute2]

I think I've taken care of all the objections for https://github.com/TravelMapping/HighwayData/pull/3073 and https://github.com/TravelMapping/HighwayData/pull/3074. Is there anything else I can do?

[yakra]

I'm setting aside sometime on Tuesday to have a detailed look at the pull requests.

[neroute2]

I'm setting aside sometime on Tuesday to have a detailed look at the pull requests.

Thanks

[neroute2]

Would it make sense to demote mexd and mexed back to preview? I have so many corrections that I'm sitting on because there's apparently no process for updating an active unmaintained system in a timely manner.

[Jim]

Would it make sense to demote mexd and mexed back to preview? I have so many corrections that I'm sitting on because there's apparently no process for updating an active unmaintained system in a timely manner.

Related to this, it looks like only 18 travelers claim any segments anywhere in Mexico, and only a handful of places have any segments with more than a traveler or two.  Most segments are untraveled.  To me, this means more flexibility in updating even in an active system.  It's not surprising so many changes are needed given how long those systems have sat with little if any maintenance and that their implementation predates some of our current tools and guidelines.

[michih]

Would it make sense to demote mexd and mexed back to preview? I have so many corrections that I'm sitting on because there's apparently no process for updating an active unmaintained system in a timely manner.

We could do it similar to the split of France. Make a new system first, e.g. mexdr and nexedr. We could test it on the 2nd instance tmtest.teresco.org first. When going live, we could just add entries to system updates like we did for France: mexd re-entered and mexed re-entered.

I think you could close your pending pull requests to mexd routes and start revising the whole system with a new pull request instead.

Just wait one or two days whether there is any objection.

Let me know whether we should merge the Mexican threads. I think one for the revision and development for the next systems should be enough.

btw: mexdfeje system name should be shortened, e.g. mexe or mexme