Right now forms only print with the atlas pages.

They are not available for data entry digitization on the scans.

Questions:

• Form per page? or
• Form per note?

Or ditch forms at that point and expand the note widget to be?

• Line 1
• Multiline 5

Look at all API vs. user pages, make sure it's consistent depending on client cookie jar expectations.

Add ability to reset password from the login page.

So the user can see how detailed the actual content on the resulting pages will be.

Now clicking on:
Take pictures of your notes.

Goes to see other people's pictures?

Upload pages you've photographed.

Takes me to the actual upload form.

Is this deliberate?

Now it is just City, Country

For instance:

http://fieldpapers.org/~mevans/fieldpapers/site/www/print.php?id=gdpcsl9x

Should be

Santa Cruz, California, USA

http://fieldpapers.org/person-scans.php?id=48lrq6kr

Always says "moments ago". Also no space between "Created" and "moments ago".

The same interface that I see here:
http://fieldpapers.org/~mevans/fieldpapers/site/www/print.php?id=gxs6pdmz

In terms of

• [DONE] - where the pages are in that area of coverage

• [DELAY] - Title of the atlas
• [DELAY] - overall context map
• [DELAY] - area of coverage

Should be a page in the atlas PDF.

Per conversation with Mike

GLO:

See:
http://fieldpapers.org/print.php?id=2l23wzsz

The atlas area is the USA. The overview shows me the American south.

For the Atlas Scans and potentially the raw Atlas Pages?

Downloads the entire set of notes added to the atlas.

The attribute tables might include

• Atlas
------ title
------ fieldpapers atlas url
------ atlas geo metadata (WOE)
------ footprint of entire area of interest?
------ footprints of each page? with attributes for bbox in latLong and their zoom and natural scale)
• Notes
------ page number
------ lat (explicate as attribute)
------ long (explicate as attribute)
------ note text

Since complicated GeoJSON doesn't turn into simple SHPs easily, you'll need to duplicate each Atlas metadata bit to a column per note? For POINT versus POLYGON features, you'll need to split out different SHP types.

Download UX goes here:

http://fieldpapers.org/~mevans/fieldpapers/site/www/print.php?id=gxs6pdmz

With a

• Download notes as GeoJSON | SHP

link added next to the PDF one.

SHP is s stub for now

asdfas

Sometimes it's hard to see certain features. Camp Roberts.

No one ever reads the stupid things.

(nvk rewrite)

OVERVIEW

• Add filters for (a) user + (b) place
• Needs to peer into the annotation free text, too (as a new "tab"?). What types of things are people marking onto the map? Tag cloud of frequently used terms, fieldsets? Heat map of note locations?

SCANS (UPLOADS)

• Indicate in the Atlaes view which have scans attached (count badge?)
• Indicate in the subsequent Page view which have scans attached (count badge?)

NOTES/FORMS/ANNOTATION

• Indicate in the Atlaes view which have "notes" attached (count badge?)
• Indicate in the subsequent Page view which have "notes" attached (count badge?)

For the Atlas Scans and potentially the raw Atlas Pages?

Downloads the entire set of pages in the atlas.

Download UX goes here:

http://fieldpapers.org/~mevans/fieldpapers/site/www/print.php?id=gxs6pdmz

With a

• Download GeoTIFFs

link added next to the PDF one.

Might come from another site entirely.

from Eric:

forget about me when I'm not logged in, then logged in

signing up in after creating an atlas retroactively makes me the author of all of the atlases I made anonymously

same as, but Atlases instead of site wide:
https://github.com/stamen/paperwalking/issues/83

We still get names with long comma strings, etc.

Paired with adding a North arrow onto the map:
https://github.com/stamen/paperwalking/issues/47

Basically, the earlier design was better.

From Eric (edited 30 March):

(KEEP riffing in the DEMO branch -- NVK)

(In order of priority)

1. DONE: When you move the map, the [widget] should move with it
2. DONE: When you scale the map, the [widget] should scale with it (get smaller or larger locked to the map)
3. DONE: You should be able to move and scale the [widget] independent of the map, but not the inverse
4. TODO: Remove snap-back logic that on mapMoveEnd, ensure widget is in view.
5. TODO: Remove zoom-out logic that on row/column page add in the widget, the the map zooms.
6. TODO: Keep the pan-over logic that on row/column page add in the widget, the the map pans.
7. TODO: Zoom in button needs to be centered on the center of the atlas page widget, not the center of the map.
8. MAYBE: Try adding pages like 1, 4, 9, 16 where it's 1x1, 2x2, 3x3, 4x4 instead of not square. That way the area-of-interest stays the same, the pages add or subtract inside that space, not expanding out from the in the top-left corner.
9. MAYBE: If you wind up with the atlas off the screen there could be a 'restore' button that takes you to a screen where the map is in the center. Near the + – buttons.

This is undocumented and not in the GUI now. But it works from our Camp Roberts exercise.

Add rough cut of how this interface would work to the site. GLO can revise.

URLs seem to generally be a mess throughout the site right now.

Add 404 display on error.

This is for the NOT gis analysts. For instance, QuickNets people who aren't GIS people.

Todd prefers this over SHP if we can only do one.

For the Atlas Scans and potentially the raw Atlas Pages?

Downloads the entire set of notes added to the atlas.

The attribute tables might include

• Atlas
------ title
------ fieldpapers atlas url
------ atlas geo metadata (WOE)
------ footprint of entire area of interest?
------ footprints of each page? with attributes for bbox in latLong and their zoom and natural scale)
• Notes
------ page number
------ lat (explicate as attribute)
------ long (explicate as attribute)
------ note text

Since complicated GeoJSON doesn't turn into simple SHPs easily, you'll need to duplicate each Atlas metadata bit to a column per note? For POINT versus POLYGON features, you'll need to split out different SHP types.

Download UX goes here:

http://fieldpapers.org/~mevans/fieldpapers/site/www/print.php?id=gxs6pdmz

With a

• Download notes as GeoJSON | SHP

link added next to the PDF one.

SHP is s stub for now

The user enters an atlas title in the make process but that is not used to display on the atlas's page or on the watch page.

For instance, this one should be called "The Rock":
http://fieldpapers.org/~mevans/fieldpapers/site/www/print.php?id=77lx4tsz

_n

From Eric:

atlases on the front page should remember what tiles you used to make the atlas

Paired with scale bar
https://github.com/stamen/paperwalking/issues/44

This is round 1. A future enhancement might be adding a magnetic north calculation. For now the user just needs to now which way is north on the map, and what "north" that is.

Replace with subprocess calls to gdal binaries for easier installation.

Emphasize these are atlases, not single sheets.

Anywhere we need to show some sort of status/error/progress, you should see that within the FP nav/footer. E.g. verify.php should take you to a Field Papers page.

Ideally, error messages would be integrated into the page it refers to. E.g., if your passwords don't match when you create an account, the error should show on the login screen itself.

Example: http://fieldpapers.org/~migurski/fieldpapers/site/www/scan.php?id=m9b8hh2d

If someone is truly anonymous, there stuff should be mixed up with every other (fake) Anonymous user.

If the username is Anonymous in the Watch bit:

http://fieldpapers.org/~mevans/fieldpapers/site/www/atlases.php

Clicking on that should show ALL atlases that haven't been claimed. Not from that default "Anonymous" user name.

I shouldn't see two separate pages:

http://fieldpapers.org/~mevans/fieldpapers/site/www/atlases.php?user=hx5k5crw
http://fieldpapers.org/~mevans/fieldpapers/site/www/atlases.php?user=vddgnq72

Those atlases should all be mixed on a single page.

Or you need to append on a random number to Anonymous user name for that user ID on creation (which is what Google does in GDocs).

From GLO:

It's important that the atlas page shows the atlas area on:

• The overview map up top -- a single shape that matches the orientation/scale of atlas area. Perhaps the zoom level of the overview map could be determined by that somehow... [NVK: Just add a Locator map icon]
• Each atlas page's border should overlay on the large map.

[DONE?] * The pages listed below should have borders, so they look like pages.

Draft text:

"Use the + and - controls on the page widget below to change your map's page coverage"

From Eric:

it should be clear that the # of pages is dependent on what's happening on the map

right now the number of pages feels like something I can change, especially since it's in the top bar in between a lot of other things I can change

For the Atlas Scans and potentially the raw Atlas Pages?

Downloads the entire set of notes added to the atlas.

The GeoJSON might include

• Atlas
------ title
------ fieldpapers atlas url
------ atlas geo metadata (WOE)
------ footprint of entire area of interest?
------ footprints of each page? with attributes for bbox in latLong and their zoom and natural scale)
• Notes
------ page number
------ lat (explicate as attribute)
------ long (explicate as attribute)
------ note text

Since complicated GeoJSON doesn't turn into simple SHPs easily, you'll need to duplicate each Atlas metadata bit to a column per note? For POINT versus POLYGON features, you'll need to split out different SHP types.

Download UX goes here:

http://fieldpapers.org/~mevans/fieldpapers/site/www/print.php?id=gxs6pdmz

With a

• Download notes as GeoJSON | SHP

link added next to the PDF one.

SHP is s stub for now

Is there an "easy" way of implementing simple line and polygon drawing?

Right now notes are simply "points" on the map.

Both drawing on the client and solutions for saving that to the server (and round tripping)